NFTeria's own source, notarized on-chain.
We hold our integrators to verifiable, on-chain proof — so we publish ours too. NFTeria's release provenance is anchored in the Access0x1 ProvenanceRegistry: the chain is the notary, and this page reads it back live. This is provenance of the source and release, not where the bundle is hosted.
- repoId
0x226f19ebabfb9d4f91a21e574d06c87dbfceeeadd28a550bfd93dbfe06057067keccak256 of NFTeria's canonical source path — the registry's host-agnostic key.
The latest anchored release, per chain.
Read straight from the Access0x1 ProvenanceRegistry on each live NFTeria chain — never asserted in this page. Until the registry deploys and NFTeria's first release is anchored, each card shows the pending state.
Not yet anchored on-chain — claim + anchor pending. The Access0x1ProvenanceRegistry deploys with NFTeria's first claim; this card reads it live the moment the address lands.
Not yet anchored on-chain — claim + anchor pending. The Access0x1ProvenanceRegistry deploys with NFTeria's first claim; this card reads it live the moment the address lands.
Claim → snapshot → release. The chain remembers.
Claim
An account claims the repo on-chain (first-claim-wins), keyed by a host-agnostic repoId — the keccak of the repo's canonical path. The chain now knows who owns this source.
Snapshot
The owner anchors timestamped snapshots — a Merkle root committing to the whole repo tree plus the source commit. Each is permanent and publicly re-derivable.
Release
The owner anchors a tagged release — a content id (the published bundle's CID), a git tag, and a Merkle root. A consumer can prove an artifact matches exactly the source the owner committed to.