2026-01-07 01:23:27

Kumbaya proposal pushes to restore the 80-byte default limit on OP_RETURN outputs. This technical adjustment aims to optimize blockchain capacity and data handling within the protocol framework. The proposal addresses previous modifications to OP_RETURN constraints, seeking to rebalance transaction efficiency with on-chain data storage capabilities.

This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.

22 Likes

Reward
22
10
Repost
Share

Comment

0/400

WinterWarmthCat

· 16h ago

Are you bringing back the 80-byte limit? Are you reliving history or is it really necessary...

View OriginalReply0

LiquidityWhisperer

· 01-09 06:14

80-byte limit? Here we go again, feels like it will never end.

View OriginalReply0

RugpullTherapist

· 01-08 20:46

Do I have to translate the 80-byte limit again? These people are really bored.

View OriginalReply0

MissingSats

· 01-08 19:38

80 bytes? Again messing with this thing, isn't it a bit unnecessary?

View OriginalReply0

PancakeFlippa

· 01-07 01:53

Return to default after 80 bytes? To be honest, I kind of miss the previous restriction... But this way, it can also optimize transaction efficiency, so it's not too bad.

View OriginalReply0

WalletManager

· 01-07 01:47

The 80-byte limit is essentially about finding a balance between on-chain data storage and transaction efficiency. Whether this move is right depends on the actual performance of on-chain GAS fees.

View OriginalReply0

MainnetDelayedAgain

· 01-07 01:43

According to the database, the "inevitably to be realized" of another technical tweak—how many days have passed since the last promised optimization? It is recommended to be included in the Guinness World Records.

View OriginalReply0

GasFeeCrier