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.
Inspect the Proof
Compare two completed mainnet payments: the new owner-approved, agent-executed Solana vault pilot and the earlier owner-funded NEAR Guard demonstration. Each proof states what it establishes and what remains unproven.
Official NEAR Intents SHIELD, separate from X3 Force Field. An operational response means no active incidents were reported at observation time; it does not certify chain health or authorize a payment.
Not checked. Provider condition is unknown.
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.
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
X3Lang f2a01a2: Rust VM, provenance, Python/browser, compile-time refusals, signed-quote baselines, NEAR Guard and compromised-model refusal checks all passed. This result covers this revision only.
Evidence reviewed November 13, 2026. The source revision is pinned so the README, contract and evidence can be inspected together. Local tests prove their tested behavior; they do not fill public-chain or independent-audit milestones.
Guard verified the official 1Click dry-quote signature, then refused it. Archived checks include a recipient mismatch and the dry-quote failures. Contract x3lang-guard-20261106.testnet.
This earlier testnet run accepted an official 1Click live quote and stopped before a deposit. Its acceptance is separate from the completed mainnet invoice_06 trade above.
Deployment transaction for x3lang-guard-20261106.testnet. Wasm SHA-256 prefix recorded in the README as ac44fa53…f8ab.
agent_register_intent failed mandate_recipient. Other guards on that intent passed. The explorer receipt can show only a generic Wasm trap; the reason is in the archived view.
Same mandate, recipient x3lang.testnet, intent_registered. The mandate was later observed revoked. Create and revoke themselves are state observations, not separately anchored transactions in that note.
Write-up: near-guard-testnet-live-2026-11-06.md
1.000000 test USDC left Base Sepolia. 0.997400 arrived on NEAR testnet for x3lang.testnet, above min_receive 980000. Program SHA-256 1398f64e7e208d3796883aa59cb169187c1042ac1af3781bd6efc014755df860 was bound on x3guardlaunch2026.testnet in block 276,595,201 before the source transfer. The README says this used a trusted testnet relay. It does not prove atomic settlement, and it is not mainnet.
Finality was checked against two public RPCs in the repo's verifier. Label this historical testnet source, not a mainnet USDC payment.
0x46c21dc305a9271c4e74c6d0734fb50f847a1e53d3cad87976133d66fd6728d9
Historical testnet payout to x3lang.testnet. These test assets and receipts are distinct from the mainnet USDC settlement above.
NEAR mainnet Guard deployment and setup are documented for x3lang.near. The archived records cover deployment, storage, scoped agent access, intent registration and owner approval. The later invoice_06 bundle above supplies the acceptance, deposit and payout records; the setup note remains a historical record. Inspect the mainnet setup evidence.
Live 1Click Explorer history is not connected on this site yet. This panel shows the published mainnet and historical testnet evidence instead. Open each link to inspect its archived evidence or public explorer receipt.
The MAINNET row links to the invoice_06 archive; the other rows are historical testnet records. Live Explorer history, once connected, remains provider-reported and does not independently prove chain finality, Guard authorization or cross-chain causality.