Paxeer EVM vs Ethereum: Key Differences

While Paxeer features full EVM compatibility, there are some distinctions between Paxeer's EVM and Ethereum itself:

• Paxeer's Twin Turbo consensus combined with machineRFT delivers ~250ms block times and instant finality - a transaction is final as soon as its block is committed.
• Paxeer achieves 5000 TPS throughput, far exceeding Ethereum's capacity.
• The various commitment levels typical for Ethereum (i.e., safe, latest, justified, finalized) do not apply on Paxeer - all confirmed transactions are final.

Opcode Differences

PREVRANDAO

Since Paxeer uses Twin Turbo consensus with machineRFT rather than Proof of Stake, it doesn't have the "randomness" artifact that can be set as PREVRANDAO's return value. On Paxeer, PREVRANDAO returns a value derived from the current block time. For strong randomness needs in contract logic, use a verifiable randomness oracle (as is advised on Ethereum itself).

COINBASE

Coinbase address on Paxeer is always set to (the EVM address of) the global fee collector.

State Root

Paxeer uses an AVL-tree for data storage instead of Ethereum's Merkle Patricia Trie (MPT). The global state root is the AVL-tree root, which is not equivalent to Ethereum's MPT-based state root.

Block Hash

The block hash on Paxeer is computed based on the block header in the native consensus format and differs from Ethereum's block hash format.

Base Fee & Tips

Paxeer supports standard EVM transaction types. Query the live gas price with eth_gasPrice rather than hard-coding it. Excess gas beyond actual usage may not be fully refunded.

Current EIP-1559 parameters can be fetched from the paxd CLI:

paxd q params subspace evm KeyTargetGasUsedPerBlock

key: KeyTargetGasUsedPerBlock
subspace: evm
value: '"850000"'

paxd q params subspace evm KeyMaxDynamicBaseFeeUpwardAdjustment

key: KeyMaxDynamicBaseFeeUpwardAdjustment
subspace: evm
value: '"0.007500000000000000"'

Finality

Paxeer has instant finality - a transaction is final as soon as its block is committed (~250 ms) - meaning that commitment levels of "safe", "latest", "justified", and "finalized" on Ethereum are all the same thing on Paxeer.

Pending State

On Ethereum the block proposer would execute its proposed block first (and update its local state) before broadcasting the proposal to others (the updated state would be marked "pending" until the node is accepted by other nodes).

On Paxeer, the block proposer broadcasts first and only executes the proposal if it's accepted (i.e., every node executes the block at roughly the same time), so Paxeer does not have a window when "pending state" exists.

Gas Model & Fees

Paxeer does not implement base-fee burning. All transaction fees accrue to validators. Fees are calculated as:

Transaction Fee = Gas Used x Gas Price

Practical implications

• Simpler fee handling: Use gasPrice (you can omit maxFeePerGas / maxPriorityFeePerGas).
• More stable fees: Higher throughput reduces fee spikes during busy periods.
• Typically lower cost: Many workloads that are costly on Ethereum become economical on Paxeer.

ERC Token Standards Compatibility

Paxeer's EVM fully supports the common token standards:

• ERC-20 (fungible tokens)
• ERC-721 (NFTs)
• ERC-1155 (multi-token)

Existing OpenZeppelin contracts and tools work unchanged.

Testing & Migration Checklist

• Re-deploy your Solidity code to Paxeer; most contracts need no changes.
• If you used SELFDESTRUCT, refactor to a soft-close pattern.
• Remove EIP-1559 fee UI complexity; use a single gasPrice input in frontends.
• If you rely on on-chain "randomness," integrate an oracle/VRF.
• Size your gasLimit with a modest buffer (parallel execution can slightly vary estimates).