Byzantine Finance
Website - Home🖥️ For Developers
  • 👋Introduction
    • What is Byzantine Finance?
      • Permissionless strategy vaults
      • Strategy layer & infrastructure layer - Explain Like I'm 5
      • Architecture Overview
    • Explanation of terms
    • Restaking explained
  • Media kit
  • 🔑Byzantine Vaults
    • What are Byzantine vaults?
    • Features of Native Vaults
      • Byzantine Oracle
      • Best practices for Validator Managers
    • Types of Native Vaults
      • Solo Staker Vaults
      • Partner Validated Vaults
      • Distributed Validator Vaults
  • ↔️Vault Interaction
    • Deposit
      • Deposit to ERC20 Vaults
      • Deposit to Native Vaults
    • Withdraw
      • Withdraw from ERC20 Vaults
      • Withdraw from Native Vaults
    • Claim Rewards
      • Restaking Rewards
        • EigenLayer Rewards
        • Symbiotic Rewards
  • 🎛️Vault Creation
    • Overview
      • Vault Configuration Guide
      • Vault Parameters
        • Byzantine Vault Parameters
        • Native Vault Parameters
        • EigenLayer Parameters
        • Symbiotic Parameters
      • Roles
    • Single Protocol Vaults
      • EigenLayer Vault
        • Eigen ERC20 Vault
        • Eigen Native Vault
      • Symbiotic Vault
        • Sym ERC20 Vault
        • Sym Native Vault
    • Cross Protocol Vaults
      • Eigen Layer / Symbiotic ERC20 Vault
  • 🤖Curation
    • Overview
    • Curator Related Roles
    • Vault Management
    • Strategy Management
      • EigenLayer Strategy
      • Symbiotic Strategy
      • Cross Protocol Vault
    • Curation Fee Management
  • 🌐Node operators
    • Operators in the Byzantine ecosystem
    • Register as a Staking Operator
    • Staking
    • Restaking Operator
      • Symbiotic
      • EigenLayer
      • Allocation to existing Restaking Operators
      • Creation of on-demand Restaking Operators
  • Claiming DV operator fees
Powered by GitBook
On this page
  1. Introduction
  2. What is Byzantine Finance?

Architecture Overview

PreviousStrategy layer & infrastructure layer - Explain Like I'm 5NextExplanation of terms

Last updated 29 days ago

Byzantine Architecture involves several components/entities (from left to right):

  • The Restaker: User providing liquidity into a Byzantine Vault to secure Ethereum as well as one or multiple AVSs/networks. Restakers are rewarded in tokens by the networks for the security they provide.

  • Byzantine front-end: The Byzantine dApp allows creating new Byzantine vaults and depositing into (or withdrawing from) it.

  • Partner's front-end: A partner's platform or dApp that allows Byzantine Vault creation, interaction and curation through the Byzantine SDK, usable permissionlessly.

  • Byzantine Vaults: The central piece of the architecture. ByzVaults can be created permissionlessly and for any strategy or desired risk level. A ByzVault has a dedicated restaking strategy that can be adjusted at any time by the defined curators.

  • The Curator (optional, can be the Vault creator themselves): In charge of rebalancing and managing the vault strategy.

  • The Node Operators: Entities operating Staking Validators (on Ethereum) and/or Restaking Operators (on the AVSs/networks). The method by which Validators are associated with Native Vaults depends on the creator's node operator selection (see the ).

  • The Restaking Protocols: Ecosystems of Proof-of-Stake networks (known as AVSs on Eigen Layer, networks on Symbiotic, BSNs on Babylon, NCNs on Jito, ...) seeking economic shared security and rewarding the restakers.

👋
types of Native Vaults