- Remove
"hex"from the decodescript RPCResult doc - Add
"segwit" to the doc
Follow up to a6099ef319a73e2255dca77065600abb22c4f5f8 and 4f933b3d23010d3b03998460290faed97cd6f236
"hex" from the decodescript RPCResult doc"segwit" to the docFollow up to a6099ef319a73e2255dca77065600abb22c4f5f8 and 4f933b3d23010d3b03998460290faed97cd6f236
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--174a7506f384e20aa4161008e828411d-->
Reviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.
625 | - " \"type\":\"type\", (string) The output type\n" 626 | - " \"reqSigs\": n, (numeric) The required signatures\n" 627 | - " \"addresses\": [ (json array of string)\n" 628 | - " \"address\" (string) bitcoin address\n" 629 | + " \"asm\":\"asm\", (string) Script public key\n" 630 | + " \"type\":\"type\", (string) The output type\n"
In commit "rpc: Clarify decodescript RPCResult doc" (faad33ff15398159115afd4799e3c97ac3df2a3a)
Might be nice to list possible type strings here.
Done
utACK fa926ec24fb3d07de32bd8f67a297f9e4f0822a6. Only change since last review is listing possible output types in the help string using a new GetAllOutputTypes function
Milestone
0.19.0