Rightshold Sign up

Documents · terms

Rightshold Terms of Service — which version is current?

The terms for using Rightshold, as one anchored document family: every revision is anchored when it takes effect, and the head of the stream is the current version. The document itself is at /terms; this page is its anchored revision history, generated live from the chain.

2current revision
2026-10-27 01:13:04 UTCcurrent revision anchored at
2revisions anchored
continuous ✓root-to-root continuity

Current revision's anchored root: 8617227eb7925037ba04ec5117a089ab38426c5a5e02adf16ac766591e37a56e

Revisions

Every revision stays resolvable after it is superseded — supersession is visible, never a silent replacement. Each revision's prev_root is the previous revision's root, starting from the genesis root 0000000000000000…0000.

RevisionAnchored at (UTC)Merkle rootPrev rootReceiptRecord
2 — current2026-10-27 01:13:04 UTC8617227eb7925037…a56e8cd4c11924118a91…f1cdcountersigned ✓revision 2 (JSON)
12026-10-27 01:09:36 UTC8cd4c11924118a91…f1cd0000000000000000…0000countersigned ✓revision 1 (JSON)

Ask the head

The countersigned head for this document — current revision, when it anchored, and how many revisions exist — is at /v1/documents/terms/head (Ed25519-signed; verify it against the public key it carries). Check it before trusting any copy of the document: if a copy claims a revision above the head, or a root the head does not name, it is not the current anchored version.

Anchor a new revision

When a new revision of this document takes effect, its publisher anchors it with the release CLI:

doc-anchor anchor --doc terms --file <the published document file>

Anchoring is append-only: the new revision becomes the head, and every earlier revision remains resolvable at /v1/documents/terms/revisions/<n>.