Keys
Two keys in the whole system. Owner-only surface.
A rehearsal, on purpose. Revoking this deployment's real delegate key would lock every visitor out of the house's memory — which is exactly the property this screen shows. The buttons play the Walrus Memory protocol's behaviour locally: revocation moves the rotation counter, and a remember() after it fails.
Rotation counter1
Delegateactive
Accountactive
owner · house
ownerby design: generated in the admin's browser, shown once, never sent to our server. In this build the account was created in the Walrus console, and the server never holds it
used for: create · register delegate · revoke · freeze
used for: create · register delegate · revoke · freeze
house · server
delegateheld in the server environment
used for: all memory reads and writes
used for: all memory reads and writes
Emergency freeze
Denies Seal decryption to everyone, the owner included. The kill switch.
Try writing a memory in the current key state.
Revoking the delegate bumps the rotation counter and the application loses access to the house's own memory — and cannot stop it. The two actions have different blast radii: a revoke locks out the app while the owner can still decrypt; a freeze locks out everyone.