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.1
  • 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. Components

Oracle Module

The Oracle module is a fundamental component of Imua, facilitating fair and accurate pricing for standardized voting power calculations. By aggregating consensus prices from validators and offering price queries for registered asset pairs, this module underpins Imua's multi-asset restaking functionality and consensus system. Through providing the fair price of restaked assets, the Oracle module is also crucial for the smooth operation of other Imua features, such as block production, reward distribution, penalty enforcement, and AVS participant weight calculations.

The oracle module is responsible for:

  1. Reaching consensus on the canonical prices for each registered asset pair, based on prices submitted by validators through price-feed transactions.

  2. Serving price queries for each registered asset pair to other modules (e.g. Operator module) or external users.

As a multi-asset restaking platform, Imua depends on fair and accurate asset prices to normalize the weights (i.e., dollar values) of the various assets restaked on each validator. By considering the amount of each asset and its corresponding weight, Imua calculates the voting power of each validator, which is utilized in the consensus and AVS System.

Example:

Consider two validators, validator A and validator B, with the following amount of restaked assets on Imua:

  • Validator A: 30 ETH, 1 BTC

  • Validator B: 50 ETH

The Oracle module provides the ETH/USDT (e.g., 3000) and BTC/USDT (e.g., 75000) prices, enabling the system to compute the equivalent USDT value of each validator’s restaked assets. In the above example, the dollar value of restaked assets for validator A is 165,000 (30 * 3000 + 1 * 60000), while validator B has a value of 150,000 (50 * 3000). These unified dollar values determine each validator's voting power, which serves as their weight for calculating rewards and penalties within both the chain consensus and the AVS system.

PreviousTestnetNextReaching Consensus on Asset Prices

Last updated 2 months ago