Bitcoin Forum

Bitcoin => Bitcoin Technical Support => Topic started by: CJNightowl on September 11, 2018, 04:50:52 AM



Title: Help with error code. \n\n64: scriptpubkey\n
Post by: CJNightowl on September 11, 2018, 04:50:52 AM
I know I am going to sound like an idiot but can anyone decipher this for me?


Title: Re: Help with error code. \n\n64: scriptpubkey\n
Post by: bob123 on September 11, 2018, 12:42:32 PM
You'll need to give us a few more information..

Where does this appear ? In core? Which version, OS, etc.. ?
This could indicate that there is something wrong with one of your outputs.

Post the raw transaction you are trying to send and/or the debug.log.


Title: Re: Help with error code. \n\n64: scriptpubkey\n
Post by: cissrawk on September 11, 2018, 01:19:28 PM
Where does this appear ?
Looks like electrum, since someone got same problem in electrum before, Electrum transaction error (https://github.com/spesmilo/electrum/issues/4472).

Based on that site, looks like you put the wrong bitcoin address (or maybe another address), try check the address if that right or not.
How does that address look like though because from the tx you pasted, it's not a bitcoin address?


Title: Re: Help with error code. \n\n64: scriptpubkey\n
Post by: CJNightowl on September 11, 2018, 01:23:18 PM
Hi guys, thank you so very much for the quick reply. I believe this is the error code error: {'code': 1, 'message': 'the transaction was rejected by network rules.\n\n64: scriptpubkey\n[01000000035cf8610f30c88a973fb0b939257e686c73269f4920d87f923dba92c810d98b1a000000006b483045022100957797d695f413d74b80f36bf35c401fa4e363d6c789aec1496

Any ideas? Thank you in advance.


Title: Re: Help with error code. \n\n64: scriptpubkey\n
Post by: pooya87 on September 12, 2018, 03:11:10 AM
there is something wrong with your transaction, the ScriptPubKey error is indicating there is an issue with one of your outputs, which is most probably turning your transaction to a non standard one which is then rejected by bitcoin core nodes.
although without seeing the actual transaction it would be impossible to say what the problem is for sure. the hex you posted above is incomplete you cut it off in the middle of your first input's scriptsig!