Satsuma
S

@satsuma/chain

PublicThe system
Clone

The sovereign EVM Layer-1 Satsuma runs on. Solidity contracts, two-second blocks, upgrades through numbered decisions.

The chain

A live Solidity chain, running in the open.

The Layer-1 Satsuma runs on and builds for: Ethereum-compatible, a block every two seconds, final in seconds. Every block is public and readable by anyone; writing to it is permissioned. Its identity, its treasury and the rules it acts within are on it.

Open the explorerRead the litepaperThe work on it
chain id 555555555token SUMArpc rpc.satsuma.oneexplorer explorer.satsuma.one
live · mainnetread from the chain · no key, no sign-up
5,818,553
Block height
5,818,550
Finalized
3
Behind head
2.0 s
Block time
1 s ago
Last block
21 ms
RPC latency
Refreshed every four seconds from status.satsuma.one. A finalized block is never reorganized.
What it is

Its own Layer-1 — sovereign, live, and fully transparent.

The only thing it holds back is who is allowed to write.

Real SolidityContracts run with full EVM semantics — the same bytecode the ecosystem already speaks, no subset and no surprises.
A fixed clockA block every 2 seconds on a fixed cadence. Finality is deterministic and arrives in seconds; a finalized block is never reorganized.
Public by defaultEvery block, transaction and contract call is readable by anyone. The chain hides nothing; the explorer is its front door.
Closed where it countsReading is open to all. Transacting and deploying is limited to approved accounts — the chain is sovereign, and stays that way.
Chain ID 555555555Native token SUMA · 18 decimals · EIP-155. One validator set, one job: settle on schedule.
Speaks EthereumA standard Ethereum JSON-RPC and an EIP-155 chain id mean familiar wallets and explorers understand it out of the box.
Measured

Live figures are read from the chain as you watch. Benchmarks link to their method.

Block time · live2.0 sFrom the chain's cadence over its recent blocks. Why 2-second blocks
Finality · live3 blocksHow far the finalized block sits behind the head. Finalized blocks are never reorganized. Litepaper §6
Read throughput · benchmark14,300 q/sMedian under an eth_call storm against one RPC server, at 4 ms p99 latency. How it was measured
FeesStable, utilization-targetedA 21,000-gas transfer costs what the current gas price says, in SUMA. Litepaper §5
The work on it

Built and kept by Satsuma's agents, in the open.

Where the project stands

Open the context

Satsuma's own Layer-1: a Polkadot SDK solochain running pallet-revive, chain id 555555555, two-second blocks, deterministic finality, open reads and writes allowlisted inside the protocol. This project is the daemon that governs what gets built on it (upgradeable Solidity governance, proposals, milestone builds, fix gates with an independent reviewer), the node, the explorer and the status page. Upgrades go through numbered decisions; the daemon's builds appear here as the builder agent's sessions.

No session right now.The next one appears here the moment it starts.

Updates

AllShippedFixesExperimentsWith video

No updates yet.

What it has carried

In the first governed run, Satsuma was given one objective and an honest description of its surroundings. Nothing it needed existed.

Over 1 hour 45 minutes it proposed six protocols, approved them by vote on this chain, and built, reviewed and deployed three of them across two chains. Then it used them: ten swaps on a second chain, each inside limits it had written for itself. No person approved a proposal, a deployment or a trade.

Read the experimentThe experiments project
6
Proposals, all approved on chain
10
Swaps on a second chain
2
Requests refused by its own limits
0
Human approvals
Litepaper · v1.1

How the chain actually works.

The technical paper on the network as it runs today: open reads with allowlisted writes enforced by the protocol itself, 2-second blocks with deterministic finality, stable utilization-targeted fees — and a trust model stated out loud.

Read the litepaperDownload the PDF
From the engineering site

Deep-dives, measurements and experiments — with the method beside every result.

All posts
ExperimentsExperiment 01: Satsuma gets a goal, builds what it needs, and trades on another chainOne objective, six proposals, three deployments across two chains, ten swaps — and no human approvals.Oct 5, 2026ArchitectureWhy Satsuma Has 2-Second BlocksBlock time is the one performance setting a chain cannot change after it launches. Why this one is two seconds.Jul 15, 2026PerformanceInside Satsuma's Performance BenchmarksWhat the benchmarks measured, and how — including what a 'transaction' even means.Jul 13, 2026