August 19, 2026 is a Qubic milestone. It is also one for us. Aigarth Cloud is live at aigarthcloud.lucidmindlabs.com, and we wanted to mark the moment in public.
Why now
The second halving of the Qubic network lands on August 19. We have spent the last eight months building the platform we think is the most interesting thing to do with Qubic's compute substrate: AI infrastructure that runs on a Useful Proof of Work chain.
The halving is the occasion. The platform is the work. Shipping the platform on a day when the network makes history felt like the right way to introduce it.
What Aigarth Cloud is, today
Aigarth Cloud is not a landing page. It is a working platform. Here is what you can poke at end to end right now.
- 12 services in production: identity, qubic, compute, gateway, billing, ann, marketplace, tissue, dataset, economy, training, and the new work runtime.
- 7 primitives under one model: adaptive intelligence (the Organism), memory, evolution, experimentation, distributed computation, verification, and external reality. ADRs 005 through 007 govern the last three.
- 600+ tests across the platform, with a 4-minute CI loop, a dual-mode pg-mem harness, and zero regressions on the 200+ cases that predate the v0.2 evolution.
- The Trinary Intelligence Layer in production: every
/decidecall returns a signed IntentEnvelope, the tissue service composes 5 consensus policies, and the HMAC signature is auditable end to end. - The Work Runtime (services/work, port 7012): 5 tables, 13 routes, a 4-tier compute model, a v1 verification stack (replication plus challenge plus reputation), and an algorithm registry. The first registered algorithm is
awork_1. - AigarthPool: on-chain settlement with a QPI contract plus a TypeScript simulator, a 30/60/10 default split, and a multi-sig treasury.
The Qubic halving, in one paragraph
Qubic emits a fixed 1 trillion QUBIC every week. That number does not change at Epoch 227. What changes is the share that gets burned.
Until now, the burn rate is 55 percent. From Epoch 227, it rises to 77.5 percent. Effective supply entering circulation falls from roughly 450 billion to 225 billion QUBIC per week.
The faucet does not shrink. The drain grows. That is the shape of the halving on a chain where gross issuance is fixed.
The interesting question
Qubic has always interested us because of the question underneath the technology: what does a network become when computation itself is a first-class resource, not a side effect of a payments ledger?
That is the territory Aigarth Cloud is built in. Useful Proof of Work, sub-second finality, zero transaction fees, native ANN execution. A substrate that is productive from day one, not after a settlement.
Aigarth Cloud is the question put in public, with a working surface attached.
From blockchain to compute substrate
The clearest way to think about Aigarth Cloud is not as a blockchain application. It is as a compute substrate coordinated by a chain. Three things in production today make that concrete.
- Useful Proof of Work means the work the chain does is real work. The Work Runtime routes work items to workers, runs the algorithm, verifies the result, and bills the payer. The chain is not a meter. It is a doer.
- Sub-second finality means a work-item result can be settled the moment it is verified. No waiting for block confirmations. No stale results. The economy is the work.
- Zero transaction fees means micro-pricing of work becomes possible. A /decide call that takes 80ms of compute can be priced, settled, and audited without the fee eating the work.
Why we are marking the moment, not the launch
Aigarth Cloud is not launching today. It has been building for eight months, across 27 phases, on 12 services. The Work Runtime shipped last week. The Trinary Intelligence Layer shipped earlier in August. The marketplace shipped in the summer. The Phase 27 deploy to lucidmindlabs shipped the week before.
What is happening today is a public marker. The thing inside the doorway has been there for a while. The halving is the moment we put on it.
We could have waited for a cleaner narrative. We could have shipped a longer roadmap first. We did not, on purpose. The platform should earn the right to a moment by being real, not by being loud.
What is next, in real dates
The roadmap is on the site. The next two phases that matter for the Qubic thesis:
- Phase 28, Q4 2026: Federated workers. Workers that live in your data center, on your laptop, on a partner's network. Cross-deployment reputation. The first tier where Aigarth Cloud runs outside our own infrastructure.
- Phase 29, Q1 2027: OC processor. The Qubic on-chain processor reads Organism work items and commits 451-of-676 computor signatures. Real on-chain verification, not a mock. This is the phase where the Work Runtime stops being Qubic-aware and starts being Qubic-native.
A community question (a real one)
We are not asking whether Aigarth Cloud should support AI inference. It does. We are not asking whether it should expose compute. It does. We are not asking whether there should be an ANN marketplace. There is.
The two questions we are asking on Epoch 227:
- What should the OC processor compute first? When Phase 29 ships, the OC processor will pick work items. The first 10 registered work algorithms shape what the network becomes. We want the Qubic community to nominate them.
- What is the v1 dispute resolution policy? Today, when three replicas disagree, the worker with the highest reputation wins. That is a default, not a verdict. The first real dispute will surface what is actually fair. We want a community signal before that lands.
Two questions, both with a real answer to ship. Tell us what you think.
The marker
Epoch 227 is a marker for Qubic. We are using it as a marker for Aigarth Cloud, too. The platform is the work. The moment is the day. The community question is the next step.