CradleScript · Blockchain Life 2026 · Dubai · 1–2 December
Write a contract once.
Ship it to every major chain.
The problem
Every chain wants its own language. Every rewrite is a new bug.
The same token, vault or staking logic written again for each runtime, by different people.
Each port is new code with its own reentrancy, access-control and arithmetic mistakes.
A fix on one chain has to be remembered, re-implemented and re-reviewed on the other five.
The answer
One chain-blind source. Idiomatic output on each chain.
CRADLE compiles CradleScript, Rust or Solidity into one intermediate representation, checks it once, costs it per chain, then lowers it to native code for every target.
A focused language with its own keywords: blueprint, store, action, funded, ensure, dispatch.
Security analysis runs on the shared representation, so one rule protects every target.
Real PDAs and SPL CPI on Solana, real mappings on EVM, native Coin on Move. Not lowest common denominator.
The pipeline
Security sits on the build's critical path
Six targets
Native on each chain
A real example
A tip jar, written once
blueprint TipJar {
store {
owner: address protected = sender;
collected: amount = 0;
}
funded action tip() {
collected = checked_add(collected, received);
}
action withdraw(amount: amount) {
ensure(sender == owner, NotOwner);
ensure(collected >= amount, Insufficient);
collected = checked_sub(collected, amount);
dispatch(sender, amount);
}
read action total() -> amount { give collected; }
}
Proven on-chain, not just compiled
Every capability has a conformance suite
Every suite runs in CI on every push, against a real Solana validator and an EVM node.
| CradleScript capability | EVM | Solana | Suite |
|---|---|---|---|
| State, roles, guards, records, time | Storage, modifiers | Account data, Borsh, Clock | counter 7/7 |
| Per-key accounts | mapping(K ⇒ Struct) | One PDA per key | pda_bank 7/7 |
| Native value in and out | Checked transfer | System-transfer CPI | tipjar 7/7 |
| Fungible-token transfer | IERC20 transfer | SPL Token CPI | token_vault 6/6 |
| Bounded loops | for loop | for loop | batch 3/3 |
| All of the above, one program | — | — | stake_pro 7/7 |
By the numbers
Small surface, wide reach
EVM deployment
One canonical address across every EVM chain
Deploy to Ethereum, BNB Chain, Polygon, Arbitrum or Base and get the same contract address on each.
Know the address ahead of time, so docs, frontends and partners can be ready on launch day.
One address to configure, not a table of addresses per network.
Builds can be verified by anyone, byte for byte.
Cradle Studio
A web IDE that also writes the contract for you
Pick a template, fill a form. Studio writes an OpenZeppelin-based contract, scans it, deploys it and exports a dApp page.
Describe the contract in plain English. It generates, compiles and fixes its own errors.
EVM or Solana, switchable any time, with a clear pass or fail security gate.
Nothing leaves 127.0.0.1 until you deploy.
Powered by Solieum
The native language of the Solieum Layer 2
The Solana program CRADLE emits is exactly what Solieum executes. Write once in CradleScript, run on Solieum, and ship the same source to every other major chain.
Optimistic rollup that settles to Solana. Same SVM, so CRADLE output runs unchanged.
Its Trust Chain anchors AI decisions on Solieum. Contracts like these are how proofs get recorded.
Start in Studio, prove it on-chain, deploy to the chains your users are on.
Solve · Cradle
Write it once. We'll show you the six outputs.
Scan for the Solve brochure
solieum.com/brochures/solve