Deployment guide
Last updated
Last updated
This section provides a step-by-step process for creating a Byzantine Vault. Byzantine offers both an and a to simplify vault creation and deployment.
(coming soon)
To make sure you choose the right configuration, we invite you to define beforehand some characteristics you want your vault to have.
Here is a guide to choose the configuration of vault that matches your needs.
There exist 2 major families of vaults, depending on their underlying :
In a Native vault, the staker will be able to deposit native ETH, that will be first staked on the Beacon Chain, and then restaked on a restaking protocol to secure AVSs or SSNs.
In an ERC-20 vault, a staker can deposit any ERC-20 token, including LSTs, Bitcoin derivatives, etc that is going to be restaked.
Below is a summary table indicating the required parameters for each type of vault.
, that sit on top of a single restaking protocol.
, that aggregate several restaking protocols in a single place.
Once you have chosen which vault suits you best and which parameters are expected, you will find a detailed Creation Walkthrough in the .
During the process, you will have to set a series of parameters, specific to the vault, that are described in the .
You will also have to attribute different to addresses that will be in charge of several curation tasks during vault lifecycle.