Smart accounts with security built in.
Each account carries its own ownership, roles and execution rules — so security isn’t added later in an app, or left to whoever happens to hold a key.
Policy that travels with the account.
When rules live in an app, anything that reaches the account another way can step around them. A governed account keeps the rules on-chain, with the assets.
Requests from our interface, yours or a script meet the same checks — according to the roles and execution paths the account grants.
Three parts, each with its own job.
Ownership, roles and execution rules work together, and each changes in its own way. Developers can use one part on its own, or all three.
Governed accountOwnership · roles and permissions · execution rules
- OwnershipKept apart from day-to-day work, so a lost key becomes a recovery process rather than a lost account — and taking ownership is slow enough to be noticed.
- Roles and permissionsOwner and recovery belong to the account and are handed on, never deleted. Every other role is yours to create and change while it runs.
- Execution rulesThe waiting period and the permitted destinations. This is the part you can put in front of a setup you already run, without adopting the rest.
Works with what you already use.
The account doesn’t replace your wallets or your apps. It holds the policy they have to pass.
On the account, not in the app
An interface can raise a request. It can’t quietly rewrite who may act or where funds may go.
Beside the signatures you trust
One key or many — signatures prove agreement. The account still holds the policy those signatures must pass.
Deploy new, or bring what you run
Start from a governed account, or put the same controls in front of a setup you already run.
When something goes wrong.
Keys get lost, apps get compromised, people make mistakes. The account gives each of these a defined path — visible on-chain, and with time to respond.
- The owner’s keys are lost
- A named recovery address can ask to take ownership. The request waits out the account’s waiting period, and the current owner or recovery must approve it — an emergency path, not a day-to-day role.
- The app your team uses is compromised
- It can raise a request — not approve one, or send value to a destination the account doesn’t permit.
- Someone loosens who may act, then moves funds
- Changing roles is itself an operation, with its own approvals and on-chain record.
You keep your keys.
Particle CS never holds your keys or assets. The account enforces its rules on-chain; key custody stays with your wallets.
Bring an account under rules.
Related: Pre-execution security · Programmable governance