◆Why Layer 2
What a Layer 2 is for
Solana is fast. The pressure is at peak, not at average — and that is a different problem with a different fix.
Solana is fast. The pressure is not average throughput — it is what happens at peak, when demand spikes and everyone competes for the same blockspace at the same moment. These are the failure modes a Layer 2 is meant to absorb.
01Pressure points
What actually goes wrong at peak
The failure rate itself, measured: Solana failed transactions →
- 01
Demand spikes
Bursts of activity — launches, liquidations, meme-coin cycles — push far more transactions at the network than the steady-state average, and they all arrive at once.
- 02
Networking limits under load
The transport layer has finite capacity for inbound traffic. Under heavy load, excess transactions are dropped before they are ever considered for inclusion.
- 03
Transactions that never reach the leader
A transaction that does not arrive at the current block leader in time is not rejected — it simply never lands, which is harder for applications to handle than an explicit failure.
- 04
Slippage expiry
In volatile markets, a trade can breach its slippage bound while it is still queued. The transaction was valid when signed and invalid by the time it executed.
- 05
Downstream pauses
When congestion persists, exchanges and custodians have at times paused deposits and withdrawals — the user-visible end of a network-level problem.
02The mechanism
What a rollup changes
Execution moves off the base layer
Transactions are executed on a separate network. The base layer's job changes from executing everything to recording results and adjudicating disputes.
Many transactions, one commitment
Batches are committed as a single state root, so hundreds or thousands of transactions share the cost of one settlement.
Security is inherited, conditionally
A rollup inherits the base layer's security only if its data is published there and an invalid state can be proven wrong. Miss either condition and the inheritance does not happen. Solieum publishes on Solana and has the proof machinery deployed on devnet; the security page tracks where both conditions stand.
Tuned for a workload
A separate execution environment can make choices a general-purpose base layer cannot — different fee rules, different block cadence, different resource limits.
03What you gain
- Throughput headroom. Bursty workloads get their own lane instead of competing with everything else on the base layer.
- Lower per-transaction cost. Settlement cost is amortised across a batch, which is what makes sub-cent actions economic.
- Workload-specific tuning. Fee policy, block time, and limits can be set for one class of application rather than for all of them. Solieum's choices so far: a flat fee paid in SOL, no separate gas token, and a block every two seconds when there is work.
- Familiar surface. Same account model, same signing, same program model — so existing Solana knowledge carries over. The node accepts a wallet's own transaction format.
04What you take on
- Two systems to secure, not one. The Layer 2 has its own contracts, its own operators, and its own bugs. Its security is the base layer's security plus its own — and the weakest link decides.
- More surface, more to get wrong. Bridges, provers, and sequencers are complex and comparatively new. Most large losses in this category have come from bridge contracts and operator keys, not from the base layer.
- Movement between networks. Assets and messages crossing between layers need routes that are themselves trustworthy. Every additional hop is another thing to evaluate. On Solieum that route is a bridge program that releases funds only against proofs, with a 48-hour challenge window and a 24-hour air gap on the optimistic path, about three days in total — deployed and initialized on devnet, where the chain still carries the seven days it was created with.
05The other side
When a Layer 2 is the wrong answer
Scaling talk is more credible from someone willing to say when not to. If any of these describe you, stay on the base layer.
Your volume fits on Solana already
If you are not hitting fee or contention pain at realistic load, an L2 adds a trust surface and an integration burden for nothing. Solana's base layer is very good; use it until it hurts.
You need atomic composability with L1 protocols
An L2 cannot call into Solana programs synchronously. If your core loop composes with L1 DeFi in one transaction, splitting it across layers breaks the atomicity you rely on.
Your users cannot tolerate the exit window
Market makers and settlement desks that need funds mobile in minutes will find a challenge window intolerable — about three days here, on the optimistic path — and LP fast-exits are a different risk they must underwrite deliberately.
You cannot absorb a young platform's risk
Every L2 is newer, less audited, and less battle-tested than its base layer, this one included: Solieum is on devnet and pre-audit. Treasury-scale funds belong on the most proven layer available until the trust model says otherwise.
If you are still reading
The architecture page shows how the machine fits together. The security page says what you would be trusting today, plainly. The use-cases page is the honest sales pitch — workloads where the trade actually pays.
Building something the base layer can't hold?
Tell us the workload. If Solieum is the wrong answer for it, we would rather say so early than have you find out at launch.