ethereum-optimism / ethereum-optimism/optimism
op-node: use block signing V2 endpoint
Open
A-op-node
A-op-signer
- Dominant language
- Go
- Stars
- 6.5k
- Forks
- 4k
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 145
Description
Introduce a new CLI flag to start using the V2 block signing endpoint.
This then allows operators to roll out the op-signer server and op-signer client changes smoothly.
At a later point we can then remove the V1 block signing, and make the new V2 the default.
Contributor guide
Research direction
Start by locating op-node's CLI flag handling and the client code that calls the block signing endpoint. Trace how the current V1 endpoint is selected; done means a new flag can opt into V2 while preserving the existing V1 default for a gradual rollout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100