Futures
Access hundreds of perpetual contracts
TradFi
Gold
One platform for global traditional assets
Options
Hot
Trade European-style vanilla options
Unified Account
Maximize your capital efficiency
Demo Trading
Introduction to Futures Trading
Learn the basics of futures trading
Futures Events
Join events to earn rewards
Demo Trading
Use virtual funds to practice risk-free trading
Launch
CandyDrop
Collect candies to earn airdrops
Launchpool
Quick staking, earn potential new tokens
HODLer Airdrop
Hold GT and get massive airdrops for free
Pre-IPOs
Unlock full access to global stock IPOs
Alpha Points
Trade on-chain assets and earn airdrops
Futures Points
Earn futures points and claim airdrop rewards
I have closely followed this controversy that is currently stirring up the Bitcoin community. It all started when TheRage posted screenshots claiming that Luke Dashjr was considering a hard fork to protect node operators against CSAM. It quickly went viral.
The interesting thing is that Dashjr immediately denied these allegations, calling the report fake news. But TheRage countered by saying they had verified the screenshots with a video proof, which fueled the controversy. Personally, I think the situation became more complicated when Adam Back, a senior Bitcoin developer, decided to get involved by linking all of this to legal theories from OCEAN, Luke Dashjr's mining pool.
What really stands out is the level of skepticism on social media. People aren't quite sure who to believe. On one side, you have Dashjr shouting fake news, and on the other, you have TheRage claiming to have proof. And in the middle of all this, developers are wondering if this controversy over a potential temporary hard fork really makes sense, especially after the default mempool parameter changes in Bitcoin Core v30.
So far, Dashjr hasn't really responded to requests for further comments, leaving many questions unanswered. Clearly, this case will continue to be a topic of discussion in the coming weeks.