Glossary

Glossary

Every witness-network term, in one line each.

TermMeans
AnchorOne signed tuple — {head, count, cumulative, as_of} — submitted to witnesses. The only thing a witness ever sees.
ChainOne agent's spend history, identified by a seed id.
Seed idThe stable identifier of a chain, derived from the public delegation. Used to read a witness: GET /v1/anchor/{seed}.
HeadThe commitment to the whole private log at a point in time. Reveals nothing about its contents.
WitnessA node that co-signs monotone growth and logs what it accepted. Sees aggregates only.
Member keyA witness's public signing key, printed at first boot. What principals put in their declared set.
Witness set (𝒲)N named members plus a threshold t, committed by a content hash carried inside every anchor.
Threshold (t)How many cosignatures finalize an anchor. t must collude to lie; N − t + 1 down blocks anchoring.
Finalized anchorAn anchor carrying ≥ t distinct cosignatures from the declared set, each with a log-inclusion proof.
CosignatureA witness's signature over an anchor it accepted.
Inclusion proofEvidence that a witness put the anchor in its append-only log, rooted in a signed checkpoint.
Duplicity proofBoth signed tuples for one (chain, index) — a portable, offline-verifiable contradiction.
EquivocationShowing two verifiers two different histories. What a duplicity proof catches.
WithholdingServing a truncated history so recent records "don't exist". What freshness catches.
FreshnessA labeled result — fresh, stale, unanchored — reported beside the verdicts, never inside them.
StaleA finalized anchor exists ahead of the history you were given. Not tampering — tampering fails outright.
UnanchoredNo anchor reachable. Freshness unknown, which is never the same as fresh.
WatcherAnyone reading many witness logs and comparing them. The market is one.
Anchor storeThe node's durable record of the last anchor co-signed per chain — its anti-equivocation memory.
Rolesanchor (spend anchors), kel (key-history receipts), cosign (log checkpoints). One node serves any combination.
Registry copyThe node's local copy of parties' public identity events, used to resolve submitters' current keys.
Conformance vectorsThe published, implementation-neutral test suite that defines what a witness must do.