November 1, 2026 is a Sunday, and the new primary writing is thin. The item with a clock on it comes from Elliptic, not from a fresh Binance filing. Elliptic’s note, updated that morning, says about $2.85 billion was verified frozen around 05:50 UTC and that Binance withdrawals were set to reopen at 06:00 UTC, bitcoin first. Those are Elliptic’s figures. The desk special keeps the longer account.
Client work and lending filled the rest of the UTC day. Grandine published 3.0.0-rc.3 at 18:55 UTC and told mainnet operators not to upgrade. It is a Gloas test build. LlamaRisk asked Aave to lift a WETH borrow cap that was 99.4% used, and a weETH add cap that was 97.7% used. A research note asked whether spend limits should live in the token rather than in the account. Coinbase reported a short delay on the Data network just after midnight UTC.
Elliptic times a $2.85 billion freeze and a withdrawal reopen
Elliptic's Binance report, in the update timestamped the morning of November 1, 2026, puts the theft at $6.43 billion across 11 chains. It says about $2.85 billion was verified frozen around 05:50 UTC that day. It also says withdrawals were set to reopen at 06:00 UTC on November 1, starting with bitcoin. Those reopen and freeze lines are Elliptic's account of the exchange, not a sentence this desk found in a Binance filing dated November 1. Do not mix them with another firm's swap math.
Grandine 3.0.0-rc.3 is a Gloas test build, not mainnet
Grandine published 3.0.0-rc.3 on November 1, 2026 at 18:55 UTC. The notes say it fixes a regression from 3.0.0-rc.2, and that upgrading is mandatory if a previous release candidate is misbehaving. They also say mainnet users should not upgrade. The build is for testing the Gloas hard fork. Among the listed changes, the project updated Rust to 1.99.1. A testnet release candidate is not a mainnet fork date.
An Ethereum Research post at 17:15 UTC on November 1, 2026 argues that most key-compromise defenses, including smart wallets and EIP-7702 delegation, enforce policy in the account's code. The author wants rate limits in the asset instead: in the token contract for ERC-20s, and eventually in the protocol for native ether. For ERC-20s the post says no protocol change is required, either through a shared registry or per-token state. Native ether, it says, would need something like a system contract checked when a balance falls. That second path is not a scheduled fork.
LlamaRisk asks Aave to lift a WETH borrow cap that is 99.4% used
LlamaRisk posted at 13:00 UTC on November 1, 2026 about Aave V3 borrow caps that had been cut on October 30 and left in force after reserves were unfrozen. On Aave V3 Core, it lists 2,098,953 WETH supplied against 1,778,949 WETH of debt, utilization 84.8% versus an optimal 92%. Debt grew by about 29,200 WETH after the cut, hit the 1,790,000 borrow cap, and was using 99.4% of it. The proposed cap is 1,810,000, which the post says would be 98.3% used. On Aave V3 Prime, WETH debt of 16,099 sat on a 16,100 cap.
A second LlamaRisk post on November 1, 2026 covers Aave V4 add caps. On the Ethereum Core Hub Main spoke, 19,533 weETH sat against an add cap of 20,000, or 97.7%. The post says supply rose from about 14,300 weETH to the 20,000 cap on October 28 and stayed near it after the spoke was unfrozen on October 30. The proposed cap is 22,000, about 88.8% used after the change. The largest position held about 24% of the reserve, the top three about 60%, and the top twenty about 99%. Nineteen of those twenty borrow stablecoins, mainly USDG.
Coinbase Data network sends lag for about half an hour
Coinbase opened a Data network incident at 18:21 Pacific on October 31, which is 01:21 UTC on November 1, and marked it resolved at 18:52 Pacific (01:52 UTC). The notice said some users might see delayed sends and receives for DATA. Buys, sells, and fiat deposits and withdrawals were not affected, and the page said funds were safe. It did not give a cause. The half hour is the status page's open-to-resolved window, not a chain halt.
