Native Vault Parameters

This page describes the parameters required to initialize a Native Byzantine Vault.

This data structure extends the ByzVaultParams used for standard ERC20-based vaults and adds native specific fields.

These additional parameters support specialized Ethereum staking scenarios such as DV Vaults, Partner Validated Vaults, or Solo Staker Vaults. You can refer to this section if you want to understand the differences between the types of native vault.

NativeByzVaultParams

Parameter	Type
byzVaultParams	ByzVaultParams
operatorId	bytes32
soloStakingFee	number
validatorManagers	address[]

Breaking down the parameters

byzVaultParams

This field embeds the entire ByzVaultParams struct. Refers to the Byzantine Vault Parameters page for full details.

---

operatorId

The ID of the Node Operator responsible for handling Ethereum validators tied to the Native vault.

• The value corresponds to a hashed identifier:

  • hash("distributed.validator.vault") for DV Vaults

  • hash("company.name") for Partner Validated Vaults

  • bytes32(0) for Solo Staker Vaults

  You can refer to this section if you want to understand the differences between the types of native vault.

• For more detail on how operator IDs are defined and managed, see the OperatorRegistry contract.

---

soloStakingFee

The solo staker fee taken from the vault's accrued staking rewards (in percentage).

• Only enforced for Solo Staker Vault, when the Ethereum validation work is not outsourced by a Byzantine Partner - when operatorId is set at bytes32(0).
• Can be set to 0 if not a Solo Staker Vault.

• Expressed in basis points:

  • 500 represents 5%,

  • 10_000 represents 100%

---

validatorManagers

A list of Validator Managers that will manage the Ethereum validator(s) tied to the Native vault.

• Only enforced for Solo Staker Vault, when the Ethereum validation work is not outsourced by a Byzantine Partner - when operatorId is set at bytes32(0).

• Can be set as an empty array if not a Solo Staker Vault.

• The Validator Manager list can be managed by the roleManager (if any)