# Lido Oracle 8.0.6 caps VEBO exit requests per report

> 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.

- URL: https://riadefi.com/on-chain/2026-08-31-lido-oracle-8-0-6-vebo-exit-cap/
- Type: Upgrade or migration
- Stage: Confirmed
- Evidence: mixed
- Materiality: material
- Event date: 2026-08-31
- Version: 1, published 2026-09-15 (first published 2026-09-15)
- Follow-up: 2026-09-05
- Advisor-relevant: no
- Affects: Lido (protocol)

Developing. Some claims here are not yet confirmed; they are listed apart from the confirmed facts. A new version replaces this one when the primary evidence changes.

## 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.

## Sources

1. [Capping the number of exit requests in a single VEBO oracle report](https://research.lido.fi/t/capping-the-number-of-exit-requests-in-a-single-vebo-oracle-report/11840) · Lido governance · 2026-08-31


---

Published by Ketju Research on RIADeFi (https://riadefi.com). Educational research for financial professionals; not investment, legal, tax, or compliance advice.