PERMADATA X1 MAINNET

Permanent storage on the X1 chain

Your file, written into the chain itself.

PermaData stores files directly on the X1 chain — no cloud, no gateway, no middleman to trust. The bytes live in the network’s own state, and you can pull them back and prove they match, byte for byte.

Upload a file → Play the film in your browser Inspect a stamp

1Two ways to store bytes

Same chain, two different guarantees. Pick on how long the bytes must survive and what you want to pay to hold them.

PERMANENTaccount state shipping · in review
  • Bytes live in rent-exempt accounts.
  • Held hot by every validator — any node reads them.
  • Cannot be pruned.
  • Deposit refundable once close ships.
~$1.39 / MB 6,960 lamports/byte · varies with XNT price

Built and byte-verified locally; not yet deployed to mainnet.

LEDGERtransaction history live on mainnet
  • Bytes live in transaction history.
  • ~78× cheaper than account state.
  • Needs a node that keeps history to retrieve.
~$0.018 / MB 81,500 lamports per 900-byte chunk · varies with XNT price

Live now. The film below proves it.

2The film is the proof

A real, complete file — Night of the Living Dead (1968) — is sealed in the chain on the ledger tier. Every number below is read live from the chain, not typed by hand.

Night of the Living Dead (1968) public domain
Size1,862,510,336 B
Chunks2,069,456 × 900 B
Runtime95.9 min
Video1920×1080 · H.264
Upload3h 11m · ~195 tx/s
Retrieval~37–39 min · ~0.80 MB/s
Content hash (sha256)
8d5f6dd2bc41ab9b16db69b182beccddef1547da2dba6e3a3301da092da3672d
Stamp address
ALuMA6zrW9NWGACyK7SbExwyWteAeDz9YEANFkizNUU4
Play it in your browser → Open the stamp page Download with the toolkit

3Live, from the chain

Read straight from the X1 RPC at load time — nothing cached, nothing hardcoded.

Stamps on chainreading…
Flagshipreading…
Programreading…

4How it works

Four steps, accurate for both tiers. No sidechain, no cloud storage, no gateway — the chain itself is the storage.

1

Chunk it

The file is split into 900-byte chunks. Nothing is compressed or rewritten — the bytes stay exactly as they are.

2

Write it

Each chunk is written to the chain. On the ledger tier, one chunk is one append_chunk transaction, so the transaction log is the storage. On the permanent tier, the bytes go into rent-exempt account state held by every validator.

3

Seal it

A Merkle root over every chunk is committed in the stamp, alongside the file’s SHA-256. That hash is the file’s permanent identity on the chain.

4

Retrieve & verify

To get the file back, the tool reassembles the chunks in order and checks the SHA-256 and Merkle root as it goes. A match means you have the exact bytes that were sealed.

5Protocol facts

The real addresses and fee schedule. Nothing here is a placeholder.

PermaData programMoViekvxc6uK6yDBf2XidPPph5ewU4XVWj2LKD4Zk3w
Royalty hookmovcBceiXZWRfaGPdHNMqTutnTWDzH1BfRQ8N5k65JB
Config PDACfSyiaWw6g3m6rkFScqEotFiX7gePtVyRYoRB7Ds1Ggf
Feemax(0.25 XNT, rate × cost) · 5% ≤10 MB · 4% ≤100 MB · 3% ≤1 GB · 2% >1 GB
Rent6,960 lamports/byte · exemption 1.0 year

Store something permanent

Pick a file, see exactly what it costs, and get the command to seal it on-chain.

Upload a file →