Lido approves replacing Kyber with Caliber in its oracle set

What happened

Lido tokenholders approved rotating Kyber Network out of the Lido on Ethereum oracle set and replacing it with Caliber.

What changed

The approved path changes the entity responsible for one oracle-set position while preserving the seat rather than removing it and adjusting quorum.

What did not change

The Snapshot approval does not itself prove that the on-chain oracle member rotation occurred, and it does not validate Caliber's production security or independence.

Confirmed

• The vote offered direct rotation to Caliber or removal of Kyber with a quorum change.
• The direct rotation option received the overwhelming voting weight.
• Caliber completed a Hoodi testnet period before the vote.
• The proposal attributes the change to Kyber's infrastructure operations transitioning to Caliber.

Still open

• The executed oracle-set membership and effective rotation date.
• The final production keys, infrastructure, and incident-response contacts.
• Operational overlap and independence between Kyber and Caliber.
• Whether quorum or other oracle controls change during implementation.

What it means for an advisor

• Review Lido's oracle-operator roster, key controls, concentration, and business-continuity assumptions.
• Verify the executed membership and Caliber's production operating evidence before treating the rotation as complete.