GitHub Actions
Workflows are public, including the judge gate, the won't-compile check, and the two-chain evidence replay. Open a run and read that run. This page does not paste a green check from memory.
Provider incident feed
Official NEAR Intents SHIELD, separate from X3 Shield. 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.
1Click Explorer history
This panel reads live NEAR Intents Explorer history when configured. Records are provider-reported · network and chain finality: unverified · independently verified: no. They do not establish X3 Guard authorization or cross-chain atomicity.
Load the configured project history. No wallet connection or transaction signing.
CI and local gates
Recorded local result
README: at commit c5a4e39, pytest printed 594 passed, 1 skipped, and the Guard crate printed 62 passed. Re-run before you cite either number against a newer commit.
Quote verification
NEAR testnet · official 1Click quote · not a deposit
Dry quote refused
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.
Live quote accepted, then stopped
An official 1Click live quote that matched the policy was accepted. The README says this stopped before any deposit. A valid signature authenticates provider terms, not a completed swap.
Guard deploy for that quote contract
Deployment transaction for x3lang-guard-20261106.testnet. Wasm SHA-256 prefix recorded in the README as ac44fa53…f8ab.
Refusal and acceptance
NEAR testnet · x3lang.testnet · no funds in the contract
Refused: attacker.near
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.
Accepted: permitted recipient
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
Settlement
HistoricalBase Sepolia to NEAR testnetTidepool relay · not official 1Click settlement
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.
Source · Base Sepolia
Finality was checked against two public RPCs in the repo's verifier. Label this historical testnet source, not a mainnet USDC payment.
0x46c21dc305a9271c4e74c6d0734fb50f847a1e53d3cad87976133d66fd6728d9
Destination · NEAR testnet
Payout to x3lang.testnet. Independently verified mainnet settlement: none published.
Not claimed
- No mainnet deployment and no funded official 1Click settlement.
- No public audited vault. Guard does not custody tokens. An unrestricted origin key can bypass it.
- No cryptographic atomic cross-chain causality for the Tidepool trade.
- No downloadable release artifact with a checksum. The commit is the artifact until a release exists.
- Report vulnerabilities in private. Do not file exploits, keys, or seeds in a public issue. SECURITY.md