• © Goverland Inc. 2026
  • v1.0.5
  • Privacy Policy
  • Terms of Use
LidoLidoby0xDbBC6A93ae517D3ea568C04219cbBBd025f01CB6zuzu_eeka

Decision on Jump Crypto's position in the Oracle Set: Rotate or remove and change the quorum

Voting ended over 2 years agoSucceeded

Jump Crypto, a Lido node operator and member of the oracle set, has expressed their intention to voluntarily exit the Lido-curated Node Operator Set and leave the Lido on Ethereum Oracle Set by the end of CY2023.

ChainLayer, another Lido node operator, has expressed their desire to replace Jump Crypto in the Oracle set.

Currently, there are 9 members in the Lido on Ethereum oracle set, with 5 being Lido node operators and the remaining 4 being 3rd party oracles. If Jump Crypto is replaced by ChainLayer, the balance between NOs and non-NOs in the oracle set will not change.

ChainLayer has a great record of participation in the Lido protocol and experience running oracle infrastructure in general.

This proposal offers two options for tokenholders: to rotate Jump crypto for ChainLayer in the Accounting Oracle and Validator Exit Bus contracts (and keep the quorum as is), or to remove Jump crypto from the Oracle set and change the required quorum from 5/9 to 5/8.

Off-Chain Vote

Rotate Jump Crypto to ChainLayer
58.65M LDO100%
Remove Jump Crypto only
627.16 LDO0%
Download mobile app to vote

Discussion

LidoDecision on Jump Crypto's position in the Oracle Set: Rotate or remove and change the quorum

Timeline

Oct 26, 2023Proposal created
Oct 26, 2023Proposal vote started
Nov 02, 2023Proposal vote ended
Oct 31, 2025Proposal updated