Ethereum Magicians drafts Know-Your-Agent ERC for trust assertions atop ERC-8004
By 8bitcrypto
September 20, 2026
Ethereum Magicians thread 29735, posted September 19, 2026, drafts a Know-Your-Agent (KYA) ERC that packages trust conclusions for autonomous agents sitting on ERC-8004 identity rails. Author garyyang-finchip points to ethereum/ERCs pull request #2012 and the garyyang-finchip/kya-standard reference repo; the draft status is explicit and an ERC number is not yet assigned. Dev Pulse files it as infrastructure for agent economies that already touch marketplace bidding, settlement bots, and NFT tooling—not as a finished mainnet mandate.
ERC-8004 already gives agents portable identity plus Reputation and Validation hooks, but it deliberately stops short of a shared way to say an agent was checked under principle X, by issuer Y, at level L, valid until T, and not revoked. The KYA draft standardizes that container: a Scheme Registry for versioned schemes, a KYA Registry of assertions with issuer, level, claim digest, issued/expiry timestamps, evidence hash, and status, plus a ZK-KYA profile and an EIP-712 handshake with /.well-known/kya.json discovery. The framework records who attested what; it does not invent a credit score or a single KYA algorithm, and the author compares that choice to leaving reputation math off-chain in ERC-8004 itself.
Revision 2 of the draft, also dated September 19 after an external design review, adds a live Sepolia reference deployment against the official ERC-8004 IdentityRegistry and agentId 10387. Worked examples on-chain include attested schemes, attestWithProof with a real Groth16 proof, policy evaluation, and an ERC-8004 bridge sync that mirrored a level into Validation under tag kya:3673f050 with a 60/100 summary readback. The author stresses the Groth16 keys are a single-party test ceremony, and that the bridge is an optional, lossy snapshot that can go stale after an agent NFT transfer until someone re-syncs. Reference contracts named in the thread include KYASchemeRegistry, KYARegistry, KYAPolicyRegistry, and KYABridge8004.
That transfer edge matters for NFT desks. ERC-8004 agents are transferable ERC-721 tokens, so “this agent is accountable” does not automatically survive a sale. Revision 2 makes binding—identity, controller, or instance—a per-scheme declaration and tells relying parties to treat controller-bound assertions as invalid after transfer. Community reply traffic on the same thread already flags that on-chain check() / optional policy evaluation may still return true unless clients implement the binding predicate themselves. Attribute those caveats to the Magicians thread; do not invent mainnet adoption numbers or marketplace mandates.
Marketplace context stays concrete without inventing volumes. Agent-driven bidding, allowlist checkers, and settlement helpers already sit next to OpenSea, Magic Eden, and Solana desks that collectors use daily. If those helpers start advertising “KYA verified” badges, the Magicians draft is the checklist: which schemeId, which issuers, what level, what expiry, and whether the ERC-8004 agent NFT transferred after issuance. Until a relying party publishes those fields, treat the badge as marketing copy, not as a desk-grade attestation. The same hygiene applies when an agent wallet asks for NFT approvals during an International NFT Day drop window.
For collectors and builders watching agentic marketplace tooling, the practical read is standards hygiene. A KYA assertion is only as useful as the scheme descriptor and the issuers you trust—empty issuer lists are rejected for the same Sybil rationale ERC-8004 uses in summary queries. ZK-KYA hides fact issuers and underlying facts while keeping subjectKey public; proofs can stay ephemeral in the handshake without touching the chain. None of that replaces wallet approval discipline when an “agent” asks to bid, list, or move an NFT, and none of it should be confused with a finished Ethereum mainnet requirement.
How to track the draft without getting farmed: follow Magicians thread 29735, ERCs PR #2012, and the reference repo’s Sepolia deployments folder for tx hashes and superseded revision-1 addresses. Skip Discord links that mint “KYA badge NFTs” claiming official Ethereum Magicians endorsement. Today’s wire is a documented draft plus testnet reference—useful for Dev Pulse readers who need agent trust plumbing next to NFT settlement bots, not a promise that every marketplace will enforce KYA tomorrow.
Disclaimer: This article is provided for informational and educational purposes only. It does not constitute financial, investment, legal, or trading advice. The NFT market is highly volatile, and past performance is not indicative of future results. Readers should conduct their own research and consult qualified professionals before making any decisions related to digital assets. The cover image for this article may have been created using artificial intelligence (AI).
