Opera is Fantom's smart-contract mainnet, with EVM compatibility and FTM as its native fee and staking asset. Its documentation distinguishes native Opera FTM from FTM represented on Ethereum. The address format can look familiar without identifying the same ledger or balance. This is particularly important when reading older exchange and wallet instructions: an asset name alone does not establish which network will receive a transfer, and a bridge is a separate mechanism rather than an ordinary same-chain payment.

The migration documentation records Sonic's December 18, 2024 launch and a transition from an initial two-way token exchange to a one-way FTM-to-S arrangement. It directs developers, users and validators to different procedures. That separation reflects a real change of network: the successor can inherit a community and a technical lineage without inheriting every old application position. For historical research, Opera remains the place where its transactions occurred, while Sonic has its own deployments and later operating decisions.

Fantom's November 2020 DeFi overview describes an effort to make trading and financial contracts practical through EVM compatibility, quick confirmation and inexpensive execution. It also outlines proposed synthetic-asset uses for FTM and staked positions. Those plans help explain the early appeal to DeFi users: they wanted more than a token to hold; they wanted an environment in which frequent interactions were affordable. The article's validator counts, activity figures and proposed products belong to that historical snapshot, not to a current performance report.

By June 2021, the Foundation's ecosystem account included on-chain governance, a lower validator threshold, a major client upgrade and integrations with oracle providers and bridges. It described a public network for independent applications alongside enterprise-oriented services. This diversity matters because the ecosystem was never a single lending pool or exchange. Its usefulness depended on a collection of independently operated applications and infrastructure, each with its own contracts, administrators and dependencies.

The strength of the base-chain pitch did not make those other components uniform.

Opera's consensus documentation describes validators exchanging event blocks asynchronously and recording their relationships in directed acyclic graphs. Transactions eventually become part of the finalized chain that an ordinary explorer displays. The internal event graph and the user-facing sequence of final blocks are therefore different views of the same agreement process. This explains why a DAG-based design can still present familiar blockchain interfaces to applications.

It does not imply that validators operate without communication, that finality has no assumptions, or that a quick transaction makes a contract trustworthy.

The April 20, 2021 Go-Opera announcement describes a rollout that improved peer synchronization, event handling and the Special Fee Contract. It also explains that migration would require a coordinated pause after validators upgraded. Such operational details are more informative than treating performance as an unchanging headline number. Node software, database layout and staking contracts can evolve on the same network.

The announcement's planned timing and estimated finality should be read as claims about that upgrade, with the distinction between a rollout announcement and completion preserved.

The staking guide describes a fluid model in which lock duration, the behavior of other stakers and total stake affect rewards. It separates running a validator from delegating to one, and identifies a validator commission on delegated rewards. This is a system for supporting consensus, not a savings account with a fixed external source of interest. Historical calculator outputs cannot establish today's attainable return, especially after a successor network changes where development, liquidity and validator attention are concentrated.

The operator troubleshooting guide warns that running an old validator instance after moving its key can create double-signing and slashing. It also discusses synchronization before restarting, downtime, undelegation and early-unlock penalties. These are practical expressions of the security model: keeping keys and infrastructure under control is part of participating, not a background administrative chore. A holder choosing a validator relies on that operator's ability to follow those procedures, even when delegation leaves ordinary wallet ownership with the holder.

A June 2020 supply report explains how accrued staking rewards entered circulating supply and identifies the historical FTM maximum of 3.175 billion across supported public representations. It distinguishes circulating tokens from rewards still held in the allocation pool. This is a useful accounting lesson: a capped maximum can coexist with increases in the amount available to trade. The report's forward-looking reward schedule is historical, and its FTM ceiling should not be silently applied to the separate S token's later issuance policy.

The Foundation's 2024 liquid-staking guide describes receipt assets from Beethoven X and Ankr that represent positions in underlying staked FTM. Such instruments made it possible to use an economic claim on stake in other applications, but added provider rules, contract behavior, fees and redemption procedures. A liquid receipt is neither an additional native consensus token nor a promise of frictionless exit at its accounting value. Its market liquidity and its route back to the underlying asset have to be examined separately.

The January 2023 governance explanation gives staked tokens voting weight and lets validators represent delegators who have not cast their own votes. Direct participation removes that delegated voting weight from the validator for the proposal. The same account says the Foundation would implement approved changes, while self-executing proposals were a future design. That is an important boundary: a transparent vote can measure preferences without automatically executing every result. Concentrated stake, delegation defaults and implementation responsibility all shape who can influence outcomes.

The Ecosystem Vault funding round offers a concrete example of community allocation. In October 2023, the Foundation published results for a round distributing transaction-fee funding among nine projects after users voted through a Gitcoin process. The participants included exchanges, lending tools, NFT applications and games. These choices reveal an ecosystem trying to finance useful applications and cultural spaces together.

A grant announcement is evidence of the allocation process, however, not proof that each funded application later became sustainable or fulfilled every development promise.

Gas Monetization entered beta on May 31, 2023 with eligible applications receiving a 15 percent share of the gas fees their contracts generated. The Foundation compared the arrangement with platforms paying creators for the activity they attract. It also retained application criteria and the ability to suspend attempts to manipulate the program. The model therefore combined an on-chain revenue source with program administration. It sought an alternative to constant token incentives, but did not remove the need for users who valued the applications enough to pay for transactions.

The launch explanation directly addresses a possible conflict: a developer paid more when users spend more gas could have an incentive to make contracts inefficient. The Foundation answered that competing applications could undercut inefficient designs and that it could remove abusive participants. That response is a theory of competitive discipline supported by discretionary oversight, not a mathematical guarantee that fee sharing always benefits users.

The August 2023 general update records another side of builder culture: hackathons, grants, educational content and gaming workshops. It also records the arrival of separate bridged versions of familiar assets through different interoperability providers. That mix could lower barriers to experimentation while increasing the number of asset representations a user had to understand. A familiar ticker in a pool was not enough information to evaluate its backing. The ecosystem's creative energy and its operational complexity grew together rather than canceling one another out.

The Foundation's March 2024 account attributes substantial ecosystem losses to the July 2023 Multichain bridge exploit. It describes a default judgment obtained for the Foundation's own losses and a proposed legal route toward a liquidator. The distinction between winning a judgment, tracing assets and distributing recoveries is essential. The announcement does not show that all affected users were repaid. Nor did a bridge's failure mean that every native Opera transaction was invalid; the economic damage concerned assets and infrastructure on which applications depended.

The April 2024 USDC.e guide presents a later effort to consolidate stablecoin liquidity around a Wormhole-bridged representation backed by native USDC on Ethereum. It explicitly treats a possible future conversion to native issuance as an option, not as something already completed. Calling an asset canonical identifies an endorsed representation within that ecosystem; it does not mean the representation has no bridge dependency. The original contract, backing location and actual redemption path remain more informative than the short label USDC alone.

The Watchdog program described by the Foundation combined static analysis, transaction simulation and monitoring of deployed contracts. Its purpose was to catch problems that an old audit might miss after application changes. The account is evidence of a security service and its intended coverage, not proof that every listed project was immune from loss. In particular, a contract-monitoring service and a bridge custody arrangement address different failure modes. Evaluating the former does not settle questions about who can move the assets backing a token.

The app-token migration guide requires each project to decide how its own assets and positions move. It discusses bridging, snapshots and hybrid approaches, with special handling for liquidity positions and multisignatures. This makes the security boundary tangible: the native FTM-to-S conversion cannot automatically recreate every contractual claim a user holds. A migrated interface may look familiar while referring to a different contract and a different position. The project's published plan, rather than a general ecosystem slogan, is the relevant evidence for that transition.

On June 23, 2026, Sonic Labs reversed a proposed Opera shutdown and committed to keeping the chain live through at least year-end, with regular bridge funding. It attributed the change to community feedback. This is the latest continuity commitment established here, not an indefinite guarantee or an audit of every service. Earlier shutdown notices must be read in light of that reversal.

January 2026 discussions, with later replies in September, show why operating commitments matter to holders. Participants asked whether Opera still had a future and reported trouble accessing old infrastructure or moving balances. These are personal accounts, not verified measurements of network-wide availability. They nevertheless identify the practical test of a transition: can a person understand the network they hold assets on and find a functioning, trustworthy route for the action they need? Declaring a successor successful does not answer that question for every remaining user.