13 · Risk factors
An honest register of what can go wrong
This section exists because a whitepaper that cannot describe its own failure modes is marketing. It is not exhaustive, and it does not replace the Risk Disclosures, which govern.
Product and market risk
Engagement may not survive scale. Transaction volume per user is not guaranteed to hold through a 10× increase in registrations, particularly if growth comes from lower-intent channels.
The registered-to-active gap may not close. A large registered base is a reactivation opportunity, but quest-acquired signups are historically hard to convert, and the gap may simply persist.
Interpretation may commoditise. General-purpose models improve rapidly. If frontier models become able to ground themselves in live on-chain state cheaply, the analytical layer's advantage narrows to proprietary scoring and cross-product signal.
Competitors can move into the intersection. Analytics platforms can add execution; trading interfaces can add interpretation. The lead is roughly nine months of production operation and a user base acquired without paid spend, a real advantage, but a lead rather than a wall.
Technology and security risk
Audits do not eliminate contract risk. The CertiK and Hacken reviews cover the contracts submitted to them, at the version submitted. New deployments, upgrades and integrations carry fresh risk.
Front-end and supply-chain compromise. A non-custodial architecture protects against operator theft but not against a compromised interface presenting a malicious transaction for signature.
Oracle and data-source manipulation. Interpretation is only as good as its inputs. Social signal in particular is adversarial, participants have incentives to manufacture the appearance of attention.
AI output can be wrong. Grounding reduces fabrication; it does not eliminate error. A confident, well-evidenced and incorrect interpretation is possible, and users act on these.
Automation risk. Pre-staged and conditional orders execute on conditions that may be met under circumstances the user did not anticipate.
Regulatory and operational risk
The regulatory position is evolving. Digital-asset regulation continues to develop, with MiCA in the EU and varying regimes elsewhere. Requirements may change in ways that restrict features or jurisdictions.
Jurisdictional restriction may expand. Access is already restricted from prohibited jurisdictions and sanctioned parties, and that list can grow.
Third-party dependency. Telegram Apps Center approval, wallet integrations, exchange listings and data providers are all outside the project's control.
Key-person and execution risk. Phases 2–4 depend on continued execution by a small team.
What is not a risk disclosure
Nothing in this document is an offer to sell or a solicitation to buy any security or digital asset, and nothing in it is investment, legal, tax or financial advice. Digital assets are volatile and participation can result in total loss of capital.
Read the full statement in Risk Disclosures.
Last updated

