Layer 2 blockchain · settles to Ethereum
Blast ticker BLAST
Summary
Optimistic-rollup design on Ethereum, forked from Optimism's node software and op-geth. One sequencer orders transactions into L2 blocks (Blast's docs give sequencer confirmation in 2 to 4 seconds) and batch data is posted to Ethereum, as blobs since May 2024 per L2BEAT. One permissioned proposer posts state roots to an output oracle contract on Ethereum; L2BEAT says the fraud-proof system is still under development, so no proof checks those roots. In Blast's design, bridged ETH is staked on Ethereum (initially through Lido) and bridged dollar stablecoins become USDB backed by DAI, and the yield reaches users by rebasing ETH, WETH and USDB balances on the L2. Block production uses no stake or work of its own. 1341013161824
Design
- System
- Layer 2 blockchainBlast Mainnet (chain ID 81457) is built as an optimistic rollup on Ethereum from a fork of Optimism's node software and posts its transaction data to Ethereum. L2BEAT lists it under Others rather than as a rollup because the fraud-proof system is not working: state roots are accepted from one permissioned proposer. ETH is the gas asset; BLAST is an ERC-20 governance token on Blast and does not pay gas.
- Settles to
- EthereumBatch data is posted to Ethereum blobs, and Blast's docs say transactions are normally final on Ethereum in 15 to 20 minutes (up to 24 hours). Withdrawals to Ethereum take about 7 days, but the state roots they rely on are posted by one permissioned proposer with no working fraud proof; if the proposer stops, withdrawals freeze, and because bridged funds are placed with Lido and the Maker savings rate, a withdrawal can be locked in a queue until the operator provides enough liquidity in the bridge, per L2BEAT. Users can force transactions through Ethereum with up to a 12-hour delay.
- Settlement family
- Ethereum / EVM
- Scarce resource
- Other
- State model
- Accounts
- Finality
- Other
- Who makes blocks
- One sequencer and one whitelisted state-root proposer, each a single externally owned account per L2BEAT; Blast's own status page monitors block production and batch submission as Blast services. A 3-of-5 Blast multisig holds the challenger role and can upgrade the core contracts. The Blast Foundation, a Cayman Islands entity, runs token-holder governance under bylaws adopted on 25 June 2024; the reviewed docs do not name the legal operator of the sequencer.
- Fork choice
- No open L2 fork choice: sequencer blocks are provisional until their batch data is posted to Ethereum and that Ethereum block is finalized, and the chain is derived from the posted batch data under Ethereum's own fork choice and finality. Blast's docs warn that a reorganization remains possible before the finalized stage.
Qualifications
- Scarce resource · Not applicable. Blast block production uses no stake or work of its own; the sequencer is operator-assigned and settlement relies on Ethereum plus the permissioned proposer and multisig.
- Finality · Partial. Blast documents four stages: pending, sequencer confirmed (2 to 4 seconds), safe or published to Ethereum (usually 5 to 10 minutes) and finalized (usually 15 to 20 minutes, up to 24 hours). Finalized means the batch data is final on Ethereum, not that the posted state root has been proven correct.
- Proof system · Contested. Blast's docs call it an optimistic rollup, while L2BEAT lists it under Others and says it does not meet even the first stage of its rollup maturity framework, because fraud proofs are not active and one proposer is trusted.
- Balance semantics · Partial. Account balances of ETH in ordinary wallets, and of WETH and USDB by default, rebase upward as yield arrives, so a balance can change without any transaction. Contracts hold non-rebasing ETH unless they opt in.
- Ecosystem continuity · Unknown. Mainnet was producing blocks on review day and Blast's status page showed all systems operational, and no sunset has been announced by Blast. Some third-party services have withdrawn: Across said it would stop Blast routes, targeting 2026-07-20.
Tradeoffs
- Emphasizes
- Scalability
- Gives up
- Decentralized operation and trust-minimized security. One sequencer orders all transactions, one permissioned proposer posts state roots with no working fraud proof, and a 3-of-5 multisig can upgrade the core contracts with no delay and no exit window, per L2BEAT. Bridged funds are also placed with Lido staking and the Maker savings rate to produce yield, which adds those protocols' risks and makes withdrawals depend on the bridge having enough liquidity.Security is not listed as an emphasis. Transaction data is posted to Ethereum, so anyone can rebuild the chain, but the correctness of withdrawals rests on the proposer and the multisig rather than on proofs. L2BEAT records that in March 2024 an upgrade was used to stop the Munchables exploiter from forcing transactions, which shows the upgrade power is real and can be used to censor.
- Full node at home
- Demanding 9101117Blast publishes no CPU, memory or disk minimums. Its advanced node guide runs the execution client in full-sync archive mode, the weekly mainnet snapshot is described as 1.5 TB or more, and a node needs an Ethereum L1 RPC endpoint plus a beacon API endpoint for blob data. Node software is Blast's own fork (Blast Geth and a forked op-node), deployed with Docker.
- Throughput claims
- No classified figure recorded
Scaling layers
No scaling layer recorded in this profile.
Capabilities
| Capability | How it is provided | Notes and sources |
|---|---|---|
| Account abstraction | Structured assessment pending | Not yet assessed for any chain. |
| Atomic swaps | Unknown | A protocol-level trust-minimized swap mechanism on Blast was not reviewed; EVM contracts could implement hash-locked swaps, but none was verified. |
| Authenticated data publication | Unknown | Not yet assessed under this row's current definition. |
| Light clients | Unknown | Not yet assessed under the current definitions; no dedicated Blast light client was found, and no light-verification method was established from the cited source. State roots on Ethereum come from a permissioned proposer and are not proof-checked, so any light verification anchored to them would trust that proposer. 18 |
| Native staking or delegation | Structured assessment pending | Not yet assessed for any chain. |
| On-chain governance | Structured assessment pending | Not yet assessed for any chain. |
| Parallel execution | Structured assessment pending | Not yet assessed for any chain. |
| Payment or state channels | Unknown | No payment or state channel layer anchored to Blast was reviewed. |
| Programmable spending | Native (protocol or core-team software) Earlier definition | Blast runs EVM smart contracts with standard Ethereum wallets and tooling, and adds a yield and gas-claim system contract that contracts can configure. Blast Mobile uses ERC-4337 smart contract accounts. 1714 |
| Protocol-verified messaging | Structured assessment pending | Not yet assessed for any chain. |
| Reversible transfers or recovery | Unknown | Not yet assessed under the current definitions; no protocol feature for reclaiming, cancelling or delaying a payment was found on Blast. Blast Mobile's passkey smart wallet asks users to back up the seed phrase of its signer key and lets them restore it inside Blast Mobile; that restores the key itself rather than regaining control without it, so it does not meet part (b). 14 |
| Rollups | Unknown | Rollups anchored to Blast were not reviewed. Blast itself is built as a rollup on Ethereum; its settlement is described in the mechanism and Ethereum dependency notes. |
| Shielded transfers | Structured assessment pending | Not yet assessed for any chain. |
| Signed partial offers | Unknown | Not yet assessed under this row's current definition. |
Reading these values
- How this feature is provided
- Built into the protocol, core-team software or independent software says where a feature lives and who can change it. These are implementation layers, not quality: core-team software is not closer to the protocol than independent software.
- Structured assessment pending
- The shared review has not assessed this feature for any chain yet (Account abstraction, Native staking or delegation, On-chain governance, Parallel execution, Protocol-verified messaging and Shielded transfers). That does not mean it is absent, and a chain’s profile may already describe it.
- Unknown
- The review has not established this for this chain under the current definition; the note beside it says why. Unknown is not absent and not a low score. A feature reads “Not present” only when a source shows it is absent.
- Earlier definition
- Payment or state channels, Programmable spending and Rollups keep the earlier definition until the next fact-check. There, “Native” does not separate the protocol from core-team software, “Ecosystem software” does not say who publishes it, and “Partial” does not say which layer.
- Reading across rows
- The list of capabilities is incomplete. Do not read these rows as a chain leading or lagging overall.
Ecosystem & custody
| Product type | Status | Notes and sources |
|---|---|---|
| Automated market makers | ThinThruster, Ambient, Blasterswap | Several AMMs are deployed on Blast; Ambient's docs list its Blast contracts. DefiLlama's DEX tracker shows little activity across all tracked Blast venues in the 30 days before review, with Thruster's V3 venue the most used. Thruster's website could not be reached during this review. Liquidity depth was not measured. 1920 |
| Issuer-native stablecoins | Native to the protocolUSDB (Blast system token) | USDB is a Blast system contract that the bridge credits when users bridge DAI, USDC or USDT; Blast says it is backed by DAI held on Ethereum and its yield comes from the Maker savings rate. It is a bridge-backed claim, not a separately issued stablecoin. Circle's native USDC list does not name Blast. 14581521 |
| Algorithmic stablecoins | Unknown | Algorithmic or hybrid stablecoins on Blast were not reviewed. |
| Bridges | Native to the protocolBlast canonical bridge (Blast bridge and standard bridge contracts), Relay (third party) | Deposits of ETH, WETH, stETH and DAI, USDC or USDT (credited as USDB) run through Blast's own bridge contracts; withdrawals take about 7 days. Relay's chain list shows Blast as enabled. Across announced it would stop Blast routes, targeting 2026-07-20. Other third-party bridges were not checked. Risk: Withdrawals rely on state roots from one permissioned proposer with no working fraud proof, a 3-of-5 multisig can upgrade the bridge contracts instantly, and withdrawals freeze if the proposer stops. Bridged ETH and stablecoins are deployed to Lido and the Maker savings rate, so losses there or a lack of bridge liquidity can delay or reduce withdrawals, per L2BEAT. 456182223 |
| Block explorers | Established in the ecosystemBlastscan (Etherscan), Blastexplorer (Routescan) | Blast's docs list six explorers (Blastscan, Blastexplorer, Parsec, DexGuru, Blockscout and Arkham) and name Blastscan in the network settings. On review day Blastscan, which Etherscan runs, loaded and showed blocks from a few seconds earlier, and Routescan's public index behind Blastexplorer returned a current Blast block. The Blockscout, DexGuru and Parsec pages returned 404 and Arkham was not checked. Explorer indexes are not canonical consensus. 2122526 |
| Hardware wallets | ThinTrezor Safe 3, 5 and 7 (through MetaMask or Rabby), Ledger (Blast behind a default-off switch) | See custody rows: Trezor lists the Blast network but routes users through third-party wallet apps and says its Suite app does not support Blast; Ledger Wallet code includes Blast behind a feature switch that is off by default. 272930 |
Hardware-wallet custody
| Device maker | Status | What users can and cannot do |
|---|---|---|
| Ledger | PartialSame as native: Unknown | Cannot: Rely on Blast appearing in Ledger Wallet: its code gates the Blast network behind a feature switch that is off by default, and no Ledger page confirms the switch is on for usersLedger Wallet's source code includes a Blast network behind a feature switch that is off by default; the remote setting that could switch it on for users could not be read, Ledger's Blast coin page returned 404, and its supported crypto assets page could not be searched. First-party support that sits behind a switch that is off by default counts only as partial support. 2829303132 |
| Trezor | Through an intermediaryMetaMask or Rabby (third-party wallet apps named by Trezor)Same as native: Unknown | Can: Send and receive assets on the Blast network with a Trezor Safe 3, Safe 5 or Safe 7, confirming each transaction on the device, through MetaMask or Rabby Cannot: Manage Blast in Trezor's own Suite app: Trezor's Blast page says Blast is not supported thereTrezor's page lists Blast as a supported network for the Safe models; older models, the BLAST token and contract-interaction coverage were not reviewed. 27 |
Public data
iKnow Blockchain has no public-data lookups for Blast yet. This is a limit of the service, not a statement about the network.
| Lookup | Status | What it covers and its limits |
|---|---|---|
| Address or account | Not available yet | Public-data lookups for this chain are not built yet. |
| Tokens and assets | Not available yet | Public-data lookups for this chain are not built yet. |
| NFTs | Not available yet | Public-data lookups for this chain are not built yet. |
| Transactions | Not available yet | Public-data lookups for this chain are not built yet. |
Sourced developments
Developments: Review overdue Reviewed Sep 27, 2026; next review was due Oct 7, 2026, 12:00 UTC.
Publication date · newest first
-
Across bridge stopped supporting Blast
Across, a cross-chain bridge, posted a notice that it was deprecating Blast support and that once disabled, targeting 20 July 2026, its routes to and from Blast would stop returning quotes. On review day its swap API chain list no longer included Blast.
- Implementation:Blast removed from the Across swap API chain list
- Release:deprecation notice published on the Across docs
- Activation:in effect on review day
Sources: Across — Chains and Contracts (Blast deprecation notice) (external site) · Across — Swap API chain list (external site)
-
Blast mainnet v1.7.0 and v1.8.0 fixed the blob fee schedule
Blast released node software v1.7.0 for mainnet with fixes to the blob fee schedule; Blast's blog says it activated on 12 February 2026. A day later v1.8.0 supplied a missing default value from v1.7.0 and was scheduled to activate on 13 February 2026. Operators of the rollup node had to add new blob-schedule settings.
- Implementation:released as v1.7.0 and v1.8.0
- Release:mainnet releases published 2026-02-11 and 2026-02-12
- Activation:v1.7.0 activated 2026-02-12 by timestamp per the blog note; v1.8.0 scheduled by timestamp for 2026-02-13, with no separate confirmation found
Sources: Blast contributors — Release v1.7.0 (MAINNET) (external site) · Blast contributors — Release v1.8.0 (MAINNET) (external site) · Blast — Release v1.7.0 (MAINNET) (external site) · Blast contributors — Releases: blast-io/blast (external site)
-
Blast mainnet v1.4.0 kept Blast compatible with Ethereum's Fusaka upgrade
Blast published node software v1.4.0 for mainnet to stay compatible with Ethereum's Fusaka hard fork, after a matching testnet release in October 2025. Because Blast reads its data from Ethereum, its nodes must follow Ethereum's upgrades.
- Implementation:released as v1.4.0
- Release:mainnet release published 2025-12-02
- Activation:tied to Ethereum's Fusaka activation; the release note gives no activation time of its own
Sources: Blast contributors — Release v1.4.0: Fusaka Hardfork (MAINNET) (external site) · Blast contributors — Releases: blast-io/blast (external site)
Topics your AI can explain
Your AI can explain these topics for Blast through the connection, with sources.
Known gaps
What this profile's review did not establish:
- The legal entity that operates the Blast sequencer and proposer, and the identities of the five multisig signers, were not sourced.
- Blast's docs describe a five-member Safety Committee multisig in the Foundation bylaws; whether it is the same 3-of-5 multisig that L2BEAT says controls the contracts was not confirmed.
- Blast's own docs do not discuss the missing fraud proofs, the permissioned proposer or instant upgrades; those points rest on L2BEAT as a secondary source.
- Blast publishes no hardware minimums for a node; the demanding rating rests on archive mode, the 1.5 TB-plus snapshot and the need for Ethereum RPC and beacon endpoints.
- The current split of bridged ETH and stablecoins between Lido, the Maker savings rate and bridge liquidity, and any past withdrawal delays, were not reviewed.
- Ledger support is partial: Ledger Wallet code keeps Blast behind a feature switch that is off by default, the Blast coin page returned 404, and the remote switch setting could not be read. Trezor coverage of older models and the BLAST token was not confirmed.
- Thruster's website did not resolve during this review, so its current front end and operator status are unknown; DEX activity rests on DefiLlama's tracker, not on venue documentation.
- Of the six explorers listed in Blast's docs, only Blastscan and Routescan's index were confirmed live: the Blockscout, DexGuru and Parsec pages returned 404, the Blastexplorer front end blocked automated access, and Arkham was not checked.
- The Across notice gives a target disable date of 20 July 2026 but no publication date, so when Across announced the change and the exact day it took effect were not confirmed.
- Third-party bridges other than Relay and Across were not checked for current Blast support.
- No governance votes after October 2024 were found on the Blast Foundation's Snapshot space in a read-only query; current governance activity was not otherwise reviewed.
- Atomic swaps, reversible or delayed transfers and recovery, channels, light clients and algorithmic stablecoins on Blast were not reviewed.
Sources
Oldest dated source check: Source checked Sep 27, 2026 Next check due Oct 27, 2026.
- About Blast (external site)
- Network Information (external site)
- Transaction Finality (external site)
- Blast Contracts (external site)
- Bridges: Mainnet (external site)
- Bridges: FAQ (external site)
- Receive and claim ETH yield (external site)
- Receive and claim WETH and USDB yield (external site)
- Docker Compose Setup (external site)
- Advanced Setup (external site)
- Node Snapshot (external site)
- Block Explorers (external site)
- Governance (external site)
- Seed Phrase Recovery (external site)
- Blast Mobile Launch Q&A (external site)
- blast-io/blast (external site)
- blast-io/deployment (external site)
- Blast (external site)
- Deployed Contracts (external site)
- DEX volume overview for Blast (API) (external site)
- USDC Contract Addresses (external site)
- Supported chains (API) (external site)
- Chains and Contracts (Blast deprecation notice) (external site)
- Blast Status (external site)
- Blast Mainnet Network (ETH) Blockchain Explorer (external site)
- Blast mainnet latest block (API) (external site)
- Blast wallet (external site)
- Supported crypto assets (external site)
- ledger-live: coin-module loaders (list of networks Ledger Wallet can add) (external site)
- ledger-live: currencyBlast feature switch (external site)
- ledger-live: feature-flag defaults (a switch declared with no value is off) (external site)
- ledger-live: useCurrenciesUnderFeatureFlag (hides networks whose feature switch is off) (external site)
Report an error
Found something wrong or out of date? Reporting is free, and every chain goes through the same process. Published corrections appear in the public log.
Funding disclosure
Funding disclosures appear here when an upkeep arrangement exists, in the form “Upkeep funded by [name]; verdicts unaffected.” The funder ledger has not been published yet. Neutrality & funding