lambdaclass / lambdaclass/ethlambda
Verify attestations and block signatures before calling handlers
Open
Nobody has claimed this yet.
performance
- Dominant language
- Rust
- Stars
- 82
- Forks
- 28
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 20
Description
We currently verify signatures inside BlockChain. We should instead verify them outside of the STF. This simplifies the code and allows us to improve signature verification performance (the main performance bottleneck) without touching the STF.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Inspect the BlockChain and STF entry points to trace where attestation and block-signature verification currently occurs. Move verification before handlers are called, and consider the work done when the STF no longer performs it while signature behavior is preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100