nimbus-eth2
nimbus-eth2 copied to clipboard
status-im
Nim implementation of the Ethereum Beacon Chain
The `json` module in the std library has several tricky issues: * it doesn't actually implement the [json standard](https://www.json.org/json-en.html) - instead, it makes up its own notions such as `JInt`...
**Describe the bug** The Nimbus client requires that response headers be set to strictly `application/json` without any `charset` specified when trying to parse REST responses during checkpoint sync so is...
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...
The operation of our fleet is still frequently disrupted by various technical problems. We can improve the situation by employing: * Canary releases to a subset of the fleet *...
We should publish binaries for Windows, macOS and Linux. It's preferable if the web-site can autodetect the OS of the user to suggest the right link. The Github releases page...
We have a couple of asserts to catch logic bugs that should never happen, for example https://github.com/status-im/nimbus-eth2/pull/1860#discussion_r503362155 Just in case they happen, we want to make sure that those are...
The CI should produce test coverage reports as artefacts of each CI run. `make test` should produce them locally on systems where this is feasible.
In `BeaconBlocksByRange`, we request a number of blocks which will result in a number of chunks in the response. If the other peer sends more chunks than that, we should...
Depends on https://github.com/status-im/infra-ci/issues/11
* [ ] When syncing, we can apply BLS batching for a sequence of blocks. * [x] Incoming attestations can be grouped together and verified as a batch (a batch...