RCO-10060 defines a signed receipt for a cleared read of a listed issuer's record. The receipt identifies the subject, the jurisdiction, the clearance rule, the stated time of the read and the hash of the signed answer supplied, and links that event into a verifiable receipt chain. The RCO door sig…
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"rco-records-record-of-cleared-orders","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Not distributed through a package registry we index.
| when | check | result | http | latency | detail |
|---|---|---|---|---|---|
| 3 h ago | mcp initialize | ok | 200 | 289 ms | server rco-records 2.5.3 · protocol 2025-06-18 · 5 tools |
| 11 h ago | mcp initialize | ok | 200 | 38 ms | server rco-records 2.5.2 · protocol 2025-06-18 · 5 tools |
Attributed to the source that supplied each field. Treated as claims, not facts.
RCO-10060 defines a signed receipt for a cleared read of a listed issuer's record. The receipt identifies the subject, the jurisdiction, the clearance rule, the stated time of the read and the hash of the signed answer supplied, and links that event into a verifiable receipt chain. The RCO door signs receipts under its own key; the producing node separately signs its content under the record key. A consumer verifies the receipt, matches the answer hash and verifies the record, and so holds attributable evidence of both the content and the read. RCO preserves the record of the read without holding the content or judging its truth. Receipt v1: {v, id, seq, writer, caller, subject, subject_type, market, rule_version, cleared_at, answer_hash, prev_hash, hash, sig, kid}. Tools: write_receipt (writer credential), verify_receipt (public), list_receipts, get_statement and issue_auditor_key (the firm's own key).
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.