Loops HouseArras

NEAR HACKATHON
Links
Team
1 member- SAOwner
Saul Jaramillo
Overview
PROBLEM. Two AI agents that have never met cannot trust each other with money or with a rating. Whoever pays first takes the risk, and reputation with no payment behind it is easy to fake.
WHAT WE BUILT, live on NEAR mainnet:
- Arras, a non-custodial USDC escrow: v2.arras-escrow.near. The payer locks native USDC with one signed transfer. The marketplace's key can only pay the accounts each payment names: worker, fee recipient, or the payer back. On-chain caps: 10 USDC per payment, 1,000 in total.
- ERC-8004 (Trustless Agents) ported to NEAR: identity-registry.erc-8004.near (agents are NEP-171 NFTs) and reputation-registry.erc-8004.near.
- A payment-proof verifier: payment-proof.arras-escrow.near. A rating carries an Arras payment as proof, and the registry checks on chain that it released money between those two accounts before accepting the score. The escrow and the verifier have no access keys: nobody can change them.
IN USE. Execution Market, where agents hire humans and agents, settles its NEAR tasks through Arras in production. In the demo, agents of our swarm hire each other: lock 0.01 USDC, deliver, get paid by the contract, and both rate with proof. Our own x402 facilitator relays every payment and pays the gas.
ALSO OURS AND LIVE. describe.net indexes these registries, so anyone can look up an agent's reputation. Our SDKs (uvd-x402-sdk on PyPI and npm) sign the payment and attach the proof.
VERIFY IT. The README section "For NEAR HACKATHON judges" gives one read-only command per claim. Example: payment 7wMcKUddY26TvkHLKWxf4ZzAD3Lsm6xKu3DVGK6CcbtJ. get_payment returns Released, and read_feedback_proof returns that id as the proof of both ratings.
HOW NEAR FITS. Meta-transactions (NEP-366) make payments gasless for the payer. Named accounts give agents readable identities. Cross-contract calls let the registry check the escrow, failing closed.
SCOPE. Every payment so far is our own test or swarm. No outside customers yet.