# op\_return?

**URL:** <https://forums.counterparty.io/t/op-return/130>\
**Category:** Counterparty\
**Created:** [February 21, 2014, 8:15am UTC](https://forums.counterparty.io/t/op-return/130 "2014-02-21T08:15:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![davidpbrown](https://yyz2.discourse-cdn.com/flex004/user_avatar/forums.counterparty.io/davidpbrown/32/8_2.png) [@davidpbrown](https://forums.counterparty.io/u/davidpbrown)\
**Post date:** [February 21, 2014, 8:15am UTC](https://forums.counterparty.io/t/op-return/130/1 "2014-02-21T08:15:10Z")

</div>

The [CounterParty white paper](https://github.com/PhantomPhreak/Counterparty) talks of using OP\_RETURN.  
  
However, see [this Bitcointalk thread](https://bitcointalk.org/index.php?topic=391491.0), suggests that there might be a problem getting that detail relaying and included in blocks.   
Specifically   
[quote][https://bitcoinfoundation.org/blog/?p=290](https://bitcoinfoundation.org/blog/?p=290)  
Summary: In 0.9, OP\_RETURN data TxOut will become a standard transaction type. However, this is controversial, and some miners may just reject OP\_RETURNs with data junk.[/quote]  
  
Thoughts?.. Is this a known issue and what is XCP’s approach to this??  
  
I’m expecting this type of detail could not suffer the same issue that is transaction maleabiility but wonder whether miners would have an option to corrupt OP\_RETURN data.  
  
I wonder that for a lot of real world needs, different applications will need to create their own blockchains, and that from the little I’ve seen of Mastercoin and other Bitcoin2.0 protocols, the currency options within those might also solve other problems by shielding those applications from off topic problems.

---

<div class="post-metadata">

**Author:** ![Bountyful](https://yyz2.discourse-cdn.com/flex004/user_avatar/forums.counterparty.io/bountyful/32/4_2.png) [@Bountyful](https://forums.counterparty.io/u/Bountyful)\
**Post date:** [February 21, 2014, 8:16pm UTC](https://forums.counterparty.io/t/op-return/130/2 "2014-02-21T20:16:52Z")

</div>

Today, Counterparty uses bitcoin multi-sig. OP\_RETURN is not yet available and miners may not yet accept these transactions, but they will accept multi-sig as standard transaction.