For AI agents
A blockchain built for autonomous agents, not around them.
Agents hold budgets, pay for services, and execute plans without a human approving each step. Satsuma is a sovereign, Ethereum-compatible Layer-1 designed from the ground up as their settlement and coordination layer.
Why agents need a different chain
Public blockchains were designed for anonymous human participants kept honest by economic incentives. Several of their defining properties are actively hostile to autonomous software:
| Property | Public L1 / L2 | What an agent needs |
|---|---|---|
| Participants | Pseudonymous, permissionless | Known, vetted counterparties |
| Inclusion | Open mempool; front-running and MEV | No anonymous adversaries observing intent |
| Fees | Auction-driven; volatile by orders of magnitude | Stable and predictable for budget-bound planning |
| Finality | Probabilistic, or minutes to settle | Deterministic, in seconds |
| Operations | Best-effort; no accountable party | An operator with a name and an obligation |
An agent cannot renegotiate its budget when gas spikes 40×. It cannot reason about a transaction that is "probably final." It should not have to defend its every intention against front-running bots in a public mempool.
What Satsuma provides instead
- A stable clock. Blocks arrive every 2 seconds on a fixed cadence — no leader elections, no mining. Agents can plan retries and timeouts against a schedule that holds under load.
- Deterministic finality in seconds. A BFT finality protocol makes blocks irreversible within roughly three blocks (~6 s). A finalized transaction can be acted on immediately and unconditionally — no confirmation counting.
- Fees an agent can budget for. Instead of a gas auction, a smooth multiplier targets 25% average block utilization. The fee an agent estimates is, in ordinary operation, the fee it pays.
- No front-running. Every account that can write is known and admitted deliberately. There is no anonymous mempool full of adversaries watching your intent.
- Reads that keep up with software. The read path sustains 14,300 queries per second at 2 ms median latency on a single commodity server — and reads are open to anyone, no API key required.
- An accountable operator. Satsuma Labs runs the network end to end and answers for it — with every administrative action recorded on a publicly readable ledger.
Your existing stack already works
Satsuma is fully Ethereum-compatible. Solidity contracts deploy unmodified, and the network
speaks standard Ethereum JSON-RPC — eth_sendRawTransaction, eth_call,
eth_getLogs, gas estimation, and the rest.
| Parameter | Value |
|---|---|
| RPC endpoint (reads open) | https://rpc.satsuma.one/eth |
| Chain ID (EIP-155) | 555555555 |
| Native token | SUMA · 18 decimals |
| Block time | 2 seconds, fixed cadence |
| Finality | Deterministic BFT · ~6 s |
MetaMask connects as a custom network; Hardhat and Foundry deploy and test against Satsuma exactly as they would against any Ethereum endpoint. Reading the chain requires no account: query state, simulate calls, and watch events straight away. Writing requires admission to the on-chain allowlist, managed by Satsuma Labs.
Satsuma changes who may transact and how the network is run — not how contracts are written. See the architecture for how the protocol enforces this, or the FAQ for common questions.