References and Resources

Links that resolve, contracts you can open on a block explorer, and an explicit list of the things that do not exist — everything checked on one date.

Everything listed here was checked on 11 September 2026, the last section again on 30 September 2026, and the contracts' upgrade authority on 1 October 2026. Anything that did not resolve is in the last section rather than in a table.

Official

Websitesolieum.com
This documentationsolieum.gitbook.io/solieum
Bridge applicationBuilt for walletbridge.org, not deployed there yet; see the last section
GitHub organisationgithub.com/Solieum

Community

X@solieum
TelegramSolieum\_layer2

These two are the only official channels. Solieum team members never contact you first. Anyone who opens a conversation claiming to be from Solieum is not.

The contracts, on Solana devnet

These are the programs the current chain settles to. Open any of them on a block explorer with the devnet cluster selected and read the transactions for yourself. That is the point of listing them.

ProgramAddress
Settlement (state roots, 48-hour window)7yH9bTF9s6d86pW6stgVdfxaSkxiCDNBQR1HvTk399YW
Data availabilityDYyVbACxqDH77DSApL2dcwfZrGzNLujQi21bKehZC1Pr
Forced-inclusion inbox9pVAsoaCm9uU7jzGgPB3AqHuXs7LKWtqkZCCeZXwmkxq
Dispute game (its enforcer is the settlement program's dispute authority)BrHfePzDnV7oSTd4c4T7f7WDwz8H9zwxYe1nJ8e3rqeA
Bridge portal (deployed and initialized)8hsKk9nDsXN7JMRH1tj5RYdXs12ohrvduGBkgwEwGqVM
Sequencer bond and slashing (the sequencer is bonded)6KQdRji1ZKg3tGLUczeUyX9ywxnivXKbSSAM3hbzzY4L

These are the programs of the current chain, gamma (chain id 7790), which replaced beta on 12 September 2026 when the state commitment changed and a new genesis was cut; the sequencer bond program is shared across chains. Two earlier chains are stopped and kept as history: alpha, whose seven-day window and plain-key dispute authority meant its verdicts did not enforce, and beta, whose 158 blocks are all final and whose four withdrawals are all paid. Each of the five gamma addresses above was checked on devnet on 12 September, and the dispute game's deployed bytes were matched to a clean build of the source, byte for byte. Each program's upgrade authority is on its program-data account for anyone to read: on 1 October 2026 all six named the same key, Bg1CnCGv7rjxFJF9ZUExfrRQKGjr2tiBTZxFc3GUbv88, which Security and Trust Assumptions says plainly.

Solve, the main framework

Solve languagesolvelang.com
Cradle Studio, web IDEcradle.solvelang.com

Solve is Solieum's main framework and has its own site and IDE. What has actually been demonstrated with it on a Solieum chain is on the Solve Framework page.

Background reading

Solieum assumes the reader knows what an optimistic rollup is. If not, the general literature on optimistic rollups, interactive fraud proofs and bisection games applies directly, and Solana's own documentation covers the base layer's fee model, compute budget and account model at solana.com/docs.

The design decisions behind this system are recorded as decision records in the protocol repository, which is not public. The records themselves are published on the site at solieum.com/decisions: when counted on 5 October 2026, 26 of the 29 then written were there. Where this paper states a parameter, it names what holds it, so that the claim can be checked against the system rather than against a document.

The same repository holds the escape-hatch kit, solieum-testnet/drills/escape-hatch/, written for someone who is not the operator: it forces a transaction onto the inbox from the user's own key, simulating unless told to send, and checks from Solana alone whether the sequencer included it by the deadline. It needs only Node.js 18 or later. Its README is the outsider's account of what forced inclusion guarantees and what it does not, and this paper cites it where it relies on it.

What does not exist

Listed explicitly, because earlier versions of this documentation linked to all of it and a reader who remembers those links deserves a straight answer.

  • No published packages. There is no @solieum/sdk, @solieum/web3.js, @solieum/bridge-sdk, @solieum/solve-cli or solieum-rs. Use standard Solana client libraries against the node's endpoint. See Solieum Programme Kit.
  • No hosted services. There is no public explorer, no bridge explorer, no hosted status page, no learning platform and no faucet. Earlier versions linked four of them at subdomains of solieum.com (explorer., bridge-explorer., status. and learn.), and none of those names resolves; neither do bridge. and faucet.. The block explorer ships inside the node and is served only from the operator's machine, where the node runs. A generator for a status page exists in the protocol repository and writes a snapshot of the fleet from the nodes' own readings; where that page will be hosted is not decided.
  • No API documentation site, but an API reference on the site. The node's JSON-RPC is documented at solieum.com/api. The api-docs.solieum.com that earlier versions linked still does not resolve, and there is no public endpoint to use the reference against yet. The node's Solana-shaped surface, /solana, answers on the operator's machine only: the gateway a public deployment would use forwards the node's own path, /, and nothing else.
  • No deployed bridge application yet. The bridge application is built for walletbridge.org and is not deployed there. That address serves an earlier page, last modified in May 2025, with no wallet or network code behind its Connect Wallet button, and its explorer page is a table of fixed sample rows rather than a bridge explorer.
  • One address on a network of value. Solieum's native coin, SEU, was issued on Solana mainnet on 19 November 2026 at 4s7fRw889RNEGbzBQoWpZmw8sHjyAEwiY9idHjXNw666 — see Fees, Economics and the Native Coin. No airdrop, and no public sale until the planned presale is announced on the official site — rights to the coin are sold privately until then. Any other address claiming to be a Solieum coin or token is a scam.
  • No Discord; Medium and YouTube as found. All three were previously listed. There is no Discord. A Medium profile, medium.com/@solieum, with three posts from June and July 2025, and a YouTube channel, youtube.com/@Solieum, with no videos, resolve under the Solieum name. The channels this paper answers on are the two above.
  • No research papers, industry reports or books. Earlier versions listed titles such as a security analysis of the architecture and a benchmark comparison against competing Layer 2 solutions. None of them were ever written, and the links pointed back at this page.

If something here should exist and does not, or exists and is not listed, tell us on one of the two official channels. We would rather fix the entry than leave it wrong.