My implementation is deployed to both testnet and mainnet at canonical address: 0x610aaca1b07dcae88602cc836bb58a437a5791f3
Sharing a short consumer-side note that came out of the MRC-14 discussion but applies just as much to reading MRC-13 attestations. @ColinkaMalinka (ProofLines) and I wrote it: the read conventions a consumer follows when it weighs declared metadata against off-chain evidence, without changing the registry.
Three conventions, each with a conformance check and a real example from the live observed feed: the update event as cache invalidation, a source id on every piece of observed evidence, and an explicit staleness bound on paired evidence. The registry-side checks map to the MRC-13 conformance harness; the observed side comes from the live feed.
1 Like