Sealed forever. Paid by no one.
Files sealed in your browser, paid for from a shielded balance, stored on Irys. The chain sees a ciphertext paid for by the pool.
What an upload leaves on chain
Encrypting a file before it goes to Irys hides what is in it. The record of the upload still holds its exact size, its time, and the wallet that paid, beside everything else that wallet has done.
An encrypted upload, paid from a wallet
- Paid by
- 7xKX…gAsU
- Size
- 2,516,582 bytes
- Content
- ciphertext
- Linked to
- Every other transaction of 7xKX…gAsU
A Geode upload
- Paid by
- the pool
- Size
- 4 MiB bucket
- Content
- ciphertext
- Linked to
- A receipt, two nullifiers, nothing of yours
The proof that pays
One Groth16 proof spends your shielded notes and is bound to one upload’s receipt. Your wallet signs nothing after the shield.
Your browser encrypts the file in chunks under a fresh key and pads it to its bucket.
await geode.store(file)
The SDK does the whole flow in one call, in the browser or in Node: seal, quote, prove, pay, store. It returns the Irys id and the file’s key.
import { createGeode } from '@geode/sdk'
const geode = createGeode({ wallet, relayerUrl })
const { id, key } = await geode.store(file)
// later, on any device the holder signs in on
const opened = await geode.open(id)Stored permanently
Each file is priced by its bucket, at Irys’s live price plus Geode’s fee, and paid from your shielded balance.
- Permanent
Geode’s fee buys $GEODE and burns it. Where the fee goes
Drop a file into your vault
Drop a file anywhere here. It is sealed on this device before anything leaves it, and it opens only for you and the people you send its link.