[Michael Saylor Releases Bitcoin Tracker Information] On December 28, Strategy founder Michael Saylor released information related to the Bitcoin Tracker. According to past patterns, Strategy typically discloses Bitcoin accumulation information the day after such announcements.

[WLFI Governance Voting Launches, Proposes Using Treasury Funds to Promote USD1 Adoption] WLFI announced on platform X that governance voting has officially started. The proposal suggests using a portion of the unlocked WLFI treasury funds to accelerate the adoption of USD1 through incentive measures. Community members will vote to determine the direction of future development to drive the next stage of growth for USD1 and WLFI.

[Vitalik Criticizes Microsoft's Windows System as 'Dystopian Design'] Ethereum co-founder Vitalik Buterin posted on the X platform criticizing Microsoft's Windows operating system. He stated that he had purchased a new computer intending to install the Linux system, but when attempting to start Windows, he discovered that the entire process required an internet connection and interaction with Microsoft's servers; otherwise, it could not be completed. He described it as 'dystopian.'

Bitwise, an ETF issuer with a management scale of $15 billion, told CNBC that the four-year cycle of Bitcoin has ended and predicts that 2026 will be an upward year. （The Bitcoin Historian）

**[deBridge Co-Founder Warns of Flow Blockchain Rollback Risks]** deBridge co-founder Alex Smirnov posted on the X platform, stating that the Flow team has decided to roll back the blockchain and is currently in a forced synchronization window with key ecosystem partners, including bridges, centralized exchanges, and decentralized exchanges. However, as one of the main bridge providers for Flow, deBridge has not received any communication or coordination. Alex Smirnov warned that a hasty rollback could result in economic losses potentially exceeding the impact of the original attack and might introduce systemic issues, affecting bridges, custodians, users, and counterparties who acted honestly during the affected window. He urged all Flow validators to stop validating transactions on the rollback chain until a clear compensation plan, ecosystem partner coordination, and security team involvement are established. Currently, RPC responses indicate that the Flow state has been rolled back, but new transactions have not yet been accepted.