Compute `Version` byte correctly

Open
#1,751 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
go
Domain
backend, blockchain

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.

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 Version itself
  • For future Validium-specific upgrades, the if ValidiumMode block is insufficient
Dominant language
Go
Stars
741
Forks
632
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from scroll-tech/scroll

All issues in scroll-tech/scroll

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.