Skip to main content

Implementation status

Status as of 29 October 2026. This page describes the reference implementation and current development tools. Public deployment and production readiness are listed separately.

FeatureReference-node statusBoundary
EVM executionImplementedPinned evmone/Osaka profile, with explicit Joltzu additions
Ethereum transactions and RPCImplementedLegacy, access-list and dynamic-fee envelopes; 1,000,000 admission gas cap; differences
Group/global consensusImplemented development profileSlot clock and clock-health rules implemented; weighted slot draws and production randomness remain open
Local devnetAvailableFour validators and an observer by default; valueless development keys
Native accounts, passkeys, recovery, grantsImplementedExplicit account policy and bounded authorization profiles
Fund energy and outflow budgetsImplementedEnergy is enabled per asset in genesis; launch durations are undecided
Spot, AMM, quotes and lendingImplemented development profilesListed native assets, configured markets and service-specific limits
Funded vouchers, escrows, conditions, bequestsImplemented development profilesEach obligation has its own funding and settlement terms
Stake, slashing, SAFU, vesting and LP farmImplemented development profilesFunding and parameters are not a published token allocation or insurance promise
State/receipt/log proofs and checkpointsImplementedTrusted finality and retention floors still matter
Public RPC gatewayImplemented development profileTLS, credentials and method allowlists; public access policy unannounced
Testnet/mainnet public hostsProposed in these docsDNS, certificates, service availability and launch unverified
Bridges, perpetuals and broader lending marketsRemaining/proposed scopeNo documented production route
World and presaleRunnable separate frontend/contractsLocal/demo screenshots; provisional date; no public sale contract verified
Browser extensionSimulator grants/payments, passkeys and native readsLive signing, executable swaps and network recovery pending
JSNVRF, scheduled callbacks, subscriptions and SigNet reference runtimeNo public service/addresses verified; application hosting and broader triggers pending
AI Agent Network and StudioSeparate reference projectsLocal worker/coordinator and visual editor; no production service certification
ExplorerSeparate frontend / Blockscout backendDefaults to a local Joltzu devnet; no public deployment established
Envio and The GraphPlanned Joltzu-hosted query APIsTestnet/mainnet URLs TBD; availability and indexed schemas unconfirmed
Identity/private records/confidential paymentsParked node scopeNo implementation or integration guide here
External security auditNot completedNo audit, bug bounty or penetration test is claimed for any component; see Safety first

Targets and unresolved work​

One million TPS and sub-second finality are design targets, not measured public-network performance. The 500 ms slot and 512-slot epoch are not promised network settings. The node's open backlog includes production DKG/randomness, weighted proposer draws, slashing-protected key custody, multi-host calibration and remote proof-availability work.

The network directory lists development chain IDs and proposed public hosts. Canonical network identities and live endpoints require launch confirmation.

The ecosystem directory links the applications, screenshots and service guides. Tokenomics explains the presale supply model. No JOLT allocation or final genesis policy is confirmed.