Client-side encryption
Estate content is encrypted with AES-GCM 256 in your browser. Only ciphertext, IV, salt, and limited metadata are stored.
Security architecture
No secret should leave the device unsealed.
Bootstrap is designed around minimum disclosure, explicit authority, and inspectable continuity rules.
Your keys stay yours. Bootstrap never asks for a seed phrase or private key. Draft plans do not move funds or guarantee an outcome.
Wallet authentication
Wallet signatures establish authority without transmitting private keys or seed phrases.
Vault contracts
Contract-based custody makes asset movement subject to declared rules rather than an offchain promise.
Configurable participants
Heirs and guardians are explicit addresses with defined roles in the recovery path.
Inactivity controls
Threshold and grace periods separate a missed check-in from an eligible recovery event.
Safe asset handling
Asset approvals, amounts, network, and destination addresses must be reviewed before every signature.
Versioned contracts
Production releases should use a transparent registry, fixed versions, and public change records.
Operational controls
Multisig administration and emergency pause are implementation directions until configured and disclosed.
Audit direction
Independent smart-contract audits and public reports are required before production use; no audit is currently claimed.
Security status. Contract addresses, deployment parameters, supported asset registry, audit reports, emergency controls, and admin multisig are placeholders until formally published. Do not transfer assets based on an unverified address.