status-im/nimbus-eth2
2
0
Fork 0
mirror of https://github.com/status-im/nimbus-eth2.git synced 2025-01-18 10:31:04 +00:00
Code Issues Projects Releases Wiki Activity

extend LC data DB rationale

Browse Source
This commit is contained in:
Etan Kissling 2022-06-29 01:19:20 +02:00
parent dc68ce86f3
commit 24aaca9e2e
No known key found for this signature in database
GPG Key ID: B21DA824C5A3D03D
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
beacon_chain/light_client_data_db.nim
View File

@ -34,8 +34,11 @@ logScope: topics = "lcdata"
# sync committee period, so storing the full sync committee is acceptable. # sync committee period, so storing the full sync committee is acceptable.
# This data could be stored as SZSSZ to avoid on-the-fly compression when a # This data could be stored as SZSSZ to avoid on-the-fly compression when a
# libp2p request is handled. However, the space savings are quite small. # libp2p request is handled. However, the space savings are quite small.
# Furthermore, the libp2p context bytes depend on `attested_header.slot`, so # Furthermore, `LightClientUpdate` is consulted on each new block to attempt
# this would need to be stored separately to avoid having to decompress. # improving it. Continuously decompressing and recompressing seems inefficient.
# Finally, the libp2p context bytes depend on `attested_header.slot` to derive
# the underlying fork digest. The table name is not sufficient to determine
# this until one is made for each fork, even if there was no structural change.
# SSZ storage selected due to the small size and reduced logic complexity. # SSZ storage selected due to the small size and reduced logic complexity.
# #
# `sealed_sync_committee_periods` contains the sync committee periods for which # `sealed_sync_committee_periods` contains the sync committee periods for which