nimbus-eth1
nimbus-eth1 copied to clipboard
status-im
Nimbus: an Ethereum Execution Client for Resource-Restricted Devices
```Nim import std/[importutils, tables], eth/trie/trie_defs, eth/common/eth_types, stew/[byteutils, endians2], unittest2, ../nimbus/db/storage_types, ../nimbus/db/core_db, ../nimbus/db/ledger, ../nimbus/db/ledger/accounts_ledger {.all.} # import all private symbols func initAddr(z: int): EthAddress = const L = sizeof(result) result[L-sizeof(uint32)..^1] =...
the most timeconsuming tests in nimbus t8n vs geth t8n (Cancun only) (most of this tests has high amount of transactions) ``` NIMBUS *** Execution time stats Total Time: :...
In several places, we do a check similar to `com.consensus == ConsensusType.POS` to determine block validation rules - similar to #2322 the block should be checked based on its own...
This module mixes exceptions, booleans, logging and other error handling styles, all in one module - it needs refactoring to use one error handling style only.
Given that actual data is stored in the `Vertex` structure, it's useful to think of the MPT as a cache for computing roots rather than being a functional requirement on...
Support for Portal testnets got added here: https://github.com/status-im/nimbus-eth1/issues/2206 However, once different data than the mainnet data gets used on a Portal network, the node will also need to be able...
``` /opt/nimbus-eth1/fluffy/fluffy.nim(377) fluffy /opt/nimbus-eth1/fluffy/fluffy.nim(365) run /opt/nimbus-eth1/vendor/nim-chronos/chronos/internal/asyncengine.nim(1210) runForever /opt/nimbus-eth1/vendor/nim-chronos/chronos/internal/asyncengine.nim(150) poll /opt/nimbus-eth1/vendor/nim-chronos/chronos/internal/asyncfutures.nim(371) futureContinue /opt/nimbus-eth1/vendor/nim-eth/eth/utp/utp_socket.nim(1643) eventLoop /opt/nimbus-eth1/vendor/nim-eth/eth/utp/utp_socket.nim(1283) processPacketInternal /opt/nimbus-eth1/vendor/nim-eth/eth/utp/clock_drift_calculator.nim(88) addSample /opt/nimbus-eth1/vendor/nimbus-build-system/vendor/Nim/lib/system/integerops.nim(15) raiseOverflow /opt/nimbus-eth1/vendor/nimbus-build-system/vendor/Nim/lib/system/fatal.nim(54) sysFatal [[reraised from: /opt/nimbus-eth1/fluffy/fluffy.nim(377) fluffy /opt/nimbus-eth1/fluffy/fluffy.nim(365) run /opt/nimbus-eth1/vendor/nim-chronos/chronos/internal/asyncengine.nim(1210) runForever /opt/nimbus-eth1/vendor/nim-chronos/chronos/internal/asyncengine.nim(150)...
Fluffy currently sets the radius at max when the node starts up. Because the radius only gets winded down when the storage-capacity hits, this can take a bit of time...
See also PR https://github.com/ethereum/portal-network-specs/pull/306