ERC-8004 & XnY: Three Paths Toward the Knowledge Layer

Protocol · · Jason (Co-founder) · 2 min read

Falling behind one year in frontier technology spaces is no different from falling behind ten. This piece examines the ERC-8004 protocol and XnY, and three potential intersections between them.

What Is the Knowledge Layer?

XnY provides high-quality training data for AI systems. Modern AI learns through data exposure rather than explicit programming. The challenge: as AI capabilities advance to complex tasks (translation, code generation, mathematical reasoning), the demand for higher-quality, more sophisticated training data intensifies.

The paradox: contributors face potential obsolescence as AI masters the skills they teach it.

XnY’s response: a platform organizing both humans and agents to produce refined data assets while providing economic compensation through ownership shares and royalty mechanisms.

Three Integration Models

1. Reconstruction

Converting XnY’s decentralized identity system (DID) to align with ERC-8004 standards for enhanced EVM ecosystem compatibility.

ERC-8004’s flexible schema, originally designed for agent credentials, can accommodate diverse identity representations. Historical precedent: ERC-721 evolved from CryptoKitties to support NFTs, PFPs, and RWA experiments. On-chain systems cannot reliably distinguish between pure code agents and human-operated systems, making unified identity schemas feasible.

2. Fusion

Creating complementary value where ERC-8004 and XnY DID enhance each other’s credibility and functionality.

For XnY: Integration with EVM ecosystem expands adoption potential across diverse applications.

For ERC-8004: Real operational history from XnY DID provides authentic identity signals superior to self-declared credentials, accelerating ecosystem adoption.

Future Scenario: AI agents operating as dual-identity entities, functioning simultaneously as ERC-8004 compliant agents and XnY data contributors.

3. Upstream and Downstream

Positioning XnY as the supply layer and ERC-8004 as the consumption layer within a complete royalty tracking system.

The “Royalty Engine” requires two elements:

  1. Complete data contribution lineage (sampling through validation)
  2. Complete data usage records

XnY tracks contribution lineage effectively but lacks visibility into downstream consumption since it doesn’t control applications using the data. ERC-8004 records agent execution, providing usage transparency that feeds back into contributor compensation calculations.

XnY Production Workflow

Dual Identity Elements (Fusion Model)

Royalty Engine Compensation

  1. One-time payments from primary data consumers
  2. Proportional ownership shares generating ongoing royalty yields

Conclusion

These approaches are testable hypotheses rather than final solutions. Implementation will determine viability. ERC-8004 remains in evolution; there are undiscovered possibilities as the standard matures.

The story isn’t finished. We’re all co-authors.

Related