Blast's starting proposition was that assets should keep earning while their owners used an Ethereum scaling network. Its documentation describes staking income for bridged ETH and a stablecoin called USDB connected to MakerDAO's DAI infrastructure. That design makes the source of yield part of the chain's economic architecture. It also introduces dependencies beyond merely executing a transfer. A growing wallet balance is an accounting result supported by those underlying arrangements, not interest created without a counterparty or protocol risk.

The launch followed an unusual order. People deposited into an early bridge before they could use the complete network. Decrypt's contemporaneous February 29, 2024 report records the mainnet opening and the release of previously locked deposits. It identifies founder Tieshun Roquerre, known as Pacman, with the Blur NFT marketplace. This history helps explain why Blast's public identity included both financial experimentation and the reward campaign habits of NFT traders.

Blast mainnet uses chain ID 81457 and ETH for transaction fees. BLAST is a separate token, and USDB is another separate asset. A wallet can therefore need ETH to move a BLAST balance or interact with a USDB application. A proposed role for BLAST inside a mobile app does not change the network's documented gas currency. Keeping these identities separate prevents a product announcement from silently becoming a false statement about consensus or transaction payment.

The published allocation begins with 100 billion BLAST: half for community incentives, roughly 25.5 percent for contributors, 16.5 percent for investors, and eight percent for the Foundation. Contributor and investor allocations have a one year cliff followed by monthly vesting within four years. Those schedules describe supply becoming transferable, not a promise that recipients will sell or that community members acquire equal influence. The Foundation determines distribution schedules within the community allocation.

For ordinary externally owned accounts, native ETH yield appears through balance changes. Contracts start differently: ETH yield is disabled unless their configuration enables it. Automatic mode increases the contract balance, while claimable mode separates the yield for a later claim. The governor address controls reconfiguration and claims. A depositor therefore needs to understand the application's treatment of yield, not simply recognize that the chain supports it. An app can handle these proceeds differently from a personal wallet.

WETH and USDB use their own rebasing token interfaces, with automatic yield enabled by default for both ordinary accounts and contracts. Developers can select other modes. The documentation also describes non-rebasing wrappers, nrETH and nrUSDB, whose value reflects underlying rebasing assets without constantly changing the holder's unit count. This distinction matters for collateral accounting and integrations: a stable number of wrapper units does not mean the economic position stopped changing.

Gas revenue sharing is another part of the design. Contracts must opt into claimable gas; otherwise the relevant fees go to the sequencer operator. Eligible base and priority fees are calculated after Ethereum data costs, and nested calls divide attribution according to gas consumed. A governor can claim the proceeds. The documented schedule increases the claim fraction as fees mature, from an initial partial share toward the full eligible amount over thirty days.

That mechanism gives builders a possible revenue source but does not automatically give application users a refund. The recipient and access controls still matter. For example, an application might retain revenue for maintenance or explicitly route it onward. Inspecting that choice is more useful than treating every transaction as subsidized. The documentation's examples also distinguish immediate claims from waiting for maturation, so gross fees paid by users should not be confused with cash an app can collect immediately.

Blast's transaction guide distinguishes pending submissions, sequencer confirmation, publication to Ethereum, and Ethereum finalization. A sequencer receipt is still marked unsafe before publication. A transaction visible in an app can therefore be further along than a pending request without yet having reached the strongest documented settlement state. The guide gives typical timings, but those are operational expectations rather than a deadline that every transaction must meet.

The official bridge FAQ describes an approximately seven day journey from Blast back to Ethereum, while entering from Ethereum normally takes minutes. That asymmetry is important for anyone who needs funds on another network at a particular time. Faster third party routes must be evaluated on their own conditions. A successful internal transfer, or the ability to withdraw from a mobile savings interface, is not evidence that a canonical Ethereum exit has already completed.

The March 2024 Gold rules made applications intermediaries in distributing ecosystem rewards. The Foundation allocated Gold to selected teams, expected it to reach users, and prohibited certain liquid proxies or arrangements designed to turn Gold into another tradable reward token. This produced a culture of comparing app allocations, interpreting eligibility, and checking whether a task justified its cost. The rules also reserved room for judgment and revision, rather than offering a permanently fixed conversion contract.

A June 26, 2024 r/ethtrader post by Every_Hunt_160 records the claim experience from a participant's perspective: watching an introductory video, installing the mobile app, and comparing the result with effort spent farming. Replies included both disappointment and satisfaction with relatively passive participation. These are individual reports, not an audited distribution study. They nevertheless preserve something an allocation table cannot: users were evaluating attention, fees, and time as costs, not simply celebrating a free token.

Phase 2 initially allocated equal reward pools to Points and Gold. Its July user announcement tied app installation to Golden Tickets and discussed multipliers, invites, and continued liquidity requirements for some vested awards. These mechanics made repeated participation a visible part of the social experience. They are historical rules, however. The later switch to liquid BLAST rewards means a tutorial written during that summer cannot safely be treated as instructions for earning today.

The July 2024 builder rules ranked apps using category, traction, execution, incentive design, and commitment to Blast. New and established applications had separate allocation groups. The Foundation asked for public dashboards and transparent distribution formulas, and discouraged rewards that could effectively be purchased through fees to the team. This was an attempt to distinguish useful activity from activity manufactured to collect another incentive. Foundation judgment remained central to scoring and exceptions.

On July 11, 2024, forum participant untamedadam proposed retroactive developer grants after describing teams that had expected an allocation and received none. The proposal linked public complaints and a preliminary list of eligible applications. It sought to repair relationships, fund future building and give developers more voting influence. This is an original record of dissatisfaction inside the ecosystem, useful for understanding why rewards can attract builders and also strain their loyalty. The account reflects its author's interpretation.

It does not independently verify every complaint or establish that the Foundation accepted the proposed grants.

The bylaws allow proposals about backing assets, yield providers, fees, reserves, and council membership. They impose proposal and voting thresholds, Progress Council review, and a role for Foundation directors. Approved votes are taken under advisement rather than creating an unconditional duty to implement them. A Safety Committee can act urgently during security emergencies. These are meaningful limits on the phrase community governed: token voting coexists with legal, administrative, and emergency powers.

Historical discussion also questioned who should control Gold. In July 2024, Andy proposed dividing allocation authority between tokenholders and the Foundation. Gwr supported broader participation but warned that large holders could steer rewards toward apps favorable to their own positions. Andy argued competing app treasuries would disperse influence. Their exchange captures a real disagreement over whether token-weighted participation distributes power or simply gives existing capital another way to organize it.

In June 2024, the Foundation described a strategy that joined the chain, wallet, and mobile and desktop experience. It defended starting with speculative crypto users and argued that controlling more of the experience could make applications easier to distribute. That was an official product thesis, not evidence that a mass consumer audience had already arrived. The important strategic change was that Blast wanted a direct user relationship beyond the underlying network.

The January 23, 2025 mobile announcement ended Points and Gold in favor of liquid BLAST incentives. It described an Earn product converting supported deposits into USDB and paying rewards in BLAST, with exposure to both DAI backing and BLAST market prices. It also described an initially restricted app distribution process. The published rate in that launch announcement is historical; it should not be presented as a current guaranteed return.

The current Earn instructions explain that retaining or adding BLAST affects the multiplier on USDB deposits, while withdrawing BLAST resets the multiplier. They describe periodic distributions and the ability to withdraw from the app. Economically, a depositor must distinguish principal held as USDB, rewards paid in a different asset, and extra BLAST held to change reward treatment. A higher displayed multiplier does not eliminate the price exposure introduced by that extra position.

Blast Mobile uses ERC-4337 smart accounts. Its recovery guide explains that an exported seed phrase controls the external signer, not directly the smart account address shown in the app. Importing that phrase into an ordinary wallet can therefore display a different address. This is a concrete example of why familiar backup terminology can mislead. The documented recovery process and secure backup of the signer material matter even when everyday login uses a passkey.

Network maintenance continued after the mobile pivot. A release notice published February 13, 2026 records activation of version 1.7.0 the previous day and identifies changes to the blob fee schedule, with required node configuration. That is evidence of a particular operational upgrade. It does not establish usage growth, profitability, or the success of the mobile strategy. Those would require separate measurements rather than being inferred from a software release.

The June 2024 BLIP2 discussion advocated awarding Points to BLAST holders to encourage participation in governance. Ham objected that directing incentives toward the chain token could pull capital away from application tokens and leave builder retention unresolved. Other participants wanted immediate execution or retroactive credit. The disagreement was about what deserved reward: holding the governance asset, supplying liquidity, or using and building applications. These were not interchangeable contributions.

A December proposal by unbanksy suggested using native yield to buy BLAST and distribute it to depositors. Thruster contributors supported the incentive argument, while nft_tipster objected to replacing the asset users expected to earn. Jenn raised questions about control of the yield contract and optional participation. The indexed historical thread documents those positions; its original live URL now redirects to Blast's app. This account does not treat the proposal's speculative price model or proposed implementation as an established result.