PAXEER X / NETWORK DOCUMENTATION
Paxeer X unites EVM applications, the LayerX agent economy, payments, markets and deterministic programs with verifiable execution and settlement.
125Native token PAX
ONE NETWORK — EVERY INTERFACE
PROBLEM
PROBLEM 1Identity scattered per appA chain address here, an agent account there. Nothing binds them, so authority has to be rebuilt for every integration.Bind the identities 
PROBLEM 2Payments without evidenceValue moves in one system while authorization, delivery and proof live in others — if they exist at all.Attach the evidence 
PROBLEM 3Zero execution visibilityResults with no canonical history cannot be replayed, audited or independently checked after the fact.Verify the result SOLUTION
MARKETSMarket performanceTrack growth across positions with margin, funding and oracle inputs as explicit protocol concepts.Perpetual markets 
ASSETSAsset allocationNative assets, tokenfactory denoms and ERC20 pointers — see exactly where value sits across both domains.Issue and manage assets 
NOTIFICATIONSActivity notificationsSwaps, rewards and security events pushed to your application the moment they settle.Set up webhooks START BUILDING
BENEFITS
COMPARISON
FRAGMENTED STACK
PAXEER X
AGENTS
PAYMENTS
PROGRAMS AND SERVICES
OBSERVE AND OPERATE
HOW IT WORKS
STEP 1Install and connectPick one of seven SDKs, the XDK or JSON-RPC and point it at your node or a public endpoint.SDK quickstarts 
STEP 2Fund and authorizeFund the account, bind identities and set the budgets and mandates that bound what can be spent.Make your first payment 
STEP 3Execute and verifySend the activity, then follow its signed receipt through batch sealing to checkpoint settlement.Verify a receipt YOUR FIRST INTEGRATION
Start with payments, agent automation, deterministic programs or an EVM application. Each path connects to the same network through the interface suited to your application.
0x7d / 125The hexadecimal value 0x7d corresponds to chain ID 125.curl 'http://localhost:8545' \
-H 'Content-Type: application/json' \
--data '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'BUILD PATHS
AGENTS
Create identities, delegate scoped authority, fund accounts and connect tools through SDKs, MCP and the agent daemon.
This path covers:
PAYMENTS START HERE
Integrate transfers, escrow, budgets and payment streams. Connect service delivery to acceptance, receipts and disputes.
This path covers:
EVM APPLICATIONS
Deploy Solidity, connect wallets and call native precompiles for account binding, custody, checkpoints, exchange and asset launches.
This path covers:
EVIDENCE, NOT PROMISES
RECEIPTSSigned at executionEvery activity returns a signed receipt you can verify against committed state — no operator statement required.Verify signed receipts 
CHECKPOINTSSealed on Paxeer XBatches of execution compact into checkpoints settled on the chain, with guarantor attestations behind them.Follow a checkpoint 
COMMITMENTInstant, sealed, finalDistinguish instant execution, sealed batches and final settlement, and match the level to the economic action.Read commitment levels 
REPLAYReplayable historyGlobal sequencing and chained state roots make the canonical history independently replayable by anyone.How sequencing works 
CUSTODY EXITSA verifiable way outWithdrawals and forced exits use verified receipt or state evidence, recipient authorization and nullifiers.Custody and exits INSPECTIONDebug from evidenceCollect the transaction and its receipt, then check the call against committed state instead of guessing.Debug a transaction BUILD WITH THE FULL SYSTEM
Architecture, integration guides and operational reference for every part of Paxeer X.
Canonical sequencing, accounting, modules and deterministic execution.
Application gateways, hosted services, webhooks and integration surfaces.
Wallet integration, chain requests, contracts and transaction inspection.
Nodes, configuration, network services and settlement infrastructure.
FAQS
Paxeer X is the EVM chain supplying execution, custody and settlement. LayerX is the kernel that orders agent activities and produces deterministic state transitions, signed receipts and checkpoints. Native precompiles connect the two domains through verifiable evidence. Compare the domains
EVM chain ID 125 (hyperpax_125-1) with native token PAX. Denominations, gas limits and endpoints are listed with the network parameters. Network parameters
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
Verify the signed receipt, confirm its inclusion in a sealed batch, then check the checkpoint settled on Paxeer X: receipt → batch → checkpoint → finalized settlement. Receipts and proofs
Yes. Deploy Solidity with Foundry or Hardhat, connect wallets over JSON-RPC, and call native precompiles for account binding, custody, checkpoints and markets on chain 125. Build on the EVM
Start with installation and configuration, then the operator guides for chain nodes, sequencers, replicas, guarantors and archive services. Run a node
Choose a domain, integrate an interface and follow the evidence through the network.