We’re combining Arcade Research and Blast Foundation operations into a single streamlined structure run by @PacmanBlur. Blast is made in the US and we will support the burgeoning crypto market in the USA.
With this change, we’re introducing Blast Mobile and over 50% APY on USD!
Reminder to withdraw your funds.
Withdrawal guide: https://t.co/6nsaAfZMNX
If you hold funds in the PWA, make sure to withdraw those funds too.
You can bridge your BLAST to ethereum mainnet on the official bridge UI at https://t.co/xLSpxUSPVs (CA 0x71b9e0FD392713A14FCaB92D9aF7A21F47E3b1Fa).
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.
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.
Regarding the recent NPM supply-chain attack:
Both Blast and Blast Mobile users are completely unaffected by the vulnerability.
We’ve confirmed across the source code that none of the affected package-versions exist in any Blast product.
Users are safe ✅
🚨 There’s a large-scale supply chain attack in progress: the NPM account of a reputable developer has been compromised. The affected packages have already been downloaded over 1 billion times, meaning the entire JavaScript ecosystem may be at risk.
The malicious payload works by silently swapping crypto addresses on the fly to steal funds.
If you use a hardware wallet, pay attention to every transaction before signing and you're safe.
If you don’t use a hardware wallet, refrain from making any on-chain transactions for now.
It’s still unclear whether the attacker is also stealing seeds from software wallets directly at this stage.
Excellent report here: https://t.co/5CtiZJHYsN
@TimStone84@safe@BrahmaFi Safe is a third party service that offered multisig functionality to users. It sounds like you never used it, so there's nothing you need to do.
We’ve decided not to renew our service agreement with @Safe.
If you previously used their frontend to access your multisig wallet, you have two options:
1. Use @BrahmaFi’s hosted frontend
2. Host your own frontend to reduce supply chain risk (instructions here: https://t.co/a1GnCo8GLo)
Why the change?
- Teams can still access their Safe multisigs using high-quality alternatives like Brahma.
- Security-conscious users can easily self-host the frontend to eliminate third-party risk.
While end-users can also use Brahma, we believe multisig wallets should be:
✅ Dead simple to use
✅ Accessible to non-technical users
That’s why we’re building multisig functionality directly into Blast Mobile—bringing secure wallet access to the entire Blast community.
NOW LIVE in Blast Mobile
🔐Seed Phrase Recovery
✅Approval-Free Transactions
Token approvals are a huge source of confusion, friction, and security nightmares for users. Blast Mobile dapps can now initiate transactions directly without approvals!
We’re hosting an AMA to discuss Blast Mobile, the App Store we just launched, and future plans tomorrow at 11AM EST.
Join us to get your questions answered! https://t.co/pmWG6nbMD1
We’re hosting an AMA to discuss Blast Mobile, the App Store we just launched, and future plans tomorrow at 11AM EST.
Join us to get your questions answered! https://t.co/pmWG6nbMD1
ICYMI
The Blast App Store is now LIVE!
The App Store is currently whitelist only. Next up, we’ll enable permissionless app launches.
More buttons coming.
Note, the first wave of dapps will go live tonight, but the reschedule AMA will NOT happen tonight. We will give ample time for people ahead of the AMA.
We’re putting in the finishing touches to ship the first wave of dapps — they will go live tonight, most likely within the next hour. Given the delay, we’re going to reschedule the X AMA as well. We’ll make an announcement once a new time has been chosen.
We’re putting in the finishing touches to ship the first wave of dapps — they will go live tonight, most likely within the next hour. Given the delay, we’re going to reschedule the X AMA as well. We’ll make an announcement once a new time has been chosen.
We’re putting in the finishing touches to ship the first wave of dapps — they will go live tonight, most likely within the next hour. Given the delay, we’re going to reschedule the X AMA as well. We’ll make an announcement once a new time has been chosen.
Some of the first-wave dapps need a bit more time for final touches. The App Store launch is now set for Monday, March 17, at 7PM EST. Afterwards, we’ll host an AMA on X at 8PM EST—join us and get your questions answered! 🚀
https://t.co/YNcxVO5yTR
Blast USD Yields & How to Earn Them
1. USDB Yield for $BLAST Holders – 79.3% APY
📥 How to Earn: Deposit USDB + $BLAST into the Earn app in Blast Mobile
2. Enhanced USDB Yield – 13.2% APY
📥 How to Earn: Deposit USDB into the Earn app in Blast Mobile
3. Standard USDB Yield – 4.75% APY
📥 How to Earn: Deposit USDC or USDT into your Blast Mobile wallet
No lockups required. Withdraw anytime.