Skip to main content
Resources·Updated Jul 2026Standard V1.0

Disclaimer

This page states, explicitly and without softening, the terms on which this documentation and the systems it describes are offered. It is written to be read, not skimmed. If anything on this page conflicts with a more optimistic reading of any other page, this page wins. If you do not accept everything below, do not interact with the protocol, contribute to any raise, or acquire any token launched under the standard.

Nothing here is advice​

Nothing in this documentation, on any affiliated website, or in any official communication channel constitutes financial, investment, legal, accounting, or tax advice, and nothing is tailored to any person's circumstances. The documentation is a technical description of deployed smart-contract systems. No statement in it is a recommendation to buy, sell, hold, or refrain from any action involving any token or contract. Before making any decision with financial consequences, consult qualified professional advisers in your own jurisdiction. No communication from the PURITY team, in docs, posts, or chats, should ever be read as advice, and any team communication that appears to promise outcomes should be treated as inauthentic (see the fraud section below).

No offer, no solicitation, no prospectus​

This documentation is not an offer to sell or a solicitation of an offer to buy any token, security, financial instrument, or investment product, in any jurisdiction, to any person. It is not a prospectus, an offering memorandum, a white paper in the promotional sense, or marketing material for an investment opportunity. No regulatory authority has reviewed, approved, or passed on anything described here. The availability of this documentation on the public internet does not constitute an offer or distribution in any jurisdiction where such an offer or distribution would be unlawful.

What tokens under the standard are, and are not​

A token launched under the PURITY standard, including $PURE, is a unit in a deterministic on-chain market structure. It is not equity, debt, a deposit, a share of revenue or profits, a claim on any company, foundation, or person, an entitlement to income, or a promise of price appreciation. It is not insured or guaranteed by anyone. Holding it confers exactly two narrow governance rights, voting on shutdown authorisation and on capped treasury-release proposals, and nothing else: no ownership, no dividends, no management rights over any entity.

The standard's mechanics, including treasury market-making, are structural properties of deployed code. They are not an undertaking by any party to generate profit for holders, and they must not be relied on as one. No person or entity is managing your tokens, pooling your funds for common profit, or working on your behalf to increase a price.

You can lose everything​

Tokens launched under the standard can lose all of their value. This is not a formality: the standard removes structural extraction, and deliberately does not touch market risk. Demand can be insufficient, attention can fade, and a token can go to effectively zero through nothing but honest market behaviour. Prices are volatile, liquidity can be thin, and no mechanism described anywhere in these docs prevents loss. Participate only with capital whose total loss you can absorb, and size every position accordingly.

The floor is not a price guarantee​

These docs describe a "dynamic floor" (P_floor) and a treasury that accumulates near it. Read precisely: the floor is a computed reference value, not an enforced price, a peg, or a promise. The market can trade below it, and the treasury's buying is bounded, conditional, and finite, not price support. The engine's liquidation bands, similarly, are behavioural thresholds, not price predictions. Any interpretation of the price-anchor system as a guarantee, a minimum value, or downside protection is wrong, and no such interpretation is intended or endorsed. If a third party markets a PURITY launch to you using the floor as a promise, they are misrepresenting the standard.

Supporter contributions can return zero​

Supporter contributions to a launch vault are not investments in the legal sense intended by that word's everyday use, and they are certainly not deposits. A supporter receives no tokens, no ownership, and no guaranteed return of any kind. The supporter return is a pro-rata share of realised liquidation proceeds, which exist only if the market generates conditions the engine will sell into. If it never does, the return is zero, permanently, with no recourse. Contributions are refundable at will only before a launch fires; after launch, the contribution is spent, irreversibly, on pool seeding and initial accumulation. Contribute only what you can afford to lose entirely.

Smart-contract and operational risk​

Every guarantee in this documentation is a property of deployed code, and code carries risk that no process eliminates:

  • Audit limits. The contracts are audited, but no audit reduces smart-contract risk to zero. An undiscovered defect is a risk shared by every launch under the standard, and immutability means a defect cannot be patched in deployed launches.
  • Immutability cuts both ways. The impossibility of rugging is the same property as the impossibility of fixing or upgrading. A deployed launch lives with its code, and with most of its configuration, forever.
  • Bounded team powers exist. A launch's team can retune six market-making dials within immutable, contract-enforced ranges. This cannot move funds, mint, change splits, or raise any cap, and every change is publicly event-logged, but it does mean the engine's bands are not frozen; a team can make its engine behave differently, within the envelope, than the configuration you first read.
  • The arbitrator is centralised. Shutdown execution runs through PURITY's multisig, whose powers are narrow but real, and which for $PURE itself is conflicted (the team is the arbitrator). See Risk & Limitations for the honest treatment.
  • Keeper dependency. Engine revenue depends on off-chain automation staying alive. Correctness does not, but unharvested opportunities are simply lost.
  • Chain and infrastructure risk. The underlying blockchain, AMM, wallets, RPC providers, and this website are all failure surfaces outside the standard's control.
  • Transactions are irreversible. There is no support desk that can reverse a transfer, recover keys, or undo a mistake.

"Verified PURITY" is not an endorsement​

Verification against the factory's provenance registry means one thing: the launch genuinely runs the standard's mechanics. It says nothing about whether the project is good, the team competent, or the token worth anything. PURITY does not curate, endorse, or vet projects, and no badge, listing, index position, or activity metric anywhere in the ecosystem is a recommendation. A verified launch can be a bad idea executed honestly, and many will fail. The standard guarantees mechanics, never merit, never outcomes.

Forward-looking statements​

Any statement in these docs about future events, the platform under development, planned features, the $PURE launch, the arbitrator transition, ecosystem growth, or intended behaviour of anything not yet deployed, is a forward-looking statement. Such statements reflect current intent, involve known and unknown risks, are not commitments, and may never come to pass. Nothing that is not deployed, verified code should be relied upon. Past behaviour of any system, and any historical data, is not indicative of future results.

Regulatory status and jurisdictional restrictions​

The legal and regulatory treatment of tokens, token launches, and on-chain market-making is unsettled, varies by jurisdiction, and is changing. It is possible that regulators in some jurisdictions would characterise tokens or supporter arrangements described here in ways that impose obligations or prohibitions on participants or operators, now or retroactively.

You are solely responsible for determining whether your participation is lawful where you live and from wherever you access the protocol. Do not participate if you are in a jurisdiction where doing so is prohibited or restricted, if you are subject to sanctions, or if you are otherwise legally barred. Nothing here is directed at any person in any jurisdiction where its publication or availability would be unlawful. The protocol is permissionless code; no one can screen your participation for you, which means the legal responsibility for it is yours alone.

Taxes​

Acquiring, holding, transferring, or disposing of tokens, contributing to or being refunded from a vault, receiving supporter or team distributions, and claiming after a shutdown may all be taxable events in your jurisdiction. Nothing here is tax advice, no party involved in PURITY will report or withhold on your behalf, and the obligation to determine, report, and pay any tax is entirely yours.

Official channels and fraud​

The only official social channel at the time of writing is the X account @purityonchain. No official Telegram or Discord exists. Any group, server, account, airdrop, presale, or website presenting itself as PURITY beyond the channels listed in these docs is unofficial and should be presumed fraudulent. The team will never DM you first, never ask for your seed phrase or private keys, never ask you to send funds to "verify" or "migrate" anything, and never promise returns; anyone doing any of these is a scammer impersonating the project. Canonical contract addresses will be published at launch, and the on-chain provenance registry, not any website or social account (including this one), is the root of trust. Verify addresses independently before interacting with anything claiming to be PURITY.

The contracts are authoritative, not these docs​

This documentation describes the deployed contracts in good faith, but it is a description, not the system. It may contain errors, may lag behind the deployed code, and does not amend, override, or supplement contract behaviour in any way. If the docs and the deployed code disagree, the code governs, without exception. Read the code, or have someone competent read it for you, before relying on any behaviour described here.

No warranty, no liability​

This documentation, the websites, and the deployed contracts are provided "as is" and "as available", without warranty of any kind, express or implied, including merchantability, fitness for a particular purpose, accuracy, or non-infringement. To the maximum extent permitted by applicable law, the PURITY contributors, the core team, and any affiliated persons and entities accept no liability for any loss or damage of any kind, direct, indirect, consequential, or otherwise, arising from or in connection with this documentation, the protocol, any token launched under the standard, any supporter contribution, any third-party launch, or any reliance on any statement here, even if advised of the possibility of such loss. Nothing in this section excludes liability that cannot lawfully be excluded.

Changes​

This disclaimer may be revised as the protocol, the documentation, and the regulatory environment evolve. The current version is always the one published at this URL, and revisions are visible in the public repository history. Continued use of the documentation or the protocol after a revision constitutes acceptance of the revised terms.

If any part of this page is unclear, that is a reason to stop, not to proceed. Participation in permissionless systems is at your own risk, on your own judgement, and under your own law.