> For the complete documentation index, see [llms.txt](https://docs.surgexrp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.surgexrp.com/roadmap.md). # Roadmap SurgeXRP Roadmap #### Q2 2026 — Inception & Project Announcement Official launch of SurgeXRP brand and public announcement.\ \ Website and documentation go live.\ \ Waitlist opens for early investors and property partners. #### Q3 2026 — Beta Launch Closed beta of the SurgeXRP application.\ \ First properties tokenized and listed on the marketplace.\ \ Early waitlist investors gain access.\ \ KYC integration live.\ \ XRPL wallet connectivity enabled. #### Q4 2026 — Full Product Release & Marketing Campaign Public launch of the full SurgeXRP platform.\ \ Open marketplace with multiple property listings.\ \ Full onboarding flow live.\ \ Marketing campaign targeting global retail investors and XRP community.\ \ Exchange listing and token listing on major crypto tracking platforms. #### Q1 2027 — RWA Lending & Staking Launch Launch of Lending Vaults: Property tokens accepted as collateral for RLUSD loans.\ \ Launch of Staking Vaults: Stake rental dividends for additional passive income.\ \ DAO governance framework activated for property token holders. #### Q2 2027 — Strategic Partnerships & First RWA Convention Formalization of strategic partnerships across real estate, DeFi, and XRPL ecosystems.\ \ SurgeXRP hosts its inaugural RWA Convention: bringing together investors, property managers, regulators, and blockchain builders to advance the real estate tokenization industry. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.surgexrp.com/roadmap.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.