Frequently Asked Questions
Plain answers before you explore.
Is this official Ripple?
No. XRP Legacy is an independent community project and is not affiliated with or endorsed by Ripple, the XRPL Foundation or the platforms it references.
Is this a wallet?
No. There is no wallet connection, recovery-phrase entry or transaction signing. Optional support payments are reviewed and sent in your own wallet.
Does it sell a token?
No. There is no XRP Legacy native token for sale, token sale, price target or promised investment return.
Is this financial advice?
No. Content is general education, independent research or labeled fiction. Prices may be delayed; an announcement is not proof of XRP use. Verify important claims with their original source.
Do I need an account?
No account is needed to read core lessons, view research, browse the Library or explore public worlds. Posting, reactions, supported account saves and some membership workspaces require sign-in. Signing in is not a wallet connection and grants no investment rights.
What stays on my device?
Preferences, supported favorites, watchlists, local lessons and some game progress stay in this browser. All•Tier chat is session-only unless you choose to remember it; export it separately. HFT has its own encrypted workspace and backup. Clearing browser data can remove local work.
What is saved to my account?
Explicit profile saves, member reactions and supported hosted worlds or collaboration records may be associated with your account. Not every browser save automatically syncs. The directory’s Save and recovery guide and each feature’s controls explain their scope.
Why do live headlines sometimes stay the same?
The website checks sources while viewed, but agencies and providers determine when new material is published. A refresh can legitimately contain no new headlines. Retained material keeps its original date; market timestamps and delays remain visible.
How do I report a problem or request a content review?
Contact caspersmiles_76115 on Discord. Include the exact URL, the issue, the time and your browser/device if relevant. For a rights concern, identify the work and your authority without sending private credentials. Requests are reviewed manually; no removal outcome or response time is guaranteed.