💥 Gate Square Event: #PostToWinFLK 💥
Post original content on Gate Square related to FLK, the HODLer Airdrop, or Launchpool, and get a chance to share 200 FLK rewards!
📅 Event Period: Oct 15, 2025, 10:00 – Oct 24, 2025, 16:00 UTC
📌 Related Campaigns:
HODLer Airdrop 👉 https://www.gate.com/announcements/article/47573
Launchpool 👉 https://www.gate.com/announcements/article/47592
FLK Campaign Collection 👉 https://www.gate.com/announcements/article/47586
📌 How to Participate:
1️⃣ Post original content related to FLK or one of the above campaigns (HODLer Airdrop / Launchpool).
2️⃣ Content mu
Bitcoin updates Core v30 "Open OP_RETURN", opposition sparks: Decentralization is dead
Bitcoin Core v30 relaxes OP_RETURN data restrictions, igniting a tug-of-war over decentralization costs and legal risks (Background: Bitcoin confirms the removal of OP_Return character limit “20% of nodes quietly forked”, OGs express: non-monetary payments are trash) (Background Supplement: Bitcoin's relaxation of OP_RETURN “angers the old OGs”: BTC becomes a junk coin, considering dumping and exiting the industry) Bitcoin Core v30 was officially launched on October 12, increasing the amount of data that can be embedded in OP_RETURN from 80 bytes to a maximum of 100,000 bytes, and under certain conditions, even approaching 4 MB. Supporters view this change as key to unlocking more on-chain applications, while opponents worry it will increase node costs and bring legal risks, replaying the debates of the 2017 “block size wars.” Update: OP_RETURN Unleashed According to the official announcement from Bitcoin Core, v30 not only includes performance optimizations and optional encrypted connections between nodes, but the core highlight is the loosening of OP_RETURN restrictions. To avoid infinite blockchain expansion, OP_RETURN had been locked at 80 bytes. The new version raises the default value to 100,000 bytes and allows developers to embed larger data in a single output. Alex Bergeron, head of Ark Labs ecosystem, stated: “To fully utilize the additional OP_RETURN space and make Bitcoin more like Ethereum, and even better.” He believes that relaxing restrictions can pave the way for Layer 2 technologies such as NFT, DeFi, and even zk-proofs. Opposition: Capacity, Costs, and Legal Shadows Purists raise three main concerns. First, the explosive increase in on-chain data may cause the costs for full node hard drives and bandwidth to skyrocket, undermining decentralization. Second, block space being occupied by non-financial data could raise transaction costs, harming the everyday payment experience. Third, the legal implications are most troubling. Cryptographer Nick Szabo warned on the X platform that if someone uploads illegal content via OP_RETURN, such as CSAM, node operators could face prosecution. He urged: “As a (hopefully) temporary measure, run Knots. I strongly recommend not upgrading to Core v30.” Pragmatists: Market Mechanisms Self-Regulate Supporters counter that block space should be determined by the fee market, not artificially limited. Pavol Rusnak, co-founder of Satoshi Labs, believes the Core team has a mature development process and peer review, and the engineering judgment of v30 is “rational and sound.” They also point out that OP_RETURN data can be pruned by nodes, resulting in a lower long-term burden than hiding data in fake public keys. Data libertarians argue that if there is strong future demand for NFTs, Rollups, etc., those willing to pay higher fees will naturally obtain space. Conversely, if the market does not support it, new features will naturally phase out without hard restrictions. The Rise of Knots: A Clash of Values Dissatisfied community members have turned to support the alternative node software Bitcoin Knots. This project, led by Luke Dashjr, advocates strict filtering of “on-chain junk” and maintaining minimal data principles. BitRef statistics show that there are now about 5,114 nodes using Knots, accounting for 21.48% of the entire network. The speed of data growth shows that many node operators tend to take a conservative route. This struggle is not just a choice of code, but more like a vote of values: should Bitcoin become a universal data layer or focus on peer-to-peer payments? The answer will influence the future flow of capital, talent, and computing power. After Trump took office, the regulatory direction in the United States remains unclear. If legal risks are amplified, the conservative tendency of node operators may accelerate, and on-chain applications will also be constrained. Conversely, if the regulatory framework allows decentralized data storage, Bitcoin could usher in a new wave of development enthusiasm. Regardless of the outcome, v30 has marked a dividing line in the history of Bitcoin development: the tussle between the benefits of open data and the costs of decentralization will continue to test community consensus mechanisms. The next step is for the market to express its stance, which is also the starting point for rethinking Bitcoin's positioning. Related Reports Bitcoin core developers plan to remove OP_RETURN restrictions, opponents shout: crazy! Will it damage BTC's core value? The biggest controversy after Bitcoin Taproot, how will the removal of OP_Return affect the BTC ecosystem? Three OP_CAT protocols in one day, is the Bitcoin ecosystem about to “change”? <Bitcoin updates Core v30 “opens OP_RETURN”, opponents ignite: decentralization is dead> This article was first published in BlockTempo, the most influential blockchain news media.