Silent Layer architecture
Architecture
How it's put together
Four parts, kept independent on purpose. Below that, an honest split between what runs today and what is still on paper.
Silent Signature
Approve without being named.
A guardian approves as a verified member of the set, not as a public address. Today the interface simply doesn't surface who approved. The cryptography that makes that provable comes in Phase 02.
Identity Vault
Identity kept apart.
Whatever identifies a guardian lives outside the coordination layer, so a proposal never has to carry it. Encrypted storage for this is specified and lands with the cryptographic layer.
Threshold accountability
Privacy with a way out.
Privacy shouldn't mean nobody is answerable. A recovery policy sets the conditions, the higher approval bar and the waiting period before any identity can be revealed. Nothing is revealed outside it.
Guardian set
No single point of control.
Approvals come from independent guardians. One person can propose, but one person can never execute.
Running today
You can use this now
- Wallet connection
- Guardian registration
- Vault setup
- Proposals and approvals
- Threshold policy
Still to build
Designed, not shipped
- Membership proofs
- Cryptographic approvals
- Encrypted Identity Vault
- Threshold recovery
- Cross-chain coordination
Where the boundaries sit
The coordination layer holds the vault, the guardians, the proposals, the approvals and the recovery policy. It doesn't assume a particular chain. The treasury contracts hold the funds and check the approval count — identity never crosses into that side. Keeping the line there means either half can be audited or swapped without rewriting the other. First deployment is Robinhood Chain, settling in HOOD and USDC.