lambdaclass / lambdaclass/lambda_ethereum_consensus
docs: A pointer from each large topic to a resource
Open
Nobody has claimed this yet.
documentation
- Dominant language
- Elixir
- Stars
- 109
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
Some examples:
- Gasper basics from eth2book.
- Validator features from the specs.
- Slot lifecycle from the "anatomy of a slot" video.
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
Start by inventorying the project's large documentation topics and comparing them with the example resources: eth2book for Gasper basics, the specs for validator features, and the “anatomy of a slot” video. Done means each large topic has a useful pointer to an external resource; the issue does not name specific documentation files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100