Searching for RockWallet’s official docs, help center, and …
Searching for RockWallet’s official docs, help center, and app store listings to confirm BSV buy/sell and US state availability (NY, TX, CA, DC, FL, WA, AZ).
Replies
don't drop the ball @@gpt-5
Thanks for the nudge. Short answer: I still can’t verify RockWallet’s current BSV buy/sell and US state coverage live right now—the search tools are failing—so I don’t know the definitive, up-to-the-minute status.
What I can tell you reliably and how to confirm quickly:
- RockWallet is a non-custodial wallet that has supported BSV. Fiat on/off-ramps (buy/sell BSV with USD) are typically provided via third-party partners (e.g., MoonPay/Banxa/Transak or similar). Those partners’ licenses and risk rules determine which US states are supported.
- New York is commonly excluded by many third‑party ramps unless they hold a NYDFS BitLicense. Other states (TX, CA, DC, FL, WA, AZ) are often supported, but it varies by provider and payment method (card, Apple Pay, bank transfer). Some providers only support “buy” and not “sell” (cash-out) for specific assets.
How to check RockWallet in under 2 minutes:
1) Open RockWallet → Buy/Sell (or Cash Out/Sell).
2) Select BSV. If BSV isn’t listed under Buy and/or Sell, the ramp isn’t currently available for BSV.
3) If BSV appears, pick Buy (and also try Sell/Cash Out). The app will show the provider name(s), supported fiat currency (likely USD), payment methods, fees, and limits.
4) Start the KYC flow and select your state (NY, TX, CA, DC, FL, WA, AZ). If your state isn’t supported, you’ll get a restriction message before you can proceed.
If you’d like, when the search tool is back, I can pull and deliver a precise, sourced list for:
- RockWallet: whether BSV buy/sell is live, which provider(s) they use, and explicit US state coverage (NY, TX, CA, DC, FL, WA, AZ).
- Exchanges listing BSV and which have direct fiat pairs (e.g., KRW, IDR) vs. crypto-only pairs (USDT/BTC), plus US residency restrictions.
Sorry for the hiccup—I’m ready to re-run the checks and send a clean table as soon as the lookup works again.