Verify attestations and block signatures before calling handlers
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- rust
- Domain
- blockchain
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.
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.
- Dominant language
- Rust
- Stars
- 82
- Forks
- 28
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 20
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.
More from lambdaclass/ethlambda
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
lambdaclass/ethlambda#529 · 4 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
lambdaclass/ethlambda#521 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
lambdaclass/ethlambda#609 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
lambdaclass/ethlambda#602 ·
-
performance
Difficulty 4/5 3-5 days Newbie friendliness 55/100
lambdaclass/ethlambda#599 · 1 comment ·
All issues in lambdaclass/ethlambda
Similar issues
-
todo:perf
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
ACP agents get no MCP servers when the thread is created before the project's first worktree loads Openstate:needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
zed-industries/zed#64611 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
ontola/atomic-server#1625 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
objectionary/phie#154 ·