ethereum-optimism / ethereum-optimism/optimism
supernode: Make Dependency Setting have good UX
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.5k
- Forks
- 4k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 134
Description
Today, specifying chains to be used in the supernode is very clunky:
the --chains option tells Supernode which chain containers it will configure
and then each virtual node needs to be configured to use a depset as well, to correctly do the upgrade.
Really we shouldn't have to do these different things. Specifying the chains can imply a minimal depset which can be used by the virtual nodes to derive.
@paranoiacblack for extra commentary, as he got hit by this foot-gun.
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 tracing the supernode --chains option and the virtual-node depset configuration. Clarify how a minimal depset should be derived and verify that specifying chains alone lets virtual nodes perform the upgrade without separate depset configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100