Basic components

Byzantine is a decentralised protocol enabling the permissionless creation of individual cross-protocol restaking strategy vaults.

It separates the roles of investor (staker), risk manager (vault manager), and infrastructure layer. Users can permissionlessly create strategy vaults based on their needs and can optionally open these up to other stakers.

Basic components

Native restaking & Eigenpods:

Native restaking & Eigenpods:	The combined staking & restaking of native ETH. The assets are not delegated directly, but rather staked and delegated via an Eigenpod.
Staking	On Byzantine, native restakers stake ETH through DVT-powered validators for increased security. Operators for these DVT clusters are selected via a highly capital-efficient auction mechanism to guarantee the best APR for stakers.
Distributed validator technology (DVT)	The practice of sharing a validator's work among several operators (usually 4). This greatly decreases the probability of slashing and the likelihood of inactivity penalties.
Node operator	Ethereum operators working as part of a DVT cluster. To join as a node operator, have a look at our node operator onboarding documentation.
ERC20 restaking	In contrast to native restaking, ERC20 restaking means restaking any ERC20 asset, such as LSTs or even USDC. With the exception of LSTs, it is the AVSs who decide which ERC20s they accept as stake.
AVS strategy	A combination of AVSs and protocols that a particular strategy vault is restaking into.
Strategy vault	A tokenised vault built around a specific AVS strategy. Can be open to the public or whitelisted.

Roles

See Roles.