You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Modify light client portal interface strategy for requesting LC finality update every slot (with finalized_slot as content key) when tracking the head of the chain.
Reguarding the "special database for beacon network"... sqlite is quite powerful and will allow a schema'd database with complex queries... I believe that our use of rocksdb is a bit of cargo-cult leftover from execution clients storing all of the state and needing blazing fast read-write access. My intuition is that in our usage pattern the database read/write speeds are unlikely to be the bottleneck.
ogenev
changed the title
Beacon Sync progress
Beacon Portal Network progress
Nov 22, 2023
This is a tracking issue of the current progress of the beacon portal network implementation.
Tasks
finalized slot
inLightClientFinalityUpdate
content key and update beacon bridge to serve the data. #1007finalized_slot
as content key) when tracking the head of the chain.FindContent
requests forLighClientFinalityUpdate
. feat: add beacon storage cache for light client updates #1084LightClientUpdate
records as a response to a period range request.historical_roots
accumulator to validate pre-Capella headers or provide it via the network.historical_summaries
beacon state accumulator to validate post-Capella headers: feat(portal-bridge(beacon)): generate and gossipHistoricalSummariesWithProof
content #1389LightClientUpdate
data into the network?LightClientUpdate
The text was updated successfully, but these errors were encountered: