On-chain (Sui)

Move registry, Seal sealing, and Walrus — the trust layer.

Warden's guarantees are enforced by Sui primitives, not by Warden's own process.

Warden's on-chain trust layerThe owner wallet registers and revokes entries in a Move registry on Sui; Seal key servers gate vault decryption on that registry, warden sign RPC-checks it before every sign, and Walrus holds the policy and audit trail.Owner walletregister · revoke · approveon-chain txMove registry · Suivault · warrant entriesrevoked? · expired?seal_approvestatus RPCSeal key serversrelease shares only if !revokedwarden signrefuses if revoked / expireddecryptswritesLocal vault — opensWalrus — policy + audit

Move — the registry

A Move registry holds vaults (keyed by address) and warrants (keyed by id), each an Entry { owner, vault_pubkey, revoked, expires_ms }. Registering takes the vault key's signature; revoking and re-enabling take the owner wallet.

Seal — sealing + kill-switch

The vault's Seal factor is encrypted to seal_approve_vault(vault_address). Seal key servers release decryption shares only while owner == sender && !revoked. So revoking the vault is a real kill-switch — the network refuses decryption, not Warden.

Walrus — durable, tamper-evident

Policy blobs and the approval audit log live on Walrus: content-addressed, off your machine, impossible to quietly rewrite. The audit log is hash-chained and periodically anchored on Sui (warden audit anchor); verify it with warden audit verify.

zkLogin

Sign in as the owner with an identity you already have — vault access can be fully passwordless.