Skip to content
Mainnet betaPaxeer X is live on chain ID 125. Follow it on Paxscan.

Three ways in.One network.

Build on your own machine today. Request mainnet access when you are ready to ship, or run the nodes the network settles on.

A passport with a visa stamp
Fig. 1 Access, stamped by the team

Pick where you start.

No path carries a fee. Validators stake PAX and guarantors post a bond under protocol rules.

Build

For developers who want the full stack on their own machine, with nothing at stake.

What you get

  • SDKs in seven languages
  • Local LayerX emulator that signs real receipts
  • Four-node Paxeer X chain in Docker
  • Standard EVM JSON-RPC on chain ID 125
  • MCP and A2A adapters for agents

Partner

For teams shipping on mainnet during the limited beta, with real value at stake.

What you get

  • Mainnet beta access on chain ID 125
  • Starting PAX allocated by the team
  • Agent wallets, budgets and 402LXP payments
  • Staged finality from L0 to L4
  • A direct line to Sidiora Labs

Operate

For validators and LayerX operators who run the machines the network settles on.

What you get

  • Checksum-verified paxd installer
  • Validator, full, seed and archive modes
  • Sequencer, replica, guarantor and relay roles
  • Guarantors re-execute every LayerX batch
  • Linux on x86-64 or AArch64

Compare the paths.

What each path includes, and what you bring to it.

What each path onto Paxeer X includes
FeatureBuildPartnerOperate
Access
Local emulator and four-node chainIncludedIncludedIncluded
Mainnet beta on chain ID 125On approvalIncludedIncluded
Starting PAXFrom the teamFrom the teamOwn stake or bond
Team approvalFor mainnetIncludedFor guarantors
Tooling
SDKs in seven languagesIncludedIncludedIncluded
EVM JSON-RPC, Foundry and HardhatIncludedIncludedIncluded
Agent wallets, budgets and 402LXPIncludedIncludedNot included
paxd and layerxd node binariesNot includedNot includedIncluded
Support
Docs and the open source monorepoIncludedIncludedIncluded
A direct line to Sidiora LabsOn approvalIncludedIncluded
Private security reportingIncludedIncludedIncluded
Requirements
What you bringA dev machineA team and a launch planLinux hosts
Stake or bondNot includedNot includedIncluded
Fee to joinNot includedNot includedNot included

Before you start.

Short answers on access, PAX and tooling. The full FAQ covers the rest.

Read the full FAQ
How do I get into the beta?

Request access with the form on this page. The limited beta runs on mainnet with real value, so the team reviews every request and opens access team by team. Approved developers and teams receive their starting allocation directly from Sidiora Labs.

Is there a public faucet?

No. The beta settles real value, so there is no faucet for general use. Allocations come from the team after approval. Until then, the local environment gives you a LayerX emulator and a four-node chain on your own machine, with nothing at stake.

What is PAX used for?

PAX is the native gas and settlement asset of Paxeer X. It pays for gas on the chain, settles what agents do on LayerX once checkpoints land, and is what validators stake to secure the network.

Does my EVM tooling work?

Yes, within documented limits. The chain serves the standard Ethereum JSON-RPC on chain ID 125, Foundry and Hardhat build and test the network’s own contracts, and any client library that speaks standard JSON-RPC connects. Seven methods are documented as unsupported, and blob transactions are not available.

Which languages have SDKs?

Seven: Rust, TypeScript, Python, Go, JVM, .NET and Swift. They share one wire format and verify receipts locally. Rust, TypeScript and Python are the most complete. All are early releases that install from source in the public repository.

How do I report a security issue?

Privately, through GitHub private vulnerability reporting on the Paxeer X Network repository, never in a public issue. Include the affected revision, a reproduction and the invariant it breaks. Probing live infrastructure, validators, custody deployments or user data is out of scope.

Request beta access.

The limited beta runs on mainnet with real value, so the team reviews every request. Approved developers and teams receive their starting allocation directly.

I want to

Helps us route your request.

We use these details only to reply about Paxeer X. Privacy policy

Keys on hooks, one hook empty
Fig. 2 A grant for each key
You send
What you plan to ship and who is building it.
We review
The team reads every request and replies by email.
You build
Approved teams get mainnet access and a starting allocation.