07About
Who is building this
Solieum Labs: the thesis behind a Layer 2 for Solana, how the team works, and why every claim here is published with the basis it rests on.
◆Company
Solieum Labs
Solieum is developed by Solieum Labs, the protocol engineering team behind the network. The same team builds Solve, the main framework for building on Solieum: programs are written in CradleScript, and CRADLE, the compiler underneath it, checks them and emits native Solana programs.
The order of shipping is deliberate: developer tooling that works against Solana today, the network's trust machinery next, marketing claims last. Where that stands: all six protocol programs are live on Solana devnet — the five settlement programs and the sequencer bond — and the node settles real blocks to them, checkable from Solana's public RPC. A team earns the right to operate a Layer 2 by showing its work in public, and that is the standard this site is written to.
The thesis
Solana is fast enough for most things and not fast enough for some. Order books, game state, and social feeds generate transaction patterns that compete badly for shared blockspace — not because the base layer is slow, but because their volume is bursty, low-value, and constant.
A Layer 2 is the standard answer, and it comes with a standard failure mode: teams ship the throughput and defer the parts that make it trustworthy — proofs, forced inclusion, exit. Those are the difference between a Layer 2 and a service that is holding your funds.
Solieum is being built in the opposite order. The trust model is published before the launch, the numbers state their basis, and each stage has a condition that can be checked from outside. It is an optimistic rollup and stays one: decentralisation goes into who sequences, never into who decides finality.
◆How we work
Publish the weaknesses
Our security page lists what is unfinished. Independent reviewers will publish it regardless — doing it first is cheaper and more useful.
No number without a method
Every performance figure carries how it was arrived at. Targets are labelled as targets.
Exit is a feature
If users cannot leave without our cooperation, nothing else on this site matters.
Say which network a claim holds on
Devnet is not testnet is not mainnet. Every page names which one a statement is true on, and "live" means on-chain and checkable by anyone — never "exists in a repository".