RUN A NODE

Run an XE node

Install the app. Get paid by the second.

Join the network with hardware you already own. Choose which jobs you accept, and get paid in XE for every second of work. Nothing to buy first.

WHAT A NODE IS

An XE node is a machine you own, doing paid work for the network. Install the app, choose the jobs you’ll take, and you’re paid in XE for every second your machine works.

Customers and agents on XE need machines in the places they choose: to serve files near their users, run a model, check a site from another country, or rent a whole GPU for an afternoon. Your laptop, gaming PC, server or GPU rig can be one of them.

The node app puts it on the network. It checks your hardware, shows the jobs it qualifies for, and takes the ones your policy allows. There’s nothing to buy first and nothing to lock up, and you can stop whenever you like.

Machines already earning
5K+
Locations
988
To settle each payment
300ms
How you’re paid
Per second
YOUR MACHINE

Every machine has work it’s good at.

You don’t need a data centre. The network matches each job to the machines that can do it, from a laptop to a rack of GPUs.

What countsBeing online, and where it is
Good forUptime checksCDN edgeLight contracts
HOW IT WORKS

Three steps.
Then it runs itself.

You set the rules once. The node finds the jobs that fit, takes the ones you allow, and is paid as it works.

  1. 01Install the appOn any machine you own: a spare laptop, a gaming PC, a rack of servers. It checks your hardware and tells you what it can take on.
  2. 02Choose your jobsContracts, images, renting out the whole machine, or all three. Say what a job may reach on the internet. Anything that asks for more is declined.
  3. 03Get paid by the secondEvery accepted job pays into escrow before it starts, and releases to you for every second of work, in XE.
YOUR POLICY

Your machine.
Your rules.

A node only takes work its owner allows. Set it once in the app, or in a file on a server, and change it whenever you like.

node.policyYour rules
1# node.policy · takes effect on the next offer
2
3accept = [contracts, images, rental]
4network = [none, gateway, verified] # never direct
5
6cpu = 12 of 16
7memory = "48 GB"
8gpu = whole # the card, or nothing
9storage = "500 GB"
10
11hours = "22:00–08:00" # while you sleep
12min_pay = 0.002 XE/s
EARNINGS

The maths is simple.

There’s no mining lottery and no reward schedule. You’re paid for the seconds your machine works, at the rate each job offers.

Seconds of workEvery second your machine spends on a job
What the job paysPer second, shown on the offer before you accept
What you earnIn XE, released from escrow as you go, each payment final in 300ms
What moves the number
01HardwareMore cores, memory and storage, or a good GPU, qualify your machine for more jobs, and better-paid ones.
02UptimeA node that’s always there is offered more work than one that comes and goes.
03LocationCustomers pay for where a job runs. A machine in a place few others cover is worth more to them.
04PolicyThe more kinds of job you accept, the more offers reach you. Accept less, and you see less.
05RecordEvery finished job adds to your node’s record. Customers and agents choose machines with good ones.
06BackingHolders who delegate XE to you bring you more work, and take a share of what it earns.
XE GATEWAYTHE JOB, SEALEDYOUR FILES
SAFETY

Someone else’s job.
Your machine, untouched.

  1. 01Sealed offEvery job runs isolated from your files, your other programs and the rest of your machine.
  2. 02Only what it declaredA job gets exactly the access it listed, and only if your policy allows it. Nothing else.
  3. 03Checked firstContracts and images are reviewed by XE before any machine owner is offered them.
  4. 04Your address stays privateJobs behind the XE gateway reach the internet on XE addresses, never on yours.
How a job declares what it may reach
WHY IT’S DIFFERENT

A node that works, not one that waits.

Most networks pay nodes to secure the chain, after you’ve bought a stake. An XE node does jobs customers pay for, and is paid as it does them.

  • What you need to startTypical validatorTokens to stake, and server-grade hardwareXE nodeA machine you already own. Nothing to buy
  • What your machine doesTypical validatorChecks and signs blocksXE nodeReal jobs customers pay for: compute, delivery, storage
  • Where the pay comes fromTypical validatorNew tokens and fees, shared out per epochXE nodeThe customer’s escrow, for the work you did
  • When you’re paidTypical validatorAt the end of each epochXE nodeEvery second, each payment final in 300ms
  • What you controlTypical validatorMostly, your uptimeXE nodeWhich jobs, what they reach, how much of the machine, when
  • If you want to stopTypical validatorYour stake stays locked while it unbondsXE nodePause any time. Running jobs finish or move on
QUESTIONS

Straight answers.

What machine owners ask before they install the app.

What is an XE node?

A machine you own, running the XE node app. It joins the XE network, takes jobs that customers and agents pay for, such as compute, delivery and storage, and is paid in XE for every second of work.

Do I need to buy XE first?

No. Install the app and start taking jobs. You’re paid in XE for the work your machine does.

What hardware do I need?

Anything that can stay online. The app checks your machine and shows the jobs it qualifies for. More CPU, memory, storage or a good GPU opens up more, and better-paid, work.

How much can I earn?

It depends on your hardware, where it is, how much it’s online and which jobs you accept. Every offer shows what it pays per second before you take it, so you always know what a job is worth.

Is it safe to run someone else’s job?

Every job runs isolated, gets only the access it declares, and was reviewed before it reached you. You choose what it may reach on the internet, and anything that asks for more is declined.

Will it use my internet connection?

Only as much as you allow. Jobs with no network access never touch it, and jobs behind the XE gateway use XE addresses, so yours stays private.

How and when do I get paid?

The customer’s payment is locked in escrow before a job starts. You’re paid for every second of work as it happens, in XE, settled in 300ms.

Can I stop whenever I want?

Yes. Pause the node or change your policy at any time. Jobs already running finish first, or are handed to another machine.

How can I earn more?

Keep your node online, finish jobs well to build your record, and cover places other machines don’t. Operators with more XE delegated to them are offered more work.

Page