Core Architecture
Maroo's foundational design — system accounts, module authority, precompiles, and genesis configuration
Core
The Maroo application (`MarooApp`) is the core software that runs a Maroo node. It's built using the Cosmos SDK framework, providing a robus...
Maroo is built on the Cosmos SDK with CometBFT consensus, featuring a fully compatible EVM execution environment and deeply integrated compl...
The genesis configuration is a JSON file (`genesis.json`) that specifies the starting state of the Maroo network. It's the foundational blue...
Maroo registers **four core precompiles** at genesis, plus the standard set inherited from Cosmos EVM. The four Maroo-specific precompiles a...
The Maroo network utilizes several system accounts, known as module accounts, to programmatically manage tokens for core functionalities lik...
A Module Authority is a design pattern in the Cosmos SDK where sensitive, state-changing functions of a module are restricted to a single, p...
The Maroo network is maintained by a diverse set of nodes, including Validators for consensus, RPC nodes for user interaction, and specializ...
The OKRW precompile resides at the static, predictable address `0x1000000000000000000000000000000000000001`. This address is hard-coded into...
The OKRW Precompile is a specialized, gas-efficient contract at a fixed address that exposes the core minting functionality of Maroo's nativ...
OKRW is Maroo Network's native token, pegged 1:1 to the Korean Won (KRW). It serves dual purposes: as a stablecoin for value transfer and as...
Maroo's architecture is built on a robust Cosmos SDK foundation, featuring a fully compatible EVM execution environment and a deeply integra...
Static registration means the addresses and functionalities of all precompiles are defined directly in the node's source code and are availa...