The ledger
Once a day we put one fingerprint of the records we wrote that day on Bitcoin, through OpenTimestamps. It proves that a record existed, unchanged, on that date. It does not prove what a stone is.
- Batches
- 0
- Records
- 0
What it proves
- A record in the ledger existed on the date of its batch and has not changed since: changing one character changes its fingerprint.
- No batch can be taken out or replaced later: each one names the one before it.
What it does not prove
- What a stone is. The ledger shows only that a record was not changed after its date.
- That a record is right. A mistake recorded on a date stays a mistake; a correction is a new record with a date of its own.
What goes in
The review record of each listing, each contract by the SHA-256 of its text, the signatures, and every step of a deal.
Batches0 batches, 0 records
Newest first. A batch waits for Bitcoin until a calendar confirms it in a block, usually within hours.
No batch yet. The first one is written on the first day the marketplace records something.
Check a batch yourself
You need the two files of a batch and the OpenTimestamps client. After the download, nothing depends on us.
- Download the manifest and its proof into one folder, under the names they come with.
- Install the OpenTimestamps client.
- Run ots verify on the proof. With a Bitcoin node it checks the block itself; without one, add --no-bitcoin and it names the block and the Merkle root to compare on any block explorer.
- To check the chain: the manifest's "previous" is the SHA-256 of the manifest of the batch before.
pip install opentimestamps-client
ots verify erebaur-ledger-N.json.ots
ots --no-bitcoin verify erebaur-ledger-N.json.ots
sha256sum erebaur-ledger-N-1.json