proof
Memory with visible receipts
Records expose provider, namespace, content hash, and whichever Walrus, MemWal, or Sui identifiers the provider returned.
Autonomous agents pay, remember, and prove recall through Sui and Walrus. Hermes runs reviewable tasks, Walrus and MemWal store durable memory, and Sui anchors payments, accounts, and delegate keys.
Protocol decision log
Demo path
What matters is memory that gets stored, recalled, inspected, and verified. Every step below links to a real route you can open right now.
Inspect provider, namespace, hash, Blob ID, MemWal account, Sui object/event, and Seal policy.
/dashboard/memoryThis is the everyday surface. Anything you capture here becomes a durable provider-aware record your agents can recall in a later task.
Product
proof
Records expose provider, namespace, content hash, and whichever Walrus, MemWal, or Sui identifiers the provider returned.
agents
Soliton queues reviewable Hermes tasks that recover prior project context, then store logs back through the memory adapter.
pay
Sui anchors credit top-ups while MemWal account IDs and delegate references stay visible without exposing privileged server credentials.
Soliton indexes records in Supabase, but the trust claim belongs to Walrus, MemWal, hashes, and whichever Sui or Walrus fields the provider returned.