# Lido advances its Pectra compatibility upgrade

> The plan would increment consensus versions for Lido's Accounting, Validator Exit Bus, and CSM oracles, replace the CS Verifier, and later revise Oracle Report Sanity Checker parameters.

- URL: https://riadefi.com/on-chain/2025-03-24-lido-lip-27-pectra-compatibility-snapshot/
- Type: Upgrade or migration
- Stage: Proposed
- Evidence: developing
- Materiality: material
- Event date: 2025-03-24
- Version: 1, published 2026-08-22 (first published 2026-08-22)
- Follow-up: 2025-04-10
- 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's Snapshot supported advancing LIP-27, a compatibility upgrade for Ethereum's Pectra hardfork.

## What changed

The plan would increment consensus versions for Lido's Accounting, Validator Exit Bus, and CSM oracles, replace the CS Verifier, and later revise Oracle Report Sanity Checker parameters.

## What did not change

The March signal did not execute the upgrade. It deliberately excluded new Pectra features such as triggerable withdrawals and validator consolidation, and no deposit pause had fired.

## Confirmed

- The Snapshot ran March 17–24 and reached quorum with a large majority in favor.
- The proposed pre-fork work covered oracle consensus versions and replacement of the CS Verifier.
- A separate post-fork vote was contemplated for Oracle Report Sanity Checker parameters.
- The proposal described pausing deposits as a fallback if compatibility changes could not be safely approved.

## Still open

- External audits, deployment verification, and the on-chain vote were still pending during March.
- The fallback deposit pause had not been invoked.
- Final execution timing depended on Ethereum's Pectra schedule and later Lido votes.

## What it means for an advisor

- Review Lido diligence because accounting-oracle and verifier behavior are core dependencies of stETH balances and validator accounting.
- Monitor for execution and any fallback deposit pause; a pause would require an immediate memo response.
- Do not infer compatibility readiness or safety from the preliminary Snapshot alone.

## Sources

1. [LIP 27: Ensuring Compatibility with Ethereum's Pectra Upgrade](https://research.lido.fi/t/lip-27-ensuring-compatibility-with-ethereum-s-pectra-upgrade/9444) · Lido Governance · 2025-01-30


---

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