{"id":1195,"date":"2025-10-27T12:51:33","date_gmt":"2025-10-27T10:51:33","guid":{"rendered":"https:\/\/ackee.xyz\/blog\/?p=1195"},"modified":"2025-10-27T12:53:06","modified_gmt":"2025-10-27T10:53:06","slug":"lido-triggerable-withdrawals-audit-summary","status":"publish","type":"post","link":"https:\/\/ackee.xyz\/blog\/lido-triggerable-withdrawals-audit-summary\/","title":{"rendered":"Lido Triggerable Withdrawals Audit Summary"},"content":{"rendered":"

Lido<\/a> is a decentralized liquid staking protocol for Ethereum. Triggerable withdrawals is a new feature based on the EIP-7002<\/a> standard that allows for the ejection of validators previously deposited through the Lido protocol.<\/p>\n

The primary purpose of triggerable withdrawals is to allow the Lido DAO to withdraw funds locked in a validator when the node operator refuses to submit a withdrawal request. This functionality became available after EIP-7002<\/a> was implemented on mainnet.<\/p>\n

Withdrawal triggering is permissionless; however, users must provide data whose hash matches one already submitted by Easy Track or trigger exits once the Oracle has provided the report data.<\/p>\n

\n

Lido engaged Ackee Blockchain Security<\/a> to perform a security review of Lido Triggerable Withdrawals with a total time donation of 38 engineering days in a period between June 5 and July 14, 2025. 10 engineering days were allocated to manually-guided fuzzing using Wake<\/a>.<\/p>\n

Lido then engaged Ackee Blockchain Security to perform a fix review of the findings from the previous revision. The review was performed between July 23 and July 25, 2025 and no new findings were discovered.<\/p>\n

Lido engaged Ackee Blockchain Security to perform a third review, this time of changes made since the previous revision with a total time donation of 0.5 engineering days in a period between September 8 and September 16, 2025 and no new findings were discovered.<\/p>\n

METHODOLOGY<\/span><\/h2>\n

We began our review by implementing and executing manually-guided differential fuzz tests in Wake<\/a> to verify the correctness of the new functionalities and to ensure the changes do not break existing invariants. Fuzzing was conducted with contracts forked from mainnet and relevant contracts upgraded to the latest version. This ensured full compatibility with the mainnet deployment. 2 staking modules were used to test the triggerable withdrawals functionality \u2013 Node Operators Registry<\/a> and Community Staking Module v2<\/a>. More details about the fuzzing process can be found in the full audit report linked at the end of this article.<\/p>\n

In parallel, we performed an in-depth manual review of the code, especially focusing on the triggerable withdrawal functionality, compatibility with EIP-7002<\/a>, and new code changes since the last audit (commit 1ffbb7e<\/code>). During the review, we focused on the following:<\/p>\n