Clarification on OP_RETURN size limit. · MetaNet Membership Club

This topic has 2 replies, 2 voices, and was last updated 6 years ago by Brendan Lee.

Viewing 3 posts - 1 through 3 (of 3 total)

Author

Posts
January 17, 2019 at 3:08 am #1831
Anonymous
- Novice
Hello,

Right now I am setting an 83 byte limit to my OP_RETURN data fields, and I wanted to check if that is correct as to being the maximum limit for a transaction to propagate under standard consensus? I’m having some trouble exactly confirming this and figured I would just ask here anyway in case there were some kind of developments around that at all that I should be aware of, as I’m writing some more APIs. ( I see that many state the length being 80 however because of the way text compresses into 7 bit fragments I read that it lets you get away with 83?)

I figured I’d ask this here just to save time as well as get any feedback or corrections to my assumptions.

Thanks!
January 18, 2019 at 3:41 am #1847
Anonymous
- Novice
FYI, for anybody using the default 400 satoshi fee that Datapay defaults to, the maximum length message you can propagate out is 196 characters long in UTF-8.
January 21, 2019 at 4:01 am #1875
Brendan Lee
- Novice
Hi WR, love your work lately.
The current consensus limit is 223 bytes in an OP_RETURN script, but this includes the OP_RETURN opcode, and the push instruction which is 1 byte for less than 73 bytes and 2 bytes (OP_PUSHDATA <datalength>) for anything more, so is fundamentally limited to 220B of actual data. That limit also includes any push instructions that you might include to help explorers parse your data. This was a limitation we hit a lot at Tokenized.
Ping me if you want more info. I can show you how we use the data carrier in our protocol.
Author

Posts

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.