Business
Records a third party can verify — without ever holding them
Anchor is Rightshold's attestation service for businesses. Your platform keeps its records where they are. At the moments records are written, it chains them into a tamper-evident history and pins a signed fingerprint of that history here, where Rightshold countersigns and timestamps it. Auditors, buyers and diligence teams can then check the history itself — its continuity, its dates, its counts — while the records behind it never leave your systems.
Live read model — computed at the moment this page is served, from the same public views the API serves. Snapshot: 2026-10-23T15:52:57.373Z · JSON · open the chain explorer
Three ways businesses use Anchor
Third-party audits
Audits stall on evidence: exports, screenshots and spreadsheets a counterparty has to take on trust. With Anchor, the audit trail is built inside your own platform at real write points — every record hashed into a chain at the moment it is written — and each period's fingerprint is countersigned and timestamped here, by a third party that has no access to the underlying records and no ability to rewrite them. An auditor verifies the chain end to end, then samples only the records you choose to reveal. Rightshold receives fingerprints, counts and timestamps. Nothing else.
Valuations
When a business is valued or sold, the price turns on whether its history is real. Anchored records carry independent timestamps from the day they were written, and every anchor commits to the one before it, so the history cannot be backdated, quietly edited or rebuilt after the fact — a break in the chain is visible to anyone who looks. Diligence gets evidence that was fixed in place before a sale was on the table, and the seller keeps the records themselves at home until the moment they choose to disclose them.
Ledger tracking
Every anchor lands in public, next to Rightshold's own Ledger, in the chain explorer: each stream, each anchor, each attested event count, and the sealed blocks of the Ledger itself. Anyone — an auditor, a buyer, a counterparty — can verify the totals and the continuity of both chains without an account, a key or permission, and the numbers at the top of this page are computed from that same record each time the page is served.
Live on the record
Streams anchoring with Rightshold today — the same streams, counts and continuity the chain explorer publishes:
Stream 1 · active · since 2026-10-23
5 anchors · 702 events attested · root-to-root continuity: continuous ✓ · see it in the explorer
Stream 2 · active · since 2026-10-23
2 anchors · 763 events attested · root-to-root continuity: continuous ✓ · see it in the explorer
What Rightshold never receives
An Anchor client chains its records locally, hashing each record together with a secret per-stream salt (leaf = SHA-256(0x00 ‖ salt ‖ chain hash)), and sends Rightshold only the Merkle root of each period — a one-way fingerprint. A root cannot be reversed into a record, and even guessing a record exactly does not let anyone check the guess, because the salt is never published or sent. Only the owner can reveal a record, with its salt and a Merkle proof, and have it verified against the anchored root (POST /v1/anchors/verify-disclosure). Visible by design: counts, period bounds, timestamps and signatures — never identity. Streams are numbered, never named: which business a stream belongs to is published nowhere. Nothing else is here.
Put your history on the record
Write to hello@rightshold.com and tell us what you need to prove, and to whom. The technical surface: the service describes itself at /v1/anchor-service-info, and the full record — every stream, anchor and Ledger block — is in the chain explorer.