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
  • Environment Prerequisites
  • AVS and Operators Prerequisites
  1. AVS Setup

Prerequisites

PreviousAVS OverviewNextEnhanced and Automated Edition of hello-avs integration guide&example

Last updated 3 months 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 . 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 to ensure proper functionality.

  • For a more detailed understanding of the AVS software code, you may refer to the detailed implementation in ; 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.

hello-world-avs
hello-world-avs
imua-avs-sdk