What RTP Protocol is, RTP Protocol docs

Neutral token-launch infrastructure for EVM networks: two launch paths on Uniswap v4, with liquidity no one can remove and terms fixed in code before anyone trades or contributes.

The protocol

RTP Protocol is neutral token-launch infrastructure for EVM networks. Its two launch paths share one philosophy: terms are fixed when a launch is created, liquidity cannot be withdrawn, and every payout is pulled by its owner from a contract ledger.

RTP Curve Launch

Any creator can launch, on an enabled launch tier, a token that trades on a constant-product bonding curve. At its funding threshold the token graduates, at the same price, into its own Uniswap v4 pool, whose single full-range position is held permanently by an immutable graduator.

RTP Fixed-Price Launch

A separate, self-contained set of contracts for a structured raise: up to six batches at one price for everyone, at least 70% of the raise in permanently locked liquidity, creator funds vested on-chain, full refunds if the raise fails, and a protected market opening.

The two paths side by side

Question	RTP Curve Launch	RTP Fixed-Price Launch
Price discovery	Continuous bonding curve, then a Uniswap v4 pool	One fixed price for all participants; the pool opens at that price or at a premium of up to 50% fixed at creation
Who can create	Any creator, on an enabled launch tier; verified tiers also need an identity attestation	Any address; display on RTP.fun is a separate platform decision
Liquidity	Raised quote plus reserved supply, locked at graduation	At least 70% of the raise, locked at settlement
Early-market protection	Decaying opening-buy tax on the curve	300 s closed market, then a 600 s decaying buy tax
Failure path	Not applicable: trading is continuous	Full refunds, pulled by each contributor
Upgradeability	None	None

Principles

Token launches fail participants in familiar ways: liquidity that can be pulled, insiders who buy at a different price, parameters that change mid-sale, and refunds that depend on goodwill. RTP Protocol is designed so that each of these is either impossible in code or disclosed up front.

Neutral by construction

Any front end can integrate the protocol through a namespaced platform id and receive the platform share of fees. RTP.fun is one integrator among potentially many. The contracts contain no logic specific to any single token or community.

Terms fixed at creation

Every curve launch and every fixed-price launch snapshots its parameters when it is created. Operators can adjust settings for future launches only, within bounds compiled into the contracts.

Liquidity that stays

Pools are seeded by an immutable graduator that holds one full-range position per token and has no withdrawal path. The rule that matters most to holders is enforced by the absence of code.

Pull, never push

Fees, refunds, vested amounts and claims are credited to on-chain ledgers and collected by their owners. Trades never push value to third parties, which removes whole classes of re-entrancy and denial-of-service risk.

Immutable contracts

No proxy, no upgrade path and no self-destruct. The trust surface is smaller; the trade-off, accepted deliberately, is that there is no emergency stop.

Threat model. The project keeps a threat model, to be published with the code, that quantifies the economic limits of its own design, including the costs of sniping, self-trading and predictable buyback flows.

What participants can rely on

Terms are snapshotted at creation. Later configuration changes apply to new curve launches or new fixed-price launches only.
Graduated liquidity has no removal path in code. It is locked, not burned: the position exists and is held by a contract that has no function to withdraw it.
The platform cannot pause trading, refunds, claims or settlement, cannot move funds credited to others and cannot upgrade contracts.
Protections are described with their limits. The opening tax raises the cost of sniping; it does not make sniping impossible.

Where it stands

Curve Launch runs on a public EVM testnet with test tokens only, from an earlier build. Fixed-Price Launch is not yet deployed. GIWA stays on testnet; both launch paths go to Robinhood Chain mainnet, and Fixed-Price Launch also to Base.

Security review in progress: internal review rounds are under way and an external audit is being arranged. Mainnet deployment follows the review rounds and one complete verification run; the external audit may not be complete by then, and its results are published when it is.

The document set

Whitepaper	Version
RTP Protocol: Overview	1.0-draft.26
RTP Curve Launch: Technical Overview	1.0-draft.26
RTP Fixed-Price Launch: Technical Overview	1.0-draft.26

Where two documents describe the same rule, the technical overview of that launch path is the reference.