restaking-eigenlayer

# Restaking / EigenLayer detection ## When this applies - AVS implementations using EigenLayer / Symbiotic / Karak / Babylon - Restaking deposit / withdrawal contracts - Operator-management contracts - LST-restaking integrations ## Detection patterns ### Withdrawal queue gaming (HIGH) User queues withdrawal, performs slashable action, unqueues if slashing didn't hit. Defense: slashing must apply to in-flight withdrawals too. ### Cascading slashing across AVSs (HIGH) One operator opts into many AVSs. A slash by AVS-A reduces stake → AVS-B's quorum requirement may not be met. Solvency check before slashing. ### AVS opt-in without delegator consent (HIGH) Operator opts into a new AVS, exposing delegators to its slashing conditions without notice. Required: opt-in announcement + delegator-side withdrawal window. ### Slashing magnitude unbounded (CRITICAL) Bad AVS spec slashes 100% on a single condition. With multiple AVSs sharing operator, this can drain the operator's restakers entirely. Cap per-slash magnitude. ### Off-chain slashable evidence verifiability (HIGH) Slashable conditions claim cryptographic provability. If proof is forgeable or the verifier has a bug, false slashing possible. ### EigenLayer strategy-manager + delegation-manager interaction (HIGH) Strategy positions and delegation are separate. Race conditions between staking, delegating, and withdrawing. Off-by-one in undelegation queue can lock funds. ### EigenPod verifyWithdrawalCredentials (HIGH) Beac...