Lion - dapplion
Lion - dapplion
## Issue Addressed - Implements https://github.com/sigp/lighthouse/issues/6767 except the backfill restart Also does a consistency check on the DB to make sure the stored columns are compatible Not tested yet ##...
## Issue Addressed _@AgeManning pointed to me that we can have experimental ReqResp protocols in Lighthouse :) so here we go_ Implements - https://github.com/ethereum/consensus-specs/pull/3845 a new ReqResp protocol to make...
## Issue Addressed Noted that we never have to verify individual RpcBlocks for sync. Lookup sync sends the block alone always, and range sync sends chain segments. ## Proposed Changes...
Currently `BlockDelays` metrics track `all_blobs_observed` which is has the "intention" to track the time at which the last blob for a block was received. This metric won't register for PeerDAS....
Currently forwards sync fetches ranges of blocks by range from either head or latest finalized until reaching the target, from a set of peers with the same status messages. This...
## Issue Addressed From https://github.com/sigp/lighthouse/pull/8382 I noted that the logic in range sync to decide _where_ to start syncing from is scattered. When manual finalization is triggered, sync will fetch...
## Issue Addressed Just visual clean-up, making logging statements look uniform. There's no reason to use `tracing::debug` instead of `debug`. If we ever need to migrate our logging lib in...
## Issue Addressed Allows Lighthouse to bootstrap into a state for a checkpoint that is not finalized. This feature could save Ethereum Mainnet when shit hits the fan (= long...
## Issue Addressed In process_gossip_unverified block we match the verification error and we should always: - log something - propagate_validation_result to libp2p However, for some variants we don't do that....
The annotated spec is an extremely valuable resource that has helped a large number of core devs to understand the spec. There's a lot of nuance and rationale not captured...