PAXEER X / NETWORK DOCUMENTATION
Applications. Payments. Programs. Build on Paxeer.
The LayerX kernel inside paxd executes and orders each transaction and builds each block; validators check and commit each block.
Explore the networkStart with the XDK
LayerX kernelEVM chain ID 125Native token PAX
The LayerX kernel executes, orders and receipts every transaction; EVM applications run on the same sequence.EVM 125 · PAXOn arrival, the kernel gives each transaction a position in one global sequence and returns a signed execution receipt. Validators check and commit each block it builds.
NETWORK INTERFACES
XDKDeveloper toolkit 7 SDKsLanguage quickstarts MCPScoped daemon tools JSON-RPCEVM chain 125 CLICommand line
Execution you can reproduceThe node orders native activities and commits their state with BFT blocks. Deterministic execution supports replay with the required state and artifacts. Authority with clear boundariesIdentity keys, scoped capabilities, delegated spending limits and revocation constrain authorized actions. Tools you already knowDeploy Solidity, connect wallets and call native precompiles through standard EVM tooling and JSON-RPC on chain 125.
APPLICATION NEEDS
Reconcile payment outcomes
Identify an authorized actor
Link payment and delivery
Reproduce program execution
Check settlement evidence
Connect agent tools
PAXEER X
Native transfer settlement (402LXP)
EVM address bound to a LayerX DID
Escrow, acceptance and receipts linked
Deterministic, replayable transitions
Signed receipts and committed blocks
Scoped MCP tools and agent budgets
AGENTS
Configure agent authority.
Create identities, delegate scoped authority, fund accounts and connect tools through SDKs, MCP and the agent daemon.
This path covers:
Agent identities and DIDs
Budgets, mandates and revocation
Scoped MCP tools
Agent-to-agent tasks
PAYMENTS START HERE
Integrate native payments.
Integrate transfers, escrow, budgets and payment streams. Connect service delivery to acceptance, receipts and disputes.
This path covers:
Transfers, holds and escrow
Paid APIs and x402 / 402LXP
Payment streams and budgets
Receipts and settlement proof
EVM APPLICATIONS
Use the tools you know.
Deploy Solidity, connect wallets and call native precompiles for account binding, native payments, exchange and asset launches.
This path covers:
Solidity with Foundry and Hardhat
JSON-RPC on chain 125
Native precompiles
Assets, launchpad and markets
BUILD WITH THE FULL SYSTEM
Find your interface. Follow it deeper.
Architecture, integration guides and operational reference for Paxeer X.
[### LayerX kernel
Canonical sequencing, accounting, modules and deterministic execution.](/layerx-kernel) [### Platform APIs
Application gateways, hosted services, webhooks and integration surfaces.](/platform-api) [### EVM JSON-RPC
Wallet integration, chain requests, contracts and transaction inspection.](/json-rpc) [### Operator guides
Nodes, configuration, network services and settlement infrastructure.](/operators)
What is the difference between Paxeer X and LayerX?
Paxeer X is the network and LayerX its kernel. LayerX executes each transaction on arrival, orders it, signs the receipt and builds the block that validators commit. EVM transactions run on the same sequence and call native precompiles. Receipt finality comes from the commit of the covering block. Explore the network architecture
Which chain ID and token does the network use?
EVM chain ID 125 (hyperpax_125-1) with native token PAX. Denominations, gas limits and endpoints are listed with the network parameters. Network parameters
How does an agent get authority to spend?
Through scoped, revocable delegation: primary and session keys, budget limits and mandates define exactly what an agent may do with money, and owners can revoke or rotate that authority. Agent budgets
How do I verify a payment actually settled?
Verify the signed execution receipt against trusted receipt keys, check its transaction and outcome, and confirm the covering block is committed. Receipts and proofs
Can I use my existing EVM tooling?
Yes. Deploy Solidity with Foundry or Hardhat, connect wallets over JSON-RPC, and call native precompiles for account binding, native payments and markets on chain 125. Build on the EVM
How do I run a node or operate the network?
Start with installation and configuration, then the operator guides for paxd nodes, validators, RPC endpoints and retained chain history. Run a node
Build an application. Connect to Paxeer.
Choose a domain, integrate an interface and follow the evidence through the network.