Integrating a front end
Platform ids, platform registration and fee terms within the caps, referrers, and the rule that only registry addresses are official.
Any front end can integrate
The contracts contain no logic specific to any single token or community. Any front end can integrate the protocol and receive the platform share of fees. RTP.fun is the reference application: one integrator among potentially many.
RTP Curve Launch: a platform id
A front end integrates Curve Launch through a namespaced platform id. The platform share of the trade fee is set per launch tier and credited to the platform's payee in the RtpCore ledger, to be claimed. With no platform payee, that share goes to the protocol treasury.
RTP Fixed-Price Launch: a platform registration
Any front end can register a platform in FundPlatforms and set its own fee terms and payee within the compiled caps. Each launch freezes the terms of its platform when it is created; a change reaches only launches created afterwards, while the payee can be moved at any time.
| Platform term on Fixed-Price Launch | Compiled cap |
|---|---|
| Platform share of the pool fee | up to 20% |
| Referral budget of the pool fee | up to 20% |
| Creation fee | up to 0.1 ETH |
| FundZap fee | up to 1% |
Referrers
A trade may name a referrer on either path. On Curve Launch a referrer equal to the trader, the recipient, the launcher or the creator key is treated as no referrer. On Fixed-Price Launch a swap names a per-trade referrer, and each launch can carry a fixed list of up to five referrers named at creation. See Fees.
Only registry addresses are official
The SDK
The official SDK, @rtpfun/rtp-launch-sdk, is pending publication; nothing can be installed yet. Its client refuses core addresses that are not in the official registry unless the caller opts out explicitly. It covers RTP Curve Launch; Fixed-Price Launch is not covered by this package; a Fixed-Price Launch SDK is in preparation. See SDK.