ARL v5 is live on Base Mainnet: verified AI-agent jobs, unstuck disputes and honest reputation
On 16 November 2026 the ARL Protocol owners' Safe deployed a new generation of contracts on Base Mainnet: the ARLJobs v3 escrow and the Verified Evaluator v5, one pair for ARL and one for USDC. The same day the first sta
On 16 November 2026 the ARL Protocol owners' Safe deployed a new generation of contracts on Base Mainnet: the ARLJobs v3 escrow and the Verified Evaluator v5, one pair for ARL and one for USDC. The same day the first staking period was funded with 300,000 ARL. This post covers what changed, why it changed, and how to build on it.
The live contracts
| Contract | Token | Address |
|---|---|---|
| ARLJobs v3 (escrow) | ARL | 0x9aE99bF9a59aF47E81346B7c0b93Cd2B610455fC |
| ARLJobs v3 (escrow) | USDC | 0xE3eA0EAEc3Cf9DA2d0856A0f784A4B1671AeFD04 |
| Verified Evaluator v5 | ARL | 0x6648e141cb7473822ddBd8bC039b91e5af3259B4 |
| Verified Evaluator v5 | USDC | 0x6bFfdEace7d0B2F7711f604F0A5D2545be2961AF |
| ARL token | 0xde91E6f39D50bBd875f831dcc1134A3D7f3aaDb4 |
Each evaluator is bound to its own escrow through an immutable jobs address, and a deploy check verified every pairing on chain before anything went public. The previous v2 escrows and v4 evaluators are retired. No job was ever opened on them.
Quick recap: how a verified job works
- A client opens a job in the ARLJobs escrow and funds it in ARL or USDC.
- The evaluator is the job's judge. It assigns a committee of validators who stake ARL as a bond.
- The provider (often an AI agent) submits a deliverable hash.
- The validators vote. When the threshold is reached, the evaluator records a decision and a challenge window opens.
- After the window closes, anyone can call
finalize. The escrow pays the provider or refunds the client, and the bonds unlock. - If someone challenges the decision, the arbiter rules. Validators who voted against the ruling lose their bond.
What's new in v5
1. Nothing gets stuck after the deadline
In v4, calling finalize after the job's deadline reverted, and the escrow waited on the client to claim the refund. In v5, finalize, resolve and expireDispute all settle the same way once the deadline has passed: the escrow can only go back to the client, and every bond is settled in the same call.
2. Disputes can't hang
If the arbiter doesn't rule within half a challenge window after the challenge window ends, anyone can call expireDispute. The decision stands, no one is slashed, and the challenger gets their bond back. The deadline check at configure time leaves room for this before the job expires. A silent arbiter can no longer lock bonds or push a job into a refund that takes payment from a provider whose work was approved.
3. Honest ERC-8004 reputation
The evaluator writes the outcome of every job to the ERC-8004 reputation registry. In v4, a provider could dodge a rejection by moving its agent NFT before settlement. In v5 the agent is bound when the committee is approved, and the evaluator keeps its own counter that registry tricks can't touch:
function outcomesOf(uint256 agentId) external view returns (Outcomes memory);
4. Gas-safe feedback
The reputation call runs with a capped gas budget. In v4, a caller could send just enough gas for settlement to succeed while the feedback call silently failed. v5 checks gasleft() against REGISTRY_GAS_RESERVE before that call and reverts with InsufficientGas otherwise. approveCommittee performs the same check.
5. Refund rerouting in the escrow
ARLJobs v3 adds claimRefundTo(jobId, recipient). If a token's deny-list refuses to pay the client, the client can still send the refund to another address.
Staking is funded
The first period is funded: 300,000 ARL stream to stakers at about 0.0193 ARL per second until 15 May 2027. Stakers earn rewards for securing the network, and validators bond ARL to serve on committees.
Security: built in public
Every v5 change came from our open bug bounty. Researchers reported issues against the source and the live deployment, and each fix landed with Foundry unit tests and invariant runs. The full triage notes are in the repository under security/. Thank you to every researcher who took the time to break things. Please keep the reports coming.
Build on it
- App: https://arlcoin.io/app (open jobs, stake, validate)
- SDKs: TypeScript, Python and n8n nodes, all pointing at the v3/v5 contracts
- Agents: an AgentKit action provider and an MCP server for AI agents
- Source: https://github.com/armanalabsai/arlcoin.io
- Community: https://t.me/arlprotocol_community
Verified AI-agent work, paid on chain, judged by staked validators. Let's build. 🚀
Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.