Symbiotic Parameters
This page outlines the parameters required to initialize a Symbiotic Byzantine Vault. These parameters enable the configuration of key Symbiotic modules: the BurnerRouter, the Vault, the Delegator, and the Slasher.
These parameters are specific to the Byzantine vaults that delegates their stake to operators and networks on Symbiotic.
SymParams
This data structure is the main container used to initialize a Sym Byz Vault. It aggregates the configuration for all Symbiotic modules: burner, vault, delegator, and slasher.
BurnerParams
This data structure defines the settings of the BurnerRouter contract tied to the vault. It configures where the slashed funds will be sent after a Symbiotic operator get slashed.
address
number
address
NetworkReceiver[]
OperatorNetworkReceiver[]
You can notice there are three different receivers in the router. Each of them have a different level of priority (1 being the highest) depending on the network and the slashed operator:
More details can be found here.
Breaking down the parameters
VaultParams
This data structure defines the settings of the Symbiotic Vault contract tied to the Byzantine Vault. It specifies ownership, implementation version, and epoch configuration for the Symbiotic vault.
number
number
Breaking down the parameters
DelegatorParams
This data structure defines the settings of the Symbiotic Delegator contract tied to the Sym Byz Vault. It handles stake delegation logic across networks and operators.
number
address
address
address[]
address
address
Before moving forward, it's important to understand the different delegator types available on Symbiotic in order to create the restaking strategy that best meets your needs.
The specific features of each Delegator type are explained in details in the Symbiotic Delegator section. To sum it up, it exists 4 types of delegators:
Network Restake Delegator (Type 0)
Allocations to networks are set using absolute numbers.
Allocations to operators are expressed as shares of the network's total allocation.
Restaking is allowed across networks, but not across operators within a single network.
Operator and network allocations can be changed at any time by the respective role holders (networkLimitSetRoleHolders and operatorNetworkLimitOrSharesSetRoleHolders).
Full Restake Delegator (Type 1)
Allocations to both networks and operators are absolute numbers.
Restaking is allowed both across networks and across operators within each network.
Operator and network allocations can be modified at any time by the designated role holders (networkLimitSetRoleHolders and operatorNetworkLimitOrSharesSetRoleHolders).
Operator Specific Delegator (Type 2)
Stake is allocated to a single, fixed operator across one or more networks.
Restaking across networks is possible only if the operator has opted in to each network.
The operator is immutable once the vault is created.
Network allocations can still be updated by the vault’s curator (networkLimitSetRoleHolders).
Operator Network Specific Delegator (Type 3)
Stake is allocated to one specific operator on one specific network.
This is the most restrictive delegation mode: both operator and network are fixed and immutable.
No allocation changes are allowed after vault creation.
Breaking down the parameters
SlasherParams
This data structure defines the settings of the Symbiotic Slasher contract tied to the Sym Byz Vault. It configures the slashing and veto rules (if enabled).
It exists so far two types of slasher on Symbiotic:
Instant Slasher (Type 0)
Common Slasher that receives slashing requests and instantly executes them
Veto Slasher (Type 1)
Allows to veto received slashing requests using resolvers
Only networks can set resolvers that can veto the slashing requests
⚠️ It is possible for the networks not to set a resolver, thus enabling an instant slashing mechanic similar to Instant Slasher.
If the Vault curator is not ready to provide a stake without the resolver, the curator may simply not allocate any stake to such networks.
Breaking down the parameters
Last updated