Layer 2 for Solana · Blockchain Life 2026 · Dubai · 1–2 December
Fast off-chain.
Final on Solana.
An optimistic rollup that executes in the Solana Virtual Machine, publishes its data on Solana, and lets Solana settle every dispute.
The problem
Solana is fast. Builders still need room of their own.
An app that wants its own execution lane, predictable costs and its own rules has had to give something up to get them.
Move finality to a new validator set. Solana becomes decoration rather than security.
Move data to an external layer. "Secured by Solana" stops being true without a footnote.
Break compatibility. Divergence from the real SVM is the one risk that cannot be bounded.
The answer
Execute off-chain. Publish on Solana. Let Solana judge.
A fork of Agave's SVM, so programs behave identically. A block every 100 milliseconds when there is work.
Every batch is compressed and published in Solana transactions. Anyone can rebuild the chain from scratch.
One 32-byte state root per batch. It becomes final only after a 48-hour challenge window passes unchallenged.
Why a Layer 2 on Solana
Four reasons, checked against what runs
Its own sequencer and blocks. A rush on Solana does not delay a Solieum transaction or change its flat fee.
A signed receipt in 14 ms, a block in about 100 ms (devnet medians, 13 Nov). Sub-millisecond is not claimed.
Solana's own runtime, not the EVM. Each chain runs exactly the programs fixed at its start.
No KYC yet. A permissioned lane must not undo forced inclusion, so that design comes first.
Failed transactions on Solieum
A failed transaction costs nothing
A quarter to a third of non-vote transactions execute and fail, and every one still pays its fee.
A transaction that would fail is run when it is submitted and refused there, with the program's own error. It never reaches a block and is never charged.
Not a trade guarantee: slippage still refuses. Not finality: blocks settle on the usual schedule. One exception: forced-inclusion entries posted through Solana are not checked first. Source: ADR-0014.
A worked example
Two buyers, one item left
- Send. Both built against "one item left".
- Execute. Alice's buys it; Bob's runs next: sold out.
- Result. Both land in a block. Bob's failed, fee paid.
Bob: failed on chain, fee paid
- Alice sends. Run against the block being built: admitted.
- Bob sends. Run with Alice's purchase included: sold out.
- Refused. Turned away at once. No block, no fee.
Bob: told no in milliseconds, 0 SOL
Bob still does not get the item. Losing the race just costs nothing. Order of events only; no timings claimed.
How it works
How a transaction becomes final
Four components carry the design: the sequencer, data availability, settlement and the dispute game. The fifth thing is Solana itself.
The dispute game
A disagreement about a batch becomes a disagreement about one instruction.
Anyone who thinks a posted root is wrong opens a dispute inside the 48-hour window.
Challenger and proposer halve the disputed execution trace each round until a single step remains.
Solana executes that one step. The loser's bond pays the winner. No committee, no vote.
Receipts keep the sequencer honest too: two receipts for the same position are a contradiction anyone can prove, and the proof takes the bond.
Design discipline
What Solieum is not
No Solieum validator set decides state or finality. A staked sequencer set is a planned stage, and it will decide ordering only.
Batch data lives on Solana. A cheaper external layer would become a second trust root. Per-market exceptions would be disclosed on the front page, never silently.
A harness replays identical blocks on different machines and compares roots byte for byte, so the fork cannot drift.
By the numbers
Small, fixed, checkable
Block cadence when there is work: the devnet chains' setting.
Challenge window, counted in wall-clock seconds since September 2026.
One root per batch carries the whole chain's state to Solana.
Programs live on Solana devnet: settlement, data availability, inbox, dispute game, bridge portal, sequencer bond.
Economics, measured
Settlement cost is per batch, not per transaction.
Rent, not fees, is the cost of running a rollup on Solana. A block pays for its own settlement at roughly 705 transactions at the flat fee, or about 452 once batch rent is returned, as it is today. Below that the chain is subsidised, and the whitepaper says so.
The native coin
SEU: Solana's shape, without Solana's inflation
Bonds and the rollup's gas stay SOL: a guarantee that weakens when a fraud is found is not a guarantee.
Not issued on any network of value. Devnet test value only. No mint on Solana, no public sale, no airdrop. Until solieum.com says otherwise, any address claiming to be SEU is a scam.
Vesting
Counted from issuance, and never one big unlock day
Private rounds start at month 9 and the team at month 12, so the two never unlock on the same day. The treasury is locked for 12 months.
Every bucket vests in an escrow anyone can read. Nothing unlocks before issuance. Signed agreements keep their own terms. Source: ADR-0028, amended 19 November 2026.
Where it stands · September 2026
Live on Solana devnet. Not on mainnet.
Ecosystem
Built with, and built on
Solieum's language and framework. Write a contract once in CradleScript; the native Solana program it emits is exactly what Solieum executes. The same source ships to EVM, NEAR, Polkadot, Aptos and Sui.
AI identities, policies and control decisions anchored on Solieum, so anyone with a proof ID can verify who authorized what.
The explorer ships inside the node. Docs on GitBook, code on GitHub, every claim published with the basis it rests on.
Solieum Labs
Let's talk at the booth.
Scan for the Solieum brochure
solieum.com/brochures/solieum