Site iconSite icon ForkLog

Bitcoin Core to Remove Data Volume Limit for OP_RETURN

Bitcoin Core to Remove Data Volume Limit for OP_RETURN

The upcoming release of the Bitcoin Core client will by default allow more than 80 bytes of information in OP_RETURN outputs and permit any number of them.

“The long-standing limit, initially a soft signal to economize block space for non-payment proof-of-publication data, has outlived its usefulness,” noted developer Greg Sanders.

Debates over the restriction on the volume of third-party data published via the OP_RETURN script intensified since late April. Bitcoin developer Peter Todd, who was dubbed the creator of the first cryptocurrency in an HBO documentary, proposed lifting the limit.

Sanders highlighted two main arguments for why the previously set 80-byte limit has become counterproductive and, in many respects, “destructive”:

According to Sanders, Bitcoin Core developers considered three options:

The innovation does not abolish the block limit of 4 million weight units. “Dust” outputs are still rejected, and signature and ancestor/descendant operation limits prevent memory pool growth, the programmer emphasized.

In his view, removing the 80-byte rule offers two main advantages:

“The change affirms that Bitcoin is governed by transparent, minimal rules, not editorial preferences. By discarding a constraint that no longer works, Bitcoin Core maintains policy integrity and allows the fee market to arbitrate competing demands,” Sanders stated.

Earlier, February’s decline in on-chain activity on the Bitcoin network to an annual low was largely attributed by analysts to a drop in OP_RETURN outputs in transactions.

Exit mobile version