EigenLayer's slashing does not show up as a sudden drop in your balance. The exact record of principal loss appears in the on-chain event logs of your withdrawal transaction, specifically as a SlashingWithdrawalCompleted event, not a regular Transfer event.
Check Whether the AVS You Joined Has Activated Slashing
Not all restaked assets face slashing risk. First, confirm whether the AVS run by your delegated operator has turned on the slashing mechanism.
Case A: Your operator has not yet opted into slashing Before April 17, 2026, EigenLayer's slashing existed only in documentation and was not live. If you delegated before that date and your operator did not actively join the new mechanism, your staked assets may be in a "non-slashable" state after the upgrade.
Case B: Slashing is active On April 17, 2025, a mainnet upgrade activated the contracts that allow AVSs to execute slashing against specific operators. If the AVS your operator runs (such as EigenDA, oracle networks, etc.) experiences downtime, misconfiguration, or is deemed malicious, the AVS can trigger slashing. Only in this situation can you face principal loss.
Completion standard: You have confirmed that the relevant AVS and operator are in the "slashable" state after activation.
Locate Slashing Evidence in the Withdrawal Transaction Logs
To determine whether your principal was actually lost, you must check on-chain records, not just your wallet balance.
What to do: In a block explorer (such as Etherscan), find the transaction hash (Tx Hash) of your withdrawal.
How to do it: Open the transaction details page and look at the Logs (event logs). If the withdrawal was affected by slashing, the logs will contain a SlashingWithdrawalCompleted event. According to EigenLayer's design, when an operator is slashed, the system emits an OperatorSlashed event for each strategy, recording the slashed proportion and exact amount.
Completion standard: You see clear slashing-related event markers in the transaction logs.
Verify the Actual Amount Received from Withdrawal
The impact of slashing on funds is permanent and irreversible.
What to do: Check the amount of ERC-20 tokens actually transferred into your wallet from the withdrawal transaction.
How to do it: On the transaction details page, view the ERC-20 token transfer records. A normal withdrawal will return your deposited stETH or other assets; however, if the asset was slashed, the transferred amount may appear as a very small value (e.g., 1 wei) because the slashed portion has been deducted or redistributed by the system.
Completion standard: You compare the received amount with the expected withdrawal amount and confirm a gap that matches the slashing record in the logs.
Under EigenLayer's slashing, slashed funds are handled in two ways: burned or redistributed. For native ETH restaking, slashed ETH is currently permanently locked in the EigenPod contract and cannot be retrieved. For LST assets like stETH, slashed funds may be directly transferred to a designated recipient address. If your operator faces slashing and you initiate a withdrawal during this period, the slashing may occur while your withdrawal is in the queue, resulting in a reduced withdrawal amount when it completes.
How to verify the operation: Open Etherscan, enter your wallet address, and under the "Internal Txns" or "ERC-20 Token Txns" tab filter by date and value changes. After finding the withdrawal transaction, open the Logs to check for the presence of a SlashingWithdrawalCompleted event.
Next step: If you confirm your principal has been slashed, the loss cannot be recovered. Immediately stop delegating to that operator, and monitor official forums for any subsequent compensation or dispute resolution channels. Also check whether the same operator is associated with other AVSs and consider withdrawing all delegations to control further risk.
