Welcome to Joltzu
Joltzu is a safety-first EVM Layer 1 designed around one shared ledger, native account policies and bounded financial authority. Solidity contracts can compose native markets and payments in the same transaction.
The C++ reference node runs local validator networks with certified finality, Ethereum JSON-RPC, WebSocket subscriptions and durable EVM/native state. The public network endpoints in this documentation are proposed; their inclusion does not announce a launch.
Choose your path
| I want to… | Start here |
|---|---|
| Understand how users are protected | Safety first, then safety controls |
| Understand the protocol | Architecture, then consensus |
| Try Joltzu as a user | Use Joltzu and connect a wallet |
| Build with Solidity | Developer quickstart |
| Move an existing EVM application | Porting from other EVM chains |
| Integrate an app or exchange | Ethereum RPC and event indexing |
| Run infrastructure | Run a node |
What makes the design different?
Safety comes first. User protection lives in the protocol, not only in wallets. Validators check account policy, fund energy, outflow budgets and locks on every spending path, whichever wallet submits the transaction. Incident response restricts the funds involved; the design never pauses the network or rewrites finalized history. Read Safety first.
Groups divide consensus work, while state stays shared. Validator groups certify batches for address ranges. Global consensus agrees on one order, and every validator executes it. Applications do not cross execution shards to interact.
Accounts have native policy. Key-derived accounts start with their own key's implicit authority. Owners can enable multisig, passkeys, recovery and bounded grants at the same address.
Services settle together. Native orders, AMM liquidity, lending and funded payments use the common ledger and transaction journal. A failed transaction rolls back its execution effects.
Authority has limits. Grants have budgets and expiry; funded commitments set funds aside; issuer controls apply to their own assets. See the safety model.
Reading the docs
“Implemented” describes the current reference-node profile. “Development default” describes a value that can change before launch. “Proposed” describes a design or deployment that is not established by this documentation. Implementation status explains the important boundaries.