Tomás Grüner
Tomás Grüner
The implementation should pass the [light_client](https://github.com/ethereum/consensus-specs/blob/dev/tests/formats/light_client/single_merkle_proof.md) spec-tests. [More info on Merkle proofs](https://ethereum.org/es/developers/tutorials/merkle-proofs-for-offline-data-integrity/). [The expected merkle proof generation function is this one](https://github.com/ethereum/consensus-specs/blob/bf09b9a7c4a7b311e86823235815daf31b117574/specs/altair/light-client/full-node.md?plain=1#L30-L36). [More info on proof formats used here](https://github.com/ethereum/consensus-specs/blob/dev/ssz/merkle-proofs.md).
We're currently ignoring invalid requests without sending any response. According to the spec, we should respond with a status code 1 and an error message. We should add this behavior...
There are multiple that can be done. For an example, see: https://github.com/lambdaclass/lambda_ethereum_consensus/blob/74663965827d5eeb0e88f40fa134e0899e73394a/test/unit/snappyex_test.exs#L102-L119 As a start, we can add it for basic types, just doing hashing of integers (for bools we...
We currently support fetching a weak subjectivity checkpoint (finalized beacon state and block) from a URL. We'd like to also be able to fetch it from a file/files.
Blocked by #726 We are currently trying a checkpoint sync with a public URL. If that endpoint were to be down, our CI would fail. This is a problem that...
We already have Snappy stream decompression, but we still need to work on compression. See #224 and #710 for context
This should also mention how to create a JWT secret: https://lighthouse-book.sigmaprime.io/run_a_node.html#step-1-create-a-jwt-secret-file
Created from: https://github.com/lambdaclass/lambda_ethereum_consensus/pull/225#discussion_r1337571028 Currently, the Peerbook just waits for a second and retries, but maybe there's a better way to handle this.