Repository navigation
Home
This wiki covers Paxeer X Network by Sidiora Labs, a deterministic execution and accounting network for autonomous agents.
paxeer.app · Source repository
Paxeer X Network is one network with two execution domains, joined by EVM precompiles and served behind one shared interface.
| Domain | Node | Role |
|---|---|---|
| Paxeer X chain |
paxd (Go), EVM chain ID 125
|
The EVM chain domain. Holds custody, checkpoint registration, guarantor bonds, challenges, withdrawals, disputes, and emergency exits. |
| LayerX kernel |
layerxd (C17) |
The agent-native execution domain. Verifies, orders, and executes agent activity and returns signed receipts. |
Every state-changing operation in the kernel enters as a signed, canonically encoded Activity. The kernel verifies the actor and its authority, consumes the account sequence, orders the activity on one global sequence, applies a deterministic state transition, and returns a signed receipt tied to the resulting state root. 402LXP is the only component allowed to write balances; modules emit validated transfer sets. The append-only activity log is the authority, and indexes can be rebuilt by replaying it.
Ordinary agent activity is executed and ordered inside the kernel, and periodic checkpoints are registered on the Paxeer X chain. An ordinary agent action does not require a chain transaction.
| Where | Components |
|---|---|
| LayerX kernel |
layerxd (LNI server and sequencer), the activity kernel and its modules, the 402LXP ledger, the activity log, and layerx-guarantor, which submits sealed batches as checkpoints to the anchor precompile |
| Paxeer X chain |
paxd: EVM JSON-RPC (pax-geth), Tendermint consensus, an OCC parallel executor, the precompiles below and their modules, and the PaxDB state store |
| Platform services |
layerx-gateway (the shared interface), layerx-indexer with its SQLite history, and a relay/archive node |
| Clients |
layerx-agentd, layerx-mcp, and layerx-sdk for agents; the human web app, layerx-human-service, and the layerx-intents typed intent compiler for people |
The gateway picks the domain from the method name: eth_*, net_*, and web3_* calls go to the chain, lx_* calls go to the kernel, and px_* calls are cross-domain reads answered from the precompiles.
| Precompile | Address | Role |
|---|---|---|
Addr |
0x1004 |
Binds an EVM address to a did:layerx key |
LayerXVerify |
0x1012 |
Verifies kernel receipts, inclusion proofs, and state proofs |
LayerXCustody |
0x1013 |
Holds custody; funds leave only against verified kernel evidence |
LayerXAnchor |
0x1014 |
Checkpoint registry, finality, availability, and guarantor bonds |
LayerXExchange |
0x1015 |
Records exchange intents for the kernel; no order is matched on the chain |
LayerXBridge |
0x1016 |
Bridge to Ethereum through layerx-bridge-relayer and PaxeerXVault
|
Launchpad |
0x1017 |
Token launches on a constant-product curve |
The kernel owns identity and authority and dispatches to nine economic modules plus Programs (include/layerx/lxp_module.h). Details are on Modules.
| ID | Module | What it does |
|---|---|---|
0x01 |
asset | Transfer sets that move value; 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 | Identity, grants, parameter changes, handover |
0x08 |
bridge | Custody credit on the Paxeer X chain, and withdrawal claims |
0x09 |
programs | Guest WASM execution; emits transfer sets, never writes balances |
0x0A |
spot | Two-asset limit and market orders, settling both legs immediately |
The limited beta has not opened yet. The gateway API becomes available when it does. This is a mainnet beta on real value, so there is no faucet for general use; approved developers receive test allocations from the team.
Details are on Status.
- Home: this overview
- Protocol: how activities are verified, ordered, and executed
- Modules: the kernel modules and Programs
- Finality: how an activity becomes final
- Payments: how agents pay
- Fees: what activities cost
- Developers: building from source, specifications, repository layout, and contributing
- Security: the security model and vulnerability reporting
- Status: current status and what the repository contains