Pre-launch · 0G Galileo + Sepolia
Coordinate securely.
Collaborate privately.
SoulVault keeps agent swarms alive across ephemeral sessions, and lets humans and agents share sensitive documents through ordinary channels. Fields are redacted locally and reconstructed only by wallets that are authorized to see them.
- AES-256
- GCM payloads
- secp256k1
- ECDH key wrap
- Isomorphic
- browser + node
- Zero PII
- on-chain
What it does
One cryptographic core, two problems it solves
The same secp256k1 ECDH and AES-256-GCM primitives that keep a swarm's state recoverable also decide which fields of a document a given wallet can reconstruct.
Foundation
Continuity for agent swarms
Agent sessions end. Their skills, memory, and shared state shouldn't. SoulVault backs up swarm state under a rotating epoch key, restores it on any machine, and governs membership through contract events.
- Encrypted backup, restore, and transfer
- Epoch rotation on membership change
- Join requests and owner approval on-chain
Extension
Selective disclosure for documents
Redaction runs locally. What travels through email or Slack carries no sensitive fields at all — so forwarding it to the wrong person discloses nothing. Authorized wallets reconstruct only their permitted slots.
- Redact locally, send the artifact anywhere
- Per-field grants scoped to a wallet
- Revocation blocks every future hydration
How it works
The document that leaks is the one that reveals nothing
Four steps, no server holding your plaintext at any point in the chain.
- 01
Redact locally
presidio-web detects PII in the browser and swaps each span for an opaque slot id. Plaintext never leaves the device during preparation.
- 02
Encrypt and commit
The removed fields are sealed under a fresh data key and stored on 0G. Only a commitment, a policy root, and a nonce go on-chain.
- 03
Send it anywhere
The redacted artifact travels through Gmail, Slack, or a USB stick. It is safe to forward, because it carries nothing that was removed.
- 04
Hydrate by wallet
The recipient connects a wallet and signs. SoulVault checks the grant, wraps the key to their session, and the browser reveals only permitted fields.
Revocation is forward-looking. It stops every future hydration, but it cannot make a recipient forget plaintext they already read — which is why fields an agent only needs to compute over are granted USE, never READ.
Demo
Watch a document survive the wrong inbox
A walkthrough of the full path: redact a referral letter, email it, hydrate it as the authorized recipient, then watch an unauthorized wallet get nothing.
Run it against a testnet in a few commands
The CLI, contracts, and protocol core are open source. Clone the repo, point it at 0G Galileo and Sepolia, and walk through the stories.