Update `OP_RETURN` Size Limit to 80 Bytes #690

Closed
adamkrellenstein opened this Issue Feb 3, 2015 · 10 comments

Projects

None yet

4 participants

@adamkrellenstein
Member

Next version of Bitcoin Core should relay transactions with an 80-byte OP_RETURN output: bitcoin/bitcoin#5286.

Still probably can't make this the default encoding mechanism yet, because it'll be slower than multi-sig. See #691.

@deweller
deweller commented Feb 3, 2015

Interesting. Out of curiosity, why would this method be slower?

@adamkrellenstein
Member

Oh, just because some minering pools have OP_RETURN support turned off, last I checked. If that ever changes, we can default to using OP_RETURN when the payload size is small enough.

@btcdrak
Contributor
btcdrak commented Feb 3, 2015

@adamkrellenstein Mining pools mine OP_RETURN, there are no problems with it but until Bitcoin 0.11 rolls out, there is no point changing the encoding defaults because most nodes wont relay 80 byte OP_RETURNs

@adamkrellenstein
Member

@btcdrak, really? We can start using 40-byte OP_RETURNs now, then. EDIT: That's big enough for a send transaction, I think.

@btcdrak
Contributor
btcdrak commented Feb 3, 2015

sure, 40-bytes relays and mines. There are a ton of services using OP_RETURN encodings already.

@adamkrellenstein
Member

As I said, last I checked, one of the big pools wasn't mining them, so there was often a delay.

@btcdrak
Contributor
btcdrak commented Feb 3, 2015

BTCGuild dont matter anymore, they are 3%. Eligius also blocks counterparty txs regardless.

@adamkrellenstein
Member

Haha. See #691.

@robby-dermody
Member

Closed, as this is implemented.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment