Point your existing tools at chain 125
If your code speaks Ethereum JSON-RPC, it already speaks Paxeer X. Change the URL and the chain ID, and you gain a signed receipt the moment you send.
viem, ethers, web3.py, Foundry and MetaMask connect as they would to any EVM chain. One added method tells you what happened before the block is even built.
Switching chains usually means re-learning how to talk to one. Not here. Paxeer X answers the same eth_ methods your wallet, indexer and test suite already call, at one URL. What you gain is what the standard never offered: a signed answer, in milliseconds, saying exactly what your transaction did.
One URL for the whole network
The router at api-mainnet-beta.paxeer.network/rpc is the front door: it relays your signed transactions, serves reads and answers every standard method. To talk to a node directly, api1 through api16.mainnet-beta.paxeer.network serve the same interface over HTTPS and WebSocket. Nodes are numbered, not ranked; pick any and fall back to another.
125
chain ID
16
public nodes, HTTPS and WebSocket
1
URL that reaches all of it
Two additions worth knowing
On most chains you send a transaction and poll for a receipt that arrives when a block does. On Paxeer X the transaction is executed on the way in. eth_sendRawTransaction returns as usual, and pax_sequencerReceipt hands you the result, logs, fee and position in the global order, signed by the network's receipt key. eth_sendRawTransactionSync does both in one call.
The second addition is that the pending block tag means what it says. A balance, nonce or contract call read at pending reflects every receipted transaction, so an agent can send ten payments in a row and see each land before the next.
Standard where it counts
| Area | What to expect |
|---|---|
eth_ reads and writes | Ethereum semantics. EIP-1559 transactions, logs, filters, proofs |
eth_getTransactionReceipt | Answers only once the transaction is committed and final, as a standard client expects |
eth_subscribe | New heads, logs and receipted transaction hashes in receipt order |
net_, web3_, debug_ | Supported |
| Mining and blob methods | Not applicable to this network; they answer with a clear error |
| Server-side signing | Never. The network signs nothing on your behalf; keys stay with you |
Each address has one nonce stream. Give concurrent workers their own session keys, each with its own address, and they never block one another.
Common questions
Related
Add the network and send a transaction
The reference lists every method, the unsupported handful, and the fields in a signed receipt.