I received a few reports that users are unable to sign the transactions generated by http://redeem.bitwatch.co, where one reported:
64: scriptsig-not-pushonly
Error making request to https://cw02.counterwallet.io/_t_api: JSON-RPC Error:
Type: Server error
Code: -32000
Message: Bad status code returned: '500'. result body: '{"result":null,"error":{"code":-25,"message":""},"id":0} '.
It's unclear to me, whether this is a) due to some new incompability between the generated transactions, b) something broken on counterwallet.io or c) a mistake made by the user.
So I gave it a try myself, but I currently face a wall of different errors:
Address Action -> Sign Transaction -> Sign and Broadcast
Similar errors appear in the log, when signing only.
The private key for that address is available and can be successfully revealed via "Show Private Key".
I received a few reports that users are unable to sign the transactions generated by http://redeem.bitwatch.co, where one reported:
It's unclear to me, whether this is a) due to some new incompability between the generated transactions, b) something broken on counterwallet.io or c) a mistake made by the user.
So I gave it a try myself, but I currently face a wall of different errors:
Similar errors appear in the log, when signing only.
The private key for that address is available and can be successfully revealed via "Show Private Key".
The raw transaction to sign:
Thanks
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.