status-im/nimbus-eth2
2
0
Fork 0
mirror of https://github.com/status-im/nimbus-eth2.git synced 2025-02-13 23:17:11 +00:00
Code Issues Projects Releases Wiki Activity
nimbus-eth2/beacon_chain/consensus_object_pools
History
Etan Kissling 40e89937c5
segregate sync committee messages by period / fork (#4953) 
`SyncCommitteeMsgPool` grouped messages by their `beacon_block_root`.
This is problematic around sync committee period boundaries and forks.
Around sync committee period boundaries, members from both the current
and next sync committee may sign the same `beacon_block_root`; mixing
the signatures from both committees together is a mistake. Likewise,
around fork transitions, the `signing_root` changes, so those messages
also need to be segregated.
2023-05-17 07:55:55 +03:00
..
vanity_logs
update Deneb ANSI art for readability 🐟 (#4885)
2023-05-03 22:25:01 +02:00
attestation_pool.nim
more consensus-specs v1.3.0 bumps (#4898)
2023-05-05 20:38:51 +00:00
blob_quarantine.nim
BlobQuarantine.hasBlobs: fix for loop bound (#4876)
2023-04-28 19:27:28 +00:00
block_clearance.nim
better batch sig verification failure message
2023-05-12 08:18:13 +02:00
block_dag.nim
Revert "accelerate getShufflingRef (#4911)" (#4958)
2023-05-15 15:25:51 +00:00
block_pools_types_light_client.nim
remove Nim 1.2-compatible push raises and update copyright notice years (#4528)
2023-01-20 14:14:37 +00:00
block_pools_types.nim
dependent slot helpers
2023-05-16 11:04:25 +02:00
block_quarantine.nim
Blob handling sync fixes (#4888)
2023-05-06 08:58:50 +00:00
blockchain_dag_light_client.nim
rename lcDataForkAtStateFork > lcDataForkAtConsensusFork (#4726)
2023-03-11 20:09:21 +00:00
blockchain_dag.nim
dependent slot helpers
2023-05-16 11:04:25 +02:00
consensus_manager.nim
Rename eth1/ -> el/ and eth1_monitor.nim -> el_monitor.nim (#4944)
2023-05-15 05:05:12 +00:00
exit_pool.nim
don't clear validator change subpools after creating each block (#4704)
2023-03-09 18:19:36 +02:00
light_client_pool.nim
remove Nim 1.2-compatible push raises and update copyright notice years (#4528)
2023-01-20 14:14:37 +00:00
README.md
automatic update of v1.3.0-rc.5 consensus spec URLs to v1.3.0 (#4848)
2023-04-21 18:52:43 +00:00
spec_cache.nim
more consensus-specs v1.3.0 bumps (#4898)
2023-05-05 20:38:51 +00:00
sync_committee_msg_pool.nim
segregate sync committee messages by period / fork (#4953)
2023-05-17 07:55:55 +03:00

README.md

Consensus object pools

This folder holds the various consensus object pools needed for a blockchain client.

Object in those pools have passed the "gossip validation" filter according to specs:

After "gossip validation" the consensus objects can be rebroadcasted as they are optimistically good, however for internal processing further verification is needed. For blocks, this means verifying state transition and all contained cryptographic signatures (instead of just the proposer signature). For other consensus objects, it is possible that gossip validation is a superset of consensus verification (TODO).

The pools presenet in this folder are:

  • block_pools:
    • block_quarantine: for seemingly valid blocks that are on a fork unknown to us.
    • block_clearance: to verify (state_transition + cryptography) candidate blocks.
    • blockchain_dag: an in-memory direct-acyclic graph of fully validated and verified blockchain candidates with the tail being the last finalized epoch. A block in the DAG MUST be in the fork choice and a block in the fork choice MUST be in the DAG (except for orphans following finalization). On finalization non-empty epoch blocks are stored in the beacon_chain_db.
  • attestation_pool: Handles the attestation received from gossip and collect them for fork choice.
  • exit_pool: Handle voluntary exits and forced exits (attester slashings and proposer slashings)