When is op_return scheduled to be 80 bytes?

[box0214]

I read somewhere op_return is going to be upped to 80 bytes from its current 40. When is this scheduled to be changed?

And what are some interesting ideas that people have developed so far to take advantage of this increase?

[TierNolan]

I read somewhere op_return is going to be upped to 80 bytes from its current 40. When is this scheduled to be changed?

I thought it was the other way around, it was going to be 80 but was dropped to 40.

And what are some interesting ideas that people have developed so far to take advantage of this increase?

If you want to commit an 80 byte piece of data, you can just commit Hash(data).  The only disadvantage is that the data isn't stored in the block chain.

[cr1776]

Here is an informative discussion:

https://github.com/bitcoin/bitcoin/pull/5286

[mmortal03]

Here is an informative discussion:

https://github.com/bitcoin/bitcoin/pull/5286

Is there a more recent answer on this? Nothing at that link seems to definitively answer the question for me, and I just heard someone say that it is still 40 bytes.

[achow101]

I'm pretty sure that it is going to stay at 40 bytes and not change back. There is no reason to.

[johoe]

I'm pretty sure that it is going to stay at 40 bytes and not change back. There is no reason to.

Am I missing something? The pull requests mentioned above was merged and 0.11 will support 80 bytes OP_RETURN:

https://github.com/bitcoin/bitcoin/blob/0.11/src/script/standard.h#L28

[TKeenan]

I'm pretty sure that it is going to stay at 40 bytes and not change back. There is no reason to.

Am I missing something? The pull requests mentioned above was merged and 0.11 will support 80 bytes OP_RETURN:

https://github.com/bitcoin/bitcoin/blob/0.11/src/script/standard.h#L28

The final decision to go to 80 was a few weeks ago I think.  You are right - it goes to 80 with V 0.11 I am pretty sure.  I don't know when that will be however.  I think fairly soon.

I'm pretty sure that it is going to stay at 40 bytes and not change back. There is no reason to.

There are huge important reasons to.  Go ask CounterParty why.  80 is a good thing.

[samson]

IMO 128-150 bytes would be better. Increased fees could be applied of course.

sha256 + sha256 + ECDSA signature + a few identifying bytes would be a nice feature to have available.

This kind of thing can only be done in alt coins at the moment.

[johoe]

IMO 128-150 bytes would be better. Increased fees could be applied of course.

sha256 + sha256 + ECDSA signature + a few identifying bytes would be a nice feature to have available.

This kind of thing can only be done in alt coins at the moment.

But you already have an ECDSA signature in the input and it is even checked by the miners before the transaction is confirmed.

All it takes is to send the transaction with an input spending from the key that you want it to be signed with.

[Nicolas Dorier]

80 bytes is scheduled on the 0.11rc1 branch.

[mikewirth]

80 bytes is scheduled on the 0.11rc1 branch.

OK - that is very cool.  But when is 0.11rc1 going to be live?  When does this stuff get adopted?  How does that work?

[Nicolas Dorier]

The rule is currently that more than 40 bytes OP_RETURN are not relayed. (relay rule, not a consensus one)
With 0.11, then some node will relay the transactions while other not.

What you will ultimately see is 80 OP_RETURN are faster and faster to be confirmed as nodes are updated.
I don't know what will be the rate of upgrade. (make your prediction with https://getaddr.bitnodes.io/)
But we know it will eventually be here.