Decision on Jump Crypto's position in the Oracle Set: Rotate or remove and change the quorum
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.
| Voter | Cast Power | Vote & Rationale |
|---|---|---|
 0x4af8...1F6A0B | 11.886M | Rotate Jump Crypto to ChainLayer |
 0xd1c7...700aAE | 8.258M | Rotate Jump Crypto to ChainLayer |
 0x7eE0...36bb6C | 5.017M | Rotate Jump Crypto to ChainLayer |
 0xD2dd...87a7b7 | 5M | Rotate Jump Crypto to ChainLayer |
 0xAe09...76256b | 4.75M | Rotate Jump Crypto to ChainLayer |
VOTE POWER
Proposal Status
- Thu October 26 2023, 03:00 pmVoting Period Starts
- Thu November 02 2023, 05:00 pmEnd Voting Period
Current Results
1-Rotate Jump Crypto to ChainLayer
58.646M
2-Remove Jump Crypto only
627.159