How it works

Two steps happen once per wallet: unlock and shield. Then every file goes through six. At each one, here is what your device holds and what anyone can read on chain.

contract-2026.pdf3.9 MB
ciphertext · 4 MiB · 1 year · paid by the pool
  1. 01

    Unlock

    Your wallet, once per device

    Your wallet signs a fixed Geode message. The signature never leaves the browser; from it Geode derives one seed, and from the seed your spending key (it owns your notes), your view key (it decrypts your manifest) and your locator (where your manifest is found).

    This signs no transaction. On a new device the same signature brings back the same keys, so your vault comes back with it.

    Stays with you

    • Seed, spending key, view key, locator

    Public

    • Nothing
  2. 02

    Shield

    Your wallet signs shield

    You move SOL from your wallet into the Geode pool. The pool records a commitment, a hash of the amount, your key and a random blinding, as a new leaf in its Merkle tree. Only you can spend it.

    This is the one transaction your wallet signs. Every storage payment after it spends from the pool with a proof.

    Stays with you

    • The note: amount, owner, blinding

    Public

    • Your wallet moved an amount into the pool
    • A commitment in the tree
  3. 03

    Seal

    Your browser

    Your browser encrypts the file in chunks with XChaCha20-Poly1305 under a fresh key made for this file alone. Its name and type go inside the encryption with it.

    The ciphertext is padded to the next power-of-two bucket, from 64 KiB up. A 2.4 MB scan and a 3.9 MB contract both become 4 MiB of ciphertext.

    Stays with you

    • The file, its name and its key

    Public

    • Nothing yet. The file has not left the device.
  4. 04

    Quote

    The relayer

    The relayer prices the bucket and the term you chose: Irys’s live price for that many bytes, plus Geode’s fee. You see the total before anything is paid.

    Stays with you

    • Which file it is

    Public

    • Nothing. A quote is not recorded.
  5. 05

    Prove

    Your browser

    Your browser builds one Groth16 proof that it owns unspent notes in the pool worth the price plus the fee, with any change going back to a new note of yours.

    The receipt, Poseidon(ciphertext root, bucket, term), names this one upload. The proof is bound to the receipt, the price, the fee and the relayer, so the SOL it releases pays for this exact upload, at this price, through this relayer, and nothing else.

    Stays with you

    • Which notes were spent
    • Your keys

    Public

    • Nothing yet. The proof is built here.
  6. 06

    Pay

    The relayer submits pay

    The relayer sends the proof to the Geode program and pays the transaction fee. The program checks the proof (under 200K compute units), checks the root is one the pool has held, records the two nullifiers so the notes can never be spent again, inserts your change note, and moves the price to the storage vault and the fee to the fee vault.

    Your wallet is in no part of this transaction.

    Stays with you

    • That it was you

    Public

    • Two nullifiers
    • A change commitment
    • The root
    • The amount
    • The receipt, its bucket and term
  7. 07

    Store

    The relayer, on Irys

    The relayer uploads the ciphertext to Irys tagged with the receipt and returns its Irys id. Your browser adds the file to your manifest, which is encrypted under your view key and stored the same way.

    A relayer that takes the payment and never uploads holds nothing it can use: the receipt is public, and your browser sends the same ciphertext again, to any relayer, against the same receipt.

    Stays with you

    • The Irys id beside the file’s name and key, in your manifest

    Public

    • A ciphertext of a bucket size, tagged with the receipt
    • An encrypted manifest under a tag only you can derive
  8. 08

    Open

    Your browser

    Your browser fetches the ciphertext by its id from the Irys gateway and decrypts it with the file’s key from your manifest.

    A share link carries that key after the #. A browser never sends that part of a link to a server, so whoever opens it decrypts the file themselves, with no wallet.

    Stays with you

    • The file

    Public

    • A read of a public ciphertext

Look at a real record

Paste any Geode upload’s Irys id or a Solana signature and read exactly what is public about it.