Lido Oracle

Lido Oracle is the off-chain daemon, run independently by each oracle member, that bridges Ethereum's Consensus and Execution layers for the Lido protocol. Members build reports off-chain and reach consensus on them via the on-chain HashConsensus contract; the agreed-upon report is then submitted on-chain and applied by Lido contracts.

For a deep technical overview, see the Oracle Operator Manual and the Oracle specification.

Onboarding of new oracle members and rotation of existing members is coordinated on the research forum in the Expansion of Lido's Ethereum Oracle set thread.

Mainnet members

Operator	Address	Forum post
Chorus One (Bitwise)	0x8dB977C13CAA938BC58464bFD622DF0570564b78	address rotation
Staking Facilities	0x404335BcE530400a5814375E7Ec1FB55fAff3eA2	post on x.com, Lido post
Stakefish	0x042a9e5acCfa17e28300F1b5967f20891E973922	address rotation
P2P	0x007DE4a5F7bc37E2F26c0cb2E8A95006EE9B89b5	address declaration
bloXroute	0x61c91ECd902EB56e314bB2D5c5C07785444Ea1c8	intent to join, address declaration
Instadapp	0x73181107c8D9ED4ce0bbeF7A0b4ccf3320C41d12	intent to join, address declaration
Chainlayer	0xc79F702202E3A6B0B6310B537E786B9ACAA19BAf	intent to join, replacing Jump Crypto
MatrixedLink	0xe57B3792aDCc5da47EF4fF588883F0ee0c9835C9	intent to join (replacing Rated), address declaration
Caliber	0x4118DAD7f348A4063bD15786c299De2f3B1333F3	intent to join (replacing Kyber)

Consensus quorum: 5 out of 9 identical report hashes are required to finalize a report. The current value is enforced on-chain and is readable via getQuorum() on each HashConsensus instance.

The authoritative on-chain set is maintained by the HashConsensus contract; the values above can be cross-checked via getMembers() on the HashConsensus instances bound to the AccountingOracle, ValidatorsExitBusOracle and CSFeeOracle.