Checked before it happens, not after.
Most security tooling explains what went wrong after an operation has run. Pre-execution security asks the account to decide whether an operation may run at all — before anything moves.
There’s no undo on‑chain.
Once a blockchain operation executes, reversing it is usually impossible or expensive. Monitoring and alerts still matter — but they describe what already happened.
Pre-execution checks move the decision earlier: the account evaluates who is asking, what would actually run, and under which conditions, and only then allows it to proceed.
What the account asks before an operation runs.
Asked by the account itself — not by whichever app happens to submit the request.
- Is this participant allowed to ask?
Permission is granted per kind of operation, not as a blanket over the whole account. Asking, approving, cancelling and submitting can be granted separately.
- Does the request match what would actually run?
Permission is checked both for the request made and for the operation it would carry out — so a permitted request can’t smuggle in a different action.
- Is the destination allowed?
An operation can be limited to permitted targets. Where a list is configured, a target that isn’t on it is refused.
- If conditions apply, are they met?
Some operations need a waiting period, an additional signature, or both. Many don’t. Where a condition applies, the operation stays pending until it’s satisfied — and can be cancelled meanwhile.
- Is the signature still valid for this request?
Right chain, within its deadline, not already used, and from a signer who holds the permission.
Every request meets the same checks.
The checks run on-chain, inside the account itself — not in the interface that sends the request. What each participant can do still depends on the roles and execution paths the account grants — including any privileged ones.
- Bloxchain PlatformYour team, in the web app
- Your applicationThrough the SDK
- ScriptsScheduled and back-office jobs
- AI agentsSoftware acting for you
- Built into the accountThe checks run in the account’s smart contract, so they apply to every request it receives — not only those sent from our app.
- Open to inspectionRules and results are recorded on the blockchain for anyone to verify. The code is open source and independently audited.
- Nothing to reverseIf a check fails, the operation simply doesn’t run — so there’s no transfer to chase or undo afterwards.
Where the checks stop.
Pre-execution checks enforce what the account is configured to enforce. They don’t make a compromised key harmless, judge whether a permitted operation is wise, or replace monitoring and key management.
Put an account behind these checks.
Related: Programmable governance · Smart-account architecture