The markovian-provenance/v1 record is registered once as an EAS schema, then each COMMIT is issued as an attestation against it. Where the data being stamped is itself another EAS attestation, the Markovian receipt attaches to it by refUID, bolting a Bitcoin-anchored proof onto an existing attestation.
An attestation carrying a Markovian record establishes that the data was committed at a point in time. It makes no claim that the data is correct. The EAS signature records who attested; the Markovian root records that the content existed and when, anchored beyond the EVM chain the attestation lives on.
External stamps carry a BN128 Pedersen commitment and a Merkle root. EAS contributes EVM-native discoverability and indexing; Markovian contributes a settlement-neutral Bitcoin anchor and a ZK commitment an EAS attestation does not have on its own.
The markovian-provenance/v1 schema is registered on the Ethereum Sepolia EAS deployment, and a real Markovian stamp was issued as an attestation against it. Both are live on EASScan and independently checkable.
EAS is itself an attestation and timestamp primitive, so the door is framed as a complement. An EAS attestation is anchored to the EVM chain it was issued on; the Markovian record adds a Bitcoin anchor, a ZK Pedersen commitment, an account-free public verify URL, and one portable receipt that also reads across the other doors, W3C VC, A2A, MCP, ERC-8004, and C2PA.
The headline wiring is refUID: take an existing EAS attestation, such as an AI model evaluation, and attach a Markovian receipt that anchors it to Bitcoin. Notarized on EAS, and anchored beyond it.
EASScan reads the schema and attestation straight from Sepolia. The public verifier returns the provenance record behind the same root, with no account and no dependency on this site.