<div dir="ltr"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid">While I am not opposing the proposal, I am not sure about your statistics because while Counterparty is not currently using OP_RETURN encoding, you should factor in the number of CP transactions that would have been OP_RETURNs if they had been permitted (100,000 since inception according their blog[1] with monthly charts at their block explorer[2]).</blockquote><div><br></div><div>Sure, but even if they are not permitted to store their data in OP_RETURN, they will still store it in the blockchain in bare multisig outputs, so it's not contributing to an overhead (in fact, it would consume less space in the blockchain if they used OP_RETURN). </div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Nov 18, 2014 at 5:47 PM, Btc Drak <span dir="ltr"><<a href="mailto:btcdrak@gmail.com" target="_blank">btcdrak@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span>On Mon, Nov 17, 2014 at 11:43 AM, Flavien Charlon <span dir="ltr"><<a href="mailto:flavien.charlon@coinprism.com" target="_blank">flavien.charlon@coinprism.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid"><div dir="ltr"><span><div>> My main concern with OP_RETURN is that it seems to encourage people to use the blockchain as a convenient transport channel</div><div><br></div></span><div>The number one user of the blockchain as a storage and transport mechanism is Counterparty, and limiting OP_RETURN to 40 bytes didn't prevent them from doing so. In fact they use multi-sig outputs which is worse than OP_RETURN since it's not always prunable, and yet let them store much more than 40 bytes.</div><div><br></div><div>For <a href="https://github.com/OpenAssets/open-assets-protocol" target="_blank">Open Assets</a>, we need to store a URL in the OP_RETURN output (with optionally a hash) plus some bytes of overhead. 40 bytes comes really short for that. The benefit of having a URL in there is that any storage mechanism can be used (Web, FTP, BitTorrent, MaidSafe...), whereas with only a hash, you have to hardcode the storing mechanism in the protocol (and even then, a hash is not enough to address a HTTP or FTP resource). Storing only a hash is fine for the most basic timestamping application, but it's hardly enough to build something interesting.</div><div><br></div><div>I've counted the number of OP_RETURN outputs in the blockchain for the month of October 2014. There were 1,674 OP_RETURNs for a span of 4,659 blocks. Assuming they were all 40 bytes (the average is probably less than half of that), that means an increase of 14.37 bytes per block. Considering a 1 MB block, that's about <span>0.0013% of the block used up by OP_RETURN data in average.</span></div><div><span><br></span></div><div><span>Increasing to 80 bytes will have a negligible impact on bandwidth and storage requirements, while being extremely useful for many use cases where a hash only is not enough.</span></div></div></blockquote><div><br></div></span><div>While I am not opposing the proposal, I am not sure about your statistics because while Counterparty is not currently using OP_RETURN encoding, you should factor in the number of CP transactions that would have been OP_RETURNs if they had been permitted (100,000 since inception according their blog[1] with monthly charts at their block explorer[2]).</div><div><br></div><div>Refs:<br></div><div>[1] <a href="http://counterparty.io/news/celebrating-100000-transaction-on-the-counterparty-network/" target="_blank">http://counterparty.io/news/celebrating-100000-transaction-on-the-counterparty-network/</a></div><div>[2] <a href="http://blockscan.com/" target="_blank">http://blockscan.com/</a></div><div><br></div></div></div></div>
</blockquote></div><br></div>