Stellar Stellar is a payments-focused Layer 1 blockchain running the Stellar Consensus Protocol, with a native JSON-RPC API via stellar-rpc, ~5-second ledger close, and no WebSocket support.
Stellar is a Layer 1 blockchain running stellar-rpc, a JSON-RPC 2.0 API over HTTPS that bundles stellar-core as a captive process. There is no WebSocket support on this client. SCP reaches ledger close in roughly 5 seconds, and gas is paid in XLM.
Stellar is built for payments-native applications — cross-border settlement, remittances, tokenized assets, and stablecoin rails — with Soroban enabling smart-contract logic such as escrows, DeFi, and RWAs alongside native payment primitives.
| Consensus | Stellar Consensus Protocol (SCP) — a federated Byzantine agreement model where each validator selects its own quorum slices from the shared validator set, rather than a fixed global validator list. Ledgers close roughly every 5 seconds. |
| Public / Private / Permissioned | Public and permissionless for users and developers. Validator participation is open; each node operator chooses its own trusted quorum. |
| Smart contracts | Soroban — Stellar's Rust/WASM smart contract platform — alongside native transaction operations (payments, offers, path payments, AMMs) that don't require a contract at all. |
| Smart contract language(s) supported | Rust, compiled to WASM, via Soroban. Most payment and DEX activity uses native transaction types instead of contracts. |
| Transaction privacy | Not by default. Stellar is a public ledger where transactions, balances, and account state are visible onchain. |
| Transaction visibility | Public by default. Transactions and ledger objects are queryable through public RPC endpoints and the stellar.expert explorer. |
| Transaction ordering | Validators agree on a transaction set through SCP at each ledger close (~5 seconds). There is no priority-fee auction in the Ethereum sense — fees are a flat network minimum that can rise only under sustained congestion. |