One protocol above the chains

Build once.
Run on any blockchain.

Tokens, trading, and smart contracts against one API. Write your app once and it runs on every chain XChain supports.
No sidechains, no bridges, no per-chain code.

Live today on Bitcoin·Litecoin·Dogecoin·more chains coming
1API, every supported chain
37on-chain ACTION commands
13open-source components
0sidechains or bridges

One integration

Stop rebuilding your app for every chain

Supporting blockchains one at a time means a separate SDK, token standard, and test matrix per chain, plus bridge glue between them. XChain replaces the pile with one protocol.

Write once

One API, every chain underneath it

Your app targets XChain, not a chain. The same code that issues a token, places an order, or calls a contract on Bitcoin does it on Litecoin and Dogecoin, and on every chain added later, with no new code on your side.

The flywheel: adding a UTXO chain to XChain is a configuration change, not an engineering project. Every chain the protocol adds multiplies where your existing app runs.

Without XChain

One integration per chain: its API, its token standard, its quirks, and bridges to glue the results together. Every new chain is another build.

With XChain

One integration: your app talks to XChain, and XChain talks to the chains. A new chain under the protocol is a new chain your app already supports.

Start building → How the protocol works →

Two ways in

Where would you like to start?

Both doors lead to the same protocol. Pick the one that matches what you came here to do.

Or start from the beginning: how it works → Already hold crypto? Why XChain →

Tokens and trading

A whole token economy, built into the chain you already use

Issuing a token, selling it, and settling the trade are all part of the protocol itself, happening on the blockchain, from your own wallet, with no middleman holding your funds.

Create a token

Name it, set the supply, and issue it in minutes. Lock the supply so no one, not even you, can ever make more.

An order book in the protocol

Place buy and sell orders; the matching engine pairs bids and asks within each block. Settlement is on-chain, with no custodian and no off-chain matching.

Dispensers & fiat pricing

Sell on autopilot at a price set in another token, a native coin, or a fixed dollar amount that auto-converts at trigger time, with no stablecoin to mint or trust.

Sell the whole project

Trade not just balances but ownership: transfer the issuer rights of a token, dispenser, or order in one atomic action, even across chains.

Pay everyone at once

Airdrop to a long list, or split a payout across every holder proportionally, from a single action.

One-of-a-kind items

A token with a supply of one and no decimal places is a consensus-guaranteed original, with the artwork itself published on-chain. Editions and collections work the same way, and they trade on the same order book.

Content only holders can open

Publish a file on-chain encrypted, so only whoever holds the token can decrypt it. Sell the token and access travels with it, with no download link to revoke.

Swap across chains, natively

Trade a token on Bitcoin for one on Dogecoin without a bridge and without a wrapped coin: validators attest that the far side really settled before either leg completes.

Rules that hold

A token can carry its own rules

Bind a small contract to a token and the network runs it before that token can be sent, traded, burned, or minted. The rule can allow the action, refuse it outright, or attach a split of the sale proceeds, and every validator reaches the same answer.

Why it holds: a creator royalty is part of the trade rather than a courtesy the venue extends, because the protocol is the only place a sale settles. It splits on-chain token proceeds, and the issuer can unbind the rule after a cooldown fixed at the moment it was bound.

Someone sends, trades, or burns the token
The token's rule runs first and decides
Allowed: the action settles, split and all

Denied and nothing changes: the action is rejected, and everything the rule touched is rolled back.

What people build with this → How trading works → Token rules & royalties →

Programmable

Smart contracts, without adopting a new chain

XChain runs a real sandboxed JavaScript VM on top of the base chain: deterministic, reorg-safe, and built so a contract bug cannot become a protocol failure.

Orchestration, not mutation

Contracts can't touch the ledger directly

On most platforms the contract is the protocol: it reads and writes state directly, so a single bug can mint tokens or drain balances. XChain separates the two. A contract can't credit a balance or move a token; it emits the platform's own validated ACTIONs (SEND, MINT, ORDER, DISPENSER…), and the same battle-tested handlers that check every user transaction also bound every contract.

The payoff: a contract bug can fail; it can't break the protocol, drain the ledger, or mint from thin air. The audit surface stays small, and an improvement to any handler benefits every contract automatically.

EVM-style model

The contract writes state directly, so a bug can mint, corrupt, or drain.

The XChain model

The contract emits validated ACTIONs, so the protocol's rules always hold.

Contracts in a language you know

Write them in JavaScript, deploy them onto Bitcoin, Litecoin or Dogecoin, and call them like any other action. Nothing new to run, and no new language to learn first.

Ask an AI, or the web

A contract can pose a question to an AI model or an HTTPS endpoint. Validators answer independently and must agree before the result is written on-chain, so the answer is checkable rather than trusted. It arrives through a callback, not instantly.

Put stake behind a promise

Any contract can declare itself stakeable. Lock tokens against it on any supported chain, with the cooldown and the slashing rule fixed at deploy time and never changeable afterwards.

Call across chains

A contract on one chain can call a contract on another and get the outcome back, relayed and verified by the validators. Across the chains XChain runs on, with no bridge in the middle.

Fourteen example contracts → The developer hub → Smart contracts, in plain English → AI & the web, on-chain →

The 37 ACTIONs

Every operation on XChain, from issuing a token to running a contract, is one of 37 versioned commands embedded in a transaction.

Betting 1

Outside-world data 2

Governance 1

Data & communication 3

Configuration 4

Validators & consensus 4

Verifiable, and in nobody's custody

You do not have to take our word for any of it

A staked validator network prices fees, attests cross-chain trades, and governs the protocol, and at no point does it hold your funds. Its price attestations, cross-chain attestations and state anchors are written back to the chain, where anyone can check them; governance itself runs off-chain in the hub.

No custody, anywhere

Tokens move between addresses under rules the protocol enforces. Validators coordinate; they never take possession, so there is no balance for anyone to freeze or lose.

Bitcoin-grade security

XChain never modifies the chain underneath it. Your tokens inherit exactly the proof-of-work security of the network they live on.

Independently verifiable

Signed state checkpoints are written back to the chain, so anyone can confirm the platform's state, or rebuild it from block data alone, without trusting any operator.

No bridges, ever

Cross-chain trades settle natively on both chains. There is no bridge contract holding pooled funds, because there is no bridge.

The validator network → State checkpoints → And what it's not →

Quality

Tested like it holds money

XChain handles real value, so it is verified like it. 39,000+ automated tests across 12 disciplines (unit, integration, end-to-end, fuzz, security, chaos, determinism and more) guard all 13 components that touch token data.

See the testing strategy → Full reference (docs)

Free and open source

XChain is released under the GNU Affero General Public License v3.0: free to use, study, run, and build on. A commercial license is available for organizations that need to keep modifications private.