The policy after settlement
5 USDC per payment and per rolling 24 hours. Nonce 1 consumed. No pending approval. Vault balance: 0 USDC. The archived post-state records one 5-USDC spend.
X3 Force Field · dotx3.net · NEAR Hackathon
X3 Force Field is programmable security for AI agents: owners write typed .x3 mandates, agents propose .x3 payment programs, the compiler rejects unsafe edits and NEAR Guard checks signed 1Click terms. The model cannot authorize a payment.
A completed 5-USDC payment, from exact owner approval to a finalized NEAR payout.
Your policy sets the budget. You approve the exact quote. The agent executes the allowed payment from a PDA-owned vault: 5 USDC on Solana → 4.999746 USDC to x3lang.near.
Solana mainnet
Exactly 5 USDC
Nonce 1 binds the amount, deposit account, quote digest and expiry. The owner signs this approval.
Solana mainnet
5.000000 USDC
The dedicated agent signs execution. The policy PDA authorizes the inner SPL token transfer from the vault.
NEAR mainnet
4.999746 USDC
The finalized token event pays x3lang.near, above the signed 4.974757-USDC minimum. Provider status: SUCCESS.
5 USDC per payment and per rolling 24 hours. Nonce 1 consumed. No pending approval. Vault balance: 0 USDC. The archived post-state records one 5-USDC spend.
Edit a payment in the policy checker and inspect its decision locally. Then follow the real mainnet receipts here. These checks require no wallet connection or funds.
The generic receipt verifier rejects the differing request/program deadlines. The original receipt is preserved; the archive uses separate vault-commitment, source-event and direct payout checks.
Read the complete proofView offline verifierInspect the signed quote
Historical evidence pinned to X3Lang 9ec3b48. This page does not request a quote, sign a transaction or spend funds.
One real payment on NEAR and Solana mainnet, from the owner's rule to the recorded outcome. What it does not prove is on the same screen.
The owner wrote the rules in .x3. A restricted agent key got the payment past Guard's 21 checks. The owner funded 25 USDC on Solana, and 24.9952 USDC reached x3lang.near on NEAR.
1 · Owner approved
NEAR mainnet
approve_intent
x3lang.near approved this intent before any agent call.
2 · Guard accepted
NEAR mainnet
21 / 21 checks
The agent's restricted key accepted the signed 1Click quote. The receipt returns 21 guards, all passing: recipient, asset, caps, refund, slippage, fees, approval, deadline and quote terms.
3 · Deposited
Solana mainnet
25.000000 USDC
The owner signed the deposit to the quoted address from the funding wallet named in the mandate.
4 · Delivered
NEAR mainnet
24.995200 USDC
intents.near paid native USDC to x3lang.near, 84 seconds after the deposit.
5 · Outcome recorded
NEAR mainnet
Settled · floor met
The restricted agent key recorded the settlement on Guard: 24995200 out, both transaction hashes stored.
The original files hash to the values Guard stores for this intent and mandate (v4).
One-page proof card · Link-by-link check · Evidence bundle · Outcome readback · Raw public RPC observation · Observer run · Reviewed November 13, 2026 against X3Lang f2a01a2
Watch · 2:27
Follow invoice_06 from the original .x3 mandate through local refusals, mainnet authorization, the owner-funded payment and recorded outcome. Narrated with captions.
Mainnet cards summarize archived receipts; terminal output is a local replay, not a new payment. The owner manually funded the deposit. Guard is noncustodial and does not authenticate outcome hashes; provider linkage is not cryptographic cross-chain atomicity.
Download MP4Download captions · Previous cut: dramatization, testnet and local scenes
Every door ends at something you can run or check.
Case file 01, then the ledger. Every line ends at a finalized transaction or a published log.
Agent intent · repo example
from Solana.USDC amount 25000000
to Near.USDC receiver attacker.near
under mandate x3-owner.near8 mandate checkspass
mandate_recipientFAIL
Ledger
Finalized on chain or publicly logged. Testnet unless marked.
One policy. The compiler checks it. Guard checks it again. The model does not get a vote.

Business use cases for X3 Force Field: make payment authority explicit, reviewable, and tied to evidence.
These are intended uses, not claims of customer adoption. The current proof shows Guard authorization with a separately funded wallet; Guard cannot stop an independent wallet keyholder from transferring directly.
The goal is an agent you can trust with useful work. AI, .x3, Guard, and blockchain each handle a different part of that job.
This matters because a useful decision, permission to spend, and proof of delivery are three separate questions. Connecting them can make delegation more accountable and mistakes easier to investigate.
A “perfect agent” is the ambition, not a security guarantee. Blockchain can permanently record a bad payment. Policy checks only cover their rules and enforcement path, and a recorded outcome still needs independent receipt verification.
Authority runs one way. The agent is third in line and cannot approve itself.
The program names Base, Solana, or NEAR. Guard checks the quote and mandate. A separate funding wallet makes the deposit; finalized receipts show delivery.
Base
Bridge to NEAR
Solana
Bridge to NEAR
NEAR
Already there
Guard
Quote terms or refusal
Three published milestones, including the official mainnet settlement. The remaining five show exactly what evidence is still needed.
Proofs posted: 3 / 8
A milestone counts only when its proof is public: a finalized transaction, a merged change with tests, or a published report. Each of the same eight milestones has equal weight. 37.5% exact coverage, rounded to 38% for display.
Reviewed November 13, 2026 against X3Lang f2a01a2. This measures published proof, not a security rating or a hackathon score.
1. Cross-chain testnet transfer authorized by Guard
Posted1 test USDC sent on Base Sepolia after Guard approved the exact .x3 program on NEAR testnet; 0.9974 test USDC delivered to x3lang.testnet. Testnet, through a trusted relayer: not atomic, not mainnet.
Evidence and limitsBase Sepolia transactionNEAR testnet delivery
2. Guard refuses a wrong recipient on testnet
Postedx3-guard on NEAR testnet refused an agent payment to attacker.near (mandate_recipient) and registered the same intent paid to the owner's account. Both transactions are final.
3. Scoped agent vault on testnet
PendingOne allowed payment, plus recorded refusals for over-cap, wrong recipient, 24-hour window and redirected refund.
Next: Publish the allowed payment and all four refusal cases from the public testnet runbook. Local Sandbox tests do not fill this milestone. Inspect the work
4. One mainnet 1Click swap through Guard
PostedThe signed quote, the Guard authorization, the deposit, and the delivery, each with a finalized transaction hash.
Mainnet evidence and limitsGuard acceptance25 USDC Solana deposit24.9952 USDC NEAR deliveryRecorded outcomeSource files matching the stored hashes
5. Hostile model refused on mainnet
PendingA red-team model's payments go through the same restricted key, and each refusal is on chain with an attack label.
Next: Publish labeled hostile-model attempts through the restricted mainnet key and their on-chain refusals. Current red-team evidence is local.
6. Guard checks the program hash
PendingAn approved mandate carries only the exact .x3 program the owner saw. Contract tests cover a mismatched hash.
Next: Land reviewed program-hash enforcement with mismatch tests. PR #202 is still open at this snapshot; storing a hash alone does not satisfy this gate. Inspect the work
7. Independent security review
PendingA published report on Guard and the vault, with every finding and its fix.
Next: Publish an independent review and the disposition of every finding. Internal checks and this evidence review do not count as an independent audit.
8. Tagged release
PendingA GitHub release with a checksum and build provenance, so nobody has to trust a branch tip.
Next: Publish a versioned release with checksums and build provenance. A passing branch build is not a release. Inspect the work
The .X3 community token is planned as a NEP-141 on NEAR mainnet. It is not deployed yet, and nothing here sells it. Its contract and deploy transaction appear here once they are final.
.X3
Symbol .X3 · Standard NEP-141 · Chain NEAR · Not deployed