Skip to main content
Channels not published yet. The Discord invite, X handle, support address and security contact are still to be decided. Until they’re filled in, this page deliberately lists none — an out-of-date or guessed support channel on a page about avoiding scams is worse than no channel at all.

Before you ask — check these first

A surprising share of reports resolve at one of these:
  • Deposit not showing? Confirm you sent USDC on the Solana network to the address shown in the app. Full checklist.
  • Trade seems stuck? The first trade on a venue that isn’t Solana-native has to bridge funds first — up to about a minute. The preview shows the ETA before you commit.
  • Withdraw button missing or disabled? Withdrawals may be off for the current deployment. Reclaiming funds from a venue back to your pool still works.
  • Withdrawal not showing up? It pays out in USDC on Solana, whichever venue the funds came from. Check a Solana wallet, not an Arbitrum or Ethereum one.
  • Balance looks wrong right after a trade? Refresh the portfolio; venue balances update on their own schedule after a fill.

What to include in a report

  1. Your wallet address — the public one you signed in with. Never a private key or seed phrase.
  2. What you were doing — deposit, trade, withdraw — and the market and size.
  3. The transaction signature or link, if a deposit or withdrawal is involved.
  4. Roughly when it happened, with your timezone.
  5. A screenshot of what you saw, including any error message in full.
We will never ask you for: your seed phrase or private key — not for support, not for recovery, not ever. A signature sent to you over DM or through a link someone shared. Payment to unlock, release, or recover funds.Anyone asking for these is trying to steal from you, whatever name or logo they’re using. ryft support will never DM you first. And since ryft’s design does not use exchange API keys at all — if anyone asks you to paste one, it is not us.

Security issues

Found a vulnerability? Please report it privately rather than publicly, so it can be fixed before it’s exploited. Contact address to be published.