Skip to content

NEAR competition · 2026

One policy. Four track perspectives.

A restricted agent call on NEAR, 21 passing policy and quote checks, and a funded Solana-to-NEAR mainnet swap. Explore what each result establishes for the four tracks.

Choose a track

Evidence reviewed November 13, 2026. Owner-selected tracks: AI Security & Defense (primary), Agent Economy, Autonomous Business and Unstoppable DeFi. These pages do not certify organizer acceptance or a saved submission.

AI Security & Defense

Who stops an injected agent from paying an attacker?

The owner writes the spending mandate. The compiler rejects unsupported requests; the NEAR Guard checks signed quote terms against the stored rules.

Agent Economy

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

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

Autonomous Business

How does a business let an AI agent spend without handing it the treasury?

The owner sets the constraints once in a .x3 mandate: per-payment and 24-hour caps, an approval threshold, recipient and asset allowlists, a refund address and an expiry. The agent can only propose payments; Guard enforces the mandate on NEAR mainnet before any cross-chain payment through NEAR Intents.

Unstoppable DeFi

What cross-chain transfer can a judge verify?

Guard checked an official signed 1Click quote on NEAR mainnet before a Solana USDC deposit. A separate historical Base Sepolia transfer demonstrates a committed .x3 source hash bound before funding.

The new mainnet evidence

For invoice_06, x3-agent.x3lang.near used its restricted FunctionCall key to accept a signed live quote on x3lang.near. The Solana deposit was 25.000000 USDC; the NEAR payout was 24.995200 USDC. Guard authorization, funding and delivery have separate records. The original .x3 files match the hashes Guard stores, the owner signed the deposit from the wallet named in the mandate, and the agent recorded a Settled outcome on Guard.

Evidence and limitsAgent authorizationSolana depositNEAR payout

Follow the evidence

Local checks

Run the browser playground to edit policy and inspect a deterministic verdict. It does not sign or move funds.

NEAR Guard

Inspect the mainnet agent authorization and the historical testnet refusal. Guard authorizes the deposit address; it does not hold the funds.

Delivered funds

Open the finalized mainnet deposit and payout, then read how 1Click status associates them. Keep the older Tidepool testnet transfer and its trust assumptions separate.

Source evidence and judge walkthroughs

What moves the proof meter next

  1. Publish an allowed scoped-vault testnet payment and the cap, recipient, daily-window and refund refusal records.
  2. Land and verify program-hash enforcement, including rejection of a mismatched program.
  3. Complete the hostile-model mainnet demonstration, independent review and release provenance gates.

Inspect the evidence behind the meter