Integra
Home/Architecture

How Integra Works

Integra is a dual-stack blockchain combining the Cosmos SDK with a fully compatible EVM module, powered by CometBFT consensus for instant finality and cross-chain interoperability.

Dual-Layer Architecture

Cosmos SDK + EVM connected via stateful precompile bridges

CosmosEVMBridge
Cosmos SDK LayerNative modules
CometBFT
New for EVM devs:BFT consensus engine with instant finality, no reorgs. Replaces PoW mining.
Staking
New for EVM devs:Delegated Proof-of-Stake. Validators stake IRL tokens; delegators earn rewards.
Governance
New for EVM devs:On-chain proposals and voting. Token holders vote on upgrades. Like a built-in DAO.
Distribution
New for EVM devs:Auto-distributes block rewards and fees to validators and delegators.
IBC
New for EVM devs:Inter-Blockchain Communication. Native cross-chain transfers without bridges.
Bank
New for EVM devs:Native token transfer module. Handles all IRL transfers at the protocol level.
EVM LayerEthereum compatible
Solidity Contracts
ERC-20 / 721 / 1155
ethers.js / web3.js
MetaMask
JSON-RPC
Hardhat / Foundry
Precompile BridgeCall Cosmos modules from Solidity via special addresses
0x0800Staking
0x0801Distribution
0x0900Governance

Precompiles are native contract interfaces compiled into the chain binary — not deployed bytecode. They execute at the consensus level with direct module access.

Transaction Flow

1
User
2
EVM JSON-RPC
3
AnteHandler
4
CometBFT
5
State Commit
6
EVM Execution

Dual Addressing

Every account has one private key that derives both address formats. The same key maps to integra1... (Cosmos bech32) and 0x... (EVM hex). Transactions on either side affect the same balance.

High-Level Architecture
Four-layer stack from consensus to application
Application Layer

dApps, Smart Contracts, RWA Protocols

User-Facing
EVM Module

Solidity execution, JSON-RPC, EIP compatibility, 0x addresses

Execution
Cosmos SDK

Staking, Governance, IBC, Bank, Auth modules

Framework
CometBFT Consensus

Block production, instant finality, Byzantine fault tolerance

Consensus
Dual Execution Environment
Integra supports both EVM and native Cosmos execution paths

Smart Contracts

Write contracts in Solidity and deploy with standard Ethereum tooling.

Developer Tools

Full compatibility with Hardhat, Foundry, Remix, and other Ethereum dev frameworks.

JSON-RPC

Standard Ethereum JSON-RPC API for wallets and dApps (eth, net, web3, debug, txpool).

Address Format

Standard 0x addresses compatible with MetaMask and all EVM wallets.

View API Reference
Address Interoperability
One key, two address formats

Every account on Integra has both an EVM-style 0x address and a Cosmos-style integra1... address. Both are derived from the same underlying secp256k1 private key, so they represent the exact same account.

EVM Format

0x5551ff857fc71597511c...

Cosmos Format

integra124gllptlcu2ew5gux...

Convert between formats
Consensus & Finality
CometBFT provides deterministic, instant finality

~5s

Block Time

Instant

Finality

DPoS

Consensus Type

Unlike Ethereum's probabilistic finality (which requires multiple block confirmations), CometBFT provides instant finality -- once a block is committed, it is final. There are no reorgs, no uncle blocks, and no need to wait for confirmations. This is achieved through a Delegated Proof-of-Stake (DPoS) model where validators vote on each block in a Byzantine fault tolerant consensus process.

Token Economics
IRL is the native token of Integra
Display Denomination

IRL

Used in wallets, staking, and governance

Base Denomination

airl

On-chain unit (1 IRL = 1018 airl)

Gas Model

Integra uses minimal gas fees (~1 gwei). Transactions require gas limits and a small fee to prevent spam.

Staking Rewards

Validators and delegators earn IRL rewards for securing the network through DPoS staking.

State Storage
How EVM state is stored within the Cosmos SDK framework

Integra uses a CommitStateDB backed by Cosmos SDK KVStores rather than Ethereum's Merkle Patricia Trie. This means EVM state (accounts, contract storage, code) is stored natively in the Cosmos IAVL tree.

Transaction Execution

EVM transactions run on a geth-forked execution engine. The resulting state changes are written back to the Cosmos SDK KVStore.

Gas Handling

The EVM computes its own gas usage, but the final gas value is overwritten by the Cosmos SDK gas meter to ensure consistency across both execution paths.

Chain ID Format
Integra uses a dual chain ID system

The chain has two distinct chain ID formats depending on which interface you are using. Both refer to the same network. The Cosmos chain ID follows the format identifier_EIP155-version, where the EIP-155 number is immutable and the version is incremented on chain upgrades.

Cosmos Chain ID

integra-1

Used by intgd CLI, CometBFT RPC, and Cosmos SDK operations. The version suffix is incremented on chain upgrades.

EIP-155 Chain ID

26217 (0x6669)

Used by MetaMask, ethers.js, and all EVM tooling. This number is immutable and never changes.

Network Parameters
Current connection details for Integra Mainnet
Cosmos Chain IDintegra-1
EVM Chain ID26217 (0x6669)
Cosmos RPChttps://mainnet.integralayer.com/rpc
EVM JSON-RPChttps://mainnet.integralayer.com/evm
REST APIhttps://mainnet.integralayer.com/api
WebSocketwss://mainnet.integralayer.com/ws
Explorerhttps://explorer.integralayer.com
Native Denomairl (IRL)
What Makes Integra Different
Key differentiators from other L1 blockchains

RWA Focus

Purpose-built for Real World Asset tokenization with compliance-ready infrastructure and precision handling for financial instruments.

Cosmos IBC Interop

Native Inter-Blockchain Communication protocol enables trustless asset transfers and messaging across the entire Cosmos ecosystem.

EVM Dev Tooling

Full Ethereum tooling support means existing Solidity contracts, Hardhat scripts, and dApps can deploy on Integra with minimal changes.

Instant Finality

CometBFT consensus delivers deterministic finality in ~5 seconds with no reorgs, unlike Ethereum's probabilistic confirmation model.

Learn about RWA Developer Guide