.X3

dotx3.net · NEAR Hackathon

.x3

Understand it, try it, inspect the proof, and get the code. An agent can propose a payment. The owner's .x3 policy decides whether Guard authorizes the deposit address.

Try the DemoLearn .x3View the CodeInspect the ProofBreak a Mandate

What .x3 does

One policy. The compiler checks it. Guard checks it again. The model does not get a vote.

.x3 protocol mark

The owner writes the rule

A mandate names the agent, the asset, the caps, the recipient, slippage, fees, and when the owner must approve.

The agent writes a program

The payment is another .x3 file. If it pays the wrong account, drops the nonce, or breaks a cap, it does not compile or Guard refuses it.

Settlement is labeled

The published trade is testnet: 1 test USDC from Base Sepolia to NEAR. Official 1Click quotes were checked and stopped before a deposit.

How a decision moves

The program names Base, Solana, or NEAR. Guard allows the deposit or it refuses. Base and Solana bridge. NEAR does not.

  1. 01

    Base

    Bridge to NEAR

  2. 02

    Solana

    Bridge to NEAR

  3. 03

    NEAR

    Already there

  4. 04

    Guard

    Quote terms or refusal

Testnet trade demo

Protocol mark in motion. The trade it stands for is on Inspect the Proof: testnet, not mainnet.

Proof meter

Six milestones between today's testnet proof and a system people can trust with money. Each fills only when its proof is posted.

Proofs posted: 0 / 6

A milestone counts only when its proof is public: a finalized transaction, a merged change with tests, or a published report. Nothing here is estimated.

  1. 1. Scoped agent vault on testnet

    Pending

    One allowed payment, plus recorded refusals for over-cap, wrong recipient, 24-hour window and redirected refund.

  2. 2. One mainnet 1Click swap through Guard

    Pending

    The signed quote, the Guard authorization, the deposit, and the delivery, each with a finalized transaction hash.

  3. 3. Hostile model refused on mainnet

    Pending

    A red-team model's payments go through the same restricted key, and each refusal is on chain with an attack label.

  4. 4. Guard checks the program hash

    Pending

    An approved mandate carries only the exact .x3 program the owner saw. Contract tests cover a mismatched hash.

  5. 5. Independent security review

    Pending

    A published report on Guard and the vault, with every finding and its fix.

  6. 6. Tagged release

    Pending

    A GitHub release with a checksum and build provenance, so nobody has to trust a branch tip.

Back .x3Proof already on testnetTry to break a mandate

One demonstration, three tracks

AI Security & Defense

Recipient and asset allowlists, caps, slippage, fees, expiry, one-use nonces. Compiler off-chain. x3-guard on NEAR testnet.

Agent Economy

Permitted, approval-required, and denied payments. Testnet shows one allowed intent and one refused intent.

Unstoppable DeFi

One .x3 program, hash bound before the source transfer, then finalized on Base Sepolia and NEAR testnet through a trusted relay.
Try the DemoInspect the Proof

.x3 on NEAR

A NEP-141 community token. Fastest launch is a factory or Smithii Token Creator — one signature, full supply to treasury, then distribute against verified mainnet trades.

.X3

Symbol .X3 · Standard NEP-141 · Chain NEAR