Four pieces.
One thing feeding them.
Most chains launch and then go looking for something to do. This one arrives with a workload attached, and the workload is what pays for the security.
A flywheel diagram is usually drawn with nothing entering it, which is the part that is never true. This one has exactly one input, it comes from people paying for a product, and the drawing cuts it every few seconds so you can see what is left.
The idea in one paragraph
A chain secured by GPUs needs those GPUs to keep showing up. A trading agent that reads social sentiment needs a lot of inference. Those are the same machines. So the GPUs mine the chain, run the inference, get paid in the coin they are minting, and the subscriptions that pay for the inference buy that coin. The protocol is its own biggest customer, and it is also an open platform, so anyone else can build on the same rails.
That is the whole thesis. Everything else on this site is detail about how each of the four pieces works and what is hard about it.
What we run and what we do not
Every project in this category says it is decentralized. Here is the actual list, in both directions, so the claim can be checked instead of taken on faith.
Not ours to switch off
- Mining, both lanes
- Full nodes and consensus
- The Compute Mesh, including the oracle service
- The exchange contracts, order book and pools
- The Strategy Marketplace
- The Governance Module
- The Signal Ledger
- The Founders' and Referral registries
If every machine we own went dark tomorrow, all of this keeps working. That is the test, and it is the only one that matters.
Ours, and we say so
- This website
- Subscription billing and account management
- The Discord and Telegram systems
- The initial sentiment model fine-tune, which is a development step rather than the inference path
Normal product infrastructure. None of it is a dependency for the chain, and none of it can stop the network producing blocks.
Where it is being built
In the open, in an organization of separate repositories, one per shippable component. Most of them are private during development and each one states the point at which it goes public: at Testnet Beta, at mainnet, or when its audit completes.
Two never go public. The trading engine, because it is the product the subscription pays for, and the web and billing systems, because they hold payment and moderation internals. Everything the chain needs in order to run without us is going public.
Outside pull requests are closed unreviewed while this is pre-testnet. That reads harshly written down, and the reason is that interfaces move weekly and several components are queued for audit. Merging outside work into that means either accepting code nobody can properly review or leaving a contributor waiting for months. Security reports are the exception and are always read by a person.