Blast will be shutting down. We launched Blast with the goal of building a self-sustaining chain for users and developers. Unfortunately, the economics of operating the chain no longer make sense: the ongoing costs of maintaining Blast exceed the revenue generated by the L2, and we do not see a credible path to making the chain economically sustainable. As a result, we've made the difficult decision to wind Blast down. We're sorry to the users and developers who believed in Blast, built on it, and supported the ecosystem. Our priority now is making the shutdown as smooth and safe as possible. We're asking all users to withdraw their assets from Blast to Ethereum mainnet, including any balances held in the Blast PWA. To make this easier, we will be reducing the withdrawal delay to 24 hours. As part of the shutdown process, we'll first begin withdrawing Blast's Lido assets. This process is expected to take approximately one week. During this period, withdrawals will temporarily be unavailable, even after the withdrawal delay is reduced to 24 hours. Once that process is complete, withdrawals will resume with the new 24-hour delay. Users will have until October 26, 2026 to withdraw through the normal Blast interface. After October 26, assets will remain withdrawable, but users will need to interact directly with the Blast bridge contracts on Ethereum L1. We'll publish detailed instructions before then. We strongly encourage everyone to withdraw their assets to Ethereum mainnet before October 26.

He has saved thousands of California acres from wildfires. The government is now increasing his labor costs by 400%, which could drive him out of business. This is Tim Arrowsmith's story:

1/6 Correct: the screenshot itself is not proof. Anyone can fake an image or PDF. The proof is Robinhood Chain's signed transaction data. PDEX: 0x5C9A6a0353f1EDC67B22f2cdcfE9294f5A889B60 Chain ID: 4663 Here is the independently verifiable trail: --- 2/6 LAUNCH CONFIGURATION The PDEX launch key signed a transaction whose raw input contains SIX extra opening-tax-exempt future addresses. Open "Input Data" and inspect the final six-address array: --- 3/6 COMMON FUNDING Five minutes and 26 seconds before launch, one coordinator transaction funded all six controller wallets in exemption-list order. Five controllers were fresh wallets. --- 4/6 THE 45% ALLOCATION Four blocks after launch, one batch transaction spent 1.463880775043543409 ETH and allocated approximately 450,000,000 PDEX, 45% of the total supply, to those six tax-exempt addresses while they were still undeployed. --- 5/6 HOW TO VERIFY IT YOURSELF 1. Launch tx: inspect the six exemption addresses. 2. Funding tx: inspect the six funded controllers and their order. 3. Batch-buy tx: inspect the six PDEX recipients and amounts. 4. Open those recipient addresses: all six now contain identical 45-byte EIP-1167 minimal-proxy code. --- 6/6 WHAT THE CHAIN PROVES - Six future addresses were deliberately tax-exempted by the launch key. - Their controllers were commonly funded before launch. - One coordinated purchase allocated 45% of supply to them. - The addresses became identical owner-gated clones. That is cryptographic evidence of a coordinated preferential 45% launch bundle.