Network Parameters
Core constants and identifiers that define the Maroo network, including chain IDs, denominations, and address prefixes.
Maroo's network parameters are the predefined constants that wallets, explorers, and dApp code need to interact correctly with the chain — Chain ID for replay protection on transaction signatures, token denominations, and the Bech32 prefixes used for validator / governance addresses. The numeric values here are stable across the V1 testnet; resolve any chain-specific overrides through the JSON-RPC eth_chainId and module params.
Chain ID
Maroo uses a different Chain ID per environment to prevent transaction replay across networks.
Verify at runtime via the
- Mainnet:
815 - Testnet:
450815
Verify at runtime via the
eth_chainId JSON-RPC method — clients should never hard-code a single value.Token Denominations
The network uses several denominations. On Maroo Testnet (
These values are measured from the live chain; read the gas denom at runtime when you can (
maroo-testnet-1):tokrw(display, symbol tOKRW): the user-facing unit of the testnet's OKRW. Test tokens have no monetary value.atokrw(chain denom): the base unit used on-chain, like 'wei' on Ethereum (astands for 'atto'): 1 tOKRW = 10¹⁸ atokrw. It is the native gas token, the x/okrw mint denom and the governance-deposit denom, and on the EVM side 1 wei = 1 atokrw.atmaroo(bond denom): the staking token. Validators and delegators bondatmaroo; bank transfers of it are disabled.
These values are measured from the live chain; read the gas denom at runtime when you can (
/cosmos/evm/vm/v1/params → evm_denom). maroo's source defaults — okrw / aokrw / amaroo, what a freshly initialised node uses — are not what the testnet runs. OKRW itself is designed as a KRW-pegged stablecoin (1 OKRW = 1 KRW).Address Prefixes (Bech32)
Maroo uses the Bech32 address format for non-EVM identifiers (validators, governance), providing checksums to prevent typos. The base prefix is
Most dApp code uses the EVM
maroo.- Account Address:
maroo1... - Validator Operator Address:
maroovaloper1... - Consensus Node Address:
maroovalcons1...
Most dApp code uses the EVM
0x… form throughout — Bech32 only matters when interfacing with validator-query / governance endpoints.HD Wallet Path
For Hierarchical Deterministic (HD) wallets like MetaMask, Maroo uses the standard BIP-44 coin type for Ethereum-compatible chains.
This means existing Ethereum derivation paths (
- Coin Type:
60
This means existing Ethereum derivation paths (
m/44'/60'/0'/0/i) work unchanged — no Maroo-specific wallet integration required.