PUBLIC CHAIN · OPEN
The chain underneath everything.
Antelope core consensus. Embedded EVM. Identity, keys and payments — open, auditable, permissionless. Same Solidity, same wallets.
space-os · The Chain
The chain underneath everything.
A public chain — Antelope consensus, embedded EVM, one token. It secures identity, keys and payments. Every product on the site sits on top of it.
Network
SPACE OS EVM
Chain ID
800000
Block time
~0.5s
Gas price
150 gwei (fixed)
Tx type
Legacy (type 0)
Native token
SPACE · 18 decimals
01 · Overview
A public chain. Not a product.
space-os is the chain. The end-user products — Web App, Desktop App, Mobile App, Inference API — sit on top of it. The chain itself is open: third-party clients can interoperate without any of our hosted services, and every message format is documented in the Open Node Protocol.
- Public, permissionless, auditable
- No vendor lock-in — open node spec
- Drives identity, keys and payments — not agent memory
- Single shared identity across every surface
02 · Consensus
Spring / Antelope core
The native chain runs Spring/Antelope — a deterministic BFT consensus producing ~0.5s blocks. An append-only signed event log. Native accounts hold SPACE for staking and chain ops. The EVM runs deterministically inside this consensus — no separate validator set, no light-client bridge.
- ~0.5s block time, deterministic execution
- Signed-op event log, append-only
- Native accounts for staking and chain ops
- EVM consensus is the same set — no bridge required
03 · EVM
Embedded Silkworm. Same Solidity.
A full EVM (Silkworm) compiled to WASM and executed inside Antelope. Standard Solidity, standard wallets — MetaMask, ethers, viem, Foundry all work unchanged. Chain ID 800000. Legacy (type 0) transactions only — EIP-1559 is not supported.
- Silkworm EVM compiled to WASM
- Chain ID 800000 · ~0.5s blocks
- 150 gwei flat (no fee market)
- Compatible with MetaMask, ethers, viem, Foundry
04 · SPACE token
One token. Gas, staking, payments.
SPACE is the native ERC-20 token (18 decimals) on the space-os EVM. It pays for gas, stakes for network roles, settles inference payments and provider payouts, and funds the treasury. No separate utility tokens — one asset, one ledger.
- ERC-20, 18 decimals, native to the EVM
- Pays for gas, inference, and provider payouts
- Stake to qualify for provider tier multipliers (Free / Basic / Pro / Enterprise)
- Used for treasury, governance and grants
05 · Wallets
Three wallets, one identity.
Every authenticated user has three keys with distinct roles. The connected wallet is your existing external EVM wallet. The proxy wallet is a server-managed EVM wallet on the space-os chain — the network operates it on your behalf. The native account is a Spring/Antelope account for chain ops and staking.
- Connected — your external EVM (MetaMask, Rainbow, …)
- Proxy — server-managed EVM on SPACE OS, holds tokens
- Native — Spring/Antelope account for staking + chain ops
- Proxy wallet abstracted as one balance across paired devices
06 · Keys (KIS)
Custody in a separate trust domain.
KIS — the Key Identity Service — holds proxy and native keys in a domain separated from the rest of the network. The chain settles, KIS signs. This means a compromise of any one network service can't move user funds without crossing the trust boundary.
- Keys never co-located with application services
- Per-device key registry on chain
- Visa Stamps — explicit per-app attestation grants
- Self-custody on connected wallets remains yours
07 · Staking
Stake to run the network.
Native accounts stake SPACE to take on network roles — GPU providers, CPU nodes, relays. Three tiers (Open, Staked, Pro) with progressively higher stake requirements and progressively richer routing. Slashing on misbehaviour. Earnings paid in SPACE.
- Three tiers — Open · Staked · Pro
- GPU, CPU, network and relay node roles
- Slashing on misbehaviour, rewards in SPACE
- Capability manifests gate which work you can take
08 · Treasury
Protocol-owned funds.
A protocol-owned treasury denominated in SPACE, with on-chain accounting. Funds grants, ecosystem incentives, security work, and operational reserves. Spends are auditable from the explorer.
- On-chain accounting, fully auditable
- Funds grants, incentives, security, operations
- No mint authority outside the protocol
- Public spend history
09 · Open Node Protocol
The network is a spec.
Every message format, capability manifest, tier ladder, capability scope, presence state, WebSocket grammar and peer-RPC call is documented in NODE_PROTOCOL.md. Third-party clients interoperate without any of our hosted services — including third-party explorers, wallets and node implementations.
- NODE_PROTOCOL.md — the canonical spec
- Capability manifests for every node role
- WebSocket grammar + peer-RPC calls documented
- No reliance on our hosted infrastructure
10 · Build on it
EVM tooling. Same as everywhere else.
Solidity, Foundry, Hardhat, ethers, viem — all work unchanged. The block explorer is open. The RPC is open. The white paper covers consensus and protocol; the developer docs cover the API surface and integration patterns.
- RPC — testnet.evm.spaceos.com
- Explorer — testnet.evm-explorer.spaceos.com
- Faucet for testnet SPACE on /developers
- Examples in JavaScript, Python, Go
Open infrastructure
Build on it. Stake on it. Audit it.
The spec is open. The code is open. The explorer is open. Pick a starting point.