Page cover

Blockchain Architecture

These values represent the initial mainnet configuration. Testnet deployments may use different parameters to facilitate experimentation, and all network settings remain subject to adjustment through on-chain governance.

Network Architecture

  • Framework: Cosmos SDK

  • Execution Layer: Ethermint EVM

  • Consensus: CometBFT (Byzantine Fault Tolerance)

  • Native Token: IRL (denom: irl, 18 decimals)

  • Core Modules: Asset Passport, Global Orderbook, Compliance, Staking, Native Stablecoin, Governance

  • Interfaces: Ethereum JSON-RPC, WebSocket, Cosmos RPC, REST, gRPC

Consensus & Validator Set

Integra uses a Delegated Proof-of-Stake (DPoS) model:

  • Active validator set: up to 100 validators

  • Bonding denom: IRL

  • Minimum self-delegation: 1 IRL

  • Unbonding period: 21 days

  • Block time: ~6 seconds

  • Finality: deterministic BFT finality at block commit, assuming less than one-third of voting power is Byzantine; in normal operation, committed blocks are not reverted.

Validators produce blocks, participate in consensus, and enforce network security. Delegators stake IRL to validators and share rewards and governance rights.

Slashing, Liveness & Security Parameters

To maintain integrity and reliability, Integra enforces strict slashing rules:

  • Signed-blocks window: 100 blocks

  • Minimum signed per window: 50%

  • Jail time for downtime: 10 minutes

  • Slash for downtime: 1% of stake

  • Slash for double-signing: 5% of stake

These values may evolve, but they reflect a production-ready, institutional-grade configuration.

Developer Environment

  • Solidity 0.8+ support

  • Full compatibility with Hardhat, Remix, ethers.js, web3.js

  • MetaMask support

  • Gas estimation compatible with EVM standards

  • Faucet & devtools available for testing environments

For stable validator operation:

  • CPU: 4+ cores

  • RAM: 8+ GB

  • Storage: 500+ GB SSD

  • Network: 100+ Mbps

  • OS: Linux (Ubuntu 20.04+ recommended)

Validators should follow strict security practices: HSM-backed key management, sentry-node topology, hardened firewall rules, VPN-restricted access, and continuous monitoring.

Last updated