Independent nodes in every country.
Nodes in every country, not three clouds.
Chains that want thousands of independent nodes in more countries, without paying for them one by one.
Decentralisation you can buy by the second. Publish a contract for validators or RPC, set a budget, and machine owners around the world run the nodes, each paid per second from escrow while it stays in sync.
Decentralised on paper, clustered in practice.
Most nodes run in the same few clouds, in the same few regions.
Decentralised shouldn’t mean three clouds.
It should mean thousands of owners.
Buy decentralisation by the second.
- Built for · 01Protocol teamsSpread validators across countries and across owners.
- Built for · 02RPC and data providersServe reads from hundreds more places, close to users.
- Built for · 03Node runnersLaunch a node in one click, paid per second.
Three ways to spread a network.
Each one is built from the same products and primitives. Pick one to see what it may reach, how it’s paid and what it’s made of.
- Reaches
- Public IPA validator talks to other validators, so it needs a public IP. Only owners who allow it ever see the job.
- Paid
- Per second, from escrow
- Built with
- IdentityPaymentXE Contracts
Three clouds, or thousands of owners.
The same number of nodes can sit in three companies’ data centres, or on machines owned by different people in the countries you choose.
- Most nodes share a handful of companies and regions.
- One provider’s outage takes a large share of the network with it.
- Every new operator is another account and another invoice.
- Each node on a different owner’s machine, in a country you chose.
- An outage takes out one machine, not a region.
- One contract pays them all, per node, per second.
A network adds validators in thirty countries.
One contract, a hundred and twenty owners. Each step lights the part of the network it runs on.
A validator set, in one file.
Name the image, the hardware and the countries. Owners there opt in, each one an independent operator.
1contract eth_validators {2 // independent validators, spread across countries3 image = "xe/eth-validator:1.9"4 cpu = 85 memory = "32 GB"6 storage = "2 TB"78 network = public // validators talk to peers9 where = countries("DE", "BR", "KE", "JP", …)10 machines = 1201112 pays = up_to(0.0005 XE/s)13 budget = 5000 XE/day14}
xe · node
Rules you write. The network enforces them.
A contract is the whole agreement with every operator: where the node runs, what it may reach and how it’s paid. Nobody negotiates node by node.
- Where
- Name the countriesOnly machines in the countries you list ever see the job, and their owners opt in.
- Who
- A different owner per machineEvery machine belongs to someone else, each an account with its own record. That’s the independence you’re paying for.
- Access
- Public only where it has to beValidators declare a public IP because they talk to peers. RPC stays behind the XE gateway, on XE addresses.
- Pay
- Per node, per secondFrom escrow, for every second each node stays in sync. Monthly invoices don’t come into it.
- Churn
- A node that drops stops being paidThe moment it stops working, and the contract stays open for another machine to take its place.
Independent machines, at network scale.
Edge Network runs on XE across hundreds of locations, and each machine belongs to someone different. That spread, owner by owner and country by country, is exactly what a validator set is looking for.