mirror of
https://gitlab.com/pulsechaincom/lighthouse-pulse.git
synced 2024-12-22 19:50:37 +00:00
775d222299
## Proposed Changes With proposer boosting implemented (#2822) we have an opportunity to re-org out late blocks. This PR adds three flags to the BN to control this behaviour: * `--disable-proposer-reorgs`: turn aggressive re-orging off (it's on by default). * `--proposer-reorg-threshold N`: attempt to orphan blocks with less than N% of the committee vote. If this parameter isn't set then N defaults to 20% when the feature is enabled. * `--proposer-reorg-epochs-since-finalization N`: only attempt to re-org late blocks when the number of epochs since finalization is less than or equal to N. The default is 2 epochs, meaning re-orgs will only be attempted when the chain is finalizing optimally. For safety Lighthouse will only attempt a re-org under very specific conditions: 1. The block being proposed is 1 slot after the canonical head, and the canonical head is 1 slot after its parent. i.e. at slot `n + 1` rather than building on the block from slot `n` we build on the block from slot `n - 1`. 2. The current canonical head received less than N% of the committee vote. N should be set depending on the proposer boost fraction itself, the fraction of the network that is believed to be applying it, and the size of the largest entity that could be hoarding votes. 3. The current canonical head arrived after the attestation deadline from our perspective. This condition was only added to support suppression of forkchoiceUpdated messages, but makes intuitive sense. 4. The block is being proposed in the first 2 seconds of the slot. This gives it time to propagate and receive the proposer boost. ## Additional Info For the initial idea and background, see: https://github.com/ethereum/consensus-specs/pull/2353#issuecomment-950238004 There is also a specification for this feature here: https://github.com/ethereum/consensus-specs/pull/3034 Co-authored-by: Michael Sproul <micsproul@gmail.com> Co-authored-by: pawan <pawandhananjay@gmail.com>
24 lines
1005 B
TOML
24 lines
1005 B
TOML
disallowed-from-async-methods = [
|
|
"tokio::runtime::Handle::block_on",
|
|
"tokio::runtime::Runtime::block_on",
|
|
"tokio::task::LocalSet::block_on",
|
|
"tokio::sync::Mutex::blocking_lock",
|
|
"tokio::sync::RwLock::blocking_read",
|
|
"tokio::sync::mpsc::Receiver::blocking_recv",
|
|
"tokio::sync::mpsc::UnboundedReceiver::blocking_recv",
|
|
"tokio::sync::oneshot::Receiver::blocking_recv",
|
|
"tokio::sync::mpsc::Sender::blocking_send",
|
|
"tokio::sync::RwLock::blocking_write",
|
|
]
|
|
async-wrapper-methods = [
|
|
"tokio::runtime::Handle::spawn_blocking",
|
|
"task_executor::TaskExecutor::spawn_blocking",
|
|
"task_executor::TaskExecutor::spawn_blocking_handle",
|
|
"warp_utils::task::blocking_task",
|
|
"warp_utils::task::blocking_json_task",
|
|
"beacon_chain::beacon_chain::BeaconChain::spawn_blocking_handle",
|
|
"validator_client::http_api::blocking_signed_json_task",
|
|
"execution_layer::test_utils::MockServer::new",
|
|
"execution_layer::test_utils::MockServer::new_with_config",
|
|
]
|