Glossary
Glossaryβ
Eigenlayerβ
An Ethereum-based protocol that enables restaking
AVSβ
Actively Validated Service ~ the term for a service on Eigenlayer
Restakingβ
Where people reuse collateral to operate β₯ 1 AVS. If this collateral is beacon chain ETH, they are a called a native restaker
LSPβ
Liquid Staking Protocol
nLRPβ
Native Liquid Restaking Protocol. The Puffer protocol offers native ETH liquid restaking on Eigenlayer
pufETHβ
The yield bearing token that represents staked ETH in Pufferβs LSP
Stakersβ
The users who βstakeβ ETH to the vault to receive pufETH
NoOpsβ
The Puffer nodes that operate an Ethereum validator (and optionally additional AVSs)
Guardiansβ
A committee of Ethereum aligned community members and organizations to assist the protocol as it matures
Enclaveβ
A secure-computing environment capable of running Pufferβs anti-slashing technology
Burst Thresholdβ
Code in our smart contracts that self-caps the vault at 22% marketshare
Puffer DAO (pDAO)β
Governance for the protocol controlled by the PUFI governance token
Beacon Chainβ
The main component of the Ethereum blockchain responsible for Proof of Stake consensus
Beacon Chain Deposit Contractβ
The smart contract to which a NoOp must deposit 32 ETH to initiate running a validator node
VEMβ
Voluntary Exit Message ~ a validator-signed message that will exit the signer when broadcasted to the beacon chain
Withdrawal Credentialsβ
A validator parameter that sets where their consensus rewards and full withdrawal eth are sent. For 0x01 (post-Shapella) withdrawals, the credentials are formatted as 0x01000000000000 ++ 20 byte ethereum address
Consensus Rewardsβ
AKA partial withdrawals or skimmed rewards. These rewards are generated by Ethereum validators performing their PoS duties
Execution Rewardsβ
The rewards earned by a validator when proposing a block. The rewards are composed of priority fees and MEV: Maximal Extractable Value". This refers to the maximum value that can be extracted from block production in excess of the standard block reward and gas fees by including, excluding, and changing the order of transactions in a block. source
Full Withdrawalβ
The validatorβs entire balance that is withdrawn from the beacon chain to the Ethereum address set by the withdrawal credentials
Slashingβ
Slashing may refer to a loss of funds triggered by either of the following:
- Misbehavior of validator nodes, such as signing two different blocks for the same beacon slot (AKA double-signing). See secure-signer for more info on this kind of slashing
- A Restaking Operator (ReOp) not fulfilling obligations defined by an AVS
Validator Ticketβ
An ERC20 token. Each Validator Ticket allows operating a validator on the Puffer Protocol for one day.
Bondβ
An amount of pufETH a NoOp must lend to the protocol during the time of running their validator node. They may lose some or all of this bond if they misbehave or are slashed. NoOps may retrieve this bond after proving they have exited their validator node from the beacon chain
Puffer Moduleβ
A contract which defines a set of AVSs which NoOps opting into the module will delegate their ETH funds to running. These NoOps will receive corresponding rewards in return by participating in this Puffer Module
Restaking Operatorβ
AKA ReOp: A NoOp that is delegated funds to operate an AVS on behalf of other NoOps, as part of a Puffer Module
Secure Signerβ
A software developed by Puffer that helps prevent validators from being slashed. It utilizes Trusted Execution Environments (TEEs) such as Intel SGX
Proof of Reservesβ
This refers to the process by which the protocol proves the amount of ETH backing pufETH, and thus determining the fair exchange ratio between ETH and pufETH
Proof of Rewardsβ
This refers to the process by which NoOps prove and receive the rewards generated as a result of running their validator node