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
    • Enhanced and Automated Edition of hello-avs integration guide&example
    • Building the AVS in Imua
    • Hello-World-AVS Example
    • Becoming AVS Operator
    • AVS Register and Deploy
    • AVS Task 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. Components

Testnet

PreviousCircuit BreakersNextOracle Module

Last updated 3 months ago

The code for the Imua network has been open-sourced and is available at .

Imua is designed to support the restaking of tokens from all supported chains to various AVSs. To achieve this, the fundamental architecture framework and the main business logic of the core modules has been developed and implemented. A cluster of nodes has been deployed to serve as Imua network validators and integrated with Ethereum Sepolia testnet as the first client chain.

As the primary accounting system for restaking, the most complex logic is maintained within the Imua network. This approach is designed to enable rapid expansion to new client chains while minimizing the risks associated with smart contract code during the integration process with new chains.

Imua Testnet will be released in three different phases:

Phase 1 - Operators

  • Imua network running with external operators

  • Restaking with native ETH support

  • AVS integration features added

Phase 2 - Restakers

  • Imua network running on public nodes

  • Client-chain smart contracts deployed

  • Restaking Dapp with LST support and the following modules:

    • Deposit

    • Withdrawal

    • Delegate

    • Undelegate

  • Explorer live

Phase 3 - AVSs

  • AVS onboarding with slashing conditions

To facilitate connections between the client chain and AVSs, and to accurately record corresponding statuses, such as asset and operator information, the following modules have been developed and released in Imua Testnet phase 1:

  1. Deposit

  2. Withdrawal

  3. Delegation

  4. Undelegation

Imua GitHub repository