lambda_ethereum_consensus
lambda_ethereum_consensus copied to clipboard
Elixir implementation of an Ethereum consensus client, which offers high reliance & fault tolerance
Context: #1013 ERC-2335 keystores have a `path` field with a [EIP-2333](https://eips.ethereum.org/EIPS/eip-2333) path for deriving the secret. We should support non-empty values of that field.
**Motivation** We need to track all supervisors and other processes with their init args, so that we can fix the restart strategies as per #1097
When using a localnet with Kurtosis, if we are chosen to build the first block we fail. Error message: `ERROR 14:11:03.050 [Validator] Failed to start building payload for slot 1....
We added #1102 to keep our db small but this breaks the spec. We should remove this logic. Instead, we should be able to serve blob_sidecars up until MIN_EPOCHS_FOR_BLOB_SIDECARS_REQUESTS epochs...
We need this to keep our db small. We will need to change this in the future since this breaks the specs.
**Motivation** Validator module is getting big and hard to follow. As part of a refactor of duties, I've extracted it into it's own module and added typespecs
We added https://github.com/lambdaclass/lambda_ethereum_consensus/pull/1092 to keep our db small but this breaks the spec. We should remove this logic. Instead, we should be able to serve block up until `MIN_EPOCHS_FOR_BLOCK_REQUESTS` epochs...
We have genservers in a supervisor tree but when they are restarted due to a failure, the new state is not in sync with the rest of the app. One...
The go libp2p module gets this error and the node doesn't recover, but process still lives. ``` panic: listen udp 0.0.0.0:9000: bind: address already in use goroutine 1 [running]: libp2p_port/internal/utils.PanicIfError(...)...
Might be a configuration issue, but when first starting the node, the following error usually appears a couple of times: ``` ERROR 09:49:52.347 #PID running BeaconApi.Endpoint (connection #PID, stream id...