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. EigenParams
  • delegationSetRoleHolder
  • operator
  • approverSignatureAndExpiry
  • approverSalt
  • 2. EigenPodParams
  • eigenPodOwner
  • proofSubmitter
  1. Vault Creation
  2. Overview
  3. Vault Parameters

EigenLayer Parameters

This page presents the configuration parameters used to set up and configure EigenLayer integration within Byzantine Vaults. These parameters are specific to vaults that delegate their stake to operators on EigenLayer or use EigenPods to manage native validator withdrawals, depending on whether the vault is ERC20-based or native ETH-based.

There are two structs that are the required initialization parameters when deploying a Byzantine Vault with EigenLayer support :

  • EigenParams — Used for both ERC20 and native vaults that delegate their stake on EigenLayer.

  • EigenPodParams — Only used for Native Byz Vaults, enabling validator interactions via EigenPod.



1. EigenParams

Used to configure EigenLayer delegation when deploying an Eigen Byz Vault.

struct EigenParams {
    address delegationSetRoleHolder;
    address operator;
    ISignatureUtilsMixinTypes.SignatureWithExpiry approverSignatureAndExpiry;
    bytes32 approverSalt;
}

delegationSetRoleHolder

The address that manages the EigenLayer delegation for the vault.

  • This role holder can:

    • delegate the vault's stake to an operator

    • undelegate the stake

    • redelegate the stake to a different operator


operator

The address of the EigenLayer operator to delegate the vault's stake to.

  • Represents the operator running the restaking strategy.

  • It is possible to leave this unset (address(0)) at vault creation and assign an operator later.


approverSignatureAndExpiry

Optional parameter to validate that the operator approves the delegation.

  • Only used if an operator is specified and that operator has set up a delegationApprover.


approverSalt

Optional parameter used in conjunction with approverSignatureAndExpiry.

  • A unique, single-use salt tied to the signature.

  • Only needed if the operator has a delegationApprover configured.



2. EigenPodParams

Used only for Eigen Native Vaults to manage Ethereum validators via the EigenPod mechanism.

struct EigenPodParams {
    address eigenPodOwner;
    address proofSubmitter;
}

eigenPodOwner

The address of the owner of the EigenPod linked to the Native Byz Vault.

  • This address can:

    • start a pod checkpoint

    • verify validator withdrawal credentials

    • set or change the pod's proof submitter

    • recover lost ERC20 tokens from the pod contract


proofSubmitter

Optional address responsible for submitting validator proofs to the EigenPod.

  • Can:

    • start a pod checkpoint

    • verify validator withdrawal credentials

PreviousNative Vault ParametersNextSymbiotic Parameters

Last updated 1 month ago

🎛️