LogoLogo
  • Imua
    • About
  • Manifesto
    • The Problems
    • The Principles
  • Architecture
    • Imua Design Principles
    • Imua Network
    • Imua Modules
    • Client Chain Bridges
      • Trustless Verification of Client Chain State
      • Handling Race Conditions between Imua and Client Chains
    • Client Chain Contracts
  • Concepts
    • Ecosystem
      • Re/stakers
      • Operators
      • Services (AVS)
        • Service Integration with Imua
        • Service Committee
        • Service Integration Details
    • restaked Proof-of-Stake (rPOS)
    • Multi-Token Restaking
    • Multi-Chain Restaking with Trustless Bridging
    • Voting Power
    • Price Oracle
    • Flexible Integration with AVS
    • Tribe Staking
  • Governance
  • Risk Management
    • Risk Analysis
      • Risk Modeling
      • Risk Parameters
      • Crypto-Economic Risk
      • Unintended Slashing
      • Black Swan Events
    • Risk Mitigation
      • Smart Contract Simplicity
      • Audits
      • Slashing Prevention
      • Slashing Vetos
      • Insurance Pools
      • Circuit Breakers
  • Components
    • Testnet
    • Oracle Module
      • Reaching Consensus on Asset Prices
      • Penalty
      • Implementation Detail
    • Smart Contracts
    • Explorer
    • Registry
  • Validator Setup
    • Prerequisites
    • Node Install
    • Compiling Binary from Source
    • Oracle Price Feeder
    • Running the Node
    • Snapshot
    • Register Option 1 (Bootstrap)
    • Register Option 2 (Post Network Launch)
    • Deposit Tokens
    • Delegating Tokens
    • Confirm Election Status
    • Faucets
    • Managing The Validator
    • Security Best Practices
    • Risks & Mitigation
    • Participation in Governance
    • FAQs & Resources
  • Testnet Upgrade to v1.1.2
  • AVS Setup
    • AVS Overview
    • Prerequisites
    • Building the AVS in Imua
    • Hello-World-AVS Example
    • Becoming AVS Operator
    • AVS Register and Deploy
    • AVS Task Example
    • Enhanced and Automated Edition of hello-avs integration guide&example
  • Whitepaper (2023)
    • .pdf
  • FAQ
    • What problems is Imua solving?
    • What are the main design trade-offs that had to be made with an omnichain design?
    • Does the omnichain design imply added trust assumptions (relative to a single-chain design)?
    • What concurrency-related challenges would you face with a different design?
    • How does Imua integrate with new chains?
    • Do specific chains prove unique challenges w.r.t. integration?
    • How is the cross-chain communication is achieved?
    • What are the known attack / censorship vectors here, if any?
    • Are the restaked tokens being pooled in a centralized account?
    • Who will run the validators in the Imua network?
    • Is Imua an AVS?
    • How does Imua address the risks of overloading L1 social consensus?
    • Does the Imua queuing system raise concerns around latency?
    • What are the main benefits of an omnichain design?
Powered by GitBook
On this page
  1. Architecture

Imua Network

PreviousImua Design PrinciplesNextImua Modules

Last updated 1 month ago

The Imua protocol is built upon three primary components:

  1. Imua network - serves as the main control plane and accounting system, facilitating the restaking of tokens onto AVSs by coordinating interactions between restakers, operators, and AVSs, while also maintaining records of all pertinent data, handling the registration and management of operators and AVSs, as well as the logic for AVS integration.

  2. One-way state pegs (trustless ZK light client) - relay restaking actions from the client chain to Exocore, which in turn responds with control actions or confirmation messages.

  3. Client chain contracts - serve as endpoints deployed on each client chain, where restakers execute restaking-related actions such as deposits, delegations, and withdrawals.

The Imua network communicates with token-hosting client chains via trustless one-way state pegs. The majority of the intricate logic within the Imua restaking platform resides within the Imua network itself. With this design, Imua is able to easily integrate with new chains while minimizing the code-related risks associated with new chain integration.

The Imua network is built using a fast and secure Ethereum Virtual Machine compatible blockchain constructed using Cosmos SDK and Tendermint BFT consensus. Imua's modular design also makes it possible for AVSs to integrate with Imua via native modules. The instant finality offered by the Imua network ensures that both cross-chain communication and the interaction between AVS and Imua remain unaffected by chain forks or block rollbacks.

The EVM is the most widely adopted run-time environment and application interface in blockchain development. Imua utilizes EVM as its primary virtual machine to cater to a variety of on-chain programming requirements, including bridging, permissionless AVS integration, and the development of potential value- added DeFi applications atop Imua's restaking tokens.