ethereum-optimism / ethereum-optimism/optimism
Make FaultDisputeGame constructor types more accurate for 'maxGameDepth' and 'splitDepth'
Open
- Dominant language
- Go
- Stars
- 6.5k
- Forks
- 4k
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 145
Description
This issue was created based on the following discussion: https://github.com/ethereum-optimism/optimism/pull/12228#discussion_r1783449535
`maxGameDepth` should be `uint64` and `splitDepth` should be `uint32` and not `uint256`.
Contributor guide
Research direction
Start with the linked pull-request discussion and locate the FaultDisputeGame constructor. Verify the constructor declarations and relevant tests or compilation checks; done means maxGameDepth uses uint64 and splitDepth uses uint32 instead of uint256.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- solidity
- Domain
- blockchain
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100