the record
Latest entries
The newest entries in the archive, as written on Ethereum by their authors.
Loading…
IWrite an entry
Draft freely — nothing leaves this page until you sign.
The exact bytes that will be recorded
Sign on Etherscan instead of this page
Draft here, then sign on Etherscan's own page, so nothing from this page touches your wallet.
The argument has to be exact. The contract will accept a malformed one, and the fee with it, but the archive will not — so this page writes it for you rather than leaving it to be typed.
This route takes a single paragraph with no straight double quotation marks — Etherscan's form rewrites both. Apostrophes and “curly” quotes are fine.
Your entry number depends on it. Connecting a wallet fills it in; nothing is signed.
IIThe archive
Every accepted entry, as the open indexer derived it from the chain — —.
Loading…
IIIBefore you write
Three things worth a minute: how it works, what it costs, and how to check any of it for yourself.
Your words live in calldata
Not IPFS. An IPFS archive survives only while someone keeps paying to pin it; when the pin lapses, the chain holds a hash and nothing readable. Here the text itself is inside the Ethereum transaction.
You own the entry, not the DAO
The Ethscriptions protocol makes a transaction's recipient the owner, so a naive design would hand every entry to the treasury. This contract uses ESIP-3 to name you as the initial owner instead.
No one can take your content first
Ethscriptions are normally unique, so a bot could copy your text from the
mempool and inscribe it before you. Entries carry rule=esip6,
which opts out of that rule — a copy can never invalidate yours.
Nothing can be deleted, including by us
Governance can vote to collapse an entry in this view, and the page will say so and link to the raw calldata. The chain is the record; this page is only one way of reading it.
| entry | gas | @1 gwei | @5 gwei |
|---|---|---|---|
| 113 characters, English | 41,233 | 0.000041 ETH | 0.000206 ETH |
| 500 characters, Chinese | 83,950 | 0.000084 ETH | 0.000420 ETH |
Gas only; the write fee is on top. These are calibrated against a real transaction rather than estimated.
Chinese costs more per character because UTF-8 spends three bytes on each one. The limit counts characters, not bytes, so every language gets the same room.
# rebuild this archive from the chain alone, # then compare your hash with the one above git clone https://github.com/indelebile/indelebile && cd indelebile npm install node src/indexer.mjs --rpc <an rpc that serves getLogs>
Re-run the indexer and you must get a byte-identical file. That property is the whole claim — please check it rather than trust it.
This page does not read the chain to show you the archive; it reads the file the indexer produced. Doing otherwise would put a second copy of the rules in the browser, free to drift from the first.
The copy you are reading is rebuilt every ten minutes by a public job; each run's log and hash are on GitHub Actions.
Step by step, including which public RPC endpoints will serve these queries and what to check if your hash differs: VERIFY.md. The contract's source is verified against the deployed bytecode on Sourcify.