nimbus-eth2
nimbus-eth2 copied to clipboard
status-im
Nim implementation of the Ethereum Beacon Chain
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...
**Describe the bug** Nimbus gnosis build with OpenEthereum as the EL, and a public RPC for failover web3. OpenEthereum is still far behind and cannot deliver the genesis contract block....
**Describe the bug** The `prepare_beacon_proposer` REST API appears to take only a single proposer object, whereas the spec states that it should take an array of objects. **To Reproduce** ```...
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...
``` ERR 2022-06-04 22:04:11.007+02:00 Unable to check beacon node's status error_name=RestCommunicationError error_message="Communication failed while sending/receiving request, http error [HttpConnectionError]: Could not connect to remote host" endpoint="localhost:11101 [Nimbus/v22.5.1-f8b5d0-stateofus]" ^CTraceback (most recent...
**Describe the bug** On a `DELETE` call of `eth/v1/keystores`, Nimbus does not return serialized slashing protection data. Instead, it returns it deserialized. As per https://github.com/ethereum/keymanager-APIs/blob/master/apis/local_keystores.yaml: "In a single atomic sequential...
**Describe the bug** On a subsequent `DELETE` call of `/eth/v1/keystores` Nimbus will return `not_found`. It should return `not_active` and the slashing protection data. From https://github.com/ethereum/keymanager-APIs/blob/master/apis/local_keystores.yaml "Additionally, DELETE must fetch the...
Adds the `--trust-sync-committee` launch option to use the light client sync protocol for obtaining the latest finalized head. Then, instead of regularly syncing forward, sync backwards to skip most block...
After this PR: ``` NOT 2022-08-03 19:22:16.939+02:00 Starting beacon node topics="beacnde" version=v22.7.0-52b32c-stateofus nimVersion=1.2.16 enr=(...) ``` IMO, the commit hash for Nim is not needed if we stick to the released...
