RPC API reqSigs for P2SH outs #13331

issue 4tochka opened this issue on May 27, 2018

4tochka commented at 7:33 AM on May 27, 2018: none

When I call RPC API > bitcoin-cli getrawtransaction de816dca84ab4af9c98f40d826807aa93600978acf62cfa98bc148c80f789c92 1

Response contains:

{ "value": 0.29932592, "n": 1, "scriptPubKey": { "asm": "OP_HASH160 59671c40861324648e16c461ded83672ccaf3609 OP_EQUAL", "hex": "a91459671c40861324648e16c461ded83672ccaf360987", "reqSigs": 1, "type": "scripthash", "addresses": [ "39qjarFnk49tD9cJR5iMqiJupY2v2vNeg4" ] }

But script under P2SH address unknown and we cant count real reqSigs API give "reqSigs": 1 for all P2SH outs, I suppose that this behavior is not correct
MarcoFalke added the label RPC/REST/ZMQ on May 29, 2018
MarcoFalke commented at 1:47 AM on April 26, 2020: member

The feature request didn't seem to attract much attention in the past. Also, the issue seems not important enough right now to keep it sitting around idle in the list of open issues.

Closing due to lack of interest. Pull requests with improvements are always welcome.
MarcoFalke closed this on Apr 26, 2020
DrahtBot locked this on Feb 15, 2022

Contributors

Labels