<p>The OP_RETURN is in the scriptPubKey, which is signed as part of the transaction, so it can't be altered. So it is not malleable.</p>

<p>The known types of malleability are described in <a href="https://github.com/bitcoin/bips/blob/master/bip-0062.mediawiki#Motivation" rel="nofollow noreferrer">BIP 62</a>.</p>

CC BY-SA 3.0
2016-12-20T16:52:19.253Z
2016-12-20T16:52:19.253Z
Ken Shirriff
<p>Can anyone alter the data after OP_return?  </p>

<p>My question needs to have more characters, so I insert an example, that doesn't hurt:</p>

<pre><code>"vout" : [
    {
        "value" : 0.00000000,
        "n" : 0,
        "scriptPubKey" : {
            "asm" : "OP_RETURN 636861726c6579206c6f766573206865696469",
            "hex" : "6a13636861726c6579206c6f766573206865696469",
            "type" : "nulldata"
        }
    }
],
</code></pre>

<transaction-malleability><op-return>
OP_RETURN malleability?
nopara73
# OP_RETURN malleability?

(Asked by: username_0 on 2016-12-20)

Can anyone alter the data after OP_return?  
My question needs to have more characters, so I insert an example, that doesn't hurt:
"vout" : [
    {
        "value" : 0.00000000,
        "n" : 0,
        "scriptPubKey" : {
            "asm" : "OP_RETURN 636861726c6579206c6f766573206865696469",
            "hex" : "6a13636861726c6579206c6f766573206865696469",
            "type" : "nulldata"
        }
    }
],

**Tags:** transaction-malleability, op-return


---

## 1 answers

### Answer by username_1 on 2016-12-20. Score: 4 | Accepted answer

The OP\_RETURN is in the scriptPubKey, which is signed as part of the transaction, so it can't be altered. So it is not malleable.

The known types of malleability are described in [BIP 62](https://github.com/bitcoin/bips/blob/master/bip-0062.mediawiki#Motivation).


---

