EVM Configuration
EIP-1559–compatible BaseFee fee market with OKRW (aokrw) gas, plus static precompiles registered at genesis.
Maroo's execution environment is a Cosmos SDK chain with an EVM module (x/vm) plus a fee market module (x/feemarket). The fee market is configured as EIP-1559–compatible with BaseFee enabled — senders pay both a base fee and a priority tip, denominated in OKRW (chain unit aokrw). Standard EVM tooling (Hardhat, Foundry, ethers.js) works without modification; gas estimation and fee suggestion behave the same way as on Ethereum mainnet, with the only difference being the gas token (OKRW instead of ETH).
Fee Market — EIP-1559 BaseFee
The
Tooling implication:
x/feemarket module manages the dynamic base fee per the EIP-1559 algorithm. Senders submit transactions with maxFeePerGas and maxPriorityFeePerGas; the chain charges min(maxFeePerGas, baseFee + maxPriorityFeePerGas) and burns the base-fee portion (priority tip goes to the validator). Both components are accounted in aokrw, so cost is predictable in KRW units.Tooling implication:
eth_gasPrice, eth_feeHistory, and eth_maxPriorityFeePerGas all return values consistent with EIP-1559. Hardhat and Foundry's default fee estimation will produce correct numbers — no special configuration required.// ethers.js — works exactly like on Ethereum mainnet
const feeData = await provider.getFeeData();
// feeData.gasPrice, feeData.maxFeePerGas, feeData.maxPriorityFeePerGas
// all populated; values are in aokrw (10^18 aokrw = 1 OKRW)Static Precompiles
Maroo registers four core precompiles at genesis: OKRW, PCL, EAS, and Agent. Each lives at a fixed, predictable address and exposes a Solidity-callable interface for chain-level functionality (stablecoin operations, compliance enforcement, attestation queries, agent identity indexing). See
maroo-precompiles for the full enumeration.Differences from Ethereum Mainnet
Beyond the gas token, two intentional differences a developer should know:
1. Compliance pre-screening — transactions hitting the Regulated Path (
2. Identity primitives — KYC/KYB attestations are queryable on-chain via the EAS precompile; agent identity (KYA, ERC-8004) via the Agent precompile. There is no equivalent on Ethereum mainnet.
1. Compliance pre-screening — transactions hitting the Regulated Path (
runOnPcl opt-in) are evaluated by PCL before EVM execution. A transaction that would succeed on Ethereum may revert here with a structured ReasonCode. See pcl-overview.2. Identity primitives — KYC/KYB attestations are queryable on-chain via the EAS precompile; agent identity (KYA, ERC-8004) via the Agent precompile. There is no equivalent on Ethereum mainnet.