Is your feature request related to a problem? Please describe.
There are now quite a lot of CLI flags (especially in spam) and they're starting to look messy.
Describe the solution you'd like
Organize the args in the help menu display first by logical groups, then alphabetically (per group). "Logical groups" in this context just means args that are likely to be passed together.
ideas for logical groups in contender spam:
common:
--rpc-url--builder-url--tps, --tpb--duration--private-key--min-balance--env
payload adjustments:
--tx-type--bundle-type--optimism--rpc-batch-size--gas-price
runtime adjustments:
--override-senders--optimistic-nonces--ignore-receipts--forever--pending-timeout--accounts-per-agent--gen-report--redeploy--skip-setup
engine API settings:
--auth-rpc-url--jwt-secret--message-version--call-forkchoice
same sort of organization should apply to the other commands.
ideally we have some spacing between the groups, and headers
Is your feature request related to a problem? Please describe.
There are now quite a lot of CLI flags (especially in
spam) and they're starting to look messy.Describe the solution you'd like
Organize the args in the help menu display first by logical groups, then alphabetically (per group). "Logical groups" in this context just means args that are likely to be passed together.
ideas for logical groups in
contender spam:common:
--rpc-url--builder-url--tps,--tpb--duration--private-key--min-balance--envpayload adjustments:
--tx-type--bundle-type--optimism--rpc-batch-size--gas-priceruntime adjustments:
--override-senders--optimistic-nonces--ignore-receipts--forever--pending-timeout--accounts-per-agent--gen-report--redeploy--skip-setupengine API settings:
--auth-rpc-url--jwt-secret--message-version--call-forkchoicesame sort of organization should apply to the other commands.
ideally we have some spacing between the groups, and headers