fix: set --fault proofs CLI default to true for built in fault-proof networks
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 88/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- go
- Domain
- blockchain, cli
Research direction
Open main.go and locate the flag.BoolVar declaration for --fault-proofs. Change its default to true, matching the faultProofs setting on the four built-in networks. Done means the shown withdrawer command no longer requires users to provide --fault-proofs explicitly.
Written by the indexing model from the issue text.
Description
All four built-in networks (base-mainnet, base-sepolia, op-mainnet, op-sepolia) have faultProofs: true and their l2oo-address set to 0x0. However, the --fault-proofs CLI flag defaults to false.
A user running a simple command like:
withdrawer --network base-mainnet --withdrawal --rpc --private-key
...gets a crash with: "Fault proofs are required on this network, please provide the --fault-proofs flag".
Since all built-in networks use fault proofs, the default should be true to match the network configurations.
Fix:
Change the default from false to true in main.go:
go
flag.BoolVar(&faultProofs, "fault-proofs", true, "Use fault proofs")
- Dominant language
- Go
- Stars
- 537
- Forks
- 373
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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.
More from base/withdrawer
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
base/withdrawer#89 · 3 comments ·
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
base/withdrawer#78 · 3 comments ·
-
rtrtrtrt Open
Difficulty 5/5 Over a week Newbie friendliness 1/100
base/withdrawer#94 ·
-
Difficulty 5/5 Over a week Newbie friendliness 10/100
base/withdrawer#93 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
base/withdrawer#73 · 1 comment · 1 reaction ·
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
enhancement needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/kueue#15947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
priority: p3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
googleapis/librarian#7636 ·