7dba1b37dd
With the introduction of batching and lazy attestation aggregation, it no longer makes sense to enqueue attestations between the signature check and adding them to the attestation pool - this only takes up valuable CPU without any real benefit. * add successfully validated attestations to attestion pool directly * avoid copying participant list around for single-vote attestations, pass single validator index instead * release decompressed gossip memory earlier, specially during async message validation * use cooked signatures in a few more places to avoid reloads and errors * remove some Defect-raising versions of signature-loading * release decompressed data memory before validating message |
||
|---|---|---|
| .. | ||
| README.md | ||
| fork_choice.nim | ||
| fork_choice_types.nim | ||
| proto_array.nim | ||
README.md
Fork choice implementations
References: