Path 01
RH Launch
A bonding curve issues the market, then graduates into a Uniswap v4 pool. LP is locked at graduation so the pool cannot be quietly pulled.
- Bonding curve
- Graduation
- LP lock
RTP Protocol · Giwa chain
Issuance infrastructure
RH Launch and Crowdfund run as parallel paths. Both graduate into Uniswap v4 pools with locked liquidity, vesting, and referral accounting. Opening tax is routed to the protocol treasury.
Two parallel issuance paths
Path 02
Crowdfund
Platforms register, campaigns accept subscription in arbitrary tokens, investor positions vest, and an opening premium applies at listing.
- Platform registration
- Any-token subscribe
- Vesting + opening premium
Accounting
Treasury routing
Opening tax collected at listing is routed to the protocol treasury. Parameters are bounded on-chain; read them from the contracts, not from marketing copy.
- Opening tax
- Treasury
- On-chain bounds
Protocol mechanisms
Split, vest, lock
Referral, vesting, and LP lock sit beside both issuance paths. Cards below are protocol surfaces, not product screenshots.
RH Launch
Bonding, graduation, and a locked Uniswap v4 pool. One of two issuance paths, not a wrapper around the other.
Open docs
Crowdfund
Open platform registration, any-token subscription, investor vesting, and an opening premium at listing.
Open docs
Referral
List referral and per-trade referral, both recorded on-chain against the campaign and the referring platform.
Open docs
Vesting
Investor schedules unlock after listing according to the campaign’s vesting module, not a side agreement.
Open docs
LP lock
Graduated liquidity is locked in protocol-controlled lockers so the pool cannot be removed on a whim.
Open docs
Invariants
Issuance, referral, vesting, and lock accounting are specified as invariants. See Security in the docs.
Open docsWhy integrate
Protocol, platform, user
Protocol
One issuance layer
RH Launch and Crowdfund share lock, vest, and referral modules. Platforms do not fork accounting to ship a market.
Platforms
Register and configure
A platform registers, sets its hook profile, and hosts its own UI. rtp.sh documents the protocol; it does not host the product.
Users
Predictable settlement
Investors and traders see vesting, locked LP, and referral attribution as contract state rather than a dashboard promise.
Ecosystem
Platforms, chain, tools
Names and logos appear only after OWNER confirmation. Until then every partner cell is a labelled placeholder.
Platforms
Frontends that register with the protocol to host RH Launch and Crowdfund flows.
Partner logo — OWNER to confirm
Partner logo — OWNER to confirm
Partner logo — OWNER to confirm
Partner logo — OWNER to confirm
Partner logo — OWNER to confirm
Partner logo — OWNER to confirm
Chains
Networks where RTP contracts are deployed. Giwa chain is the home network.
Giwa chainHome network for RH Launch and Crowdfund.
Partner logo — OWNER to confirm
Partner logo — OWNER to confirm
Partner logo — OWNER to confirm
Tools & Infra
Indexers, explorers, oracles, and operational tooling.
Partner logo — OWNER to confirm
Partner logo — OWNER to confirm
Partner logo — OWNER to confirm
Partner logo — OWNER to confirm
SDK & AI Agents
TypeScript SDK, quote interfaces, and agent-facing integration surfaces.
Partner logo — OWNER to confirm
Partner logo — OWNER to confirm
Partner logo — OWNER to confirm
Partner logo — OWNER to confirm
Built on RTP
rtp.fun jump-out
rtp.fun is a product built on the protocol. These cards leave rtp.sh. No product UI is embedded here.
Data & trust
Contracts, audits, invariants
Addresses come from the deployment list. Unpublished rows stay TBA. No count-up metrics until a live source exists.
Giwa chain testnet
Chain ID TBA · TBA| Contract | Address | |
|---|---|---|
| RH Launch factory | TBA | TBA |
| Crowdfund factory | TBA | TBA |
| Referral registry | TBA | TBA |
| Vesting module | TBA | TBA |
| LP lock | TBA | TBA |
| Treasury | TBA | TBA |
Giwa chain mainnet
Chain ID TBA · TBA| Contract | Address | |
|---|---|---|
| RH Launch factory | TBA | TBA |
| Crowdfund factory | TBA | TBA |
| Referral registry | TBA | TBA |
| Vesting module | TBA | TBA |
| LP lock | TBA | TBA |
| Treasury | TBA | TBA |
Audits
Auditor names and reports land here after OWNER confirmation. Until then this is an empty slot, not a claim.
Audit register →Invariants
Issuance supply, LP lock, vesting, and referral splits are specified as invariants the test suite is expected to hold.
Invariant list →Roadmap preview
Three phases, no dates
Direction only. No dates, yield, or price commitments. Status labels are placeholders pending OWNER confirmation against the deployment list.
Phase 1
Foundation
OWNER to confirm
- RH Launch protocol on Giwa chainOWNER to confirm
- Crowdfund protocol r3OWNER to confirm
Phase 2
Expansion
OWNER to confirm
- EVM multi-chain, Uniswap v4 onlyPlanned
- Optional yield adapter for locked ETHPlanned
- TypeScript SDK, quote interface, integration docsIn progress
- AI agent integrationPlanned
Phase 3
Next
Planned
- Identity verification, stage twoPlanned
- Ladder pricingPlanned
- Token bridgingPlanned
- Per-platform hook configurationPlanned