Solutions · Smart Accounts

An account that carries its own rules

Recovery, delays, and roles ship with the account — not as later add-ons.

Owner

0x71C9…bE3

Recovery

0x84D1…22E7

Time lock

24 hours

Broadcasters

The argument

Instead of — A key that is only yes-or-no

Rules live on the account

Roles, waits, permitted targets, and recovery are properties of the account — enforced through our interface, your integration, or a script.

Instead of — Recovery as a favour or a filing cabinet

Designated parties restore access through the same governed path as any sensitive change: requested, delayed, recorded.

Instead of — Each protection living in a different tool

Transferring ownership or replacing recovery is a request that waits and can be cancelled — never a quiet signature.

Instead of — Changing rules by moving the assets

Grant and revoke permissions, change waits, and add operation types on the account you already run.

This covers

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

Platform in the browser, or Protocol in your own systems.

Alpha · Testnet · Personal workspace