<p>Can you give the full transaction, and decode it? </p>

<p>The default client nodes will not broadcast your transaction because it is not standard. That may be the problem. If it is mined into a block, however, they would not refuse that block just because it had non-standard transactions, because the transaction would be <strong>valid</strong> even though it might not be <strong>standard</strong>. For more on this, you may find the below questions helpful. </p>

<ul>
<li><p><a href="https://bitcoin.stackexchange.com/questions/21123/which-scripts-are-currently-considered-standard-and-therefore-actually-propagate">Which scripts are currently considered standard and therefore actually propagated?</a>. </p></li>
<li><p><a href="https://bitcoin.stackexchange.com/questions/23435/what-node-implementations-and-mining-pools-relay-and-process-non-standard-scri">What node implementations and mining pools relay and process &#39;non-standard&#39; scripts?</a>. </p></li>
</ul>

<p>That might not even be the problem, though. It could be signed incorrectly. You should make sure that the OP_RETURN output was included before the transaction was signed. You can verify that the signature of the transaction is valid using the code in this question: <a href="https://bitcoin.stackexchange.com/questions/32194/how-to-verify-ecdsa-of-a-sample-litecoin-tx-using-pycoin/32217#32217">How to verify ECDSA of a sample litecoin tx using pycoin?</a>. </p>

CC BY-SA 3.0
2014-10-31T13:57:56.197Z
2014-10-31T14:15:58.790Z
2017-04-13T12:47:32.940Z
morsecoder
<p>I created transaction with OP_RETURN adding some information. Even though transaction hash created successfully, the transaction doesn't go to blockchain properly. Could you please help me to do this transaction properly?</p>

<p>"scriptPubKey": </p>

<p>{</p>

<p>"asm": "OP_RETURN 726173656c6140676d61696c2e636f6d7e39383732363733383834",</p>

<p>"hex": "6a1b726173656c6140676d61696c2e636f6d7e39383732363733383834",</p>

<p>"type": "nonstandard"</p>

<p>}</p>

<bitcoind>
OP_RETURN transaction doesn't go to the blockchain
Rasela Don
# OP_RETURN transaction doesn't go to the blockchain

(Asked by: username_0 on 2014-10-31)

I created transaction with OP\_RETURN adding some information. Even though transaction hash created successfully, the transaction doesn't go to blockchain properly. Could you please help me to do this transaction properly?

"scriptPubKey":

{

"asm": "OP\_RETURN 726173656c6140676d61696c2e636f6d7e39383732363733383834",

"hex": "6a1b726173656c6140676d61696c2e636f6d7e39383732363733383834",

"type": "nonstandard"

}

**Tags:** bitcoind


---

## 1 answers

### Answer by username_1 on 2014-10-31. Score: 1

Can you give the full transaction, and decode it?

The default client nodes will not broadcast your transaction because it is not standard. That may be the problem. If it is mined into a block, however, they would not refuse that block just because it had non-standard transactions, because the transaction would be **valid** even though it might not be **standard**. For more on this, you may find the below questions helpful.

* [Which scripts are currently considered standard and therefore actually propagated?](https://bitcoin.stackexchange.com/questions/21123/which-scripts-are-currently-considered-standard-and-therefore-actually-propagate).
* [What node implementations and mining pools relay and process 'non-standard' scripts?](https://bitcoin.stackexchange.com/questions/23435/what-node-implementations-and-mining-pools-relay-and-process-non-standard-scri).

That might not even be the problem, though. It could be signed incorrectly. You should make sure that the OP\_RETURN output was included before the transaction was signed. You can verify that the signature of the transaction is valid using the code in this question: [How to verify ECDSA of a sample litecoin tx using pycoin?](https://bitcoin.stackexchange.com/questions/32194/how-to-verify-ecdsa-of-a-sample-litecoin-tx-using-pycoin/32217#32217).


---

