XE PRIMITIVE

Payment

Paid in 300ms. Fractions of a cent. Nothing queues.

Every account has its own chain, so a payment never waits behind anyone else’s. A $0.001 payment settles like a $1,000 one, with no fee, and escrow can pay a machine for every second it works.

WHAT PAYMENT IS

Payment on XE moves value between accounts, final in 300ms and free to send, because XE Lattice gives every account its own chain and nothing waits in line.

A payment is two small blocks: a send on the payer’s chain and a receive on the payee’s. Nobody bids for space. That makes payments small enough for machines: an agent can pay a fraction of a cent per API call, a robot can pay the charger it plugs into, and a customer can release a budget to a machine for every second it works.

Transfers

Account to account, final in 300ms, with no fee auction and no queue.

Escrow

Locked up front, released by the second, and the rest back when the job stops.

Micropayments

No minimum. Pay per call, per frame, per charge, and each one settles like any other.

Spam guard

XE Proof of Work on each block, instead of a fee. Sending stays free; spam doesn’t pay.

THE PROBLEM

Machines pay all day. Every rail charges by the payment.

Today
  • A fee that’s often more than the payment itself.
  • Every payment waits in one line.
  • Seconds on a shared chain, days on a card.
  • Dollars are the smallest amount that makes sense.
  • Monthly invoices, net-30.
With XE Payment
  • No fee to send.
  • No line: every account has its own chain.
  • Final in 300ms.
  • Fractions of a cent, settled like any other payment.
  • Escrow, released by the second.
WHY NOTHING WAITS

One line for everyone,
or a chain for each.

On a shared chain every payment waits in the same line, and the line grows as the network does. On XE the payer’s own chain takes the payment, so there is no line.

Built with
IdentityDiscoveryPaymentComputeMessaging

0x7f…a2

Agent

0x2c…91

Inference API

$0.0002 per call
Paid so far$0.014472 calls, each settled on its own
Network fee$0.00
Final in300ms
Queuenone
Payment

Pay per call, per job, per use. No fees eating the margin, no queue, no waiting for a block. Payments small enough for machines to pay each other all day long.

Send the same payments to both. Watch where they wait.

One line for everyoneA shared chain
Waiting for the next block
Blocks, a few payments at a time
No block yet.
0Still waiting
0In a block so far
A chain for each accountXE
  1. 0x7f…a2Final
  2. 0x2c…91Final
  3. 0x51…e4Final
  4. 0x9b…c0Final
  5. 0x4e…19Final
  6. 0xd3…07Final
  7. 0x18…5fFinal
  8. 0xa6…3bFinal
0Waiting
0Final, each in 300ms
The same payments go to both. Watch where they wait.
THE TRANSFER

Two small blocks.
No fee.

Each is signed by its own account, on its own chain. The receive names the send it settles, so the money can only be claimed once.

send · the payer’s chainSigned block
1{
2 "type": "send",
3 "account": "7f3a…c2e1", // the payer's own chain
4 "previous": "c81d…90ab", // its last block
5 "destination": "2c91…e4b7", // the payee
6 "amount": 400,
7 "balance": 1999600, // what the payer holds after
8 "asset": "XE",
9 "hash": "9f3c…a1d0",
10 "signature": "e2c9…5d18",
11 "pow_nonce": 81234 // XE Proof of Work, not a fee
12}
receive · the payee’s chainSigned block
1{
2 "type": "receive",
3 "account": "2c91…e4b7", // the payee's own chain
4 "previous": "4be0…13c7",
5 "source": "9f3c…a1d0", // the send it claims, once
6 "balance": 88400,
7 "asset": "XE",
8 "hash": "d07a…6e21",
9 "signature": "71fb…c0a4",
10 "pow_nonce": 5520
11}

What the two blocks say

From
The payer’s own chain, signed with its own key
To
Any account, a machine’s or a person’s
No fee
XE Proof of Work rides along instead
Claimed once
The receive points at the send it settles, and only once
No queue
Each block follows its own account’s last one, not everyone’s
Settled
The payee’s balance, the moment its chain takes the receive
HOW IT WORKS

Send on one chain. Receive on another.

The sender signs a send block and the network hears it. The recipient signs a receive block that points back to it. If anyone tries to spend twice, XE Consensus settles it and the honest block wins.

0fees per payment
2blocks per payment
300msto final
67%of the vote settles a conflict
ESCROW

Locked up front.
Released by the second.

The budget goes into escrow before the work starts. The machine is paid for every second it works, and the moment the job stops, the rest comes back.

The customer can’t skip the billThe money is locked before the first second of work.
The machine can’t overchargeIt’s paid for seconds worked, and nothing else.
Stop whenever you likeWhatever hasn’t been released goes straight back, final in 300ms.
Locked in escrow5.000 XE
Rate, per second0.00061 XE
Machine working for00:00
Releasing
Paid to the machine0.00000 XE
Still in escrow5.00000 XE
Shown at 10× speed.
FOR BUILDERS

Pay per call,
from its own account.

A payment is a signed send block. The payee claims it with a receive block. Both are final in 300ms, and neither costs a fee.

SendA signed block on your own chain: who, and how much
ReceiveThe payee claims it with a block on theirs
Any sizeFractions of a cent per call, or a whole budget
1const node = process.env.XE_NODE
2
3// a send block on your own chain: who, and how much
4const block = sign(me, {
5 type: "send",
6 account: me.address,
7 previous: me.frontier,
8 destination: api, // the account you're paying
9 amount: "0.0004",
10 asset: "XE",
11 pow_nonce: await work(me), // XE Proof of Work, instead of a fee
12})
13
14await fetch(`${node}/blocks/send`, {
15 method: "POST",
16 body: JSON.stringify(block),
17})
FOR AGENTS

An agent pays by the call.

Its own moneyIt pays from its own account. No card, and no person to approve it.
By the callEach call paid on its own, final in 300ms.
Nothing to reconcileNo invoice at the end of the month. Every payment is already on both chains.
FAQ

What people ask about payment.

Why are there no fees?
Every account writes to its own chain, so there’s no shared block space to auction. XE Proof of Work on each block stops spam instead.
When is a payment final?
As soon as the network has it, in about 300ms, unless the account tried to spend the same money twice. Then XE Consensus decides, and the honest block wins.
How can a payment be a fraction of a cent?
Because nothing about sending it costs more than it’s worth. There’s no fee, and every account writes to its own chain, so a $0.001 payment takes the same path, and the same 300ms, as a large one.
How does escrow work?
The customer locks a budget before the work starts. It’s released to the machine for every second it works, and when the job stops, whatever is left goes straight back. The customer can’t skip the bill, and the machine can’t charge for work it didn’t do.
What do machines pay with?
Leases are paid in XUSD, priced in dollars, and machine owners are paid in XE when a lease settles. Accounts can send either.
Can it handle lots of tiny payments?
Yes. Accounts never wait on each other, so thousands of small payments can happen side by side.
Does it slow down as more people use it?
No. Accounts write to their own chains in parallel, so capacity grows with the number of participants instead of being shared out between them.
Page