Increasing the OP_RETURN maximum payload size



Summary:

In a discussion about OP_RETURN, Flavien Charlon expressed concern that it encourages using the blockchain as a transport channel. However, Pieter argued that Counterparty, which is the main user of the blockchain for storage and transport, uses multi-sig outputs to store more than 40 bytes. The limit was not imposed to stop Counterparty from using it, but to avoid giving others the impression that OP_RETURN was intended for data storage. For Open Assets, they need to store a URL in the OP_RETURN output along with some bytes of overhead, which 40 bytes are insufficient for. Storing a URL allows any storage mechanism to be used, whereas with only a hash, the storing mechanism must be hardcoded in the protocol. Pieter raised concerns about publishing the data to everyone, exposing oneself to censorship and potentially decreased privacy for users. For most colored coin applications, just having the color transfer information in external data sent directly to the receiver with transactions committing to it should suffice.


Updated on: 2023-05-19T19:30:40.720376+00:00