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
  • Key Characteristics of the Curation Fee
  • Summary Table
  • 1. Claim Curator Fees
  • 2. Manage the Curator Fee Claimer Role
  1. Curation

Curation Fee Management

Curators can earn a fee on the restaking rewards generated by the assets deposited in Byzantine Vaults. This section details how curation fees are managed within ERC20 and native ETH vaults created using the ByzVaultParams or NativeByzVaultParams structures.

Key Characteristics of the Curation Fee

  • The curator fee is defined at vault creation in the ByzVaultParams.curatorFee field.

  • It is expressed as a percentage out of 10,000. For example:

    • curatorFee = 1000 means 10%

    • curatorFee = 2500 means 25%

Summary Table

Action
Role Required
Function

Claim curator fees

curatorFeeClaimer

claimCuratorFees()

Manage the Curator Fee Claimer Role

curatorFeeClaimerRoleAdmin

grantRole() / revokeRole()

1. Claim Curator Fees

  • Role Required: curatorFeeClaimer

  • Function to Call:

    function claimCuratorFees() external;
  • Description: The address designated as curatorFeeClaimer can claim the accrued curation fees. These fees come from the rewards generated by the restaking strategy (e.g., EigenLayer or Symbiotic) and are periodically made available to the curator.


2. Manage the Curator Fee Claimer Role

  • Role Required: curatorFeeClaimerRoleAdmin

  • Functions to Call:

    function grantRole(bytes32 role, address account) external;
    function revokeRole(bytes32 role, address account) external;
  • Description: Only the curatorFeeClaimerRoleAdmin can:

    • Assign the curatorFeeClaimer role to a new address

    • Revoke the role from an existing address

    • Renounce their admin role if needed

This role is not managed by the roleManager unlike other roles in the vault.

PreviousCross Protocol VaultNextOperators in the Byzantine ecosystem

Last updated 1 month ago

🤖