scroll-tech / scroll-tech/scroll
Compute `Version` byte correctly
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 741
- Forks
- 632
- PR merge metrics
- No merged PRs in 30d
Description
This issue is to track the behaviour of https://github.com/scroll-tech/scroll/blob/9c8782fc1283ce95b7406039bbb621606b8a9044/coordinator/internal/utils/version.go#L13-L38
post merging https://github.com/scroll-tech/scroll/pull/1737
- Galileo support must be added in
func Versionitself - For future Validium-specific upgrades, the
if ValidiumModeblock is insufficient
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 with coordinator/internal/utils/version.go at the Version function and compare its behavior with pull request #1737. Determine the expected Version byte for Galileo and future Validium-specific upgrades; the work is complete when both checklist items are resolved and the resulting behavior is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, blockchain
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100