
One binary, four node modes
Validator set and node operation
Validator, full, seed and archive profiles written by one init flag on the paxd binary.
You pick a mode at paxd init --mode validator|full|seed|archive, and it writes the config.toml, app.toml and EVM RPC settings that match. Validator and seed hosts start with the REST API, gRPC, state store and EVM RPC off, full nodes keep 100,000 blocks, and archive prunes nothing. During an incident you change logger levels on a running node with paxd log level set, over an admin service that only accepts a loopback address.
What it does
paxd is the node binary for the Paxeer chain, the EVM base layer at chain ID 125 (Cosmos chain ID hyperpax_125-1). It runs in four operating modes: validator, full, seed and archive. paxd init --mode <mode> writes the config.toml, app.toml and EVM RPC settings that match the chosen mode, so a validator host exposes nothing a validator does not need and a query host exposes everything a query host does. Operators run it under systemd, and a loopback-only admin gRPC service lets them change log levels on a running node without a restart. Consensus is CometBFT, so the active validator set is the CometBFT set and its voting powers are read from any synced node's RPC.
Key capabilities
- Four modes from one binary: validator, full, seed and archive;
fullis the default. - Validator and seed modes disable the REST API, gRPC, gRPC-web, state store and EVM RPC.
- Full nodes keep 100,000 blocks of history; archive nodes prune nothing.
- Seed mode raises the P2P connection limit to 1,000 and allows duplicate peer IPs.
paxd log level set|get|listchanges logger levels at runtime over a loopback admin service.- Upgrades halt by height only, through the governance upgrade plan, and resume after a binary swap.
Who it's for
Validator operators and anyone running a full, seed or archive node on Paxeer X.
Why it matters
One binary and one flag produce the right configuration for each job, so an operator does not hand-assemble the service, pruning and RPC settings per host. Validator hosts start with their query surfaces off rather than needing them switched off afterwards, and log levels can be raised during an incident without restarting a node that is signing blocks.
Differentiators
Archive is a fourth mode added on top of CometBFT's validator, full and seed set: it takes the full-node CometBFT configuration but sets state-store keep-recent and min-retain-blocks to 0. min-retain-blocks also drives receipt-store retention, so block and receipt history stay aligned without a second setting. Runtime log control is exposed only on a loopback address, and a non-loopback admin_address is rejected rather than accepted.
Outcomes
- Provision each host from one flag, not hand-assembled config files.
- Keep query surfaces off on validators from the first start.
- Raise log levels without restarting a node that is signing blocks.
Technical notes
- Mode is chosen at
paxd init --mode validator|full|seed|archive; an unknown value is rejected. Archive is written as CometBFT modefulland differs in app config only. - Validator and seed keep the loopback defaults for CometBFT RPC (
127.0.0.1:26657) and P2P (127.0.0.1:26656); full and archive bind both to0.0.0.0. Validators set the tx indexer tonull, full and archive tokv. - Full nodes set state-store keep-recent and
min-retain-blocksto 100,000; archive sets both to 0. Validator and seed modes turn the state store off entirely. - The admin gRPC server is off by default (
admin_server.admin_enabled = false) and listens on127.0.0.1:9095. When enabled it must be a loopback IP: a hostname or a routable address fails validation at startup. - Consensus timeouts are on-chain consensus params (
baseappsubspace,TimeoutParams), so they change by a param-change proposal, not by editingconfig.toml. - Every consensus key must map to exactly one host and one node home; a key present in two homes double-signs. After a coordinated halt, consensus resumes only once validators holding more than two thirds of the voting power are back up.
- The node image builds
paxdfor the target architecture and needslibwasmvm,libwasmvm152andlibwasmvm155, fetched per architecture fromnode.hyperpaxeer.comand checked against pinned SHA-256 digests. - The repo sets no validator count, minimum self-stake or hardware floor for Paxeer validators; the staking module's
max_validatorsis a chain param read at runtime, not a value this repo fixes.
paxd init <moniker> --chain-id hyperpax_125-1 --mode validator # validator profile
paxd init <moniker> --chain-id hyperpax_125-1 --mode archive # keeps all history
paxd start
paxd log level list modules/evm # loggers and their levels
paxd log level set 'modules/evm/*' debug # glob, or "*" for all loggers
paxd log level get modules/evm/stateMore in Network
Staged finality ladder L0 to L4
Five finality steps, each with a liable party
ExploreBonded guarantors with slashing
Bonded operators re-execute every batch
ExploreCross-domain precompile connector
Verify LayerX evidence inside an EVM call
ExploreData availability commitments and challenges
Prove the data behind a state root
ExploreBuild on Paxeer.
Give your agent a wallet, set its policy, and settle your first call on LayerX.