FAQ
short answers.
The questions buyers ask most. Setup errors are in Troubleshooting.
01Frequently asked
Do I need a server or a database?
No. SOLSCOPE is a client app. The web build is a static folder, and the optional admin config is one JSON file you can host anywhere.
Can I see or recover my users' keys?
No. External wallets sign on their side, and the in-app account is encrypted on the user's device. If a user loses both the device and the recovery phrase, nobody can restore it.
Does the product ship with API keys?
No. Helius, QuickNode, Alchemy and Birdeye forbid sublicensing a key. The app runs on keyless sources and shows which figure a key would unlock.
Do I need Firebase?
No. There is no Firebase dependency. If you already use Remote Config, the admin JSON keys are shaped so you can serve an export of it (docs/FIREBASE.md).
Which fee should I choose?
A business decision. The fee is hard-capped at 100 bps (1 %) in code and the console flags rates above 50 bps; common front ends sit between 20 and 85 bps. A fresh build starts with no fee and you can change it at any time.
Why did no fee arrive on some swaps?
Either the route could not carry a platform fee, the fee account was not a token account for that mint, or the fee was off on that device. See Setting up earnings.
Is there a referral programme?
No, on purpose: the admin contract has no field that maps a code to a wallet.
Does it trade automatically?
No. Alerts notify; nothing in the code places an order on anyone's behalf.
Which wallets can users connect?
Phantom, Solflare and Backpack on Android and iOS: the wallet app opens, the user approves, and the wallet returns to SOLSCOPE through the solscope:// link. On Android, iOS and macOS users can also create an in-app wallet (a 12-word recovery phrase, shown once and confirmed) or import one. The web build reads and previews but does not sign.
Is there a macOS or Windows app?
The documented targets are web, iOS and Android. The macos/ folder builds, with outbound network access granted in both entitlement files; the in-app wallet on macOS keeps its key in the login keychain, which needs no Keychain Sharing capability or development team. Sign with your own team only when you distribute the Mac app. Linux and Windows are not generated.
How many terminals may I publish?
Your licence decides. Read the Regular or Extended licence terms on the CodeCanyon item page.
Where do I ask for help?
On the CodeCanyon item page: the Support tab or the comments. See Support.