Prediction: Will Bitcoin reach a high of 94000 on November 11, 2026?
Let's review the entire rebound that began at the low on July 1. Here's where things stand now: Wave 4: The correction has 13 days left in its cycle. Range: 76000–81000 Wave 5: The rebound will complete in 13+20=33 days. Range: 85000–94000 In other words, the correction should continue for about two more weeks.
Within a month, a high of $BTC 94000 will be reached! Mark my words! #比特币反弹至8.3万美元
BTC experienced the largest hack in history during what should have been a pullback. A weak rebound began during the accelerated decline, but recovery won't happen quickly. This is simply the accelerated completion of the WXY structure that began on 9/22. The upcoming midterm election results will definitely trigger a wave of mild panic, with a short-term drop to around 74,000, followed by a C-wave rebound and recovery. Then the market will consolidate in preparation for the bull market. Just hold your spot assets. As for futures, absolutely don't open a position if you don't have enough margin!
I just paid my TradingView membership fee through Binance, and everything is working normally! Withdrawals have almost fully recovered.
As for the unscrupulous KOLs on social media who are coordinating to smear Binance over this theft and urge people to withdraw their funds, I personally think it’s completely pointless! Among CEXs, there’s currently no other exchange capable of covering losses of this amount. Many smaller exchanges might go bankrupt outright after an incident like this! Don’t spread rumors, don’t believe rumors, and trust Binance!
Whale movements are all transfers to Binance’s new hot wallet. Many platforms haven’t labeled it, so don’t panic! And don’t believe any rumors either—the withdrawal volume is probably tiny. The most important thing at this stage is to keep an eye on official Binance announcements! Still, it must be tough for @heyibinance—pregnant and yet still online, playing customer service rep Xiao He 🙏
Latest update on Binance’s response to the hack: 90% complete Binance’s speed and efficiency are pretty good now. More than 6.34 billion in reserve funds! Everyone, rest assured. @cz_binance @heyibinance have repeatedly promised that Binance will take full responsibility to prevent panic and maintain stability in the industry. Believe in Binance, believe in the spirit of crypto!~ 💪
So many people are spreading rumors that Binance needs to sell its SpaceX shares to cover the stolen funds. I can’t understand how these people think. They don’t even know who the real enemy is. Hacker groups and evil forces are the biggest enemies in the crypto world. Don’t forget that Binance provides liquidity for the entire industry. No one can escape the fallout from Binance’s losses!
Regarding the incident in which Binance was hacked and a large amount of funds was stolen Binance CEO @heyibinance speaks on video! Safeguarding the industry is fundamental to our survival! The real enemy is hackers—those who take liquidity away from our crypto world!
Usually, every black swan event is followed by a second leg down, but it looks like that won't happen this time.
This isn't the top of the bull market—it's a short-term sell-off amid tightening liquidity. But the sell-off in U.S. stocks has begun, with INTC plunging 30%.
I believe gold and Bitcoin are about to see a major influx of liquidity! Still bullish on Bitcoin—the rebound will continue before 11/10!
Bitcoin originally had a chance to break out during the midterm elections. Now all we can do is watch, but at least we finally saw the 76,000 I predicted…
1. Blockaid disclosed the attack method (not confirmed by Binance): Unable to guess the nonce of Binance 14's hot wallet, the attacker packed 50 EIP-7702 authorizations into a single transaction, and only one matched. This authorization delegated the hot wallet to an unverified malicious contract, whose sweep() function could only be called by an address specified by the attacker to transfer out ETH and ERC-20 tokens, leaving 1 ETH behind each time as a fee. On-chain data currently shows that this delegation from Binance 14 has been revoked, with a balance of about 0.81 ETH.
2. The hacker continues to dump tokens: According to PeckShield, one address downstream from Hacker 2 swapped some of its tokens worth about $5.7 million for 805 ETH, while another address swapped 3.6 million ZRO for 2,156 ETH. Both amounts of ETH were consolidated into a new address, 0x8d4b8EE62124B7ee140A51dDd07390A56F1c9E19, worth about $6.5 million.
3. Mempool co-founder mononaut said Binance's announcement that its "operations laptop was compromised" confirmed his earlier assessment: the issue was with the internal wallet control system, not a private key leak.
The amount frozen remains about $3 billion, and deposits and withdrawals are still suspended.
1. Binance’s preliminary investigation found that a DevOps engineer’s laptop may have been compromised, allowing the attacker to access a service container and submit unauthorized withdrawals. No wallet private keys have been found to be compromised so far. A full technical postmortem will be published after the investigation concludes.
2. Losses and reimbursement: Binance estimates that the incident affected approximately $6.3 billion in total, of which about $3 billion has been frozen on-chain. SAFU and the company’s own funds will fully cover the losses. Proof of Reserves will be updated once remediation is complete. Deposits and withdrawals remain suspended, authorizations for affected addresses have been revoked, and law enforcement and blockchain analytics firms are investigating.
3. CZ posted: “User funds are SAFU.” He said hundreds of Binance employees worked through the night, and that some industry peers—even competitors who had not been particularly friendly in the past—had stepped in to help. He added that this incident hurts, but they will get through it.
4. Arkham’s figures: 70 addresses linked to the hacker have been identified. The hacker holds approximately $5.759 billion in total, including $1.77 billion in USDT, $1.41 billion in BTC, and $1.05 billion in ETH. These figures reflect Arkham’s own methodology and differ from Binance’s estimate of $6.3 billion.
5. Mempool co-founder mononaut speculated that each theft transaction transferred about 44% of the hot wallet’s remaining balance, as if to evade Binance’s internal limits. As soon as the transactions entered the mempool, the attacker split the transferred bitcoin into neat, uniform-sized chunks. This is his personal theory; Binance has not confirmed it.
6. Binance Wallet announced that the launch of trading for PREDICT Alpha, originally scheduled for 17:00 today, has been postponed. A new time will be announced later.
1. Binance made another statement at 09:36: it will cover all losses. Deposits and withdrawals remain fully suspended. It will publish a full post-mortem after the investigation concludes, but has not yet given a loss amount or a timeline for resuming services.
2. The hacker has finished dumping all 217.5 million ENA (about $33.93 million). Afterward, a newly created wallet deposited 2 million USDC into Hyperliquid and opened a 3x leveraged long position of about 22.78 million ENA (about $4.09 million)—buying the dip after the sell-off.
3. ZachXBT praised Circle and Tether for acting quickly to freeze funds. There is no new official figure for the total frozen; it remains around $3 billion.
4. On-chain checks show that Binance 14 no longer has any EIP-7702 delegations, and its balance has not changed again.
Market: BNB 700.4, BTC 77153, ETH 2210. BNB is back above 700.
1. Total frozen: Binance’s official figure is about $3 billion; ZachXBT puts it at over $2.83 billion. Efforts to freeze more funds are ongoing.
2. The hacker has sold all of the UNI, ENA, PEPE, LINK, AAVE, ONDO, and WLD, converting them into 70,480 ETH (about $158 million). This includes 7.02 million UNI, 217.5 million ENA, and 7.77 trillion PEPE. Selling pressure on these tokens has largely cleared.
3. Arkham has identified the hacker as an entity and labeled 70 addresses.
4. SlowMist’s Cosine believes the hacker used EIP-7702 simply to make it easier to sweep hot wallets in bulk. The technique was crude, and the attacker practiced for several hours beforehand. The 7702 mechanism itself is not at fault.
5. Deposits and withdrawals remain suspended. Binance has not yet announced the final loss amount or released a full post-mortem.
Market prices (24 hours): BNB 694.8, down 7.98%; BTC 77052, down 4.91%; ETH 2214, down 5.78%. BNB has edged up from its low of 680.
Latest update on the Binance hot wallet hack (as of 08:35)
1. Binance has officially pledged to cover all losses. All deposits and withdrawals are suspended while it conducts security checks, freezes funds, and cooperates with law enforcement. It will publish a full post-mortem after the investigation concludes. The exact amount of losses has not yet been disclosed.
2. The authorization for Binance 14, the compromised hot wallet, was revoked at 08:10. However, the 2,961 ETH that had been stuck was transferred by the hacker before the revocation.
3. Freezing progress: Binance says it has confirmed that $2.54 billion has been frozen. The Arbitrum Security Council has frozen an additional approximately $30.5 million.
4. After deducting the frozen stablecoins, net losses from the theft are approximately $3.43 billion. The hacker has not moved the 18,270 BTC in their possession. They continue to swap altcoins for ETH and now hold approximately 467,000 ETH.
5. ZachXBT says it is “very likely Lazarus,” but there is no evidence yet.
Market prices (24 hours): BNB at 685, down approximately 9.8%; BTC at 77,177, down approximately 4.9%; ETH at 2,207, down approximately 6.3%. The hacker is still selling altcoins for ETH. Watch for selling pressure on ENA, PEPE, and others.
How the Binance hack unfolded — preliminary timeline
Binance replenished 200 million USDT, and hackers swept it away in just 72 seconds
At 5:42 a.m. on October 30 (Beijing time), Binance transferred 200 million USDT from its own wallet, Binance 124, to the hot wallet Binance 14. But that wallet was already under the attackers’ control, and 72 seconds later, all 200 million had been transferred out.
Here’s what on-chain records show:
04:20, The attackers used EIP-7702 to set up delegation for Binance 14 and pre-signed 50 authorizations, one of which took effect 04:24, Binance 16 signed a transaction itself, transferring 55.74 million USDT to the attackers 05:42, Binance deposited 200 million USDT into the already-compromised Binance 14 05:44, The attackers swept away all 200 million, but Tether had already frozen the address 06:22 Binance suspended withdrawals; 17 minutes later, another 128 ETH and more than 50 types of tokens were swept from Binance 14 06:55 Binance began moving the remaining coins into cold wallets, but at 06:57, the attackers’ delegation was still active and had not been revoked
After the hack, 2,199 ETH were transferred into Binance 14, and 2,198 ETH were swept away; 206 million USDT came in, and 204 million was swept away. The biggest question is that every authorization had to be signed with Binance 14’s private key, and Binance 16 also used its own private key to sign the outgoing transfer. This doesn’t look like someone was tricked into signing once; it looks more like the entire signing system was compromised. Information compiled from on-chain data. Please refer to Binance’s official announcements.