How exactly do “sync committees” help a light client sync up in Eth 2.0 Altair hard fork? : ethereum

Date:

[ad_1]

I’ve learn just a few issues in github about “sync committees” in Eth 2.0 Altair onerous fork. For instance:

https://github.com/ethereum/annotated-spec/blob/grasp/altair/beacon-chain.md#sync-committee

enable gentle purchasers to simply sync up with the header chain with very low computational and knowledge price. The aim is to make a lightweight consumer straightforward and environment friendly sufficient that it may be run inside any surroundings (cell system, embedded {hardware}, browser extension, and even inside one other smart-contract-capable blockchain)

Additionally noticed some code right here:

https://github.com/ethereum/consensus-specs/blob/dev/specs/altair/sync-protocol.md

Nevertheless it isn’t clear to me what precisely these sync committees do to assist a lightweight consumer sync (for instance, do they retailer checkpoints from block headers and supply signatures to gentle purchasers that the proof of stake consensus has developed accurately?) And likewise not clear to me how this ensures {that a} gentle consumer can’t be “fooled” by an attacker to simply accept a fabricated chain.

[ad_2]
Source link

JOIN OUR NEWSLETTER

spot_imgspot_img

Popular