Tomás Grüner
Tomás Grüner
We should check that uint64 numbers are between `0` and `2**64 - 1`.
Find the underlying issue of this flaky test: https://github.com/lambdaclass/lambda_ethereum_consensus/pull/347
The spec specifies a lot of the parameters used in the libp2p. We should double-check we are setting all of them. Related issues: - [x] #144 - [x] #164
From https://github.com/lambdaclass/lambda_ethereum_consensus/pull/324#discussion_r1371536270: > I still find this interaction weird and not very elixir-like. Initializing a different module from here and not from a supervisor, or the other's module init is...
The spec says about `ssz_snappy`'s header: >**Encoding-dependent header:** Req/Resp protocols using the `ssz_snappy` encoding strategy MUST encode the length of the raw SSZ bytes, encoded as an unsigned [protobuf varint](https://developers.google.com/protocol-buffers/docs/encoding#varints)....
Other implementations (lighthouse and prysm, at least) use different types of queues (i.e. FIFO, LIFO) for inter-"process" communication. This enables them to prioritize, for example, newer attestations and older slashing....
Since the macros are using the `+` repetition operator, documentation (i.e. `///`) is needed for the macros to work. Changing this to `*` makes it optional.