KYA: Verifying AI Agents On-Chain - Live Workshop with Team1 LatAm, Sept 24
Updated October 2, 2026: the workshop took place on September 24. 39 people registered and 19 attended (our team's count). 13 demo attestations were issued on the night of the workshop and 5 more on October 2, to the first 5 respondents of an open follow-up form, 18 in total, all on Fuji testnet through a demo flow without identity verification. 150 USDC in prizes were paid on Avalanche C-Chain mainnet in 11 transfers: 6 prizes of 15 USDC drawn live among those who completed the on-chain exercise, and 5 more on October 2 (2 of 15 and 3 of 10 USDC) to the first people who filled in the follow-up form and posted their attestation on X. The text below was written before the event and is unchanged.
Updated September 30, 2026: clarified that the workshop attestations were issued through a demo flow on Fuji testnet, without identity verification.
Two protocols shipped this year that quietly changed what an autonomous AI agent can do on its own. A2A (Agent2Agent), originally contributed by Google and now hosted by the Linux Foundation, lets agents from different vendors discover, authenticate, and delegate tasks to each other over a standard open protocol. x402, Coinbase's HTTP-native payment standard now co-governed with the Linux Foundation, lets an agent hit an HTTP 402 "Payment Required" response, sign a stablecoin payment, and complete the transaction - no account, no human in the loop. This isn't a paper protocol: x402's own live dashboard shows 75.41M transactions and $24.24M in volume in just the last 30 days (checked September 20, 2026).
Neither protocol answers a simple question: when one of those agents moves real money, who's accountable if it goes wrong? A2A authenticates that an agent is who it claims to be. x402 moves the payment. Neither one verifies who stands behind the agent.
That's the gap KUMPLY's Tier 5 (KYA) attestation is built to close - see our deep dive on the mechanism if you want the full technical breakdown. On September 24, 2026, 7:00 PM Mexico City time (CDMX), we're running a live, hands-on workshop with Team1 LatAm to show it working end-to-end, not slides.
Where this actually bites
Three scenarios, illustrative mechanism examples, not documented incidents - the point is the shape of the gap, not that any specific one already happened:
An autonomous trading agent requests a large fill from a lending protocol. Today, the protocol has no way to tell a vetted institutional bot from an anonymous exploit script probing for a bad price - both look like a wallet calling a function. With a Tier 5 check in front of the fill, the protocol either sees a valid, unexpired credential tied to a KYB'd owner and proceeds knowing who's accountable, or it doesn't, and falls back to a human signer or rejects the trade outright - before any capital moves.
An agent pays another agent's service for compute via x402. The payment itself settles in seconds, no account needed - that part already works, at the real scale cited above. But the seller has no standard way to know who's actually behind the paying agent if the request turns out to be abusive, fraudulent, or simply needs a dispute resolved. A Tier 5 credential gives the seller something to check before fulfilling a high-value request: not just "this wallet paid," but "this wallet is accountable to a real, KYB-verified entity."
Two agents from different companies negotiate a multi-step task over A2A. A2A's Agent Cards handle "who are you and what can you do" - real interoperability, genuinely useful. What they don't answer is "should I delegate something with real stakes to you, and who's on the hook if you don't deliver." Requiring a Tier 5 credential before accepting a delegation with real value attached adds exactly that missing check, on top of A2A's own discovery layer rather than instead of it.
Why this matters now, not in two years
This isn't a future-proofing exercise. x402's own live numbers, cited above and checked the same day this post went up, are already real: 75.41M transactions and $24.24M in volume in the last 30 days alone. That volume is moving today, through a protocol that's barely a year past its foundational governance moving to the Linux Foundation. The payment and discovery rails already carry real value; the accountability layer riding alongside them doesn't exist yet as a standard. That's not a two-years-out problem - it's a today problem with real money already flowing through the gap.
What KYA doesn't solve
Worth being precise about the limits, the same way we're precise about what's shipped versus roadmap in the deep dive. A Tier 5 credential is not a legal-personhood determination - agents aren't legal persons, and KYA doesn't pretend otherwise; it verifies the accountable owner behind the agent, not the agent's own standing. It's not a substitute for a real regulatory or legal opinion in any specific jurisdiction - it's a technical verification layer, not legal advice. It doesn't prove the agent's own model or behavior is safe, bounded, or bug-free - deeper agent-specific verification (model fingerprinting, behavior bounds, liveness checks) is planned, scoped for a future AgentRegistry.sol extension, and doesn't exist in the contracts today. And it doesn't force a bad-faith owner to make things right - it ties accountability to a real, KYB-verified entity so there's someone to hold accountable, but enforcing that accountability in the real world is still a legal and regulatory question, not something a smart contract can do on its own.
Who's presenting
Monserrat Mendoza and Giovanny Amador, KUMPLY's co-founders and Avalanche Team1 LatAm Collaborators, are running the session together. Giovanny ships most of what's in the repository today - every commit attributable to him, verifiable in the public history. Monserrat has led KUMPLY's product and UX/UI direction, and has shipped real code here too (commit 49177e0, address validation before a contract read) - a second technical contributor, genuinely real, just not yet shipping at the same pace.
What you'll build - and leave with
This isn't a slide deck about compliance theory. You'll deploy your own attestation contract live, in Remix, no local setup: WorkshopKYA.sol, a stripped-down practice version built for the session (open issueTier(), no roles or expiry logic) that mirrors the same attest -> tier -> verify() pattern KUMPLY actually runs in production, without the production complexity - fast enough to deploy live in one sitting. It's a teaching tool, not KUMPLY's real code, and it says so in the contract itself.
Then every attendee leaves with an on-chain Tier 5 attestation issued live by KUMPLY to your own wallet (Fuji testnet, demo flow without identity verification), address-only, no personal data ever requested - the same batch-issuance path we already tested end-to-end ahead of the session. And KUMPLY's actual production contracts are real and live too, not a claim you have to take on faith: AttestationStore and ComplianceGate are deployed and verified on both Fuji and Mainnet C-Chain today - see the addresses below and check them yourself.
The contracts are real, and you can check them yourself
Nothing shown live is staged. AttestationStore is deployed and verified at 0xa3Bc5564A18e107807aF41fF2a5215Db050b22dD on Fuji and at 0xa116261Ed3a848A9E1cd34923D5A0442D1455F71 on Mainnet C-Chain (read-only beta, fee at zero) - both confirmed live on-chain the same week this post went up. Bring a browser and check totalAttestations() yourself on Snowtrace before, during, or after the session.
Sources: Google Developers Blog, A2A announcement, A2A Project, Linux Foundation, Coinbase, introducing x402, x402.org, live protocol stats (checked 20-Sep-2026).