Elixir
  • About Elixir
  • Network Architecture
    • Validators
    • Fraud Proofs
    • Exchange Orderbook Connections
  • deUSD
    • deUSD Architecture
      • deUSD's RWA Institutional Program
      • Execution Buffer Fund
      • Centralized Exchange Execution
      • (Upcoming) Decentralized Exchange Execution
    • Addresses
    • Utility
    • Yield Calculation
    • Potion Rewards
    • Dashboard (WIP)
    • API
    • Risks
      • Smart Contract Risk
      • Custody Risk
      • Execution Risk
      • Collateral Risk
      • Regulatory Risk
  • Native Exchange Integrations
    • Building Orderbooks
    • Preventing Gamification
    • Exchange Rewards
  • The ELX Token
  • Staking / Delegation
  • Running an Elixir Mainnet Validator
  • Audits
  • Bug Bounty
  • Socials
  • FAQ
Powered by GitBook
On this page
  • Exchange Feeds
  • Data Aggregator
  • Validator Network (DPoS)
  • Relay Nodes
  • Dispute Resolution

Network Architecture

Under the hood of Elixir

Last updated 3 months ago

Elixir's modular network infrastructure is decentralized and high-throughput. The network reaches DPoS consensus for deUSD's mint/redeem mechanisms and orders placed on exchanges. Fraud proofs are posted to Ethereum mainnet, where staking and delegating flows live.

Exchange Feeds

Data Aggregator

The data aggregator collects data from multiple exchange feeds and combines them into a deterministic data frame, signs them, and broadcasts them to the validators and auditors. This piece of the Elixir tech stack enables validators to act upon accurate data related from the exchange feeds.

Validator Network (DPoS)

Elixir's validator network operates off of a decentralized proof of stake system with 66% consensus required, which is enforced at the relay node. End users delegate their stake to validators, and the top-staked validators based on stake weight will receive will receive the largest portion of validator emissions, based on a curve, for securing the network.

Relay Nodes

Relay nodes hold trading keys for individual exchanges and tally order proposal frames from the individual validators. After the order proposal has expired, it is passed to an auditor to verify correctness. Long term, API keys will be protected via SGX + Shamir's Secret Sharing within these nodes.

Dispute Resolution

The dispute resolution layer (comprised of the Auditor and Controller) works to ensure that the network is acting honestly, and to resolve any conflicts should they arise. Specifically, this layer ensures that the validators are running the market making algorithm, with properly set parameters based on the initial guidance. Furthermore, auditors also work to incentivize honest behavior from validators via a bounty, while penalizing dishonesty.

Exchange feeds hold read-only credentials for each exchange, and individually subscribe to a single update stream, broadcasting that data to the data aggregators. For more information about how Elixir connects to the central limit order books on exchanges, please take a look at the "" sub-section.

Exchange Orderbook Connections