How Etchd Works, in Detail
How the calendar turns a hash into an anchor on Ethereum Classic, what it publishes, and how to check a proof or keep a copy with the CLI. The pages link to the code and specs behind them.
How It Works
- Why EtchdWhat timestamp proofs are for, the public record kept each minute, OpenTimestamps and the case for Ethereum Classic.
- ArchitectureThe Workers, Durable Objects, storage and Workflows behind the calendar, and what keeps going without Cloudflare.
- StampingHow a hash leaves your machine, joins a one-second round and comes back as a pending proof.
- Worked ExampleOne real stamp of hello.txt, byte by byte, from the digest to an ETC transaction and back through verify.
- TicksThe tick root sealed each UTC minute, what goes into it and the beacon chains it records.
- The ETC AnchorThree Merkle trees, one ETC transaction a minute and the open contract it calls.
- VerifyingWhen the calendar serves a proof, what the verifier checks, including the sender and the confirmation count, and what a reorg does to it.
- The Bitcoin BridgeBitcoin heads go into every tick, and every hour the ticks go into Bitcoin.
- What a Proof ProvesWhat a proof shows and leaves open, how precise its time is, and the quantum argument for proof of work.
Data and Keys
- What We PublishThe calendar records, every witness capture with its normalized form, the raw bytes we keep, and what we never publish.
- SignersWhich key signed which anchors, the window each key is accepted in, and how we rotate to a new one.
- Daily BundlesOne CAR file per UTC day, the export index, and single blocks by CID from our own gateway.
- MirrorsKeeping a checked copy of the daily bundles with etchd mirror, on disk, a Kubo node or a pinning service.