zah
zah
https://github.com/status-im/nimbus-eth2/pull/3944 The use of nested `awaitWithRetries` calls would have resulted in an unexpected number of retries (3x3). We now use regular `await` in outer layer to avoid the problem. https://github.com/status-im/nimbus-eth2/pull/3943...
The Capella beacon chain spec changes are defined here: https://github.com/ethereum/consensus-specs/blob/dev/specs/capella/beacon-chain.md#introduction As a first step, we should implement the Capella state transition in expectation of test vectors that might be published...
Currently, we are not implementing the following spec rule: > _[IGNORE]_ A valid sync committee contribution with equal `slot`, `beacon_block_root` and `subcommittee_index` whose `aggregation_bits` is non-strict superset has _not_ already...
We need to review the recent changes introduced in the Engine API (one example is the inclusion of the `safeBlockHash` field in the fork-choice update call). Some relevant spec PRs:...
To be broken down into smaller steps that will be tracked here as an epic.
A validator client can be configured to talk to multiple beacon nodes at the same time (i.e. one instance of Nimbus, Prysm, Teku and Lighthouse). When it's time to propose...
Other changes: * More DRY encoding of the Nimbus content type preference. * Switch if/elif/else to exhaustive case statements to guard the code better from future changes.
Software updates and planned restarts should be handled with zero-downtime. This is a challenge because deploying a new installation takes time and any restart is associated with reloading at least...
Since it's possible to implement this entirely on NBC's side by supplying a custom bootstrap nodes list on start-up, it looks like `nim-eth` should provide at most some optional helper...