Native Vault Parameters

This page describes the parameters required to initialize a Native Byzantine Vault. This struct extends the ByzVaultParams used for standard ERC20-based vaults and adds native staking-specific fields.

These additional parameters support specialized Ethereum staking scenarios such as DV Vaults, Partner Validated Vaults, or Solo Staker Vaults. For context on shared parameters, refer to the Byzantine Vault Parameters page.

NativeByzVaultParams

Additionnal struct that completes the ByzVaultParams struc, to add the native details.

struct NativeByzVaultParams {
    ByzVaultParams byzVaultParams;
    bytes32 operatorId;
    address[] validatorManagers;
}

---

byzVaultParams

Includes the full set of standard Byz Vault parameters.

• This field embeds the entire ByzVaultParams struct.

• Covers vault configuration, access roles, deposit settings, fees, metadata, and tokenization.

• Refer to the Byzantine Vault Parameters page for full details.

---

operatorId

The ID of the Node Operator responsible for handling Ethereum validator duties on behalf of 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 the Types of Native Vaults section for more details.

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

---

validatorManagers

A list of Validator Managers that will manage the Ethereum validator(s) for Solo Staker Vaults.

• This field is only used if operatorId is bytes32(0) (i.e. a Solo Staker Vault).

• Must be left empty otherwise.

• The addresses stored in this array cannot be removed once set, so they should be chosen carefully.