Lido Oracle 8.0.6 caps VEBO exit requests per report

What happened

Lido released Oracle 8.0.6 with a temporary cap of 500 validator exit requests in each VEBO report to keep report transactions below the EIP-7825 transaction-gas limit.

What changed

The oracle iterator stops after 500 requests and carries remaining demand into subsequent approximately five-hour reporting frames. The notice estimates maximum reporting throughput of roughly 2,400 exit requests per day.

What did not change

No Lido contract or protocol upgrade was announced. Exit ordering, forced-exit priority, hash consensus, and the report-submission flow are unchanged, and the stated cap remains above Ethereum’s cited validator-exit throughput.

Confirmed

• Oracle 8.0.6 contains a 500-request per-report cap.
• Remaining exit demand is carried into later VEBO frames.
• The transaction gas limit is configurable, with the EIP-7825 limit used as the default.
• The official notice says no funds were at risk and describes the change as precautionary rather than incident remediation.

Still open

• Whether every VEBO oracle committee member has installed the release.
• Whether sustained demand can produce a material reporting backlog despite the stated daily capacity.
• When Lido will revisit or remove the temporary cap.

What it means for an advisor

• Reopen the Lido memo under its withdrawal-mechanism review criterion once committee adoption makes the change operational.
• Evaluate the distinction between oracle reporting capacity and Ethereum validator-exit capacity during a severe withdrawal-demand spike.
• Do not interpret the precautionary release as evidence that withdrawal risk has been eliminated.