RTP.FUN brings market discovery, trading, token launches and community alliances into one web app. Follow market and social activity, explore launches, and work with your alliance without losing the context behind an action.
Open RTP.FUN · Read the user guide · Explore Alliances · Release notes and scope
| Start with | What you can find | Open |
|---|---|---|
| Market discovery | Pulse market views, Signals updates, Calls and tracking surfaces. | Pulse · Signals |
| Trading | Trade and Swap workflows with amounts, fees and execution review; Portfolio for account context. | Trading guide |
| Token launches | A launch catalogue and token-creation workflows, with availability specific to each network and route. | Launchpad |
| Community alliances | An alliance directory for signed-in users, plus membership, Calls and task bounties for community work. | Alliances |
| More to explore | Live and Gacha directories for signed-in users. | Live · Gacha |
Communities have a place to keep their identity, share Calls and organize work. Traders can follow the activity around an asset and move into its trading or launch workflow. A listed asset, community or third-party post is not an RTP.FUN endorsement.
Launchpad Explore listed launches and network filters. |
Alliances Find communities and explore their shared activity. |
These are real product-page captures from 24 October 2026. They exclude the account header, wallet balances and private drafts. Listed assets, community statistics and third-party content are historical screen content, not current quotes or performance claims. Image provenance and sizes.
- Start with the overview and user guide. Market, launch and alliance directories require an RTP.FUN account. Supported shared token and alliance-detail links can be viewed without signing in.
- Learn the Wallet roles. Login establishes your RTP.FUN account. The execution wallet, called AMS in the architecture documentation, signs supported transactions in the user's browser. Wallet guide.
- Review the specific action. Network, route, asset, amount and fees matter. A visible route or tool does not establish that every path has been exercised in production.
- Check the result before repeating an action. A transaction with an uncertain outcome needs verification; uncertainty is not confirmation of failure.
Some product surfaces are still incomplete, and market data or external services can be unavailable. Feature visibility, interface checks and completed on-chain execution are different kinds of evidence. The dated release note explains the scope of the latest published observations. No new funds were moved for that review.
Identity and transaction signing are separate roles. RTP.FUN's server prepares and relays supported transactions; the intended signing boundary keeps plaintext AMS keys out of the server. The public architecture and AMS profile describe these responsibilities and their limits.
This repository does not publish an independent security assessment or certification. Architecture descriptions and internal checks do not establish either. Evidence vocabulary · Responsible disclosure.
This is RTP.FUN's public product and documentation repository. The running application and its private source are maintained separately; this repository has no application install or build step.
| Read | Purpose |
|---|---|
| Official Docs | How to use the product |
| Product overview | Product areas and the language used to describe them |
| Status and limitations | Dated observations and how to read capability claims |
| Public architecture | Identity, signing and server responsibilities |
| Security policy | Reporting a security concern privately |
| Claims registry | Scoped product and architecture statements |
| Publication policy | What is appropriate to publish |
| Contributing | Documentation corrections and public feedback |
The token transparency framework records disclosure principles only. It is not a sale announcement, a published token allocation, an airdrop entitlement or a promise of token-holder income.