From 49a63eb383869e1d1f3aaba52dddb3ffd113c9ba Mon Sep 17 00:00:00 2001 From: Amir Forouzani <46984622+amirhosf@users.noreply.github.com> Date: Sat, 9 Nov 2024 17:27:20 +0700 Subject: [PATCH] Update guardians.md (#59) * Update guardians.md * Update guardians.md --------- Co-authored-by: JasonVranek --- docs/guardians.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/guardians.md b/docs/guardians.md index 25c954d..c0229af 100644 --- a/docs/guardians.md +++ b/docs/guardians.md @@ -21,6 +21,7 @@ Guardians have three main responsibilities within the Puffer Protocol: - Its beacon chain balance falls below below the DAO threshold. - Its [module](/protocol/puffer-modules#puffer-modules-) was slashed due to an AVS violation. - It consumes all of its validator tickets without renewal. + - The protocol requires ETH liquidity to satisfy pufETH withdrawal requests (validators will be selected randomly). 2. **Provisioning or skipping validators**: When a NoOp registers a validator, the Guardians are responsible for vetting the registration before provisioning them 32 ETH. If the registration is invalid (e.g., uses the wrong withdrawal credentials, is signed with the wrong fork version, uses the wrong enclave version, or the validator already exists) or they failed to properly encrypt keys for the Guardians, they will be skipped. If a NoOp's registration is skipped, their full bond will be returned but a portion of their validator tickets will be penalized to prevent NoOps from griefing the protocol.