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")
All four built-in networks (base-mainnet, base-sepolia, op-mainnet, op-sepolia) have
faultProofs: trueand theirl2oo-addressset to0x0. However, the--fault-proofsCLI flag defaults tofalse.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
trueto match the network configurations.Fix:
Change the default from
falsetotruein main.go:go
flag.BoolVar(&faultProofs, "fault-proofs", true, "Use fault proofs")