Skip to main content

Studio, explorer and AI services

Studio and visual scripting​

Joltzu Studio is a visual development environment. Build function graphs, generate editable Solidity 0.8.37 for Osaka, compile in the browser and export artifacts. Contract, App and Data modes cover the graphs, generated frontend, Envio indexer and REST API. Export produces a project archive rather than locking development to a hosted editor.

Its optional AI assistant can help design and revise a project. The model provider is separate from the chain; generated code still needs privilege review, invariants and independent testing. Publish neither API credentials nor private project input without the user's authorization. JSN hosting of reviewed Studio releases is planned; the current JSN runtime does not provide application hosting.

AI Agent Network​

The AI Agent Network is a C++26 reference implementation with a durable coordinator, independent workers, signing tools, SQLite persistence, a native SDK and a local demo. Requests bind inputs, execution profiles, signed votes, budgets, dispute periods and callback state. It implements that service's state machine rather than the rest of the L1. In the protocol design, AI workers run as a JSN service, while request records, escrow and any holds would sit on the protocol side. Agents could not transfer assets, edit code or stop block processing; AI-initiated holds are proposed to start in shadow mode.

The bundled screening detector is explicitly a lexical rule baseline, not an LLM or a security audit. Its local funded ledger and signed replay journal do not establish a production on-chain deployment. Agreement between workers also does not establish factual truth.

The wallet's local documentation assistant is another component: it explains permissions and prepares requests, using the ordinary approval queue. It is not this network's worker runtime.

JSN risk proposals and council authority​

The JSN risk-proposal service accepts structured evidence and temporary-budget proposals, with an optional external inference endpoint. It validates model output and stores the exact action/digest for review. Execution requires a council-scoped request and signatures from more than two-thirds of the configured council roster; a bearer token or agent result cannot provide those signatures.

That service's execution path covers the native applyBudget action at 0x1005. It cannot use that path to mint, confiscate funds, freeze every account or pause the network. The relayer key pays transaction fees rather than owning council authority. See native safety controls.

Explorer​

Joltzu Explorer has a Next.js frontend and a Blockscout v10.2.6 backend. Its current frontend defaults to a local Joltzu devnet, chain 31337, JOLT. It reads blocks, transactions and balances from the devnet's observer RPC.

The explorer shows the fee sponsor of native transactions and lists native JOLT transfers, including those made inside contracts. It explains a failed call by re-running it against the parent block. Joltzu nodes have no tracing methods, so internal calls are not indexed.

RPC supports block/transaction reads; indexed address history, token holders and verified contracts need the configured indexer. The frontend does not sign transactions. A proposed Joltzu explorer hostname in the network directory is separate from the frontend's configured chain.

Hosted indexing APIs​

Joltzu-hosted Envio HyperIndex and The Graph endpoints are planned for testnet and mainnet, with all URLs TBD. Use the indexing endpoint guide for the directory and query template. These services expose indexed application data; they are separate from the explorer and transaction-submission RPC.

Other release scope​

Bridges, game-engine plugins, private identity/records, bank on/off-ramps and confidential payments are planned or research features. Their deployment, provider partnerships and integration details remain unconfirmed. Perpetual futures require their own margin, funding, liquidation and loss rules. These remain explicit release/research work, while the native utility guide covers implemented aliases, hooks and oracle observations.