Your own Arc, built around you
Most people and applications share one public chain with everyone else. They pay the same fees, compete for the same block space and follow the same rules as everyone else on it. That is fine for many things. Some things deserve a space of their own, though: a household ledger, an application's own token, or a record of exactly what an AI assistant was allowed to do.
On Dijets, that space is called an Arc. Arc Studio is where you learn what Arcs are, design one around a purpose, and launch it.
What is an Arc?
An Arc is a chain of your own on the Dijets network:
- Its own chain. An Arc is a dedicated chain running the Dijets asset VM, with its own assets and its own transaction history.
- Its own validators. An Arc is secured by a committee you choose: at least three of the network's current primary validators, each with a weight you set.
- Its own owner. An Arc is controlled by an owner you define, either a single address or a set of addresses with a threshold, such as "2 of 3".
- Registered on Dijets. Every Arc is registered on the Method Chain. Its identity is the chain ID that the network assigns when it is created, so nobody can invent or copy that identity.
Your activity on an Arc stays on that Arc, so it never competes with traffic on the rest of the network.
What Arc Studio does
Arc Studio has four parts.
Discover
Discover explains Arcs in plain language: what they are, why you might want one, and what you can do with one. It also shows which Arcs are registered on the network right now.
Applications
Applications shows what an Arc is for through five working demonstrations, each with a template you can start from:
| Application | What it shows |
|---|---|
| Personal finance assistant | A ledger of your own and an assistant that prepares payments, within spending limits it cannot exceed |
| Private AI workspace | A verifiable record of what an AI assistant did, with SHA-256 commitments instead of your content |
| Everyday transaction assistant | Bills and everyday payments, prepared for you and approved under rules you set |
| Agent-to-agent coordination | Software agents that settle with each other on a shared ledger |
| Dedicated application environments | An application's own assets and activity, separate from everything else |
The demonstrations run in your browser on sample data and a simulated clock, and each is clearly labelled. The policy checks and the cryptographic commitments are real code. Nothing is signed or sent. You can type instructions to the assistants, or speak them using your browser's own speech recognition. Arc Studio never records or stores your voice. Voice and text can only prepare an action: signing, approving and switching rules on always stay buttons that you press.
Studio
The Studio walks you through configuring an Arc step by step:
- Purpose. What the Arc is for and which capabilities it needs. This is kept in your browser and never written to the chain.
- Name. A label for your Arc.
- Assets. The tokens the Arc starts with: name, symbol, decimal places, and a fixed or mintable supply.
- Owner. The address or addresses that control the Arc, and how many must sign.
- Committee. The validators that will run it, chosen from the network's live validator set, and their weights.
- Validation window. How long the committee is engaged, within the network's own limits.
- Review. A full summary of the Arc, its costs and every step needed to launch it.
The Studio checks each choice against the same rules the network applies, so problems show up while you configure, not after you launch.
How Arcs work and My Arcs
How Arcs work explains the life of an Arc in detail. My Arcs follows the Arcs you have launched. You can see each one's lifecycle (pending, initialising, active, degraded, stopping, stopped or failed), its committee, its events and its recent history, all read live from the network.
How launching works
Arc Studio never asks for your private key, and it never sends one anywhere.
When your configuration is ready, Arc Studio exports it as an Arc specification, a small file describing exactly what to create. You then launch it with arcctl, the Dijets command-line tool, using a key file on your own machine. arcctl re-checks your committee against the live validator set, then:
- creates the Arc's permissioned network;
- adds each committee member;
- waits for the committee to be ready;
- creates the Arc's chain.
As soon as the chain exists, Arc Studio picks up its chain ID and follows it live. Each committee member then adds the Arc to the networks their node tracks, and the Arc becomes active.
How it benefits you
Your own space
An Arc's activity and fees belong to that Arc. A busy period elsewhere on the network does not slow it down, and its history is not mixed in with everyone else's.
Your own rules
You decide who controls the Arc, who validates it and which assets it holds. Templates give you a sensible starting point for common purposes, and the Custom Arc template gives you a blank one.
Assistants that work for you, not instead of you
Arc Studio's applications are built around one idea: an assistant can prepare an action, but your rules and your signature decide what happens. Spending limits are checked before anything is signed, and the key never belongs to the assistant.
Clear from the start
Every screen states what the network supports today and what it does not, so you never configure something that cannot be launched.
What sets it apart
Real data, clearly separated from demonstrations
Everything Arc Studio shows about the network, including registered Arcs, their lifecycle, validators, fees and limits, is read live from the network. Everything that is a demonstration is labelled as one. Arc Studio never shows a launch, a transaction or a result that did not happen.
Keys stay with you
Configuration happens in the browser, and signing happens on your machine with a tool you run. There is no hosted service holding your key, and Arc Studio has no way to act on your behalf.
The same rules as the network
The Studio checks names, assets, owners, committees and validation windows against the network's own rules. arcctl applies those rules again before it signs, and the validators apply them a final time.
Honest about today's limits
Arcs are new, and Arc Studio says plainly what they cannot do yet:
- Arcs run the Dijets asset VM. EVM Arcs are not yet supported.
- Arcs are public. Anyone can read their balances and transactions, so private data does not belong on an Arc.
- Arcs use a permissioned committee. Other security models are reserved for later.
- Assets cannot yet move directly between an Arc and the main Dijets chains.
- Committee members cannot yet be added or removed after launch.
- Names from the Dijets Name Registry point to Value Chain addresses, not to Arcs.
What's next
We are working on launching an Arc directly from a browser wallet instead of the command line. Next come managing an Arc's committee after launch, and richer shared descriptions and icons for Arcs.
Links
- Arc Studio: discover, configure and follow Arcs.
- How Arcs work: the full explanation.
- Applications: five demonstrations and their templates.
- Dijets Names: a readable name for your Dijets address.
- Nodebook: the Dijets browser wallet.