Eigen Native Vault
TODO
Not live yet
This flow is for launching vaults that accept native ETH as collateral, including DV, Partner Validated, or Solo Staker Vaults.
1. Determine the type of Native Vault you want
Choose the type of Native Vault you want, based on how you want the staking validation to be handled. there are 3 types of vaults :
Solo Staker Vault
Partner Validated Vault
Distributed Validator Vault
2. Construct the NativeByzVaultParams struct
You must populate:
byzVaultParams
: Same structure as for the Eigen ERC20 Vault creation.operatorId
: The value corresponds to the hashed identifier of the type of vault you have chosen in section 1:hash("distributed.validator.vault")
for DV Vaultshash("company.name")
for Partner Validated Vaultsbytes32(0)
for Solo Staker Vaults
validatorManagers
: Required only for Solo Staker Vaults. Addresses of validator managers. Cannot be changed after creation.
3. Configure EigenParams struct
4. Prepare EigenPodParams struct
Set the following:
eigenPodOwner
: Controls pod checkpoints and withdrawal credentialsproofSubmitter
: (optional) Can submit withdrawal proofs
5. Call the Factory
Call the following function from the Byzantine Factory with your parameters:
Once called, the factory:
Deploys a proxy contract for the native ETH-compatible vault
Initializes the vault with the provided configuration
Configures delegation and pod interaction with EigenLayer
✅ The function returns the new vault address. You can now deposit native ETH.
Last updated