01
On-chain enforced
A transaction cannot be released until the required signatures and policy checks are satisfied.
Product · ControlRail
An execution condition for institutional transactions.
Policy, KYT, approval, and audit ride with the transaction. The wallet stays non-custodial; nothing executes until the condition is met.
01Why ControlRail
The ledger enforces the boundary, not the server.
Approval that lives only in an app or backend can be bypassed.ControlRail turns approval into a condition of execution.
02
Non-custodial
Users keep wallet authority. Institutions govern when a signed request can execute.
03
Audit ready
Allowed, held, rejected, and executed requests become reviewable evidence.
04
Risk before release
KYT screening happens before the transaction reaches the rail.
02How it works
Before execution, every request passes one gate.
Four steps: prepare the request, check risk and approval, enforce the condition, and leave evidence.
01
01Step 01
Prepare
The wallet builds the request; ControlRail attaches the policy that must be met before release.
Policy before signing
Policy
- User key remains outside institutional custody
- Amount, route, counterparty, and program rules are attached
- The request becomes reviewable before it reaches execution
02
02Step 02
Approve
The institution approves through a narrow path. ControlRail checks KYT risk and required approvals first.
Risk and approval path
KYT
- Low-risk requests can move faster
- High-risk requests can be held or rejected
- Approval becomes part of the execution evidence
03
03Step 03
Enforce
Only requests that meet the condition are submitted through the chain adapter.
Execution condition
Approval
- Approved requests move to the execution path
- Rejected or incomplete requests stop before submission
- The chain-specific enforcement happens in the next layer
04
04Step 04
Audit
Every approved, held, rejected, or executed request leaves a record to inspect later.
Proof after execution
Audit
- Policy version and approval path
- Risk decision and rejection reason
- Execution status and transaction reference
03Chain enforcement
One control model, multiple enforcement paths.
ControlRail sets the execution condition once, then maps it to each chain's enforcement primitive. Same logic everywhere: check policy, screen risk, collect approvals, record the outcome.
Smart account validation
In EVM, the smart account verifies the required approvals during validation, and only approved transactions execute.
On-chain multisig quorum
On chains with native multisig, a transaction that misses quorum is blocked on-chain.
04Delivery
Connect where the institution already works.
ControlRail ships as a module, a dedicated wallet, an SDK, or a backend gateway. The integration point stays narrow — policy decision in, execution proof out.