QALS
HomeHubCompareUse casesAsk AIQALS
HomeHubCompareUse casesAsk AIDate: 2026-09-11 · Method: compare mechanisms, not marketing. Every row is verifiable in this wiki.
| Dimension | QALS (private) | IOTA (public, 2026) | Bitcoin | Solana |
|---|---|---|---|---|
| What it is | qalarc's private value+data ledger (IOTA-fork) + services | public L1, Sui-fork since Rebased | public L1, PoW | public L1, PoS |
| Consensus | Starfish (inherited), 1→4 validators we run | Starfish, public validators | PoW | Tower BFT + Proof of History |
| Finality | sub-second (private committee) | sub-second | ~60 min (6 conf) | ~13s (optimistic ~400ms) |
| Fees | gas sponsored in-app (Qal Pass); zero user friction | low, paid in IOTA | high variance | low, paid in SOL |
| Value unit | credit: AU$1-anchored, no cash-out Phase 1-2 | market-priced token | market-priced | market-priced |
| Supply | 1M max, sales cap 500K in bytecode, zero inflation | cap abolished 2025, ~6%/yr emission | 21M hard cap | inflationary schedule |
| Who can join | qalarc ecosystem (licensed phases open it) | anyone | anyone | anyone |
| Smart contracts | Move (qal_data/credit/reserve live) | Move + EVM layer | script-only | Rust/Anchor + SVM |
| Trust root | qalarc (validator set + reserve) → opens via gates | public validator set | miners | validators (VC-heavy) |
| Data layer | first-class (anchors, receipts, audit trails) | first-class (notarization) | none (OP_RETURN only) | costly on-chain data |
| Best for | companies wanting money+data+compute rails w/o token risk | IoT/trade provenance on a public net | absolute scarcity store | high-throughput public apps |
The honest position: QALS is not competing with public chains — it uses one lineage privately. When external trust is needed, checkpoint-anchoring to public IOTA is the bridge (and the real-IOTA swap gateway is designed, gated on licensing).
| Tailscale | QALS identity layer | |
|---|---|---|
| Identifies | machines on the network (nodekeys) | humans, agents, devices — economically (DIDs, anchored) |
| Answers | "which machine is this?" | "who may spend, how much, provable?" |
| Proof | WireGuard keys, ACLs | ed25519 sigs + anchored docs + caps |
| Revocation | remove from tailnet | DID REVOKED + ledger agent revoked (~2s) |
| Relationship | QALS binds tailscale nodekeys INTO device DIDs — network identity becomes part of value identity (qalid tailscale-bind) |
They're complements, deliberately joined — Tailscale is the transport perimeter, QALS is the trust-and-value layer on top.
| QALS chat (qalchat) | ||
|---|---|---|
| E2E encryption | Signal protocol (double ratchet, full FS) | X25519+HKDF ratchet + AES-GCM + ed25519; ratchet-lite FS (MLS upgrade documented) — honest gap |
| Key verification | QR safety-number compare | QR invite PINS + anchored DIDs + relay proof-of-possession |
| Metadata from relay | Meta sees who/when (sealed sender partial) | relay is ciphertext-blind by construction (byte-proven) |
| Value transfer | none (payments via partners, regional) | first-class: ⚡ payments in-conversation, escrowed, capped, receipted |
| Data provenance | none | conversation Merkle roots + file hashes anchored on-chain |
| Self-host | impossible | relay is one file, runs anywhere; multi-relay + offline ferry |
| Groups/communities | yes | workspaces/channels/threads/roles/pay-to-post (Discord-model) |
| Agents/Bots | limited, platform-gated | first-class (DID'd, capped, MCP-driven) |
| Trade-off | mature, universal, phone-SMS onboarding | ecosystem-internal today; FS not yet Signal-grade |
PROS 1. Capped agents: bytecode-enforced spend ceilings — the runaway-agent failure is structurally impossible (nobody else ships this). 2. Full-reserve credit: born from AU$1, retired from circulation on use, redemption accounted to the cent — no fractional reserve anywhere. 3. Finite supply as code (over-cap sales refused; sellable supply pre-endowed in the issuer wallet) — not policy, not promise. 4. Escrow everywhere: escrow holds bound every purchase's worst case before it starts. 5. Receipts on-chain: every job, trade, redemption, exec, and ceremony is an anchored, publicly-verifiable fact. 6. Encryption with teeth: ciphertext-blind relays (proven), pinned contacts, proof-of-possession registration. 7. Private-chain pragmatism: no token volatility for users, no public-attack surface, enterprise-clean story. 8. Recoverable by design: agents/devices controller-bound; humans mnemonic-rooted; nothing self-sovereign that can't be revoked. 9. Zero-dep services: every component is one Python file; audit-able in an afternoon; fleet-deployable in minutes. 10. Real testing culture: 25+ suites, ~700 assertions, two red-team campaigns, a full-system lifecycle ceremony — all re-runnable. 11. AI-native: MCP control plane, agent marketplaces, gmux fleet wallets — built for the agent economy, not adapted to it. 12. Composable money: the same credit pays compute, content, chat value, API calls, and service redemption at one rate.
CONS (own them honestly) 1. Trust concentration: qalarc runs the validators, the reserve, and the escrows today. Mitigation path exists (fleet validators, on-chain escrow, audits) — but today, you trust us. 2. Ratchet-lite forward secrecy: not yet Signal-grade; MLS upgrade designed, not built. 3. Paper-phase money: the ledger of record is loopd; the on-chain twin is proven but not yet the live rail. Real value isn't moving yet — deliberately. 4. Single-machine fragility (improving): core services on superlocal; relay #2 federated but DERP-flaky; bb-mini still offline. Multi-validator milestone pending. 5. Legal gate is the bottleneck: everything public (transferability, real-IOTA swaps, cash redemption) waits on VASP/licensing — slow, external, non-technical. 6. Python services at scale: rails are fine for thousands/day; a Rust rewrite of loopd/relay will be needed for hundreds of thousands (planned, priced). 7. Ecosystem lock-in: credit spends inside qalarc rails Phase 1-2 by design — freedom is gated on the legal path. 8. No formal audits yet: internal + red-team coverage only; the paid Move audit is budgeted, not spent. 9. WebAuthn gap on Linux: passkeys degrade (WebKitGTK limitation) — documented, plugin path exists. 10. Operational maturity: monitor exists, on-call is documented — but this is a founder-scale operation, not an SRE team.
The one-line summary: a legally-boring, receipt-anchored private economy with bytecode-capped agents — trading public-chain decentralisation and Signal-grade crypto maturity for control, compliance, and shipping speed today, with the upgrade paths designed and gated, not hand-waved.