-
Notifications
You must be signed in to change notification settings - Fork 206
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update OP_RETURN
Size Limit to 80 Bytes
#690
Comments
Interesting. Out of curiosity, why would this method be slower? |
Oh, just because some minering pools have |
@adamkrellenstein Mining pools mine |
@btcdrak, really? We can start using 40-byte |
sure, 40-bytes relays and mines. There are a ton of services using |
As I said, last I checked, one of the big pools wasn't mining them, so there was often a delay. |
BTCGuild dont matter anymore, they are 3%. Eligius also blocks counterparty txs regardless. |
Haha. See #691. |
Closed, as this is implemented. |
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.The text was updated successfully, but these errors were encountered: