Know who answersfor each payment.
The Paxeer X chain is a BFT EVM chain where a committed block is final. LayerX activity climbs five named stages to settle on it, and each stage names who answers if it is wrong.

- Latest block
- 45,943,157
- Block time
- 333ms
- Gas price
- 0.88gwei
- Transactions today
- 139,652
- Addresses
- 36,505
- 45,943,157Paxeer EU-East Berlin V31s ago
- 45,943,156Paxeer EU-East Berlin V32s ago
- 45,943,155Paxeer EU-East Berlin V32s ago
- 45,943,154Paxeer EU-East Berlin V32s ago
Running now.
Blocks from the Paxeer X chain as Paxscan records them. Once a block is committed it is final: no confirmations to count and no reorganizations.
- Consensus
- CometBFT
- Chain ID
- 125
- Execution
- go-ethereum EVM
- Final at
- Commit
Transactions in a block execute in parallel. A differential suite replays them one by one to prove the results match.
Open Paxscan(opens in a new tab)Five stages from receipt to settled.
A LayerX activity is not declared final at once. It climbs a ladder, and each stage names the party that answers for its claim.
- L0
Accepted
The sequencer orders the activity into the current batch and signs a receipt chained to the state root.
Answers for it: Sequencer
- L1
Sealed
A signed batch header fixes the order and commits to every activity, receipt and event in it.
Answers for it: Replicas
- L2
Distributed
The sealed batch and its data-availability bundle go out to the guarantor quorum.
Answers for it: Data availability
- L3
Attested
Bonded guarantors re-execute the batch and sign only if their result is byte-identical.
Answers for it: Guarantor bonds
- L4
Settled
The checkpoint lands on the Paxeer X chain and is final once the challenge window passes.
Answers for it: Paxeer X custody
Ask for the evidence you need.
A submission names the commitment it requires. The gateway returns that evidence or refuses. It never hands back a weaker success.
- executed
- A verified receipt signed by the sequencer.
- batched
- Adds proof that the receipt is included, byte for byte, in a signed batch.
- finalised
- Adds the checkpoint whose header matches that batch exactly. A newer head is never substituted.

lx_sendActivity commitment finalised
error -32001 Requested commitment unavailable
state pending the checkpoint is not final yet
lx_getActivityStatus 0x9c4e…a1f0
commitment finalised
batch evidence checkpoint evidence verified
Recover a pending activity with lx_getActivityStatus and lx_getReceipt instead of sending it again.
Questions about the network.
The limited beta runs one active sequencer and a small guarantor set. These answers say what that covers and what it does not.
How fast is Paxeer X?
Fast enough that a calling agent does not wait: LayerX orders an activity and returns a signed receipt straight away, and settlement follows at the next checkpoint. Paxeer X does not publish throughput figures it has not measured. Figures in the repository are labelled measured, configured or targeted.
Is LayerX decentralized today?
Not yet in full. The limited beta runs one active sequencer and a small guarantor set that is not yet operationally independent. Guarantor attestation is an economic guarantee backed by bonds, not a validity proof, and the network says so plainly.
What if LayerX stops?
LayerX never holds the money. The Paxeer X chain does, and pays withdrawals only against proof. If checkpoints stop arriving within the liveness bound, a holder proves a balance under the last finalized state root and exits without LayerX.
Can I run a node?
The paxd binary runs validator, full, seed and archive modes from one flag. LayerX roles, from sequencer and replica to guarantor, relay and archive, run from the layerxd daemon.
How is the network upgraded?
Through on-chain governance. A software upgrade passes by proposal and halts the chain at a set height, operators swap the binary, and the chain resumes. LayerX parameters are bounded and can be paused.
Where can I see what is happening?
On Paxscan, the Paxeer X explorer at paxscan.io. It is a Blockscout fork that adds LayerX receipts, checkpoint anchors and the settlement stage each transaction has reached.
Follow one request to the end.
Read the architecture in the docs, then send a first activity and trace it from receipt to checkpoint.
