twoeths
twoeths
**Is your feature request related to a problem? Please describe.** Refer to https://github.com/achingbrain/uint8arrays/issues/30#issuecomment-1199120924 Given how efficient protobuf creates a string from Uint8Array in one go, we could try to use...
**Is your feature request related to a problem? Please describe.** Some consumers only want first n bytes after calling `digest()` and they have to use this pattern: `digest(something).slice(0, n)`, note...
**Is your feature request related to a problem? Please describe.** Right now these utils convert to BigInt unnecessarily and we know that we have performance issue with using BigInt **Describe...
With typescript 4.4.2, the `node.ts` is compiled to: ```js export abstract class Node implements HashObject { // this is to save an extra variable to check if a node has...
## Motivation: + Currently the struct `hashTreeRoot()` returns a Buffer while a TreeBacked returns Uint8Array, we want both of them to return Uint8Array
part of https://github.com/ChainSafe/lodestar/issues/2046 this is a simple test to calculate `hashTreeRoot` ```ts it.only("set validator valances", function () { this.timeout(0); const originalState = state.getOriginalState(); // cache hashTreeRoot config.types.BeaconState.hashTreeRoot(originalState); const balances =...
### Describe the bug There are too many unknown peers in test mainnet nodes this does not happen to nodes with connected validators ### Expected behavior Should investigate who they...
### Problem description As an execution client, Nethermind expects consensus client to call notifyNewPayload as soon as possible. ### Solution description Prysm already does that almost right after they receive...
**Motivation** - Experiment n-historical states by adding `nHistoricalStates` flag, by default leave it `false` **Description** - Consume state caches based on the new `chain.nHistoricalStates` flag - We can configure `chain.maxBlockStates`...
### Describe the bug It takes up to 5.84s to get `eth1DataAndDeposit` for block production for a mainnet node ### Expected behavior this issue rarely happen, actually it's the 1st...