-
Notifications
You must be signed in to change notification settings - Fork 71
Home
A deterministic execution and accounting network for autonomous agents.
LayerX is the shared ledger where agents transact, delegate authority, buy work from each other, and leave a receipt they cannot rewrite. Routine activity is ordered and executed here. Custody, checkpoints, bonds, challenges, and exits settle on Paxeer Network (EVM chain ID 125).
This GitHub repository is now the LayerX + Paxeer monorepo. Paxeer node source lives under paxeer-network/ with its own build, release tags (paxeer-network/vX.Y.Z), and trust boundary. Co-location does not grant LayerX or Paxeer new authority over the other.
Limited beta opens September 7. Source is open for inspection while we qualify the public lane.
Website · Whitepaper · Repository · Security
Agents do not just need wallets. They need one system that can express limited authority, budgets, paid services, escrow, streams, attestations, trading, and settlement — then keep an account of what happened.
Putting every one of those actions on a general-purpose chain ties routine work to block time and settlement fees. Keeping everything off-chain with no verifiable state gives you speed without a record anyone else can replay.
LayerX splits the two jobs:
| Layer | Owns |
|---|---|
| LayerX | Identity, delegated authority, global ordering, balances, payments, agreements, trading, receipts, replay, data availability |
| Paxeer | Custody, checkpoint registration, guarantor bonds, challenges, withdrawals, emergency exits |
Thousands of LayerX activities can collapse into one periodic checkpoint. A normal payment or agent action does not require a Paxeer transaction.
Every state-changing operation is a signed, canonically encoded activity (LXC/1). The protocol checks the actor and its authority, consumes the account sequence, orders the activity globally, applies a deterministic state transition, and returns a signed receipt tied to the resulting state root.
Three design rules sit at the center:
- One canonical history. Every accepted or failed activity gets a global sequence. State roots chain per activity, not only per batch.
-
One financial doorway.
402LXPis the only component allowed to write balances. Modules emit validated transfer sets; they do not mutate funds themselves. - One reproducible result. Consensus-critical execution excludes floating point, local clocks, database iteration order, and other sources of nondeterminism.
The append-only activity log is authoritative. Indexes are disposable projections. Replicas and bonded guarantors independently replay batches before a checkpoint is attested to Paxeer.
Read Protocol, Modules, and Finality.
Identity and authority live in the kernel. Oracle intake is a Crossverse adapter outside the kernel. Programs are a separate runtime surface, not a ninth module ID (0x09).
| ID | Module | What it does |
|---|---|---|
0x01 |
asset | Transfer sets for balances; 402LXP writes them |
0x02 |
escrow | Money held until the terms are met |
0x03 |
budget | A hard ceiling on what an agent may spend |
0x04 |
stream | Paying continuously, by the unit |
0x05 |
service | Agreeing work, proving it, delivering it |
0x06 |
perps | Leveraged positions and their margin accounts |
0x07 |
governance | Changing protocol settings, on a timelock |
0x08 |
bridge | Custody on Paxeer L1, and withdrawal claims |
Full writeup: Modules.
HTTP already had a status for "you owe me money": 402 Payment Required. LayerX uses it.
The API answers with a price. Your agent pays from a payer grant — a signed permission that caps how much may be taken and what for. The service delivers against the receipt. No checkout, no stored card, no session, no human.
| Op | Meaning |
|---|---|
SEND |
Your agent pushes the money |
RECEIVE |
The payee pulls, within your grant |
You pay for work done (bytes, signatures, state) — not a zero-fee line. The specified base fee is 5,000 µUSDX (~½¢) per activity. See Payments and Fees.
An activity is not final all at once. Each step names who is on the hook if the claim is wrong.
| Step | Name | What it means |
|---|---|---|
| L0 | Accepted | The sequencer orders the activity into the current batch |
| L1 | Sealed | The batch is sealed; ordering is fixed |
| L2 | Distributed | The sealed batch goes to the guarantor quorum for re-execution |
| L3 | Attested | Bonded guarantors re-execute and attest byte-identical results |
| L4 | Settled | The checkpoint lands on Paxeer L1. Custody never leaves Paxeer |
The guarantee behind a batch is not a validity proof. It is bonded re-execution, a challenge window, and withdrawal limits. Walk Finality and Security.
| Stage | Limited beta opens September 7. |
| Source | Source-available during qualification — built for review now; broader license after release qualification. |
| Public endpoints | None yet. No RPC, no faucet, no explorer for LayerX itself. Private rollout; source is open. |
| Token | There is no LayerX token and no token sale. USDX is the unit agents hold inside LayerX. USDL is the asset held on Paxeer L1 behind it. PAX is Paxeer's gas token. |
| Contact | The GitHub repository is the only public channel. |
Details: Status.
make build
make test
make test-contracts
make paxeer-ci # optional: Paxeer-specific gate
make monorepo-ci # optional: monorepo-wide gateNormative behavior lives in spec/ (KVX first). See Developers.
This wiki is LayerX Protocol by Sidiora Labs, specified as LXP1, settling on Paxeer Network.
Ours: sidiora.xyz · github.com/Sidiora-Labs · paxeer.app
Other companies use this name. A page that does not trace back to one of those three is a different LayerX.