Skip to content

NEAR competition

Agent Economy

How can an agent request a payment within its owner's budget?

How .x3 fits

A payment program references an owner mandate with recipient and asset allowlists, per-payment and daily caps, approval thresholds, fees, slippage and expiry.

The owner's spending mandate

mandate x3_shopping_agent {
    owner x3-owner.near
    agent x3-agent.near
    spend Solana.USDC
    per_payment 50000000
    per_24h 200000000
    allow recipients x3-demo.near
    allow assets Near.USDC
    refund_to 4Nd1mzi8Y1QYxJt9wZWBYZpG7S4pYkZs6YzD3Vt9aBcD
    require slippage <= 1%
    require fees <= 100 bps
    approve above 30000000 by 1 of x3-owner.near
    expires 30d
}

Amounts use token base units. These accounts are example or historical testnet identities; use the source guide before adapting a program.

What the evidence establishes

Published result

A dedicated Solana agent signed execution from a policy-PDA-owned vault: 5 USDC deposited, 4.999746 USDC delivered to x3lang.near. The owner first approved the exact quote. The earlier NEAR FunctionCall-key quote acceptance is separate evidence.

Trust and limits

The new agent executed one exact owner-approved quote. Owner upgrade/recovery authority remains trusted. This is not unrestricted autonomous spending, and no additional NEAR Guard call is claimed for this pilot.

Next evidence: Keep the reviewed recovery authority and verify broader agent workflows in a zero-value environment before extending the bounded pilot.

Reviewed November 13, 2026 against X3Lang f2a01a2.

Judge walkthrough

  1. Read the mandate and payment source. Identify recipient, asset, amount, nonce, deadline and refund terms.
  2. Run the local policy preview. Change the recipient to attacker.near and inspect the refusal; local results do not prove chain execution.
  3. Open the mainnet invoice_06 bundle and the separately labeled testnet records. Match each contract, transaction and network to its claim. Check that the two published .x3 files hash to the values Guard stores for invoice_06.
  4. For delivery, inspect the source and destination finalized records and the relay assumptions separately from Guard authorization.

Full judge guide