Naar hoofdinhoud
Live markt
Block #9

Dossiers

The Solana ecosystem dossier

Since its launch, Solana has positioned itself as a blockchain designed for high throughput and low transaction costs, without the layered approach that Ethereum uses. That choice has given the network a large and active user community, from trading platforms to memecoin launches, but has also repeatedly led to outages that called its reliability into question. This dossier describes the technical choices behind Solana, the major incidents in the network's history, and the ongoing debate over decentralisation versus performance.

Bram HoekstraWritten by Redacteur security, EindhovenUpdated Checked by the editorial desk

Timeline

  1. Collapse of FTX/Alameda hits Solana hard due to close ties with the exchange.
  2. Network processes record number of transactions per day amid memecoin trading surge.
  3. Firedancer validator client reaches major testnet milestone for network stability.
  4. Alpenglow consensus upgrade approved to further shorten settlement times.

A monolithic design for speed

Where Ethereum outsources transaction processing to separate layer 2 networks, Solana opts for a monolithic setup: all transactions are processed on a single base layer, optimised to handle thousands of transactions per second at a fraction of a cent each. That does require validators to run significantly heavier hardware than is common on many other networks.

A core part of this design is Proof of History, a mechanism that records a verifiable order of events before consensus is reached. That allows validators to agree faster on transaction ordering, an important contributor to the network's high throughput.

The downside of this approach is that the requirements placed on validators raise the barrier to participation, raising questions about the degree of decentralisation compared with networks that deliberately set lower hardware requirements for their base layer.

Outages and network interruptions

Solana has repeatedly experienced full network outages throughout its history, requiring validators to restart the network through coordinated coordination. Causes ranged from overload caused by bots flooding the network with transactions to bugs in the consensus logic that only surfaced under specific load conditions.

These incidents have repeatedly damaged the network's reputation and fuelled criticism that Solana prioritises performance over robustness. Following several outages, the development team implemented changes such as priority fees and local fee markets to better isolate congestion caused by individual applications from the rest of the network.

  • Multiple full network outages required coordinated restarts by validators
  • Causes ranged from bot-driven overload to bugs in consensus logic
  • Later changes introduced local fee markets to isolate congestion

Firedancer: a second validator client

Much of Solana's robustness problems were attributed to the fact that almost all validators ran the same software, meaning a single bug could potentially bring down the entire network. In response, an outside party developed Firedancer, an independently written validator client that can run alongside the existing software.

The idea behind client diversity is that a bug in one implementation does not automatically cause a network-wide outage, because validators running the other client can keep operating. The gradual rollout of Firedancer is seen within the community as one of the most important steps toward structurally improving the network's stability.

Memecoins, trading volume and the role of speculation

In recent years, Solana has become a central hub for issuing and trading memecoins, helped by the low transaction costs and fast settlement that make launching new tokens low-effort. Platforms that simplify the creation of such tokens have driven periods of extremely high transaction volume on the network.

This dynamic has brought the network both users and criticism. Supporters point to proven scalability under heavy load, while critics argue that a large share of the activity is speculative in nature and has little to do with sustainable, longer-term applications.

At the same time, the influx of users and developers has also led to broader applications beyond speculation, including payment processing, decentralised exchanges and experiments with tokenising real-world assets.

Alpenglow and the next phase of consensus

Alongside Firedancer, the development team is working on Alpenglow, an overhaul of the underlying consensus mechanism intended to further shorten the time to final transaction settlement. That is relevant for applications that depend on fast, irreversible confirmation, such as financial trading.

The upgrade marks one of the larger changes to Solana's core architecture since launch and is being rolled out in phases, with extensive testnet testing before validators are asked to implement the change on the mainnet.

  • Alpenglow aims to further shorten the time to final settlement
  • Relevant for applications requiring fast, irreversible confirmation
  • Rollout proceeds in phases after extensive testnet testing

Decentralisation versus performance: a lasting tension

At the heart of the debate around Solana remains the trade-off between performance and decentralisation. Higher hardware requirements for validators theoretically limit the number of parties able to participate in consensus, which can affect censorship resistance over the long term.

Critics of this course point to networks that deliberately opt for lower base-layer throughput to keep participation broadly accessible. Proponents of Solana's approach argue that falling hardware costs naturally narrow this gap over time, and that users benefit from a fast, cheap network that is usable today.

Frequently asked questions

Why is Solana faster and cheaper than many other blockchains?

Solana processes all transactions on a single base layer optimised for high throughput, partly through the Proof of History mechanism, rather than outsourcing transactions to separate layer 2 networks.

How often has Solana experienced network outages?

The network has experienced several full outages throughout its history that required a coordinated restart by validators, with causes ranging from congestion to software bugs.

What is Firedancer and why does it matter?

Firedancer is an independently developed validator client that runs alongside the existing software. This increases client diversity, so a bug in one implementation cannot immediately bring down the whole network.

Why is Solana so popular for memecoins?

Its low transaction costs and fast settlement make it cheap and easy to launch and trade new tokens, which has driven a large influx of activity to memecoin launch platforms.

Is Solana as decentralised as other major blockchains?

That remains a matter of debate. The relatively high hardware requirements for validators theoretically limit the number of participants, while proponents argue that falling hardware costs gradually narrow this gap.

Read next

Newsletter

Bitcoin for breakfast, Brussels for lunch

One short email with what actually matters: prices, regulation and the banks that move. No hype, no noise.

  • Daily at 07:00
  • 2 minute read
  • No spam

Free. Unsubscribe in one click.