XE IMAGES

XE Images

One click. Any machine. Checked first.

Launch a ready-made setup, like a blockchain node, a model server or a game server, on any machine whose owner allows it. Every image is reviewed before it runs.

READY-MADE SETUPS

XE Images is a catalogue of ready-made setups, a blockchain node, a model server, a game server, that you launch in one click on any machine whose owner allows it.

An image is the whole setup, packaged once by a builder: the software, its configuration, and a plain declaration of what it needs and what it may reach. XE reviews it before anyone can launch it. It runs paid per second from escrow, and the builder earns a royalty every time it boots.

LauncherYou want it running
Does
Picks an image and where it should run, then clicks once.
Gets
A working setup in seconds, with no account and no cloud signup.
Controls
The country, the price, and when it stops.
BuilderYou made the setup
Does
Packages it once, declares what it needs, and submits it for review.
Gets
A royalty every time it boots, anywhere on the network.
Controls
Versions, updates, and what the image asks for.
Machine ownerYou run the hardware
Does
Sets in the node app which images and access levels it accepts.
Gets
Paid per second, from escrow, for every image it runs.
Controls
Everything that starts on the machine. Nothing runs that its policy doesn’t allow.
THE PROBLEM

The same setup, by hand, every single time.

By hand
  1. 01Open an account with a host, and wait for approval
  2. 02Provision a server, then install the software on it
  3. 03Find a configuration that works, and hope it’s safe
  4. 04Open the ports it needs, and close everything else
  5. 05Pay by the month, whether it runs or not
  6. 06Do it all again for the next one
With XE Images
1 clickNo account, no cloud signup, no afternoon lost to installation. Checked before it reached you.
  1. 01Pick an imageFrom the catalogue, by what it does and where it can run.
  2. 02Pick whereA country, a price, or the first machine that fits.
  3. 03It’s runningPaid per second from escrow, stopped whenever you want.
THE CATALOGUE

Ready-made, reviewed,
one click away.

Each image says exactly what it needs and what it may reach, so it only starts on machines whose owners allow it. Choose one, choose where, and launch it.

Built on
IdentityDiscoveryPaymentComputeMessaging
LaunchSolana RPC nodesolana-rpc:1.18.4
Where

$ xe images launch solana-rpc:1.18.4 --country sg

THE MANIFEST

One folder. One file.
Nothing it didn’t declare.

xe-image.tomlXE Image
1[image]
2name = "solana-rpc"
3version = "1.18.4"
4kind = "node"
5
6[needs]
7cpu = 16
8memory = "256 GB"
9storage = "2 TB"
10
11[access]
12network = "gateway" # served on XE addresses
13ports = [8899, 8900]
14
15[earn]
16royalty = "per_boot"
CHECKED FIRST

Nothing boots until it’s been checked.

Every image passes review before a single machine owner is offered it. The builder locks XE to submit, so every listing has something at stake.

The reviewsolana-rpc:1.18.4
  1. It builds, starts and does what its description says
  2. It asks for the CPU, memory and storage it declares
  3. It reaches only the network it declares
  4. It has a named publisher with XE locked behind it
  5. It’s different enough from what’s already listed
ROYALTIES

A royalty on every boot, anywhere on the network.

Package a setup once and publish it. Every time someone launches it, on any machine, in any country, you’re paid.

Lock XEBehind the image you publish. It lists the image, and it stops junk copies of someone else’s work.
Every bootAnyone, anywhere, launches it on a machine that allows it. Each launch is recorded to the image.
Your royaltyPaid to you for every boot, for as long as people run it. Your lock comes back when you unlist.
FOR BUILDERS

Package it once. Earn every time it boots.

An image is a folder with a manifest: what it is, what it needs, what it may reach. Build it, test it against the review’s own checks, and publish it from your terminal.

PackageWith the XE SDK, from a folder you already have
DeclareCPU, memory, storage, ports and network access
UpdateShip a new version; launches pick it up from then on
1[image]
2name = "solana-rpc"
3version = "1.18.4"
4kind = "node"
5
6[needs]
7cpu = 16
8memory = "256 GB"
9storage = "2 TB"
10
11[access]
12network = "gateway" # served on XE addresses
13ports = [8899, 8900]
14
15[earn]
16royalty = "per_boot"
FOR AGENTS

An agent can launch one in a single call.

An agent that needs a node, a model or a database doesn’t install anything. It picks a checked image, pays for it from its own account, and gets back an endpoint.

Checked, so it’s safe to pickAn agent can’t audit a setup. The review already did.
Paid per secondIt stops the image the moment it’s done, and the rest of the escrow comes back.
An endpoint, not a serverWhat comes back is an address to call, not a machine to manage.
Page