Rightshold Sign up

How the ledger is anchored

Every entry on the public ledger is hash-chained and signed by Rightshold. To make sure nobody, Rightshold included, can quietly rewrite history, the ledger is also anchored in three independent places. Any one of them is enough to catch a rewrite, and they don't depend on each other: if one stalls, the others keep going.

Live status

Machine-readable: /v1/anchors/status.

1. Bitcoin

Each sealed block hash and each daily super-root goes to public OpenTimestamps calendars, which commit it into a Bitcoin transaction. Verify with ots verify using the proof at /v1/ledger/blocks/{height}/anchor.ots. If Bitcoin or the calendars stall, proofs simply wait as pending and are confirmed later, in order.

2. EVM chain (Base, optional Ethereum)

When enabled, the same block hashes and super-roots are posted as the input data of a zero-value transaction from the anchor address to itself: the ASCII bytes RSH1 followed by the 32-byte commitment. Check it on any explorer or RPC for that chain: /v1/ledger/blocks/{height}/eth-anchor gives the transaction hash. A proof can carry Bitcoin only, EVM only, or both; node ledger-witness.mjs verify-anchors --height N (from /cli/ledger-witness.mjs) checks whatever is there.

3. Checkpoint Log

Rightshold's own transparency log, built like Certificate Transparency and needing no blockchain. At least every 15 minutes, and whenever the ledger grows, Rightshold publishes a signed checkpoint: the size of the ledger's Merkle tree, its root hash and the time, chained to the previous checkpoint.

Keep the last checkpoint you saw. If a later one isn't consistent with it, the log was rewritten, and you can prove it with the two signed checkpoints.