Repository
dotx3 hosts the website and browser tools. X3Lang hosts the compiler, contracts and evidence. The separate X3 chain runtime is outside the NEAR judge path; use the source and network named by each demonstration.
Current evidence snapshot
Reviewed November 13, 2026: mainnet invoice_06 records a restricted NEAR agent authorization, 25 USDC deposited on Solana and 24.9952 USDC delivered to x3lang.near. The committed RPC observation, checksum and exact-revision CI are linked below. The original .x3 files match the stored hashes and the agent recorded a Settled outcome. Guarded custody and authenticated outcome records remain unfinished work.
Proof card (start here)Mainnet archiveRPC observationsSHA256SUMSReviewed revision CI
X3Lang source: f2a01a2ae144c69e115fd807a642bddfd8668f9f
Install from source
Python intent tools
git clone https://github.com/Cyptopimpinainteazy/x3lang.git
cd x3lang
git checkout f2a01a2ae144c69e115fd807a642bddfd8668f9f
python3 -m venv .venv && . .venv/bin/activate
pip install -r x3-lang/requirements.txt pytest
python3 x3-lang/cli.py x3-lang/examples/arb_solana_eth.x3Rust surface, workspace only
cargo test --manifest-path x3-lang/Cargo.toml
cargo run --manifest-path x3-lang/Cargo.toml -p x3-tools --bin x3c -- parse x3-lang/examples/trading_core_v1.x3Releases page: github.com/Cyptopimpinainteazy/x3lang/releases. This guide installs from source. Inspect release artifacts and their provenance separately before choosing a version.
Recheck the mainnet record
Read-only public RPC observer, from the pinned X3Lang checkout
python3 scripts/hackathon/observe_mainnet_invoice06.py --out /tmp/x3-invoice06-observation.jsonThis observer uses public RPC, signs nothing and sends no funds. The archived run reported 18 checks passed, zero failed and one fact unreadable on chain. Fresh balances, key allowances and final blocks may differ. The 1Click status record associates the chains; the observer does not prove cryptographic cross-chain causality.
Choose the NEAR integration level
1Click handles the higher-level swap workflow. The separate Intents SDK exposes lower-level intent execution and withdrawals. Official NEAR Intents has no testnet version; our historical Tidepool testnet delivery is a separate trusted-relay experiment. X3 Force Field is also separate from official NEAR SHIELD.
An explorer helps inspect records; an API key enables provider access. Neither establishes a funded swap or destination settlement. Keep distribution-channel credentials on the server.
1Click integration
These server-side examples cover tokens, a dry quote and a status query. Docs: NEAR Intents 1Click quickstart. The adapter verifies the quote signature before it reads terms. A live quote requests a deposit address; a separate wallet funding step can spend real funds. The adapter’s official 1Click route is distinct from the historical Tidepool community testnet.
Use a 1Click partner credential in the server-only NEAR_INTENTS_API_KEY environment variable and send it through X-API-Key. Authorization: Bearer is also accepted for that partner credential on ordinary 1Click calls. Aurora, Explorer, user-session and SHIELD credentials have separate roles; do not assume they are interchangeable. Never put a partner key in browser code or a public environment variable. Official authentication guide.
Tokens (server-side)
curl https://1click.chaindefuser.com/v0/tokens \
-H "X-API-Key: $NEAR_INTENTS_API_KEY"Dry quote template (server-side; replace placeholders)
curl -X POST https://1click.chaindefuser.com/v0/quote \
-H "Content-Type: application/json" \
-H "X-API-Key: $NEAR_INTENTS_API_KEY" \
-d '{
"dry": true,
"swapType": "EXACT_INPUT",
"slippageTolerance": 100,
"originAsset": "nep141:wrap.near",
"depositType": "ORIGIN_CHAIN",
"destinationAsset": "nep141:arb-0x912ce59144191c1204e64559fe8253a0e49e6548.omft.near",
"amount": "1000000000000000000000000",
"recipient": "0xYourAddress",
"recipientType": "DESTINATION_CHAIN",
"refundTo": "your.near",
"refundType": "ORIGIN_CHAIN",
"deadline": "REPLACE_WITH_FUTURE_ISO_8601_UTC_TIMESTAMP"
}'Replace the recipient, refund address and deadline before using the template. The deadline must be a future ISO 8601 UTC timestamp that allows time for origin-chain confirmation. Confirm asset identifiers against the current token list. Keep dry set to true for a preview; it does not return a deposit address.
Status (server-side JavaScript; existing quote only)
// quote is the quote field from an existing saved response.
const apiKey = process.env.NEAR_INTENTS_API_KEY;
if (!apiKey) throw new Error("Missing server-side 1Click partner key");
if (!quote.depositAddress) throw new Error("This quote has no deposit address");
const query = new URLSearchParams({ depositAddress: quote.depositAddress });
if (quote.depositMemo != null) query.set("depositMemo", quote.depositMemo);
const response = await fetch(
"https://1click.chaindefuser.com/v0/status?" + query.toString(),
{ headers: { "X-API-Key": apiKey }, redirect: "error" },
);
if (!response.ok) throw new Error("1Click status unavailable: " + response.status);
const status = await response.json();URLSearchParams encodes the address and the exact quote.depositMemo when supplied. A status response is provider-reported execution state; it does not independently prove a destination transfer or finality.
For supported one-time swaps, a live quote supplies quote.depositAddress. Reusable addresses use a separate ANY_INPUT workflow and quote.chainDepositAddresses, with both a partner API key and the owning user's session. The current X3Lang and dotx3 clients do not implement reusable-address creation. Official reusable-address guide.
Repo commands, not this website: python3 x3-lang/near_intents.py quote FILE.x3 for a dry quote. --live asks for a deposit address. The tool does not sign the deposit.
Available resources and release review
dotx3.net includes language guides, browser tools, track pages and published evidence. These resources are available in the current site:
- Security track — policy checks and Guard limits
- Who gets paid? video — an explainer with local, testnet and dramatized scenes
- Labs — compiler, signed-quote demo, judge cases and attack lab
- NEAR hub — Security, Agents and DeFi perspectives
Review by revision
Read the judge guide at the reviewed source revision and the repo's private vulnerability reporting steps. The explainer video is not settlement evidence or a confirmed hackathon submission. Check release artifacts, checksums and submission links against the revision you intend to use.
Community, unverified as to whether each post is current: @x3starchain · t.me/x3starchain · nearhackathon.com · docs.near.org
A static browser demo is published separately at x3-guard.pages.dev. Public demos and videos do not establish the status of a hackathon submission.