lambdaclass / lambdaclass/lambda_ethereum_consensus
Config/Preset parsing is fixed on SSZ_NIF
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 109
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
In Elixir, the Chainspect is generated following a set of preset yamls but on the SSZ_NIF, config.rs (which is really the preset as mentioned in #604) sets all values as fixed Unsigned types in the config structs. This is error prone and it stays out of date when the yaml changed. We need to fix it.
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 reading config.rs in SSZ_NIF and the preset YAML files used to generate Chainspect, then review the context from issue #604. Trace how the config structs are built and compare their fixed Unsigned values with the YAML definitions. Done means the SSZ_NIF configuration reflects the preset YAMLs instead of remaining manually fixed and becoming outdated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir, rust, yaml
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100