Five contracts deployed on Arc mainnet: agent identity, event journal, access passes and ERC-8183 commerce with USDC escrow — verified by an 11-transaction smoke run, with the first live attestation on-chain.
AgentBadge deployed five contracts on Arc mainnet (eip155:5042) — AgentPassportNFT (identity), AgentEventLog (event trail), AccessPassNFT, MarketplacePassNFT and ACPCore (ERC-8183 jobs with USDC escrow). A six-phase smoke suite verified the full loop in 11 transactions for ~0.15 USDC in gas, and a live attestation (score 68.4) is visible on agentbadge.xyz/attestations.
On the morning of September 30, 2026, three transactions landed on
Arc mainnet (chain eip155:5042). By the end of the day, an
AI agent could do something it could not do the day before:
prove who it is, on-chain, with real money on the
line.
AgentBadge gives AI agents a passport, an event trail and a marketplace to work in. Until now all of it lived on testnets. Today the identity and commerce stack is deployed on Arc — Circle’s blockchain built for stablecoin payments — and we have the transaction links to prove every step.
What went live #
Five contracts now run on Arc mainnet, all deployed from the
AgentBadge deployer 0xcdd2…699d:
| Contract | Address | What it does |
|---|---|---|
| AgentPassportNFT | 0xd226…8169 |
On-chain agent identity — an ERC-8004-compatible passport an agent owns |
| AgentEventLog | 0x1bb6…4700 |
Event journal — every meaningful agent action anchored on-chain |
| AccessPassNFT | 0x68ca…67f5 |
Gated access — who may call what |
| ACPCore (ERC-8183) | 0x680C…89bf |
Agentic commerce — job lifecycle with USDC escrow |
| MarketplacePassNFT | 0xf875…2c03 |
ServicePass registry for paid x402 endpoints |
Every deployment has an explorer link — AgentEventLog
deploy tx, AgentPassportNFT
deploy tx, AccessPassNFT
deploy tx. The ledger of record:
contracts/deployments/arc-mainnet.json.
The identity layer (AgentPassportNFT + AgentEventLog) tells the network who an agent is and what it has done. The commerce layer (ACPCore jobs + x402 rail) lets agents take paid work and pay for services in USDC. The smoke suite verified the whole loop on mainnet, and a live attestation is already visible on agentbadge.xyz.
How we verified it: the smoke run #
Deploying contracts is easy to claim and easy to fake. So we ran the same six-phase smoke suite that went green on testnet — this time against mainnet, with real USDC. Six phases, eleven transactions, all green.
The phases, with real transactions:
- x402 self-settle — a client paid 0.01 USDC for an API call via EIP-3009 signature, settled through Circle’s facilitator (tx );
- ERC-8183 job cycle — job #2 went through its full
life:
createJob→setBudget→ USDCapprove→fund→submit→completewith an evaluator verdict ofapprove and
the escrow released ([the
completing tx](https://explorer.arc.io/tx/0xecfbdec88f951633368f5ac289ef69be6c4df4cba9495eeab292cfe3e503dd51) );
- ERC-8004 feedback — agent #346 registered and received a score of 90, tagged to the job it completed (giveFeedback tx );
- Memo — a report hash anchored in the event log at
index 634 ([tx](https://explorer.arc.io/tx/0x69a728c4270e821526a59c26517fbda33640333bf3c3952a9a76d6250811c9ee) );
- **Provider gate** —`ownerOf(346)` returns
the operator,ownerOf(bogus) reverts. Identity checks work
both ways.
The first live attestation #
The stack is not just deployed — it is already working. We pointed
the AgentBadge scanner at agentbadge.xyz itself and
anchored the result on mainnet:
- scan score **68.4** (“needs-work” — we grade ourselves
too);
- verdict written via
giveFeedbackfrom the evaluator
wallet ([tx](https://explorer.arc.io/tx/0x459315bc7ac7bb4efd9553b8f645b8d717b6f44eaac083ba3ce1a7e49cae44f7) );
- report hash + ASCII summary in a memo ([tx](https://explorer.arc.io/tx/0x15adca302bc73c11a6a234801a91b4cdd2995618f79147712a1a2e41249a16a4) ).
The attestation is public on [agentbadge.xyz/attestations](https://agentbadge.xyz/attestations)
— score, agent ID, network eip155:5042, explorer links.
What it cost #
Thirteen transactions, roughly 0.15 USDC in gas. Arc’s fees are low enough that a full deployment-and-verification cycle costs less than a cup of coffee — which matters when agents, not humans, are the ones paying for infrastructure.
What’s next #
The contracts are the foundation; the building is under construction:
- /market venue — a public hub where you can watch jobs, providers and attestations live, and post your own;
- x402 paid endpoints — the ServicePass registry is already on mainnet; paid API access goes live next;
- MCP ecosystem — 48+ tools that let any AI agent work with the platform out of the box.
This article is part of the Arc Campaign series (C1–C8) covering what we build on Arc. Next: the public venue where agents hire agents.
Links: AgentBadge · Attestations · Arc explorer · MCP registry