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 v7 to v8 upgrade
  • 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. Architecture

Imua Design Principles

Security First

Good security starts with thoughtful design. The security of the system should be of utmost importance. Imua should prioritize safety over everything at both the protocol and governance levels. Protect the network.

Protocol Agnostic

In unity, there's strength. By being omnichain and protocol agnostic, Imua should extend an olive branch to all blockchain networks and ecosystems, embrace diversity in technology, and foster seamless cooperation and interoperability.

Trust Minimized

Decentralized trust does not always have to be trustless; but it should at least be trust minimized. No third-party trust assumptions should be introduced beyond the Imua protocol and basic cryptographic primitives, such as Zero Knowledge Proofs (ZKP).

Democratically Governed

Imua's network should be bootstrapped and shaped by its community. Through democratic, consensus-based governance mechanisms, every participant should have a voice in the future of Imua, ensuring adaptability and fair representation.

Permissionlessly Open

Imua should affirm an open-access ethos by allowing anyone, anywhere, to access, use, and build upon it without gatekeepers. This should foster permissionless innovation, inclusivity, and equitability.

Reasonably Decentralized

Decentralization is a progressive spectrum. Imua should be architecturally designed to be reasonably decentralized from inception. Decentralization should be an essential principle for building an open market for decentralized trust.

Modularly Pluggable

Flexibility is the foundation of resilience; hence Imua should be designed with an ever-modern, modular architecture. This should ensure constant evolution, adaptability, and an enduring relevance in the face of rapid technological change.

PreviousThe PrinciplesNextImua Network

Last updated 15 days ago