Questions and answers
Direct answers, including to the awkward ones.
Status
Is Solieum live?
Not publicly. Solieum is pre-mainnet: the gamma chain's six programs are deployed on Solana devnet — the five that carry settlement, plus the sequencer bond it shares with the stopped beta chain; a 48-hour window, the dispute game's enforcer as dispute authority, account data committed by root — and the L2 node publishes batches and commits roots to them, checkable from Solana's public RPC. There is no public RPC endpoint yet, external audits are not complete, and no assets should be committed to it. Anything on this site not marked live is not live.
Is there a token?
No token has been issued, and none is needed to use Solieum: fees are paid in SOL. If a token is ever issued, its jobs are bonding, verifying, challenging and staked sequencing, with at most an optional fee discount — SOL stays the default. It will be announced here first, and anyone claiming otherwise is not us.
When is mainnet?
No date. The roadmap lists conditions rather than quarters, because dates slip and then sit on the site as evidence of slipping. The conditions for each stage are published and checkable from outside.
Have the contracts been audited?
Not yet. External audits of the settlement programs, bridge, and dispute game are a prerequisite for mainnet, and the reports will be published in full — including findings whose risk was accepted, and why.
Security
What am I trusting today?
An operator who can upgrade the core contracts with a single key, a single sequencer, and a proof system that is deployed on devnet — and, on the beta chain, the settlement program's dispute authority — but enforcing nowhere that holds real funds. The bridge program releases funds only against proofs — no signer set does — and is deployed and initialized on all three devnet chains, the beta and gamma ones each with an air-gap guardian on a key that is not the operator's and is not shared between them. That is Stage 0, stated on the security page rather than left to be discovered.
Is Solieum a rollup or a sidechain?
An optimistic rollup, and it will stay one: batch data and state roots live on Solana, an invalid root is removable by fraud proof, and there is no validator set of our own deciding finality. Decentralisation goes into who sequences — a staked, rotating sequencer set is a later roadmap stage — never into who decides state. The one pre-authorised exception is per-market validium for data, disclosed on that market's page if it ever happens.
Does Solieum inherit Solana's security?
Only under specific conditions: batch data published, invalid roots provable by anyone, and exit possible without operator cooperation. All three are built; the first two are live on devnet; none is enforcing on a network that holds funds. Until they hold in production, the accurate statement is that Solieum settles on Solana — not that it is secured by it.
Can Solieum take my funds?
The design says no: the bridge releases funds only against a proven withdrawal, and a pause cannot block one. The honest answer today is that the upgrade key can change that code, so it depends on whoever holds the key — currently a single operator key. The multisig, threshold and timelock that will hold it are published before mainnet, and the roadmap's last stage makes the timelock longer than the withdrawal window.
What happens if Solieum shuts down?
The intended answer is that you exit against the last final state root using public tools, with no cooperation from us. That path is built into the bridge program and will be demonstrated in a public drill by someone unaffiliated before it is claimed as working.
Using it
How long do withdrawals take?
Long enough for the challenge window to close, then the air gap after it: 48 hours plus 24 hours (ADR-0016, ADR-0015), so about three days, plus minutes of overhead. Read the total rather than either half. The gamma devnet chain enforces the 48 hours, as the beta chain did from 2026-09-05 until it stopped on 2026-09-12 with every root final; the alpha chain before them was created with seven days and kept them, because the window is fixed at initialization and there is no setter. The reasoning is published with the parameter. Faster routes via liquidity providers are a different trust model and will be labelled as such.
Why is a withdrawal slower than a deposit?
A deposit only has to wait for Solana to confirm. A withdrawal has to wait for the period in which someone could prove the L2 state wrong. The wait is the security.
Do my Solana programs work unchanged?
Mostly, not entirely. Timing sysvars, fee accounting, rent economics, and anything touching stake or reading L1 state directly all differ. The compatibility matrix names each divergence.
Which wallet do I use?
Existing Solana wallets are the intent, and the pieces are in place: the node accepts a wallet's own transaction format, verifies every signature, and answers the blockhash and status calls wallets make — verified on the devnet chain with transactions built exactly as a wallet builds them. Named wallet support is confirmed with the public testnet rather than promised now.
Building
Can I deploy today?
Not publicly — there is no public endpoint, and the protocol repository is not yet public either; both open with the public testnet. The chain runs against devnet today on the team's side. Solve works against Solana now, so programs written with it are not blocked on Solieum — its Counter has already run unchanged on a local Solieum chain, registered at node start.
Are the SDK packages published?
Not yet. Package names appear in the documentation but are not on npm or crates.io. The resources page lists exactly what exists and what does not.
How do I get involved early?
Get in touch, especially if you intend to run a verifier or you have a workload the base layer is squeezing. Early teams get direct access to the protocol engineers.