An agent requests validation and names the Markovian validator address. The Markovian relayer watches for that request, resolves the provenance behind it against the public verifier, and answers on-chain. The two calls are shown below.
The ERC-8004 response is a score from 0 to 100. A 100 from Markovian means a provenance record was found and recorded on the chain, not that the agent's work is correct. The tag set to provenance is the firewall that stops a 100 from being read as a correctness claim. Any consumer can filter by that tag and read the score for what it is.
External stamps carry a BN128 Pedersen commitment and a Merkle root, and nothing more. They establish that data was committed at a point in time. They make no claim about whether the data is right.
A real Markovian stamp travelled through the ERC-8004 Validation Registry envelope on the Sepolia testnet. Every artifact below is live and independently checkable on Etherscan and against the public verifier.
The canonical ERC-8004 Validation Registry is not yet deployed to mainnet. That portion of the standard remains under active development with the TEE community. Markovian is proven today against the reference Validation Registry interface on Sepolia, and the mainnet path follows when the registry ships.
Until then, the live mainnet route is the ERC-8004 Reputation Registry, which carries the same provenance record as an off-chain feedback link. The COMMIT object stays identical across both. Only the on-chain envelope changes.
The Etherscan links above read the response straight from the chain. The public verifier returns the provenance record behind the stamp, with no account and no dependency on this site.