Users
Anchor your attestation
Add the anchor leg to export-attestation: collect cosignatures to your threshold and publish an aggregate whose rollback is evidence.
Three flags on the export-attestation you already run.
Before you start: your witnesses' names and member keys, and their URLs.
auths-mcp export-attestation \--live-dir ./live \--agent <agent-did> --root <root-did> \--out ./public/activity.json \--anchor-to https://w1.example.com \--anchor-to https://w2.example.net \--witness "w1=<w1 member key>" \--witness "w2=<w2 member key>" \--witness-threshold 2
You should see:
The finalized anchor is embedded inside activity.json. Publish it exactly as before — verifiers that predate the network ignore the extra field.
Below threshold, the export fails
If cosignatures don't reach --witness-threshold, the whole export fails and nothing is written. There is no silent fallback to an unanchored publish once you asked for anchoring.
The flags
| Flag | Meaning |
|---|---|
--anchor-to <URL> | A witness endpoint. Repeat per witness. |
--witness "<name>=<key>" | A declared member — the name and member key the operator gave you. Repeat per member. |
--witness-threshold <t> | How many cosignatures finalize. Default 1. |
If it fails:
- "below threshold" — check each witness answers
GET /health, and that every--witnesskey matches the key that node actually cosigns with. - refused by a witness — your submission wasn't a monotone extension, or that witness's registry copy is stale. See acceptance rules.
The payoff
The market derives its tier from the verified anchor, never from anything the document claims. Your listing badge upgrades from market-witnessed to quorum-anchored (t-of-N).