Welcome to Solieum
Solieum is an optimistic rollup on Solana: transactions execute off-chain in an SVM environment, the data is published on Solana, and the resulting state is committed to Solana where an invalid commitment can be proven wrong.
Solieum is a Layer 2 for Solana. Transactions execute off-chain in a Solana Virtual Machine environment, the data needed to check that execution is published on Solana, and the resulting state root is committed to a Solana program that will not finalize it if anyone proves it wrong.
That is the whole claim, and the rest of this paper is about whether it holds. Three conditions decide it, and each one is a section below:
- The data is published on Solana. If batch data is withheld, nobody can rebuild the chain, nobody can prove fraud, and nobody can exit without the operator's cooperation. Where the data lives is what makes this a rollup rather than something else with a rollup's vocabulary.
- An invalid state can be proven wrong on Solana. A dispute narrows a disagreement about a whole batch down to a single instruction, which Solana verifies directly.
- Funds leave against a proof, not against a signature. The bridge vault releases lamports only for a withdrawal proven against a state root the settlement program holds as final.
Miss any one of the three and the security a rollup is supposed to inherit does not arrive.
Where Solieum stands today
Dated 11 September 2026. This table is the honest answer to "is it live", and it is meant to be read before anything else in this paper.
| Status | |
| Network | A public Solana devnet chain. No mainnet, no public RPC endpoint, no user funds. |
| Programs on Solana | Six, deployed on devnet: settlement, data availability, forced-inclusion inbox, dispute game, bridge portal, sequencer bond. |
| Sequencer | A single operator. It is a liveness and ordering monopoly, and forced inclusion ships beside it rather than after it. |
| Proofs | The dispute game is deployed and its verdicts are the settlement program's only route to a challenge outcome. No dispute has yet been played on a live chain. |
| Bridge | Deposits credited end to end. Withdrawals proven against final roots and paid out of the vault: four on the retired beta chain and one on gamma as of 12 September, all to the team's own addresses. |
| Audits | None. Two sequential audits and a proof-system specialist are planned before mainnet. |
| Token | Does not exist. Gas is SOL. Any address claiming to be a Solieum token today is a scam. |
What this paper will not tell you
It will not give you a transactions-per-second headline.
A rollup's real throughput ceiling is set by data availability, not by execution, and Solana has no separate blob market, so batch data competes in the same fee market as everything else. The honest form of a throughput claim is therefore an arithmetic derivation with a cost per byte in it, not a number on a banner. That derivation, with the compression figures measured from the code that ships in the repository, is in Technical Architecture and Fees, Economics and the Token.
Earlier versions of this document carried a throughput table with figures nothing in the system had produced. It is gone. Every number now in this paper is either a measurement, with the thing that measured it named, or a parameter, with the file that holds it named.
What it costs you
The cost of an optimistic rollup is the exit. A withdrawal on the canonical path waits for the challenge window and then for an air gap: 48 hours plus 24 hours, about three days in total on the mainnet design. Quote the total, never the window alone. A fast-exit provider will front the funds sooner for a spread, which is a market, not a protocol guarantee.
The reasoning behind both numbers, and what happens inside each of them, is in Security and Trust Assumptions.
Notices
{% hint style="warning" %} SECURITY ALERT: Solieum team members will never contact you first. If someone claiming to be from Solieum opens a conversation with you, it is not us. {% endhint %}
{% hint style="danger" %} NO TOKEN EXISTS. No sale, no airdrop, no allocation. Any address claiming to be a Solieum token is a scam. When that changes it will be announced on the official site first. {% endhint %}
{% hint style="info" %} TRANSLATION NOTICE: This documentation is written in English. Machine translations may lose precision in the technical sections, where precision is the point. Read the English for anything load-bearing. {% endhint %}
Where to go next
| Page | What it answers |
| Introduction | What Solieum is, in one page, and what it is not |
| Why Solana Needs a Layer 2 | The case for a Layer 2 on a fast Layer 1, stated without inflating it |
| About Solana | The base-layer properties the design depends on, and the ones that constrain it |
| Technical Architecture | Sequencing and admission, data availability, settlement, the state commitment, the trace a dispute is about, and the one-step verifier |
| Security and Trust Assumptions | What the operator can do to you, what it cannot, and who holds which key |
| Wallet Bridge | The deposit record, the withdrawal encoding, the proof format, and the one key that reaches a proven withdrawal |
| Fees, Economics and the Token | What a transaction costs, what a block costs to settle, the size of the subsidy, and what the token is for |
| SVM Compatibility | Where Solieum is identical to Solana, where it is redefined, and where something is absent |
| Solieum Programme Kit (SPK) | What a developer can use today, and what does not exist |
| Solve Framework | Solieum's main framework, and a program it compiled running unchanged |
| Status and Roadmap | What is done, what is next, and the condition each stage is gated on |
| Protocol Parameters | Every parameter, its value, where it is fixed, and what changes it |
| Glossary | The terms, as this paper uses them |