Case summary
What happened
Yay! reported that a security incident affecting Kelp, one of the protocols used by Yay! Staking, led Yay! to pause new ETH staking and warned that unstaking could be delayed because it depended on Kelp contracts. On 2026-05-18, Yay! said Kelp's rsETH protocol had resumed but the Always Gain agETH vault used by Yay! Staking was still awaiting reopening. Around 2026-05-25, Yay! reported that the agETH vault had reopened and that unstaking and withdrawals were again operating normally.
Customer result
Customer outcome
Not applicable
Reviewed evidence documents temporary impairment followed by restoration of unstaking and withdrawals. It does not establish a bankruptcy/claims process, platform-wide customer loss, or a repayment program, so CYA does not assign a recovery percentage.
- Estimated recovery
- Not applicable
- Repayment started
- —
- Repayment completed
- —
- Confidence
- Medium
Asset treatment
Terms risk
Unclear
The incident demonstrates upstream dependency and withdrawal-availability risk. CYA does not infer principal protection, platform custody, or a guaranteed recovery right from the campaign documentation.
- Affected product
- Yay! ETH staking via Kelp / agETH
- Confidence
- Medium
The reviewed public material establishes a user-facing Yay! staking campaign connected to partner protocols, but does not establish a complete legal characterization of custody, beneficial ownership, insolvency treatment, or loss allocation across Yay!, Kelp and the agETH vault.
Known unknowns
Uncertainty
Reviewed evidence supports a temporary product/path-level impairment and later service restoration. It does not establish Yay! insolvency, project shutdown, permanent customer loss, a platform-wide withdrawal freeze across every Yay! staking path, or a universal customer recovery percentage.
Chronology
Historical record
Kelp incident impairs Yay! Staking agETH withdrawal path
A Kelp security incident beginning 2026-04-18 affected the Kelp-dependent ETH staking path used by Yay! Staking. Yay! paused new ETH staking and warned that unstaking could be delayed because it depended on Kelp contracts. On 2026-05-18 the Always Gain agETH vault remained closed even after rsETH resumed, and around 2026-05-25 Yay! reported the vault reopened and unstaking/withdrawals returned to normal.
This is a bounded product/path-level withdrawal and unstaking impairment with documented recovery. It must not be generalized into Yay!-wide insolvency, project shutdown, or permanent customer loss.
Source record
Evidence dossier
Filter by claim, reliability, source type, and whether evidence is linked to a specific event.
Entity
2 sourcesYay! Staking introduction
Yay!
First-party documentation establishing Yay! Staking as a staking/yield campaign using protocol partners including Kelp and StakeStone.
Kelp Q1 2026 Report
KernelDAO / Kelp
First-party Kelp report confirming the Always Gain agETH vault as a Kelp Gain product and providing product context. It is not used by itself to establish the Yay! incident chronology.
Event
2 sourcesYay! Japan incident and recovery updates mirrored from @Yay_JP
TwStalker mirror of Yay! Japan
Indexed mirror reproduces Yay! Japan's April 19 incident notice, May 18 recovery-progress update, and later resolution notice stating that Kelp's Always Gain agETH vault reopened and Yay! Staking unstaking/withdrawals returned to normal. Used with attribution because the original X status URLs were not durably recovered during this review.
Yay! Global incident resolution updates mirrored from @Yay_Global
Instalker mirror of Yay! Global
Independent indexed mirror of the official English Yay! Global account, reproducing the May 18 agETH-vault reopening delay and the subsequent resolution statement.
No evidence records match the current filters.
Comparative records