- Topic
376 Popularity
120 Popularity
124 Popularity
162k Popularity
28 Popularity
- Pin
- 🎉 Hey Gate Square friends! Non-stop perks and endless excitement—our hottest posting reward events are ongoing now! The more you post, the more you win. Don’t miss your exclusive goodies! 🚀
🆘 #Gate 2025 Semi-Year Community Gala# | Square Content Creator TOP 10
Only 1 day left! Your favorite creator is one vote away from TOP 10. Interact on Square to earn Votes—boost them and enter the prize draw. Prizes: iPhone 16 Pro Max, Golden Bull sculpture, Futures Vouchers!
Details 👉 https://www.gate.com/activities/community-vote
1️⃣ #Show My Alpha Points# | Share your Alpha points & gains
Post your - 💙 Gate Square #Gate Blue Challenge# 💙
Show your limitless creativity with Gate Blue!
📅 Event Period
August 11 – 20, 2025
🎯 How to Participate
1. Post your original creation (image / video / hand-drawn art / digital work, etc.) on Gate Square, incorporating Gate’s brand blue or the Gate logo.
2. Include the hashtag #Gate Blue Challenge# in your post title or content.
3. Add a short blessing or message for Gate in your content (e.g., “Wishing Gate Exchange continued success — may the blue shine forever!”).
4. Submissions must be original and comply with community guidelines. Plagiarism or re
Controversial Changes to Bitcoin Codes Being Discussed! The Community is Divided, Here are the Details
Bitcoin Core developers are planning to completely remove the 80-byte data limit on OP_RETURN outputs in the upcoming release of the Bitcoin (BTC) software. This move has sparked discussions within the developer community.
OP_RETURN is a feature that allows a small amount of data to be embedded in Bitcoin transactions and creates an unspendable output (UXTO). This method gained significant attention, especially during the ordinals and inscription craze that occurred in early 2024.
Bitcoin Core contributor Greg Sanders stated in a GitHub announcement on May 5 that the current 80-byte limit would be completely removed and an unlimited number of OP_RETURN outputs would be allowed. Sanders argued that the current limit has lost its functionality and that removing this restriction would encourage less harmful behaviors on the chain.
"This boundary directs users towards alternatives that are more challenging for the network and lack transparency," said Sanders, arguing that large data inscriptions and various indirect methods used to bypass the existing limit lead to unnecessary load on the network, and added: "When the gentle path is closed, determined users turn to non-gentle paths. Some use naked multisig or fake output keys, which is exactly the outcome that OP_RETURN aimed to prevent."
Developers evaluated three options: maintaining the border, enhancing it, or completely removing it. While the first two options were deemed arbitrary and ineffective, the proposal for unlimited access found broad but non-consensual support in discussions on GitHub.