Jacek Sieka
Jacek Sieka
This will cause keys to be loaded by both VC and BN resulting in high slashing risk (ie the slashing DB _may_ prevent it, but it's not certain) This is...
Similar to the beacon node, each validator client instance should log the time of its next action such that an auspicious time for its restart can be picked. ``` INF...
When BN goes down, VC logs several error/warning messages per second due to various subcomponents failing independently - at most one ERR/WRN log per slot should be printed in this...
``` INF 2022-05-31 15:39:12.235+02:00 Beacon node has compatible configuration endpoint="localhost:11101 [Nimbus/v22.5.1-755821-stateofus]" INF 2022-05-31 15:39:12.235+02:00 Beacon node has compatible configuration endpoint="localhost:11101 [Nimbus/v22.5.1-755821-stateofus]" INF 2022-05-31 15:39:12.235+02:00 Beacon node has compatible configuration endpoint="localhost:11101...
`--metrics` should expose validator client metrics such that it can be tracked and monitored similar to the BN
- My ideal mode of operation would be to add both `--trusted-node-url` and `--backfill` as command line arguments to the normal `nimbus_beacon_node` command (i.e. "no action"), and include them if...
Gossip messages are decompressed twice in the current flow: During message id generation: https://github.com/status-im/nimbus-eth2/blob/74f2350a2c85b60230e2d181ef34fe1831a5ba1a/beacon_chain/networking/eth2_network.nim#L1846 Once during validation: https://github.com/status-im/nimbus-eth2/blob/74f2350a2c85b60230e2d181ef34fe1831a5ba1a/beacon_chain/networking/eth2_network.nim#L1952 Once would be enough, really - messages that fail to decompress are...
One problem in ethereum is the public proposer election and the ability to map validator to IP and thus DoS all proposers one by one. Also, when upgrading, all peers...
If a project has a lock file, plain `nim` and tooling should be prevented from ever looking into the nimble folder, so as to avoid that random code from the...