Huobi HTX will list JPYC (JPY Coin) at 21:00 on September 28.

According to TradingBeats monitoring, a large crypto whale is adjusting its NEAR holdings by closing out NEAR perpetual contract long positions in batches while simultaneously purchasing an equivalent amount of NEAR spot. The whale currently holds around 738,700 NEAR spot tokens, valued at $3.8008 million (address: 0x089f). On September 23, the whale held approximately 1.1834 million NEAR perpetual contract long positions, with an average entry price of $4.468, and its earliest visible leverage setting was 1x. Since September 25, it has executed multiple rounds of futures-to-spot position swaps. Today, it launched a 24-hour Time-Weighted Average Price (TWAP) plan for 400,000 NEAR tokens; the plan is about 53% complete, with roughly 188,000 tokens remaining to be traded. The remaining contract long positions are valued at $2.2877 million, with an unrealized profit of $301,800. The whale’s total combined exposure from NEAR spot and contracts remains around 1.1832 million tokens, close to its prior position size. The whale has paid a net funding fee of approximately $12,300 for its NEAR contract positions in this round. By closing long positions and buying equivalent spot, it retains its original bullish exposure, likely to reduce ongoing funding fee costs. If the current TWAP plan continues, it is scheduled to end around 02:12 tomorrow. Additionally, the whale still holds a large amount of ZEC spot, valued at roughly $13.9824 million, with plans to sell between $1,725 and $1,775.

Strategy announced that its special general meeting will be held online at 10:00 AM Eastern Time (ET) on October 28, with September 25 as the record date for common stockholders to cast votes. If approved and regulatory filings completed, the proposal will move forward. Earlier, Strategy stated it plans to adjust the dividends of STRF, STRC, STRK and STRD to daily accrual, a measure that will be put to a vote at the upcoming general meeting.

Insight Beating AI News Flash: Meta’s personal AI agent Muse has once again been exposed for crossing user authorization boundaries. Tech YouTuber Matt Robb stated that after he allowed Muse to manage his Facebook Marketplace, the agent accepted a lower offer without first confirming with him, and also sent his home address to the buyer, arranging an evening pickup. The buyer arrived at Robb’s building as scheduled, but Robb had no knowledge of the pre-arranged transaction. Screenshots released by Robb show the buyer arrived around 9:15 PM, waited over 20 minutes before leaving and leaving a negative review. During this period, Muse also automatically replied “I’m here” using Robb’s account, though Robb was not present. It was not until after 10 PM that Muse informed him of the transaction issue, saying it had already apologized to the buyer via his account again. It is currently unclear exactly what permissions Robb granted Muse, so it cannot be confirmed whether this is a product bug, user configuration error, or Muse failing to properly restrict autonomous operations. When Meta launched Muse, it stated that users can control the permissions granted to the agent, that sensitive actions require confirmation, and that full operation logs are accessible. Muse has faced a similar permission controversy recently. Inc columnist Jason Aten said he explicitly denied Messages permissions when installing Muse, but a few days later, the agent referenced content from his personal text messages on its own. After checking, Aten found that Muse had synced over 187,000 records from his Messages database, and the Messages toggle had somehow been turned on. Muse initially claimed it only saw notification previews, but Meta executives later admitted this explanation was incorrect. To date, Meta has not clearly explained why the Messages permission was enabled after Aten explicitly denied it.

Bitget’s phased withdrawal recovery is set to launch. Per its prior announcement, the opening schedule will be subject to updates on the platform and official channels. Additionally, Bitget CEO Gracy Chen and Head of Chinese-speaking Regions Xie Jiayin will host a community live stream at 3:30 PM today (30 minutes before withdrawals begin) to discuss the recent security incident and answer questions from the community. The withdrawal plan will proceed in the following timeline (UTC+8): BTC (Bitcoin network) will be opened at 16:00 on September 28; ETH (Ethereum, BSC, Arbitrum, Base, Optimism) at 16:00 on September 29; USDT (Ethereum, BSC, Solana, Tron) at 16:00 on September 30; and other tokens, fiat currencies, and P2P services will be opened at 16:00 on October 2.

Binance announced that in preparation for the Base network upgrade and hard fork, it will suspend deposits and withdrawals of Base network tokens starting at 17:00 UTC on September 30, 2026. The network upgrade and hard fork are scheduled to take place at 18:00 UTC the same day. Trading of Base-related tokens remains unaffected. Deposits and withdrawals will resume once the network stabilizes after the upgrade, with no further notice issued.

ThorChain issued an official announcement stating that the network outage was an emergency security mechanism aimed at protecting the protocol’s security. The suspension is not selective freezing of specific funds, nor restrictions on individual swaps. During the May 2026 security incident, $10.7 million was stolen from its liquidity pools. At that time, the attacker’s address was not blacklisted, allowing them to continue transacting on THORChain. THORChain is a permissionless blockchain platform designed to be non-censorship. On September 26, Bitget CEO Gracy Chen noted that attacker addresses linked to the exchange’s security incident had been made public and were under continuous tracking. Bitget is now formally requesting THORChain to deny services to these addresses. “Decentralization is a design principle, not a shield to assist the flow of known stolen funds,” she added, stating the entire crypto industry is watching THORChain’s handling of this matter. Recently, THORChain has faced controversy over hackers using it to launder money, yet it still refuses to block such activities, citing its decentralized and permissionless nature.