Project Research Dossier: Ritual — 7 October 2026

Project Research Dossier Ritual 7 October 2026

Constraint Use this only if the primary docs still show no public sale and no TGE. If a sale page exists on the day you post, pick another project. This draft does not invent a date or a price.

Goal Ritual is building an execution layer for AI workloads on-chain and off-chain, so a smart contract can request a model result instead of only moving tokens. The stated reason it matters is that today model calls sit with a company API. A chain-native request would let a contract check an output. That matters only if the request, the proof, and the response can be tied together. A demo is not that tie.

Tokenomics No FDV, circulating supply, allocation split, cliff, or emissions rate is used in this draft. If those figures are not in a primary document, they are undisclosed. A points program is not a cap table. A testnet is not a TGE.

Unlock and dilution No unlock calendar is cited. Dilution cannot be modeled. Missing is unknown, not low. A future sale document would replace this section rather than be guessed in advance.

Team verification Public technical posts and a documentation site can verify that a team is publishing. They do not verify every contributor, an audit, or custody of any future token. Team score stays partial until an audit and a named-operator page are linked.

Key risks Technical: model inference is non-deterministic unless the system constrains inputs, hardware, and proofs. A proof gap is the core risk. Execution: a testnet workflow can stall before mainnet. Incentive: if node rewards are unpublished, the people running models have no checkable schedule. Legal: model outputs and training data can carry copyright and privacy duties.

Disclosure No holding, no grant, no allocation. Not financial advice. Re-check the docs URL on the day of posting.