-
Notifications
You must be signed in to change notification settings - Fork 71
Fees
Cursor Agent edited this page Aug 24, 2026
·
1 revision
You pay for work done, not time taken.
Site: Fee schedule (LXP1 §10.2)
You pay for what your agent actually uses: bytes, signatures, state reads, state writes. How long the work took never enters the calculation.
| Base fee | 5,000 µUSDX per activity (~½¢) |
| Congestion | Multiplier from 1× to a 64× ceiling, from measured load, same for everyone, visible before you sign |
This is the specified schedule. It is not a "zero fees" line.
| Unit | Role |
|---|---|
| USDX | What agents hold and spend inside LayerX |
| µUSDX | Fee quote unit. 1 USDX = 1,000,000 µUSDX |
| USDL | Held in contracts on Paxeer L1. Every USDX is backed one-for-one by USDL |
| PAX | Paxeer's gas token. Pays for checkpoint transactions on L1. Not a LayerX asset |
There is no LayerX token. See Status.
| Meter | What it counts |
|---|---|
BYTES |
Size of the signed record |
SIGVERIFY |
Each verified signature |
STATE_READ |
Each stored-state read |
STATE_WRITE |
Each stored-state write (costs more than a read) |
HASH |
Hash operations on activity bytes and commitments |
TRANSFER_LEG |
Each leg of a transfer set |
MODULE_STEP |
Module-local steps inside an activity |
Never wall-clock time. Anyone re-running the activity counts the same work and reaches the same price.
Proportions are fixed in the protocol:
| Share | bps |
|---|---|
| Sequencer | 3000 |
| Guarantor quorum | 3000 |
| Insurance fund | 2000 |
| Treasury | 2000 |
The money goes to the parties carrying the risk, and to the reserve that stands behind failures.
Ordering activities, re-running them, and reconciling custody on Paxeer L1 is real work, done by parties with their own money at stake. Charging nothing would only mean somebody else was paying for it.