status-im/nimbus-eth2
2
0
Fork 0
mirror of https://github.com/status-im/nimbus-eth2.git synced 2025-01-09 13:56:23 +00:00
Code Issues Projects Releases Wiki Activity
nimbus-eth2/beacon_chain/consensus_object_pools
History
Jacek Sieka 9e9db216c5
Harden block proposal against expired slashings/exits (#4013) 
* Harden block proposal against expired slashings/exits

When a message is signed in a phase0 domain, it can no longer be
validated under bellatrix due to the correct fork no longer being
available in the `BeaconState`.

To ensure that all slashing/exits are still valid, in this PR we re-run
the checks in the state that we're proposing for, thus hardening against
both signatures and other changes in the state that might have
invalidated the message.

* fix same message added multiple times

in case of attestation slashing of multiple validators in one go
2022-08-23 18:30:46 +03:00
..
vanity_logs
compatibility with Nim 1.4+ (#3888)
2022-07-29 10:53:42 +00:00
attestation_pool.nim
compatibility with Nim 1.4+ (#3888)
2022-07-29 10:53:42 +00:00
block_clearance_light_client.nim
compatibility with Nim 1.4+ (#3888)
2022-07-29 10:53:42 +00:00
block_clearance.nim
cache shuffling separately from other EpochRef data (fixes #2677) (#3990)
2022-08-18 21:07:01 +03:00
block_dag.nim
update spec ref URLs (#4005)
2022-08-20 16:03:32 +00:00
block_pools_types_light_client.nim
update LC spec references for v1.2.0-rc.2 (#3982)
2022-08-17 19:47:06 +00:00
block_pools_types.nim
cache shuffling separately from other EpochRef data (fixes #2677) (#3990)
2022-08-18 21:07:01 +03:00
block_quarantine.nim
compatibility with Nim 1.4+ (#3888)
2022-07-29 10:53:42 +00:00
blockchain_dag_light_client.nim
do not prune LC data by default (#4008)
2022-08-21 11:24:59 +02:00
blockchain_dag.nim
update spec ref URLs (#4005)
2022-08-20 16:03:32 +00:00
consensus_manager.nim
update spec ref URLs (#4005)
2022-08-20 16:03:32 +00:00
exit_pool.nim
Harden block proposal against expired slashings/exits (#4013)
2022-08-23 18:30:46 +03:00
light_client_pool.nim
update LC spec references for v1.2.0-rc.2 (#3982)
2022-08-17 19:47:06 +00:00
README.md
update spec ref URLs (#3979)
2022-08-17 11:33:19 +00:00
spec_cache.nim
update spec ref URLs (#4005)
2022-08-20 16:03:32 +00:00
sync_committee_msg_pool.nim
Implement a missing ingnore rule for sync committee contributions (#3941)
2022-08-09 12:52:11 +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)