Document architectural choices
Maintainers usually reply within 6 days
@dicethedev is already working on this.
Since Jul 29, 2026.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- rust
- Domain
- blockchain, documentation
Research direction
Review #520 and compare crates/blockchain/src/lib.rs with crates/blockchain/src/store.rs, including how the spec-test runner exercises store.rs. Document the preference for changes in lib.rs and for wrapping leanVM primitives in ethlambda-crypto; the work is done when these architectural choices are recorded for future contributors.
Written by the indexing model from the issue text.
Description
#520 is an example. Generally, modifying crates/blockchain/src/lib.rs should be preferred over modifying crates/blockchain/src/store.rs. We have this weird split between kind-of-pure stuff in store.rs and non-pure stuff on lib.rs, because store.rs is ported almost one-to-one from the spec. The spec-tests exercise only that module, and any changes to store.rs will likely impact our spec-test runner.
Another preference would be wrapping leanVM primitives inside ethlambda-crypto. This is done to centralize changes due to leanVM updates.
We can start by writing this down in a document and later expand on it with other preferences.
- Dominant language
- Rust
- Stars
- 86
- Forks
- 34
- Avg merge
- 9d 20h
- Merged PRs (30d)
- 77
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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#850 ·
Maintainers usually reply within 6 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
lambdaclass/ethlambda#777 · 1 reaction ·
Maintainers usually reply within 6 days
-
Run all gossip validation testsMay be free again @dicethedev claimed this 9 days ago, and no pull request is open. Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
lambdaclass/ethlambda#725 · 2 comments ·
Maintainers usually reply within 6 days
-
Handle malformed DB dataMay be free again @dicethedev claimed this 115 days ago, and no pull request is open. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
lambdaclass/ethlambda#529 · 4 comments ·
Maintainers usually reply within 6 days
-
validator: accept a JSON produceBlockV3 answer, so proposals work behind blobberPossibly taken @MegaRedHand claimed this today. Open
Difficulty 3/5 1-2 days Newbie friendliness 30/100
lambdaclass/ethlambda#861 ·
Maintainers usually reply within 6 days
All issues in lambdaclass/ethlambda
Similar issues
-
help wanted needs investigation priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
AstrBotDevs/AstrBot-desktop#197 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
tomast1337/Puppeter-PptxGenJS#440 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
n0-computer/iroh#4709 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
qingjian-team/qingjian#1114 ·
Maintainers usually reply within 2 days