Lido node operator Gateway.fm details August signing and exit failures

What happened

Gateway.fm, operator 35 in Lido's Curated Module, disclosed two August incidents involving unavailable validator signers, invalid signatures during recovery, and delayed processing of four exit requests.

What changed

The operator added on-chain key reconciliation, signer-deployment verification, automated share provisioning, redundant exit endpoints, paging, and positive liveness monitoring; it also reimbursed 1.0054 ETH.

What did not change

The operator reports no slashing, double-signing, loss of stake, or missed duties for the four validators whose exits were delayed. The postmortem does not independently verify completion or effectiveness of every remediation.

Confirmed

• Eight validators could not attest for between 7.5 and 13.1 hours because their signing shares were not loaded.
• A recovery misconfiguration caused rejected signatures and prevented approximately 7,300 validators from attesting for 75 minutes.
• Four oracle-requested validator exits were delayed, with the longest delay lasting 14 hours 15 minutes.
• Gateway.fm reported that all affected validators exited and reimbursed 1.0054 ETH on September 2, 2026.
• The operator reported no slashing or stake loss.

Still open

• Independent verification that all remediation controls are deployed and operating.
• Whether Lido changed operator allocation, monitoring, or penalties in response.
• The event's net effect on protocol-wide validator performance beyond the stated reimbursement.

What it means for an advisor

• Add the incident and remediation claims to Lido node-operator diligence.
• Confirm whether operator allocation or monitoring policy changed before the next memo review.
• Do not interpret the absence of slashing as proof that the operational control weakness is immaterial.

Previous interpretation

The Lido memo identifies node-operator behavior and validator-exit mechanics as direct dependencies.