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?

Permissionless strategy vaults

The existing paradigm around restaking pools is a highly centralised one:

  1. Governance (or the core team) decides AVS / protocol mix and updates

  2. Assets are pooled into a single one-size-fits-all strategy

  3. Limited predictability of portfolio changes

Instead of relying on governance to make decisions, Byzantine is designed to leave choices up to the users. We allow anyone to create AVS strategy vaults with any AVS / protocol mix & any collateral asset and for users to interact with any deployed (open) strategy.

This flexibility is urgently necessary in an increasingly complex and fragmented space. Right now, there are no solutions for users:

  • Whose juridiction banned certain AVS

  • Who have specific requirements around risk / rewards

  • Who want their own liquidity token

  • Who want to accept specific input tokens

The vault parameters are set when it is created. They are either immutable or can be adjusted by the vault creator in the future. This means that Byzantine applies to use cases requiring either:

  • Certainty in the stability of the portfolio in the future, or

  • Trust in a dedicated entity to adapt the portfolio to market changes

It is left up to the vault creator to set immutability at launch and up to the staker to invest in vaults representing their preferred investment philosophy.

Vault risk as well as fund flows (including rewards) are fully segregated at all times.

PreviousWhat is Byzantine Finance?NextStrategy layer & infrastructure layer - Explain Like I'm 5

Last updated 29 days ago

👋