# Ritual: demand should be measured in useful completed work

Shared research basis - Ritual

Research date: 28 September 2026 (UTC). This is pre-launch research, not an offer or price target.

Eligibility and goal. Official materials reviewed describe testnet and a forthcoming mainnet launch. No public raise or active ICO/TGE was identified in those materials; a disclosed private allocation is not a public sale. Recheck status immediately before publishing. Ritual aims to connect AI and external computation with smart contracts. The practical thesis is better application composition; actual adoption must be demonstrated rather than inferred from documentation. [S1, S2]

Economics. The initial 10B allocation is: contributors 29%, ecosystem/R&D 25%, network incentives 14%, Labs investors 11.3%, Foundation 10%, Labs treasury 5%, AI grants 4.7%, Foundation private sale 1%. Launch-unlocked supply is 1.8B, not confirmed market circulation. Contributor cohorts have 33%-50% one-year cliffs and finish at months 36/24. Investors have a 50% one-year cliff and finish at month 24. Network incentives have a 15-month lock; original allocations finish within four years. Initial issuance is about 5% annualised, alongside base-fee burning. [S1]

Unlock analysis. The clearly specified contributor/investor month-12 cliffs total 1.522B-2.015B. That is 84.56%-111.94% of launch-unlocked supply, without assuming any sale. An exact calendar needs the launch date, cohort weights and the remaining release terms. Unlocking existing allocations changes availability; minting increases total supply; burns reduce it. These should not be combined into one unexplained dilution number.

Valuation. Initial-supply value is 10B multiplied by price; circulating market cap is verified circulating supply multiplied by price. At a purely hypothetical $0.10, initial-supply value is $1B and launch-unlocked value is $180M. Neither is an observed valuation, and 10B is not a permanent cap. A no-burn sensitivity using 5% annual compounding on total supply gives 12.155B after four years. That assumption is not a promised issuance schedule.

Verification and risk. The official team page names Niraj Pant and Akilesh Potti. Their biographies are first-party claims. GitHub verifies the ritual.net organisation, but it currently displays no public repositories; current deployment-matched code and audit coverage were not established in this review. Technical trust assumptions, delivery, treasury control, demand and emissions remain material risks. The regulatory whitepaper index says the filing is not authority-approved. [S2-S5]

Disclosure. I have no Ritual holdings, investment rights, airdrop activity or team relationship. This research was prepared with AI assistance for a Republic quest eligible for VP rewards. The conclusions and scenario assumptions remain open to correction and substantive challenge.

My research focus

The product question I would prioritize is whether developers need Ritual's execution model enough to accept the cost of adopting another chain. An impressive demonstration can show that a workflow is possible without showing that customers prefer it, pay for it or return after incentives disappear.

A useful evaluation would start with one narrow application: an agent that retrieves information, performs inference and settles a bounded action. I would compare its completed-task cost, latency, failure rate and recovery process with a conventional application using a model API and existing settlement infrastructure. This is a proposed comparison, not a benchmark I have performed. The documented execution constraints should be included in that design. [S2]

My preferred demand indicators are repeat paying applications, successful jobs per application, fee revenue after subsidies and retention across several weeks. Raw transaction or agent counts can rise through retries, automated loops or reward-seeking behavior. Even legitimate automated activity needs an identifiable user benefit to support an economic thesis.

Ritual becomes more compelling if native scheduling and coordinated settlement remove operational work that customers otherwise struggle to maintain. The case becomes weaker if similar reliability is available more cheaply elsewhere. Until there is comparable production evidence, architecture quality and commercial demand should remain separate conclusions.

A useful evaluation would start with one narrow application: an agent that retrieves information, performs inference and settles a bounded action. I would compare its completed-task cost, latency, failure rate and recovery process with a conventional application using a model API and existing settlement infrastructure. This is a proposed comparison, not a benchmark I have performed. The documented execution constraints should be included in that design. [S2]

My preferred demand indicators are repeat paying applications, successful jobs per application, fee revenue after subsidies and retention across several weeks. Raw transaction or agent counts can rise through retries, automated loops or reward-seeking behavior. Even legitimate automated activity needs an identifiable user benefit to support an economic thesis.

Ritual becomes more compelling if native scheduling and coordinated settlement remove operational work that customers otherwise struggle to maintain. The case becomes weaker if similar reliability is available more cheaply elsewhere. Until there is comparable production evidence, architecture quality and commercial demand should remain separate conclusions.

Primary sources

[S1] Token allocation, vesting and supply plans: https://tokenomics.ritualfoundation.org/ [S2] Developer docs; Quick Start labels the network testnet: https://docs.ritualfoundation.org/ [S3] Named team and linked profiles: https://ritual.net/team [S4] GitHub organisation verified to ritual.net: https://github.com/ritual-net [S5] Regulatory whitepaper index; published 22 Jul 2026: https://www.ritualfoundation.org/whitepapers/regulatory All accessed 28 September 2026 (UTC). [S5] lists publication on 22 July 2026. Other cited pages do not establish a publication date for this snapshot.