Interoperability

What this is

Each entry below is work performed on a specification written by somebody else: an implementation built from the published document alone, an independent execution of the conformance evidence the document relies on, or executable checks written from the published document to test the document itself where it publishes none. Each case states whether the work was self-initiated or commissioned; where commissioned, that relationship is disclosed. The deliverables are published with their hashes, anchored to the Bitcoin blockchain, and accompanied by the steps needed to reproduce them.

Two rules govern this family. Where a document could not be resolved without asking its author, the ambiguity is recorded as a defect rather than resolved by asking. And nothing is claimed here that a reader cannot check: what each exercise establishes is stated alongside what it does not.

This is distinct from Verification records, which document the provenance of work published on this site rather than work performed on documents by others.

Cases

• Independent implementation — Bitcoin-anchored temporal proof

  draft-fassbender-scitt-time-anchor-03

  A producer-side implementation written at the author's invitation, from the published document alone, with no guidance from her. One anchored artifact, its verified Anchor Proof, reproducible construction steps, and one specification defect report. The verifier built here returns valid against a self-operated Bitcoin full node, meeting the header-source and confirmation-depth conditions the profile requires.

  July 2026 · artifact anchored at block 960175 · nine Python modules · MIT

• Independent verification — attestation reconciliation conformance

  draft-hillier-scitt-arp-03

  An independent reproduction of the author's conformance run on a third platform, and a property verifier written from RFC 8949 to close a coverage gap the author had declared himself. The reference encoder passes on the full corpus; the widely used library encoder diverges on the key pair where the two deterministic orderings of RFC 8949 disagree.

  August 2026 · three artifacts, anchored at block 962042 before delivery · BSD-3-Clause

• Executable review — attested payment authorization

  draft-hawkins-scitt-attested-agent-payment-01

  Executable checks written from the published specification to test its grammar, its sequencing rules and the wire definitions its own text makes load-bearing, in a document that publishes no test vectors. Outputs reproduced byte for byte on a second reviewer-operated machine.

  August 2026 · eight artifacts, anchored at block 962892 before delivery · BSD-3-Clause