Dead code, not used since the submitblock RPC was introduced in #1691 5 years ago.
EDIT: This PR now renames the unused arguments in submitblock and prioritisetransaction
I assume thar argument exists for compliance with BIP 22?
Indeed. We could perhaps trim down on the docs (since Core doesn't use it), but including the object shouldn't be made to error.
ok, pushed new version:
723 | if (request.fHelp || request.params.size() < 1 || request.params.size() > 2) {
724 | throw std::runtime_error(
725 | - "submitblock \"hexdata\" ( \"jsonparametersobject\" )\n"
726 | + "submitblock \"hexdata\"\n"
727 | "\nAttempts to submit new block to network.\n"
728 | - "The 'jsonparametersobject' parameter is currently ignored.\n"
I think this line should be kept, as well as the (\"jsonparametersobject\") above.
Removing the details of the parameters below is fine with me if they're all ignored, but just state that exlicitly.
2. \"parameters\" (string, optional) object of optional parameters (currently ignored, but accepted for BIP22 compatbility)
Lets just call them "dummy" instead of bothering to name and define something that is ignored.
updated to change the name of the argument to dummy
I've cherry-picked @TheBlueMatt's commit from #10488 into this PR since they're doing similar things. This PR now renames the unused arguments in prioritisetransaction and submitblock to dummy.
#10488 renamed the unused parameter in prioritisetransaction to dummy. This does the same for submitblock.
(I cherry-picked the commit from #10488 into here because they were doing the same thing for two different RPCs so I thought it made sense to combine them into a single PR. Now that #10488 is merged I've rebased this onto master so this PR only affects submitblock).
utACK 0ef7de953f5eeb27651690871c18c4dc1ee4f83b