TESTNET

The XE network, live

Use it. Then try to break it.

XE’s public testnet runs on core nodes in London, Frankfurt and New York, and this page reads it as you look. Some of it works today and some doesn’t yet, and the page says which.

Asking… core nodes up

THE TESTNET

XE’s public testnet is live, and open to anyone. Run a node, move XE, call the API, and try to break it before mainnet.

It runs the same xe binary any node runs. Three core nodes, in London, Frankfurt and New York, are its front doors: a new node meets its first peers there, then finds the rest of XE Mesh on its own.

XE is pre-1.0, so some of what this site describes is built and running, and some of it isn’t yet. This page reads the network as you look, and marks every figure with where it comes from: live from the core nodes, or as the testnet publishes it.

Finality
Testnet
~3s
Fees
Testnet
0
Core nodes up
Live
—
Providers advertising
Live
—
XE supply
Testnet
42M
accounts—blocks—last block—network—build—asking the testnet…
STATUS

What works today, and what doesn’t yet.

XE is pre-1.0 and this is a testnet, so some of what this site describes is built and running, and some of it isn’t. Here’s the split, as it actually stands.

9 of 15 working today6 on the roadmap

Working today09
  • Build the binary and run a node that joins the testnet
  • Join the peer-to-peer XE network
  • Wallets, addresses and keys
  • Get 1,000 XE per account per day from the faucet
  • Send, receive and check balances in XE
  • Burn XE
  • The explorer and wallet UI, embedded in the node
  • REST API and live event streams
  • Signed peer-to-peer chat
On the roadmap06
  • XUSD issuance, and its use for compute leasing
  • Compute leasing, including escrow, collateral, XE Timekeepers timing and settlement
  • SSH over XE into your leased VM
  • GPU compute
  • End-to-end encrypted messaging
  • Dispute arbitration
CORE NODES

Three ways
onto the network.

A new node dials one of these to meet its first peers, then finds the rest of XE Mesh on its own. They also serve as XE Timekeepers, witnessing when leases start and stop.

Londonldn.core.test.networkStatus…Build—Network—Peers—Round trip—
Frankfurtffm.core.test.networkStatus…Build—Network—Peers—Round trip—
New Yorknyc.core.test.networkStatus…Build—Network—Peers—Round trip—
Round trips from xe.network’s server to each nodechecking…
CAPACITY

What’s on offer
right now.

Every machine advertising for leases on the testnet, added up, one block per vCPU. It’s small because it’s early: put yours on it.

vCPUs on offer
—
Across every provider
Memory on offer
—
Added up
Disk on offer
—
Added up
Providers advertising
—
Machines offering themselves for leases
Leases running
—
Right now
Leases, all time
—
As the providers report them
Offer a machine
$ xe node -provide -vcpus 4 -memory 4096 -disk 40 -dial ...
QUICK START

Type into
the testnet’s CLI.

Build the binary, make two wallets, move XE between them. The terminal is a simulation of the real CLI, so type in it. Against the live network the faucet, sends and balances work; leasing isn’t open yet, but the shell still shows you what it does.

Then run it for real
From source
$ git clone https://github.com/xeprotocol/xe
$ cd xe && make build
$ ./xe wallet create
xe-testnet · simulated
Try
CAPABILITIES

What the network does,
and what’s open on it yet.

Nine things XE is built to do, each marked with where it stands on this testnet: live, live in part, built, not open yet or still to come.

  • [LAT]Live
    XE LatticeEvery account keeps its own chain, so payments never queue behind anyone else’s. Parallel, non-blocking and final in seconds. No miners, no waiting line.
  • [P2P]Live
    XE MeshThe encrypted peer-to-peer network nodes use to find and talk to each other, with no central servers. Nodes find each other automatically and sync directly.
  • [CON]Live
    XE ConsensusAgreement only when it’s needed. Honest blocks are final without a vote. Representatives, weighted by delegated XUSD, vote only when an account signs two blocks for one place, and 67% of the weight settles it.
  • [XE]XE live · XUSD later
    XE today, XUSD laterXE is the native asset: it’s what providers earn when a lease settles. XUSD, the stablecoin that will price compute, is specified but not issued on this testnet yet. No transaction fees.
  • [MSG]Live · E2E coming
    Signed messagingSend signed messages between any two accounts, in real time, encrypted in transit across XE Mesh. End-to-end encryption of the message itself is coming.
  • [DAO]Built
    XE State ChainThe network’s rulebook, as a chain of its own. Every change is signed jointly by the XE Keyset, so parameters evolve with no hard forks.
  • [VM]Not open yet
    Compute leasingLease a real VM from a provider, SSH in and settle on-chain. Escrow, collateral, witnessed timing and cancellation are all built, but leases are priced in XUSD, which isn’t issued on this testnet yet.
  • [PRV]Not open yet
    Earn by providingRun a provider node, offer your spare compute, and earn XE emissions every time a lease settles. Until leasing opens, this side of the market is wide open.
  • [UP]Upcoming
    Provable uptimeIn design: XE Uptime Proofs will show that a machine really was online and serving, small enough to keep on the chain. Not implemented yet.
HELP US BREAK IT

We want this testnet hammered.

Push it until something gives, and tell us what did. Top bug hunters and heavy users will be recognised on mainnet.

01Make transactions, run a node, and try to make the ledger disagree with itself
02Try to spam it, grief it, or find consensus bugs
03Feed a node malformed blocks and see what falls over
04Report anything weird: open an issue on GitHub

Critical or severe? Email security@xe.network first, not a public issue.

Bug bounty · phase 1 of 7 openPaid at mainnet launch
Up to 10,000 XEper finding, paid in native XE at mainnet launch. The same five tiers apply in every phase.

Catastrophic protocol breaks: unauthorised mint, double spend, key recovery, ledger compromise.

Programme phases
  1. 01 transactions & running a nodeopen now
  2. 02 p2p networking & syncupcoming
  3. 03 consensus & finalityupcoming
  4. 04 api, web ui & user surfacesupcoming
  5. 05 leases, escrow & computeupcoming
  6. 06 tokenomics & emissionupcoming
  7. 07 gpu computeupcoming

Amounts are ceilings, set by severity at the XE core team’s discretion. Rewards pay in native XE at mainnet launch and are contingent on it; the bounty pool is still being finalised, and XE carries no guaranteed monetary value. Findings outside the active phase aren’t eligible yet, except critical and severe ones, which are eligible in any area.

RELEASES

Seven releases in two months.

From the first XE Lattice build to multisig wallets, and at the head, the build the network runs right now.

The full changelog
  1. Running now… on …asking the core nodes…
  2. v0.6.013 Apr 2026Multisig wallets and the testnet token model
    • Multisig accounts, with key groups you can rotate
    • A one-time genesis mint of XE; XE can no longer be claimed
    • Voting weight now follows XUSD balances
  3. v0.4.22 Apr 2026Performance certificates
    • XE Benchmark: a one-minute test on startup that proves what a machine can do
    • Built so the test can’t be faked or handed to another machine
    • Results shared with every node and checked on every lease
  4. v0.4.11 Apr 2026One CLI, mandatory attestations
    • A single xe binary with 15 commands, node included
    • Leases can’t be accepted or settled without XE Timekeepers
    • A network ID sealed into every block, so blocks can’t be replayed across networks
  5. v0.3.113 Mar 2026Multi-resource leases and the account directory
    • Leases priced by vCPUs, memory and disk
    • An account directory, so any account can be reached by its peer
    • Account-to-account chat, routed through the directory
  6. v0.3.010–12 Mar 2026XE State Chain, VMs, messaging and XE Timekeepers
    • The XE State Chain, for governance
    • Peer discovery across XE Mesh
    • XE Timekeepers, for lease timing
  7. v0.2.024 Feb – 6 Mar 2026Two assets and compute leasing
    • XE and XUSD, tracked per account
    • Leasing compute on other machines
    • The explorer and the web wallet
  8. v0.1.021–23 Feb 2026The XE Lattice
    • A chain for every account
    • XE Signatures, for identity and signing
    • Every block encoded and fingerprinted the same way on every node
QUESTIONS

About the testnet.

Straight answers on what’s live, what isn’t, and how to take part.

What is the XE testnet?

The public test network for XE, the first Agent-Native Network. It runs the same xe binary any node runs, with core nodes in London, Frankfurt and New York, and anyone can join it, use it and try to break it before mainnet.

What can I do on the testnet today?

Build the binary and run a node that joins the testnet, make wallets and keys, claim XE from the faucet, send, receive, check balances and burn XE, use the explorer and wallet built into the node, call the REST API and its event streams, and send signed peer-to-peer chat.

What doesn’t work yet?

XUSD isn’t issued on the testnet yet, so compute leasing (with its escrow, collateral, attested timing and settlement) isn’t open, and neither is SSH into a leased VM. GPU compute, end-to-end encrypted messaging and dispute arbitration are on the roadmap too.

How do I get testnet XE?

From the faucet: 1,000 XE per account per day. With the CLI, run xe faucet and then xe receive to take it into your account. The web wallet built into the node can claim it too.

How fast is the testnet, and what does it cost to use?

Transactions on the testnet are final in about three seconds, and there are no transaction fees. The finality and fee figures on this page are the ones the testnet publishes; the node, provider and ledger figures are read from the network live.

Is there a bug bounty?

Yes. It runs in phases, one area of the system at a time, and Phase 1, transactions and running a node, is open now. Findings are worth up to 10,000 XE, paid in native XE at mainnet launch, at the team’s discretion. Report critical and severe findings privately to security@xe.network first, and everything else as an issue on GitHub.

How do I run a node?

Clone github.com/xeprotocol/xe, run make build, and start the binary with xe node, dialling one of the core nodes to find your first peers. From there it finds the rest of the network on its own. The node guide covers offering your machine to leases.

Where does the live data on this page come from?

From the core nodes themselves. The site asks each one for its status, build, network and peers, reads the providers and the account chains from the first node that answers, and asks again every 15 seconds while the page is open.

Page