The Network Map — click a node, double-click to open its guide
Qalnet is a private, Apache-2.0 fork of the IOTA node (Sui-lineage, Move objects, Starfish-class DAG-BFT consensus) run across qalarc's own fleet. Click any node for a plain-English summary; double-click it — or use the green link that appears below — to jump to the full guide page.
Follow a Payment — animated
Follow one Australian dollar: it enters the segregated Reserve, issues one backed Qal, pays for compute, and unused value goes home. Press play, or step manually.
Why this can't break
Every backed Qal in existence was issued only after the Oracle Committee confirmed a matching AU$1 landed in the segregated client-money account — and the sellable supply was pre-endowed in the genesis issuer wallet, so a sale never creates credit. The chain is the liability ledger — anyone can compute the invariant:
reserve_aud_cents ≥ b_qals_supply × 100 (every block)
The two token classes
| backed Qals | growth Qals | |
|---|---|---|
| Born | AU$1 deposited | growth allocations |
| Backing | AU$1, in Reserve | none (FloorVault floor) |
| Redeem | AU$1.00 of services value anytime | bought at ~AU$1.20 |
| When used | used up + revenue | used up (supply shrinks) |
Hire a Computer — click the states
Hiring a computer on Qalnet is tracked like a parcel: the payment is escrowed up front, the work is checked, and settlement is automatic. Click any state to see the rules, who can act, and what the chain enforces.
Compute receipt NFT
Every SETTLED job mints a ComputeReceipt: model hash, input anchors, GPU-seconds, cost, provider DID. It doubles as provenance for AI outputs (C2PA-style, on-chain) and as collateral in the Qalx receivables vault.
Vouchers — compute as a gift
ComputeVoucher objects are transferable GPU-hour credits. Move's linear types make double-redemption impossible — the compiler enforces it, not a promise.
Spending & Daily Caps — simulate an account
Every app user, device and AI agent gets an account — the owner can set spend limits (optional, uncapped by default). Simulate one: drag the sliders and watch a month of metered usage settle.
Holds (pre-authorisations) auto-expire — no orphaned holds, ever. Caps are enforced by the Move VM: an agent cannot overspend even if compromised.
The AU$1 Backing — 36-month simulator
The honest engine room: backed Qals are born 1:1 from deposits and are used up as you spend (left chart — the invariant always holds). Growth Qals carry no claim, but a revenue-funded FloorVault raises their floor (right chart — coverage is honest and slow; parity needs scale). Drag the assumptions.
No simulator output is a promise. Growth-Qal coverage typically stays under 0.01 Qals for years — the wiki dashboard publishes the real number monthly.
Keeping It Safe
The stack that makes Qals boringly safe: hard rules in the code, multisig humans, time delays, and public proof. Toggle any control to see what fails without it.
Proof-of-Reserves (live example)
| Item | Value | Source |
|---|---|---|
| backed Qals outstanding (on-chain) | — | Qalnet RPC (public) |
| Liabilities (AU$) | — | supply × AU$1 |
| Reserve (segregated AUD) | — | Oracle Committee attestation |
| Coverage | — | reserve ÷ liabilities |
| Last attestation | — | signed statement, on-chain |
Values update from Module 5's month-36 simulation — try it.
Who can do what (privilege map)
| Role | Power | Check |
|---|---|---|
| Oracle Committee | attest reserves, trigger investigate | 3-of-5 multisig |
| Treasury Council | fees/floor/LTV params | 2-of-3 + 48h timelock |
| Emergency pause | halt issuance/redemption/pools | multisig, 72h auto-expire |
| Validators (Fleet) | order transactions | Starfish BFT, 3f+1 |
| Move VM | everything else | linear types — code can't cheat |