Applications and partners

Solieum is pre-mainnet, so this page lists what is real and in use — the programs it settles with, the node, the tools that already work, and integrations that are agreed and in progress — rather than a logo wall. Everything here is Solieum's own. It grows as things go live, and nothing appears before it is real.

Nothing confirmed to announce in this category yet. We would rather show an empty list than a speculative one.

• Solieum settlement programs

  Live

  Settlement, data availability, forced inclusion, the bridge portal and the dispute game — the five programs that carry settlement, deployed on Solana devnet three times: the alpha chain (2026-09-02, now frozen), the beta chain (2026-09-05), whose settlement program carries the 48-hour window and takes the dispute game's verdicts, and the gamma chain that succeeded it (2026-09-11). Every root and every batch is a transaction against them, and the resources page links each one.

• Solieum node

  Live

  The node that orders, executes, publishes and settles — one binary with the RPC and the explorer inside it. It runs the beta and gamma devnet chains today, replaying every block from published data on restart with each state root re-verified. Since 2026-09-10 its own measurements survive that restart too. When a transaction was admitted, how long its receipt took, when it executed and when its root committed are not facts about the chain and cannot be rebuilt from it — a block's timestamp is whole seconds — so the node writes them down beside the chain data and restores them before replay. They are kept strictly apart from consensus: never read while a block is being applied, never touching a state root, and a missing or truncated file costs measurements rather than stopping the node. A public endpoint arrives with the testnet.

• Sequencer bond and slashing

  Live

  The receipt-signing key posts a bond on Solana; two validly signed receipts for the same batch and position with different order hashes take it — a share to whoever reports them, the rest burned. Deployed on devnet, the devnet sequencer bonded, and the slash exercised ON CHAIN against a test bond: 0.1 SOL taken at devnet slot 492324128, 49,985,000 lamports to the reporter and 50,000,000 burned to the incinerator, in transaction 3tAAVMwhLVh2r2dbWZS4ATsEfLiJpa1zNUjjn5c9ZjZ2meSU1AY11cdYfBr1rU5nzqty2yjSMo7UTQrS5nvx8tNu. The beta sequencer's own bond reads unslashed because nobody has equivocated on that key.

• Solieum block explorer

  In progress

  Ships inside the node: blocks, transactions, accounts, settlement rows, the bridge and signed ordering receipts, served from the same process as the RPC. Each transaction also carries its own settlement clocks — admitted, receipted, executed, root committed, finalized — and these now persist across a node restart instead of resetting to nothing. A transaction the node never measured says so and stays blank: nothing is reconstructed for history, and an interval whose end precedes its start is reported as absent rather than as zero. A public instance arrives with the public endpoint.

• Solve

  Live

  Solieum's main framework, from the same team: programs written once in CradleScript, checked for common vulnerabilities when they build, and compiled to a native Solana program as well as five other chains. Works against Solana now.

• Cradle Studio

  Live

  The web IDE for CradleScript, Solidity and Solana programs, live at cradle.solvelang.com.

• Solieum SDKs

  Planned

  JavaScript, bridge and Rust packages. Not yet published; the node speaks a wallet's own wire format, so the Solana client libraries already work for sending.

• Wallet compatibility

  In progress

  Built into the node: it accepts a wallet's own transaction format, verifies every signature, and answers the blockhash and status calls wallets make, so no Solieum-specific wallet build is needed. Named wallet support is confirmed with the public testnet rather than promised now.

• Solieum bridge

  In progress

  Deposits to a program-owned vault; withdrawals proven against final roots with no signer set. Built and exercised in the harness; deployed and initialized on all three devnet chains; on the beta chain the first deposit was credited on the L2 in the next block, the first withdrawal was proven against a final root and paid by the vault after the air gap (2026-09-07), and the air-gap guardian is a key separate from the operator's. Token deposits are not credited yet. On the gamma chain that succeeded beta the portal was initialized on 2026-09-11 with its own guardian key, and its first deposit was credited on the L2 in block 2; no withdrawal has been made there yet.