# Ritual: accountability requires more than recognizable names

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

A public team profile is a useful starting point for attribution, not a substitute for operating accountability.[S3] The questions I would ask are narrower: who can change the protocol, who can move treasury assets, who can stop or resume critical functions, and which decisions require consent beyond the founding team? Those answers matter more to a prospective participant than a collection of impressive biographies.

The technical documentation provides a design to examine, while the verified GitHub organisation identifies a domain-controlled account. That account currently displays no public repositories, so it does not provide inspectable chain code for this review.[S2][S4] A stronger evidence package would connect a release tag or commit, deployment addresses, privileged roles and audit scope. I would distinguish that chain of evidence from claims about security, decentralization or research quality. Unresolved mappings should remain explicit research gaps.

For governance, my preferred milestone is a published authority map with change procedures, emergency powers, and communication responsibilities. Token voting should be assessed alongside concentration and operational vetoes; the presence of a voting mechanism does not automatically distribute control. If a material parameter changes, a reader should be able to identify the decision-maker, the notice period, and the source documenting the change. Clear responsibility would increase confidence even before the system becomes more decentralized.

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.