Point your existing Ethereum toolchain at chain ID 125 and deploy without a translation layer. The node builds a go-ethereum EVM for each transaction, applies fork rules through Prague, and writes logs, receipts and state changes into Cosmos SDK stores in the same block. It serves the eth, net, pax, txpool, web3 and debug namespaces over HTTP and WebSocket, and nineteen precompiles let your contracts call staking, governance, oracle, IBC, CosmWasm and LayerX modules directly.

What it does

The Paxeer chain is the EVM base layer of Paxeer X. Its EVM module builds a go-ethereum vm.EVM for each transaction, runs it through go-ethereum's state transition, and writes the resulting logs, receipts and state changes back into Cosmos SDK stores. EVM chain ID 125 is bound to the Cosmos chain identifier hyperpax_125-1; a node started on any other identifier resolves to 713714 instead. The same node serves the Ethereum JSON-RPC namespaces and exposes the chain's native modules to Solidity through fixed-address precompiles.

Key capabilities

• Runs EVM bytecode through go-ethereum's state transition, with fork rules from genesis through Prague.
• Serves the eth, net, pax, txpool, web3 and debug JSON-RPC namespaces over HTTP and WebSocket.
• Exposes nineteen precompiles so Solidity can call native staking, governance, oracle, IBC, CosmWasm and LayerX modules.
• Binds EVM chain ID 125 to the Cosmos chain identifier hyperpax_125-1, and nothing else.
• Persists EVM logs, receipts and state changes into Cosmos SDK stores within the same block.
• Refuses the test_ namespace and the unsafe keyring RPC on any mapped live chain identifier.

Differentiators

Native Cosmos modules and the LayerX agent-domain modules are callable from Solidity at fixed precompile addresses on the same chain. Checkpoint settlement and the guarantor bond, for example, are reached at 0x0000000000000000000000000000000000001014 with no contract deployed. A pax namespace runs beside eth on the same endpoint and serves account-association reads and filters.

Outcomes

• Ship Solidity with standard wallets, libraries and the eth namespace.
• Call staking, governance or LayerX custody without deploying a bridge.
• Run paxd with EVM HTTP on 8545 and WebSocket on 8546.

Technical notes

• EVM chain ID 125 is derived only from the Cosmos chain identifier hyperpax_125-1; an unmapped identifier falls back to 713714, which is not a live chain identifier and therefore enables the test namespace and the unsafe keyring RPC.
• Consensus parameter defaults, as configured in code: block max bytes 21 MB, max gas 100000000, max gas wanted 50000000, minimum 10 transactions in a block, propose timeout 1s, vote timeout 50ms, commit timeout 50ms. These are configured defaults, not measured results.
• The EVM module enforces no block-level gas limit; gas limits are per transaction, and gas is converted between native and EVM units by a configurable normalizer.
• hyperpax_125-1 is not one of the embedded well-known chains, so paxd init writes the default module genesis for it; the hosted bring-up script supplies the custody and anchor genesis sections and refuses any chain id other than 125.
• Operator configuration is read with the PAX environment prefix. Bring-up defaults are EVM HTTP 8545, EVM WebSocket 8546, CometBFT RPC 26657, P2P 26656, gRPC 9090, gRPC-web 9091.
• go-ethereum is pinned through the pax-geth fork at v1.15.7-pax.17.

import { PxClient } from "paxeer-xdk";

const px = new PxClient({ endpoint: process.env.PAXEER_RPC_URL! });
const head = await px.getNetwork();

console.log(head.paxeer.chainId); // 125n
console.log(head.paxeer.latestBlock);

More in Paxeer chain