時価総額: $3.8601T -0.240%
ボリューム(24時間): $201.6346B -2.360%
  • 時価総額: $3.8601T -0.240%
  • ボリューム(24時間): $201.6346B -2.360%
  • 恐怖と貪欲の指数:
  • 時価総額: $3.8601T -0.240%
暗号
トピック
暗号化
ニュース
暗号造園
動画
トップニュース
暗号
トピック
暗号化
ニュース
暗号造園
動画
bitcoin
bitcoin

$116533.928400 USD

-2.08%

ethereum
ethereum

$3625.487129 USD

-0.71%

xrp
xrp

$3.090958 USD

-3.61%

tether
tether

$1.000499 USD

0.01%

bnb
bnb

$761.565506 USD

-2.75%

solana
solana

$179.985209 USD

-5.92%

usd-coin
usd-coin

$0.999938 USD

0.00%

dogecoin
dogecoin

$0.226524 USD

-7.37%

tron
tron

$0.312482 USD

0.65%

cardano
cardano

$0.800592 USD

-2.49%

hyperliquid
hyperliquid

$41.584924 USD

-5.86%

stellar
stellar

$0.418925 USD

-3.17%

sui
sui

$3.638506 USD

-3.44%

chainlink
chainlink

$17.535026 USD

-4.41%

bitcoin-cash
bitcoin-cash

$523.015814 USD

0.58%

暗号通貨のニュース記事

Bitcoin (BTC) Core Developers and Community Clash Over OP_RETURN Limits

2025/04/30 18:24

Bitcoin (BTC) Core Developers and Community Clash Over OP_RETURN Limits

Bitcoin Core developer Peter Todd has proposed removing arbitrary size limits on OP_RETURN, a move that could have far-reaching implications for the cryptocurrency's ecosystem.

The proposal, which is still pending approval, has sparked heated debate among developers and community members, highlighting deep divisions over Bitcoin's purpose and future.

OP_RETURN, or operation code, is a small data payload that can be embedded in Bitcoin transactions. It is currently limited to 80 bytes, which several use cases have nearly filled to capacity.

The proposal, no. 32359 on GitHub, aims to streamline Bitcoin's codebase by removing the limit, which is easily bypassed by substitution and forks of Bitcoin Core anyway, according to Todd.

"The proposal is to simply remove the arbitrary size limit and instead set a maximum input count for each transaction (which is currently limited to 200, and which would also prevent transactions from becoming too large), and also to add an output size limit (which is currently limited to 80, and which could be set to something like 512 to provide lots of room for new use cases)," explained the developer.

Many community members have expressed concern over the proposal, arguing that it could lead to a shift in focus away from Bitcoin's monetary use cases.

"Sidechain builders shouldn't influence Bitcoin Core. Bitcoin on its base layer is money and should be only focused on money," said Willem S, founder of Botanix Labs.

"It's also setting a bad precedent to change standard rules like this to make development easier, when there are already workarounds in place."

This isn't the first time Bitcoin developers have had to contend with spammers and adjust the limits accordingly. Back in 2014, during the so-called OP_RETURN wars, services like Veriblock began flooding the chain with data, leading to increased transaction fees and a discussion about the role of maximalism in development.

After testing the limits of 40 bytes, leading to a service called BlockChainComplete pouring gigabytes of data into the chain, developers decided to reduce the cap to 40 bytes.

The heated debate unfolding in the community comes as Bitcoin developers are making progress toward a new version of the standard node software.

免責事項:info@kdj.com

提供される情報は取引に関するアドバイスではありません。 kdj.com は、この記事で提供される情報に基づいて行われた投資に対して一切の責任を負いません。暗号通貨は変動性が高いため、十分な調査を行った上で慎重に投資することを強くお勧めします。

このウェブサイトで使用されているコンテンツが著作権を侵害していると思われる場合は、直ちに当社 (info@kdj.com) までご連絡ください。速やかに削除させていただきます。

2025年07月26日 に掲載されたその他の記事