Skip to main content

​
Owner

The owner is the Sui wallet address that created the MemWalAccount. The owner has full control:
  • Add and remove delegate keys
  • Deactivate (freeze) and reactivate the account
  • Decrypt any memory encrypted under their address via SEAL
Each Sui address can only create one MemWalAccount (enforced by the AccountRegistry).

​
Delegate

A delegate key authenticates API calls through the relayer. Delegates can:
  • Store memories (remember, analyze)
  • Recall memories (recall)
  • Restore namespaces (restore)
  • Decrypt SEAL-encrypted content (via seal_approve)
Delegates cannot:
  • Add or remove other delegate keys
  • Deactivate or reactivate the account
  • Transfer ownership

​
SEAL Access Control

The contract’s seal_approve function is the SEAL policy that controls who can decrypt memories. Access is granted if the caller is:
  1. The data owner — the key ID ends with the BCS-encoded owner address and the caller is the account owner
  2. A registered delegate — the caller’s Sui address is in the account’s delegate_keys list
The account must also be active (not frozen). If the account is deactivated, all SEAL access is denied.

​
Permission Boundary

These are separate layers that work together:
LayerControlsEnforced by
OwnerAccount control — keys, activation, ownershipSui smart contract
DelegateApplication access — read/write memorySui smart contract + relayer verification
RelayerBackend execution — encryption, storage, searchServer-side auth middleware
The relayer verifies every request against the onchain contract before executing any operation. Even if the relayer is compromised, it cannot forge delegate permissions or change ownership — those are cryptographically enforced onchain.