2.04M+ agents are registered on ERC-8004, per @8004_scan's latest snapshot.
Finding the agent is the easy part now. Knowing who actually gets paid isn't.
So check both before your agent signs: look the agent up on 8004scan, then confirm the payTo in its 402 belongs to its ENS name.
Our wizard runs both checks in one place. https://t.co/cCbF0WHTwa
ERC-8004 Weekly Update | Nov 5β12
8004scan now tracks over 2M ERC-8004 agent registrations.
This week we look at a new rule for agent-only pools, agents you can rent by the day, and an onchain validation request. Plus a Devcon replay and an agent that hires its own video crew β
2.04M+ agents are registered on ERC-8004, per @8004_scan's latest snapshot.
Finding the agent is the easy part now. Knowing who actually gets paid isn't.
So check both before your agent signs: look the agent up on 8004scan, then confirm the payTo in its 402 belongs to its ENS name.
Our wizard runs both checks in one place. https://t.co/cCbF0WHTwa
ERC-8004 Weekly Update | Nov 5β12
8004scan now tracks over 2M ERC-8004 agent registrations.
This week we look at a new rule for agent-only pools, agents you can rent by the day, and an onchain validation request. Plus a Devcon replay and an agent that hires its own video crew β
Your agent will pay whatever address a 402 response tells it to.
Nothing checks that the payTo belongs to the service you meant to pay. A swapped field settles just like a real one.
Verified Payee fixes that before signing: the 402 names the payee, your client reads its ENS records on Ethereum mainnet and confirms the origin and payTo match.
Live on @x402fi_ today. Open proposal at the x402 Foundation.
Agree. Once agents are spending at machine speed on services they pick themselves, "would I trust this agent?" isn't the useful question.
Don't trust, verify: does this payTo belong to the name in the 402?
Verified Payee is an open proposal for that check.
https://t.co/shoQFtSg3K
Builders: list your x402 service on x402Fi. It's free, we take 0%.
You get a dashboard with your revenue, a 30-day chart, and a full ledger you can export as a CSV. Buyers pay you directly in USDG.
The dedicated x402 marketplace on Robinhood Chain.
https://t.co/2w6N7c4xE5
Two figures are out about x402 on Base.
@fabdarice posted a $30 median: bigger payments, real businesses, agents buying on their own.
On the open market, a week of on-chain counts found 1.2M signed USDC payments totaling $34k. Typical payment: about 2 cents. 99% went to sellers averaging under a dime.
Both can be true. They count different sellers.
At $30 or at 2 cents, the check before signing is the same: does this payTo belong to the name in the 402?
Verified Payee is an open proposal.
https://t.co/Ykuyfsaonv
Part 4 is up.
Verified Payee left the WG thread and landed in a live marketplace.
@x402fi_ on Robinhood Chain is the first to ship the verify wizard and the name registration widget in its listing flow. List, bind payTo, get paid.
Open proposal, running code, real storefront.
https://t.co/wBS8iKm8tE
HoodFi Names is the first x402 endpoint listed on @x402fi_, the new x402 marketplace on Robinhood Chain.
AI agents can now register HoodFi Names through x402. Weβre also integrated into the x402Fi wizard with Verified Payee, a new spec from @x402identity that helps agents verify the payTo address.
https://t.co/09mNbEmmev
https://t.co/rp30UDA9wz
Congrats to @x402fi_, the x402 marketplace on Robinhood Chain, for being the first to integrate the Verified Payee wizard and the name registration widget π
Builders can now list services, register a name, and pin their payout address all in one place, so payers can check who gets paid before they sign.
https://t.co/0LtiraNALK
Nearly 2M registered agents tracked by @8004_scan β‘οΈ
Agent discovery and payee verification answer different questions: which agent can do the job, and is this payment going to its authorized recipient?
We're building X402 Identity Hub to help answer the second.
ERC-8004 is closing in on 2M registered agents β‘οΈ
οΈ
Latest on 8004scan:
β’ 1,946,164 registered agents
β’ 872,860 feedback records
β’ 3,139,907 unique wallets
The ecosystem keeps growing. Browse agents by chain and see what they can do β
https://t.co/UhDjTLpzcr
@padrinoIG@8004_scan The core binding is ENS name β authorized payout address. Before signing, the payer checks payTo against that name's on-chain records for the payment network. Domain control is a separate check: an ENS match alone doesn't prove the endpoint belongs to that name.
@8004_scan Almost 2M registered agents! Congrats to the 8004 ecosystem β‘οΈ
As discovery grows, checking who gets paid matters too. That's where Verified Payee complements ERC-8004: checking the payment's payTo address against the endpoint's ENS records before signing.
What are people building with ERC-8004?
We looked through the skills and domains published by more than 18K mainnet agents on 8004scan.
The largest cluster looks like a crypto research desk: news synthesis, market insights, crypto analysis and geopolitical research.
Hereβs what else we found β
ERC-8004 Ecosystem Highlight: Zyfai
@Zyfai_ builds agents that monitor DeFi yield opportunities and rebalance positions from user-controlled accounts.
Zyfai has registered Rebalancer Agents under ERC-8004. Hereβs where the standard fits in β
@8004_scan@BNBCHAIN Great roundup. Spending controls and escrow pair well with payee checks: limit how much an agent can spend, and confirm who it's paying before it signs. Good week for agent safety tooling.
@Marc0Zane@xona_agent One endpoint, many chains is a great UX. The tricky part is making sure the payTo on each chain is legit. A single ENS name can list them all (Solana, Base, other EVM chains), so agents can check whichever one they're paying on.
@topblaster@PayAINetwork Facilitators make settlement easy. The piece that's still on the buyer: is this payTo really the seller's? We built a free way to publish and check that via ENS, now incl. Solana and Lightning node keys: https://t.co/5csAxf2O5C