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. AVS Setup

Becoming AVS Operator

Node Operators in the Imua Network

Operators, comprising both individuals and organizations, serve as integral participants in the Imua Network. Upon registration, these entities facilitate the delegation of staked assets from stakeholders, including native tokens and Liquid Staking Tokens (LSTs). Subsequently, Node Operators have the opportunity to offer a diverse array of services to Active Validator Sets (AVSs), thereby contributing to the enhancement of network security and operational efficiency.

Operator Register

For operators who want to operate the AVS, they need to firstly register into the Imua Network

imuad tx operator register-operator \\
    <meta-info> \\
    <from> \\
    <commission-rate> \\
    <commission-max-rate> \\
    <commission-max-change-rate> \\
    <home> \\
    <chain-id> \\
    <keyring-backend> \\
    <fees>

where

  • <meta-info> the operator's meta info (like name).

  • <from> the sender's address which is used to approve the delegations made to the operator.

  • <commission-rate> the commission rate of the operator. It is a decimal between 0 and 1, expressed as a percentage.

  • <commission-max-rate> the maximum commission rate for the operator. It is also a decimal between 0 and 1, expressed as a percentage.

  • <commission-max-change-rate> the maximum rate of change in the operator's commission rate. It is also a decimal between 0 and 1, expressed as a percentage.

  • <home> refers to the path of Imua's node home directory.

  • <chain-id> the chain ID of the Imua network.

  • <keyring-backend> the backend type of Imua key repository. In the above example, it is set to 'test' as the backend type.

  • <fees> the fees that need to be paid in this operation.

Query Status

Verifying Registered Operator Information Status

To check the registration status of your operator, utilize the following command:

imuad query operator GetOperatorInfo <OPERATOR_ADDRESS>

For example:

imuad query operator GetOperatorInfo 0x1f9840a85d5af5bf1d1762f925bdaddc4201f984
PreviousHello-World-AVS ExampleNextAVS Register and Deploy

Last updated 3 months ago