LogoLogo
  • Imua
    • About
  • Manifesto
    • The Problems
    • The Principles
    • .pdf
  • Whitepaper
    • Abstract
    • The Problem
    • Exocore Restaking
      • restaked Proof-of-Stake (rPOS)
      • Multi-Token Restaking
      • Multi-Chain Restaking with Trustless Bridging
      • Flexible Integration with AVS
      • Union Restaking Among AVS
    • Related Work
      • Proof of Stake
      • Liquid Staking Token
      • EigenLayer
      • Babylon
      • Cosmos
      • Other Restaking Endeavors
      • TrustBoost
    • Exocore System Architecture
      • Exocore Design Principles
      • Exocore Network
      • Exocore Modules
      • Client Chain Bridges
        • Trustless Verification of Client Chain State
        • Handling Race Conditions between Exocore and Client Chains
      • Client Chain Contracts
    • Exocore "Exosystem"
      • Restakers
      • Operators
      • Actively Validated Services
        • AVS Integration with Exocore
        • AVS Committee
        • AVS Integration Details
    • Restaking Mechanism
      • rPOS Operations
      • Multi-Token Restaking
      • Voting Power Calculation
      • Exocore Price Oracle
      • Union Restaking
    • Open 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
    • Potential Applications
      • Bridges
      • Oracles
      • App Chains
      • RPC Networks
      • Sequencers
      • Consensus Protocols
    • References
    • .pdf
  • 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 v7 to v8 upgrade
  • 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
  • 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
  • Environment Prerequisites
  • AVS and Operators Prerequisites
  1. AVS Setup

Prerequisites

PreviousAVS OverviewNextBuilding the AVS in Imua

Last updated 27 days ago

Environment Prerequisites

Here are the environment prerequisites for integrating external AVSs with Imua.

The integration involves two key components:

  • The Imua on-chain AVS smart contract. To begin, it's necessary to develop a customized AVS smart contract based on the provided Solidity smart contract template within hello-world-avs. This requires a Solidity environment version 0.8.17 or higher for contract deployment.

  • The Imua off-chain AVS client software, which facilitates interaction with the Imua Networks for AVS Service. It is necessary to install, build, and run the AVS client software hello-world-avs to ensure proper functionality.

  • For a more detailed understanding of the AVS software code, you may refer to the detailed implementation in imua-avs-sdk; the hello-world-avs project relies on this as a dependency.

AVS and Operators Prerequisites

The AVSServiceContract.sol and IAVSManager.sol contracts should be deployed on the Imua chain, similar as following:

The precompiled contract efficiently manages all essential functions for onboarding preparation, facilitating support for EVM transactions. Such as:

  • As the AVS need to choose the operator that they want to register, so the according operators must register into the Imua network.

  • The AVS should be aware by Imua network, so the AVS must register with Imua chain.

  • Tasks must be defined for the AVSs on the Imua chain to facilitate future on-chain task verification, reward, and other operational purposes.