mirror of
https://github.com/OffchainLabs/prysm.git
synced 2026-01-09 15:37:56 -05:00
9e40551852
* Implement KZG proof batch verification for data column gossip validation * Manu's feedback * Add tests * Update beacon-chain/sync/batch_verifier.go Co-authored-by: Manu NALEPA <enalepa@offchainlabs.com> * Update beacon-chain/sync/batch_verifier.go Co-authored-by: Manu NALEPA <enalepa@offchainlabs.com> * Update beacon-chain/sync/kzg_batch_verifier_test.go Co-authored-by: Manu NALEPA <enalepa@offchainlabs.com> * Update beacon-chain/sync/kzg_batch_verifier_test.go Co-authored-by: Manu NALEPA <enalepa@offchainlabs.com> * Update beacon-chain/sync/kzg_batch_verifier_test.go Co-authored-by: Manu NALEPA <enalepa@offchainlabs.com> * Update beacon-chain/sync/kzg_batch_verifier_test.go Co-authored-by: Manu NALEPA <enalepa@offchainlabs.com> * Update beacon-chain/sync/kzg_batch_verifier_test.go Co-authored-by: Manu NALEPA <enalepa@offchainlabs.com> * Fix tests * Kasey's feedback * `validateWithKzgBatchVerifier`: Give up after a full slot. Before this commit: After 100 ms, an un-batched verification is launched concurrently to the batched one. As a result, a stressed node could start to be even more stressed by the multiple verifications. Also, it is always hard to choose a correct timeout value. 100ms may be OK for a given node with a given BPO version, and not ok for the same node with a BPO version with 10x more blobs. However, we know this gossip validation won't be useful after a full slot duration. After this commit: After a full slot duration, we just ignore the incoming gossip message. It's important to ignore it and not to reject it, since rejecting it would downscore the peer sending this message. --------- Co-authored-by: Manu NALEPA <enalepa@offchainlabs.com>
76 B
76 B
Added
- KZG proof batch verification for data column gossip validation