What this Explorer shows
XnY is the on-chain data lineage and royalty protocol for human and agent intelligence. It turns units of data work — sourcing, labeling, validation, agent-generated traces — into verifiable contribution fingerprints, assembles them into data assets, and routes downstream revenue back through a royalty graph.
This Explorer is a read-only window onto the resulting lineage. Every page answers one question about protocol state: what a record is, where it came from, who is attached to it, and how ownership and royalty flow from it. Three things about that are worth knowing before you trust a number on screen.
- Indexed, not live
- Values are read from an indexer that follows the chain, not from a node at request time. A transaction that just landed can be missing here for a short while, and a record can be a few blocks behind the chain tip. Every on-chain record shows the block it came from, so you can always see how current it is.
- References, not content
- A payload reference identifies data; it does not give access to it. Content, access policy and decryption live behind an authorization surface this Explorer never touches — so a hash being visible here says nothing about whether the underlying data is readable by you.
- Read-only
- There are no accounts, no sign-in and no writes. Nothing done on this site can change protocol state; every action is a read.
Where work happens
Every contribution is made under a task, which belongs to a campaign, which belongs to a frontier. Nothing exists outside that hierarchy.
- Frontier
- A top-level data domain on the network; campaigns, tasks, and dataset versions all roll up to one frontier.
- Campaign
- A collection effort inside a frontier that defines what data is wanted and issues tasks to contributors.
- Task
- A unit of work issued under a campaign — a SUBMISSION that adds data or a VALIDATION that reviews it.
Identity
Participants are identified by DID, not by wallet. Wallets are replaceable signers; the DID is what contributions, shares, and royalties attach to.
- DID
- Decentralized identifier (did:xny:…) for a contributor — the stable identity that fingerprints, shares, and royalties attach to.
- DBA
- DID-bound account — the wallet address that receives this contributor's shares and royalties.
- Owner
- A DID holding claimed shares in a dataset — ownership is tracked per-DID, not per-wallet.
Contribution
A unit of data work is anchored on-chain as a fingerprint. Only identifiers and hashes are recorded — the data itself stays off-chain.
- Contribution fingerprint
- The on-chain record that a contribution exists: its content hash, kind, and the contributor DID it belongs to.
- Kind
- What a contribution is: SAMPLE (raw data), LABEL (annotation), AMENDS (a correction), or VALIDATION (a review).
- Payload
- The contribution's actual data. This explorer references it by hash and URI only; retrieval, decryption, and any policy that applies happen outside this read API.
- Metadata
- Descriptive fields the indexer fetches from off-chain sources; the status shows whether that enrichment has completed.
- Manifest
- The off-chain file describing a dataset's contents; the chain records only its URI, not the data itself.
- Merkle root
- A single hash committing to the full contributor/share list; individual claims verify against it without storing every entry on-chain.
- Examples
- Approved contributions indexed as members of this dataset — a small sample, not its full membership.
Validation
Contributions are reviewed before they can be assembled into a dataset. The review is itself a contribution, recorded the same way.
- Verdict
- Outcome of validation: PENDING (not yet reviewed), APPROVED, or REJECTED.
- Grade
- Quality grade assigned at verification, on an ascending scale D < C < B < A < S (S is best).
- Execution
- How the task was carried out — by a HUMAN contributor or by an AGENT.
Ownership and royalty
Validated work assembles into a dataset whose ownership is fractional. Shares are claimed per-DID, and revenue is routed by the shares actually claimed.
- Shares
- Ownership units in a dataset, claimed per-DID; a contributor's share balance determines how royalties are routed.
- Claim
- Shares start unclaimed, so an approved contributor's balance stays 0 until their DID claims against the contributors merkle root.
- Royalty
- Revenue attributed to a dataset, split among DIDs in proportion to the shares they have claimed.
- Grant
- An on-chain allocation of shares to a DID — the entry that entitles a contributor to claim ownership in a dataset.
- Network
- Base Sepolia
- Chain id
- 84532
- Block explorer
- Basescan ↗
Every on-chain value shown in the Explorer was written by one of these contracts. The addresses are published so anything here can be checked independently, without trusting this site.
- ContributionFingerprintRegistry0x807baCABEDFF64313F86EE41a00C566462C8b6Fc
- FrontierRegistry0x7E4a5835bb3C4eca7850850A8B91F933ae96E43E
- DatasetVersionRegistry0x901a624FA56c2168e2D370d0F0Aa5BbA5a22dC13
- OwnershipRegistry0xf994bb70f4F038227592EfdC89046c0cfa381897
- RoyaltyEngine0x726F93FFdCc757519644DE6eE72607b0D680f078
- GrantAnchorRegistry0x6631BD982a85DA2a2ECd3b5C2a60E03e2E5a673A
- DidBoundAccountRegistry0xB3855ab28E36208A00ba957b4148EEEe9Ea7E783
- DIDRegistryExternal0x49bc9d93B52367b9Fc173C5bA206d0202A89643a
Implementation addresses behind the upgradeable proxies are deliberately not listed — a proxy shown beside its implementation only raises which of the two to verify. External marks a contract this protocol uses but does not deploy. Source for the XnY protocol contracts is not published yet; the addresses are, and they are enough to read every record independently.