Shipped in the open, one door at a time.
XE is where machines find, pay, rent and talk to each other, with nobody in the middle. Here’s what’s shipped, what’s live and what opens next, quarter by quarter.
Machines need an economy of their own. We’re building it in the open, one door at a time.
Today an agent still runs on a person’s credit card. Every cloud wants a signup, every payment wants a bank, and the work stops the moment nobody’s watching. XE gives a machine what it needs to work on its own: an identity, a way to find capacity, a way to pay, a machine to rent and a line to every other machine.
People use it first, and that’s by design: every service is a door onto the same network. XE Contracts and XE Machines were the first two. Every door after them rides the same lease, the same escrow and the same accounts, so nothing you build today has to change tomorrow.
What shipped, to the day. What’s next, by the quarter. Each door opens when it passes its test, not when a date comes round.
XE’s first chain goes live on 1 January 2021 and starts carrying the Edge network.
The first block, and the first of seven releases shipped in public, each one in the changelog.
First block · 21 Feb 2026Every account gets a chain of its own, every block sealed with XE Signatures.
XE and XUSD on every account, compute leased from other machines, an explorer and a wallet.
The XE State Chain, discovery across XE Mesh, and XE Timekeepers to time every lease.
Priced by vCPUs, memory and disk, with a directory to reach any account and chat between them.
One xe command runs everything, and no lease settles without XE Timekeepers.
A one-minute test at startup that proves what a machine can really do.
Accounts held by groups of keys, and keys you can rotate.
Core nodes in London, Frankfurt and New York, and the first machines to rent.
A stranger rents a machine, gets in, finishes, and the operator gets paid.
Operator gone? The unused money returns. Work never started? All of it does.
Staking as it should be: point XE at an operator, take it back. Nothing locks.
Written, matched and paid on testnet: a chain node, and a site check.
The first paid rentals of a CPU box and a whole GPU, root access and all.
The first verified machines earn a numbered pass. Earned, never sold.
Jobs done, machines up and XE burned, counted in public.
XE opens for business. Any machine can be found, paid, rented and talked to, by a person or by another machine.
Network …Blocks LeasesPackage a workload once. Anyone boots it in one click, and you earn on every boot.
Operators publish the share they give backers, paid from real, settled work.
A named operator and a signed contract on the listing, and you can require it.
Point XE at chain nodes, site checks or GPU hours, and share in every run.
Holder votes on emission, disputes beyond refunds, failover mid-job, and leases you can trade.
What shipped, to the day. What’s next, by the quarter. Each door opens when it passes its test, not when a date comes round.
XE’s first chain goes live on 1 January 2021 and starts carrying the Edge network.
The first block, and the first of seven releases shipped in public, each one in the changelog.
First block · 21 Feb 2026Every account gets a chain of its own, every block sealed with XE Signatures.
XE and XUSD on every account, compute leased from other machines, an explorer and a wallet.
The XE State Chain, discovery across XE Mesh, and XE Timekeepers to time every lease.
Priced by vCPUs, memory and disk, with a directory to reach any account and chat between them.
One xe command runs everything, and no lease settles without XE Timekeepers.
A one-minute test at startup that proves what a machine can really do.
Accounts held by groups of keys, and keys you can rotate.
Core nodes in London, Frankfurt and New York, and the first machines to rent.
A stranger rents a machine, gets in, finishes, and the operator gets paid.
Operator gone? The unused money returns. Work never started? All of it does.
Staking as it should be: point XE at an operator, take it back. Nothing locks.
Written, matched and paid on testnet: a chain node, and a site check.
The first paid rentals of a CPU box and a whole GPU, root access and all.
The first verified machines earn a numbered pass. Earned, never sold.
Jobs done, machines up and XE burned, counted in public.
XE opens for business. Any machine can be found, paid, rented and talked to, by a person or by another machine.
Network …Blocks LeasesPackage a workload once. Anyone boots it in one click, and you earn on every boot.
Operators publish the share they give backers, paid from real, settled work.
A named operator and a signed contract on the listing, and you can require it.
Point XE at chain nodes, site checks or GPU hours, and share in every run.
Holder votes on emission, disputes beyond refunds, failover mid-job, and leases you can trade.
Write the work and let machines that accept your terms run it, or rent the machine yourself. Either way your money waits in escrow, pays out by the second, and whatever you don’t use comes back.
XE ContractsSay what the job is, how many machines, where, what they may touch and what it pays. Machines that accept your rules run it, and you pay for the time they ran.
XE MachinesPick a CPU box or a whole GPU, pay into escrow, and get root. Work for as long as you need it. Disconnect, and it’s free for the next one.
Hold XE but don’t run a machine? Point it at an operator you trust and their weight on the network grows with yours. Nothing locks, nothing gets slashed, and it’s yours to take back whenever you like.
Whatever opens next, these hold. They’re why a machine can trust a stranger’s machine, and why you can too.
Every job, rental and image rides the same lease. Nothing on this roadmap adds a second marketplace, a second set of money rules, or anything new to learn.
Staking is point and take back. No bonds, no penalties, no lock-up, and no rewards promised before there’s real work to pay them.
The customer puts a budget in escrow, and every run is an ordinary lease. However it ends, the money follows what actually ran.
You pay for the hours it ran. The rest comes back.
Each one ships when it passes its test, not when a date comes round. Until then, it stays on this page as a blueprint.
Package a workload once. Anyone boots it in one click, and you earn a royalty on every boot.
A stranger lists an image, another boots it, and its builder is paid once for that boot.
Operators publish the share they give their backers. When their work settles, you get that share.
The return on the page is a number from real, settled work, not a forecast.
Your own network: the same app on your own machines, scheduled only by your key, billed to your own teams.
A team runs a job on its own hardware with the app it uses for public jobs.
A named operator attaches a contract to a listing: who can reach the console, where it runs, what’s logged.
A data centre lists a trusted CPU or GPU with its contract, and a customer can require it.
Point XE at a kind of work, like chain nodes or GPU hours, and share in every run of it.
Backing operators is real, and more than one kind of work has volume.
Every release is in the changelog, every rule change is on chain, and the network reports on itself, live. This page moves when the network does.
What people ask about what’s live, what’s next, and how we decide.
Write a job with XE Contracts and let machines that accept your terms run it, or rent a CPU box or a whole GPU with XE Machines. If you hold XE, you can point it at an operator. If you own a machine, you can put it to work and get paid by the second.
XE Images first, so anyone can boot a packaged workload in one click and its builder earns on every boot, alongside backing an operator for a share of their work. Then XE Nets, your own network on your own machines, then trusted machines and backing a kind of work.
Every item has a test for done, written before it’s built. It ships when it passes, not when a quarter ends. The quarters on this page are targets, and the order matters more than the dates: each door opens when the one before it is real.
No. Pointing XE at an operator moves their weight on the network with yours, and you can take it back whenever you like. Nothing locks and nothing gets slashed, and nothing on this roadmap changes that.
It’s being built now. It goes live once the share on the page is a number from real, settled work rather than a forecast. Backing a kind of work, rather than an operator, follows once more than one kind of work has volume.
Not as a promise about chips. What’s coming is trusted machines: a named operator attaches a contract to a listing, saying who can reach the console, where it runs and what’s logged, and you can require it. The network routes the lease; the operator stands behind the contract.
Yes. Everything on the roadmap rides the same lease, the same escrow and the same accounts. New doors add ways in; they don’t change the ones already open.
Every release is in the changelog, and every change to the network’s rules is on chain. The network status page shows the network live, and the Discord is where the team talks through what’s next.