Lido

Linea + Lido: Aducând Venit Nativ la L2s

Cu Venitul Nativ, @LineaBuild va integra infrastructura stVault Lido V3 pentru a susține motorul său DeFi durabil, non-custodial, permițând tuturor ETH-urilor transferate să câștige automat recompense de staking.

↓

100% Ethereum

[Divulgare de Securitate] O vulnerabilitate a fost raportată și atenuată în legătură cu Lido CSM și contractul de verificator fără permisiuni utilizat pentru a verifica retragerile validatorilor.

Vulnerabilitatea nu a fost exploatată, iar niciun Operator de Nod CSM nu a fost afectat. Deținatorii de stETH nu au fost afectați în niciun fel.

Ca parte a remedierii, o soluție a fost implementată prin atenuarea Oracle (dezactivarea arderii obligațiunilor) și votul DAO 190.

O recompensă pentru erori a fost plătită unui whitehat care a divulgat responsabil problema prin programul Lido × Immunefi.

Detalii complete și pot fi găsite pe forumul de cercetare Lido:

Testnet-ul Lido CSM v2 este aici.

http://csm.testnet.fi

↓

Stivuirea ETH, staking ETH

Cum arată următorii 10 ani ai Ethereum?

Introducerea Compensației pentru Bug Bounty cu Guvernanță Duală 🐛

În colaborare cu @immunefi, vânătorii de bug-uri pot beneficia acum de un bonus de 100.000 USD, pe lângă recompensa maximă originală de 2 milioane USD, pentru trimiterile legate de Guvernanța Duală Lido.

Prezentare completă aici:
https://immunefi.com/audit-competition/lido-bug-bounty-competition/information/

Staking instituțional, simplificat 🏦

@caladanxyz acceptă acum stETH ca garanție pentru tranzacționarea OTC instituțională.

Clienții instituționali pot acum să folosească stETH pentru opțiuni și produse structurate - toate acestea păstrând recompensele de staking și lichiditatea.

Mai multe aici: https://blog.lido.fi/caladan-integrates-steth-as-institutional-otc-collateral/

crede în ceva

crede în ceva

Planul Lido pentru Pectra, Partea 3

Ethereum, Lido și optimizarea economiei de staking cu consolidarea validatorilor.

https://blog.lido.fi/lidos-roadmap-to-pectra-delivering-validator-consolidations-in-the-protocol/

Guvernarea Lido DAO: Iulie

Voturile din iulie sunt live, inclusiv două inițiative cheie - CSM v2 și Retrageri Activabile - care îndreaptă Lido spre o stakare mai descentralizată și fără permisiuni.

Snapshot: 21 iulie → 28, 16:00 UTC
Aragon: 23 iulie → 28, 09:44 UTC

https://t.co/hBJ2MofyKC

👇

Introducing the newest Lido withdrawal aggregator: @JumperExchange ⚡

Skip the Ethereum withdrawal queues with instant swaps between stETH/wstETH and ETH using Jumper Exchange.

👇

Built on Ethereum. Built for Ethereum.

[Security Disclosure] A griefing vulnerability was responsibly reported via Immunefi, affecting the RageQuit mechanism in Lido’s Dual Governance (DG) system.

User funds are not affected. The vulnerability has not been exploited and a set of mitigations are in place.

Thanks to the “training wheels” phase of DG rollout and the readiness of the Emergency Committee to intervene if needed, Lido contributors are equipped to fully neutralize any potential abuse.

Next steps:
• Emergency Committee is on standby to intervene if needed
• A fix is being proposed, tested, and audited
• DG testnet bounty
• Onchain vote to ship fix
• Fix fully enacted

Lido contributors are grateful to the anonymous whitehat for the high-quality report and to Immunefi for supporting responsible disclosure.

Details and updates can be found on forum:

[Security Disclosure] A griefing vulnerability was responsibly reported via Immunefi, affecting the RageQuit mechanism in Lido’s Dual Governance (DG) system.

The issue could have delayed ETH withdrawals during a RageQuit state, but no user funds were ever at risk.

Thanks to the “training wheels” phase of DG rollout and the readiness of the Emergency Committee to intervene if needed, Lido contributors are equipped to fully neutralize any potential abuse.

Next steps:
• Emergency Committee is on standby to intervene if needed
• A fix is being proposed, tested, and audited
• DG testnet bounty
• Onchain vote to ship fix
• Fix fully enacted

Lido contributors are grateful to the anonymous whitehat for the high-quality report and to Immunefi for supporting responsible disclosure.

Details and updates can be found on forum:

[Security Disclosure] A griefing vulnerability was responsibly reported via Immunefi, affecting the RageQuit mechanism in Lido’s Dual Governance (DG) system.

The issue could have delayed ETH withdrawals during a RageQuit state, but no user funds were ever at risk.

Thanks to the “training wheels” phase of DG rollout and the readiness of the Emergency Committee to intervene if needed, Lido contributors are equipped to fully neutralize any potential abuse.

Next steps:
• Emergency Committee is on standby to intervene if needed
• A fix is being proposed, tested, and audited
• DG testnet bounty
• Onchain vote to ship fix
• Fix fully enacted

Lido contributors are grateful to the anonymous whitehat for the high-quality report and to Immunefi for supporting responsible disclosure.

Incident details and updates can be found on forum:

As contributors to Lido, the objective is to advocate for a future that maximizes long-term value for the Ethereum ecosystem.

With that in mind, Lido contributors recommend the following potential headliners for Glamsterdam.

Execution Layer
• EIP-7928 (Block-level Access Lists): a straightforward, high-leverage improvement to transaction execution. Minimal complexity, real scalability gains.

Consensus Layer
Slot pipelining is essential. Lido protocol support two viable paths:
• EIP-7886 (Delayed Execution): simpler, more predictable to implement and monitor
• EIP-7732 (ePBS): more efficient and mature, but more complex and operationally demanding

Credible Neutrality
• EIP-7805 (FOCIL) brings censorship resistance into the protocol. It’s not just a feature - it’s the foundation.

Read the full recommendation: