Introduction

Purpose & Scope

This document defines the rationale, structure, and behaviour of PURITY: a deterministic standard for launching tokens and managing their market lifecycle without discretionary extraction.

It is not a whitepaper in the promotional sense.
It does not attempt to sell an opportunity, forecast outcomes, or persuade participation.

Instead, it serves as:

• a description of observed failures in token market design,
• a set of economic and structural constraints derived from those observations,
• and a precise on-chain system that enforces those constraints through code.

Where possible, claims in this document are grounded in empirical market behavior rather than ideology or aspiration. The focus is not on what token markets should be, but on how they actually function under real conditions of liquidity, speculation, and incentive pressure.

PURITY does not claim to eliminate risk or guarantee success. Its scope is intentionally narrow: to remove avoidable structural unfairness at the point of launch and throughout a token’s lifecycle, so that market outcomes reflect demand rather than extraction.

Who This Is For

This document is written for readers who are comfortable engaging with market structure, incentives, and on-chain systems.

This includes:

• builders designing token economies and launch mechanics,
• traders and analysts seeking to understand how supply control and liquidity shape price behaviour,
• researchers studying reflexive markets and incentive design,
• and technically literate participants evaluating whether PURITY aligns with their risk tolerance and values.

No prior affiliation with PURITY is assumed.
Skepticism is expected and appropriate.

This document focuses on system structure and economic behavior, and is written for readers seeking a clear, non-promotional explanation of how PURITY operates.

How to Read These Docs

The documentation is organised by what you need rather than as a single linear document.

Getting started holds the context: why token launches fail structurally, and the analysis the standard is built on (Why PURITY). Protocol is the precise description of the system itself: the standard's constraints, the contract architecture, the market engine, and how value flows, is governed, and resolves. $PURE covers the first live instance and ecosystem anchor. Launch is the practical path for teams launching under the standard, and Resources holds the parameter reference and glossary.

The Protocol sections are written to be precise rather than accessible. Readers primarily interested in implementation detail may go straight there, but the design choices are difficult to evaluate without the context that precedes them.

This document does not assume that PURITY is correct.
It assumes only that market structure matters, and that structure can be reasoned about.

Whether PURITY is an appropriate model is ultimately an empirical question. This document exists to make that question testable.