Open cipig opened 5 years ago
BTG uses sighash forkid AFAIK, should be easy to fix.
@cipig is this still a problem or can we close this issue?
nothing changed, so i assume the problem is the same i can try again, we now have "sighash forkid" param
oh, i see in my docs that i already tried in the past with fork_id and signature_version
{
"coin": "BTG",
"name": "bitcoingold",
"fname": "Bitcoin Gold",
"rpcport": 12332,
"pubtype": 38,
"p2shtype": 23,
"wiftype": 128,
"fork_id": "0x40",
"signature_version": "witness_v0",
"txfee": 10000,
"segwit": true,
"bech32_hrp": "btg",
"mm2": 1,
"required_confirmations": 1,
"avg_blocktime": 10,
"protocol": {
"type": "UTXO"
}
},
tried with all 3 possible signature_version and all 3 failed: witness_v0: mandatory-script-verify-flag-failed (Operation not valid with the current stack size) (code 16) fork_id: mandatory-script-verify-flag-failed (Signature must be zero for failed CHECK(MULTI)SIG operation) (code 16) base: mandatory-script-verify-flag-failed (Signature must be zero for failed CHECK(MULTI)SIG operation) (code 16)
sendrawtransaction
with BTG fails (sighash)it is the same as with BCH and needs special treatment in the code this special stuff was in mm1, maybe it can be simply ported