Transfer Assets
Waiting
3.2 ETH
CancelApprove
Solutions · Approval Workflows
Critical actions wait for a second person
Request, wait, and approve on-chain — not in a chat thread that never settles with the transaction.
Paths
Paths change with the policy
The same operation can take different paths — delay, cancel, or sign before execute.
The argument
Instead of — Off-chain process invisible on-chain
Policy on the blockchain
Roles, waiting periods, and rules for external calls are enforced by the contract. The interface cannot override the chain.
Instead of — Admin keys that concentrate irreversible power
Evidence as part of the operation
Who did what, when, and under which rules remains part of chain history — not a screenshot of a chat thread.
Instead of — Hard-coded workflows that do not match real orgs
Composable open-source foundation
Adopt the full governed-account stack or the parts you need — vaults, payments, tokens, factories — with the TypeScript SDK.
Instead of — An emergency path that becomes everyday
Separation of duties by design
Critical actions follow a governed lifecycle — who configures is not who operates; who proposes is not who alone can finish.
This covers
- Approval flows
- Roles & permissions
- Waiting periods
- Policy enforcement
- Operational processes
Questions
-
Who is allowed to move funds?
Whoever you name, and only for the operations you name them for. Roles decide who may request, who must wait, who may approve, and who may execute — and the contract refuses an unauthorised call before it reaches your funds, rather than relying on an interface to prevent it.
Roles and approvals -
Can someone bypass the rules through the interface?
No — the interface cannot override policy. The same on-chain rules apply whether the request comes from the Platform, from your own application through the Protocol, or from a script, because enforcement sits in the contract rather than in any of the things asking.
Pre-execution security -
What stops a compromised integration from draining an account?
Each operation type is limited to a list of permitted targets, so a mistyped address or a compromised integration has nowhere to send funds. Automation can hold a role and still be bounded by the same policy as a person — a signing key is not an all-or-nothing grant.
Automated operations -
Do we have to use your application?
No. The Platform runs these operations in the browser; the Protocol builds the same rules into systems you already run. They enforce identically because they enforce in the same place — the contract — so the choice is about where your team works, not about how much control you get.
Build on the Protocol
Related
Also in this group
Put the workflow where it cannot be skipped
Protocol in your own systems, or Platform in the browser.
Alpha · Testnet · Personal workspace