Connect your wallet
to begin sealing.
Your wallet is the treasury controller. Connect to sign and deploy your succession plan onchain. All installed wallets are detected automatically.
Define your treasury
and project.
Set the treasury wallet address and identify the project. This information is sealed with the plan onchain.
When should silence
trigger succession?
Set how long the treasury controller can be inactive before the succession plan becomes executable. A grace period allows the founder to cancel before execution.
After the inactivity window closes, a grace period gives the founder a final chance to confirm proof-of-life before execution begins.
What should happen
when silence is proven?
Select one or more protocol modes. Each mode defines a category of action the protocol takes when the inactivity condition is met.
Founder Recovery
Control transfers to a backup wallet or multisig you designate.
Wallet transferCommunity Vault
Treasury moves to a community-controlled multisig or DAO vault.
Community controlContributor Distribution
Assets distributed to predefined contributors, builders, or beneficiaries.
DistributionAgent Continuity
An AI agent or automated wallet continues basic operations.
AutomationFinal Message
A sealed message is published onchain when conditions are triggered.
MessageDefine successors
and allocations.
Add wallet addresses and assign percentage allocations. Total must equal 100%. Each address can be a wallet, multisig, DAO vault, or agent wallet.
Leave a final message
for the community.
This message is encrypted and sealed onchain. It will be automatically published when the succession condition is triggered.
Review your plan
before sealing.
Once sealed onchain, this plan is immutable. Verify every address, allocation, and condition carefully before deploying.
Onchain deployment is irreversible. The plan will begin monitoring immediately after sealing. Verify all successor addresses and allocations above before proceeding.