structured yield · Global / Blast ecosystem

Blast Native Yield

Blast L2's protocol-native yield system for ETH and stablecoins. Blast announced an orderly network wind-down on October 2, 2026 and began unwinding Lido-linked assets, temporarily interrupting withdrawals while directing users to exit to Ethereum.

Also known as: Blast native yield, Blast L2 native yield, Blast USDB native yield

Status
Withdrawals suspended
Outcome
Unknown
Confidence
High
Last verified
2026-10-08
Launch2024-02-29
End—
Failure reasonVoluntary shutdown
Events2
Evidence3
Products1

Case summary

What happened

Blast embedded yield into bridged ETH and stablecoin balances. On October 2, 2026, Blast announced that L2 operating costs exceeded revenue and that no credible route to economic sustainability remained. The team directed users to withdraw to Ethereum, reduced the withdrawal delay to 24 hours, and said withdrawals would be temporarily unavailable while Blast's Lido assets were withdrawn, a process expected to take about one week. Normal interface withdrawals are planned through October 26, after which users can still interact directly with Blast bridge contracts on Ethereum L1.

Customer result

Customer outcome

Unknown

Blast is in an orderly network/yield wind-down with withdrawals temporarily interrupted during the Lido unwind. No insolvency, claims process, fixed recovery percentage, or customer-loss outcome is established, so CYA keeps the terminal outcome unknown rather than not_applicable.

Estimated recovery
Unknown
Repayment started
—
Repayment completed
—
Confidence
High

Asset treatment

Terms risk

Varies by product

Blast's native-yield mechanics differ between ETH and stablecoin balances. During the wind-down, withdrawal timing also depends on the Lido unwind and bridge operation. CYA does not infer guaranteed yield continuity, instant withdrawals, principal protection, or a universal post-shutdown interface.

Affected product
—
Confidence
High

Source: Blast — native yield for ETH and stablecoins

Known unknowns

Uncertainty

CYA does not infer a customer loss, insolvency, fixed recovery rate, or that October 26 is a final asset-recovery deadline. The exact completion time of the Lido unwind and the effective end of all native-yield accrual require follow-up.

Chronology

Historical record

yield program startedHigh impact1 sources

Blast mainnet launches with protocol-native yield

Blast mainnet introduced protocol-native yield for bridged ETH and stablecoin balances as part of the L2's core design.

Launch event establishes the yield mechanism's historical start on mainnet.

OtherCritical impact2 sources

Blast announces network wind-down and native-yield unwind

Blast announced an orderly L2 wind-down, directed users to withdraw to Ethereum, and said withdrawals would be temporarily unavailable while Blast's Lido assets were withdrawn before the exit process resumed with a 24-hour delay.

The announcement is a wind-down transition, not evidence of insolvency or a completed customer-loss event. Blast said normal interface withdrawals would remain available through October 26 and direct L1 bridge-contract withdrawals afterward.

Source record

Evidence dossier

Filter by claim, reliability, source type, and whether evidence is linked to a specific event.

Showing 3 of 3 evidence records

Entity

1 sources

Event

2 sources
News articleMediumEvent linked

Ethereum layer-2 Blast is shutting down

The Block · 2026-10-02

Reports the official Blast wind-down announcement, Lido unwind, temporary withdrawal interruption, 24-hour delay, October 26 interface boundary, and later L1 bridge-contract withdrawal path.

Comparative records

Independent archive

Help maintain customer-outcome records

Support court-document review, source preservation, corrections, broken-link replacement, and long-term archive maintenance. Support does not influence classifications or evidence standards.

Support CYA

Record maintenance

Report this record

Report incorrect dates, status, customer outcome, terms-risk interpretation, URL history, or missing evidence.

Submit correction →