Changelog
what changed, when.

011.1.0

Current 2026-09 · app 1.1.0 · admin panel 1.1.0

Changed

• Safe defaults: on a fresh install the swap fee is off and every fee wallet is empty.
• The swap fee is capped at 2 % (200 bps) in the admin and in the app.
• Admin → Monetization has two fee wallets: an EVM wallet for 0x and 1inch swaps and a Solana wallet for Jupiter swaps. Jupiter pays the fee into the Solana wallet's token account for the token the user receives; that account must exist.
• Bridge fee, referral commission and bonus days, and Stripe PRO checkout are marked Not active in this version in the admin.
• The admin config address is now the ADMIN_CONFIG_URL build setting, empty by default (Remote Config only), instead of an address written in the code.
• The package no longer contains firebase_options.dart; flutterfire configure is required for both apps.
• The admin demo mode exists only in builds made with the demo build switch; there are no default demo credentials.

Fixed

• Jupiter (Solana) swap fee: the fee is now sent to your token account for the token the user receives. 1.0.0 sent the wallet address, which Jupiter rejects, so Solana swaps earned nothing.
• The Revenue screen counts a fee only when a fee was attached to a completed swap.
• The full test suite completes (two tests used to hang); flutter analyze reports no errors or warnings.
• Android builds no longer depend on a path from the author's machine.

Migration from 1.0.0

1. Config addressIf you had changed kAdminConfigUrl in lib/core/config/app_config.dart, move that address to ADMIN_CONFIG_URL in crypto_wallet/.env (how).
2. Firebase settingsKeep your own lib/firebase_options.dart in both apps, or run flutterfire configure again.
3. FeeIf your fee was above 2 %, set 2.0 % or lower and publish. To earn on Solana swaps, fill the Solana fee wallet and create its token accounts (how).
4. RedeployFunctions and rules, then release new app builds (How to update).

021.0.0 · 2026-09

App 1.0.0+9 · admin panel 1.0.0+1

• Flutter wallet for iOS, Android and web: EVM networks, Bitcoin, Solana, Tron and Sui; create and import wallets; send, receive, swap (0x and 1inch on EVM, Jupiter on Solana), bridge, buy; NFTs; Discover and dApp browser; WalletConnect v2; PRO subscription; price alerts; security center.
• Flutter web admin with 21 screens, from Overview to Publish Config.
• Firebase backend: rules and indexes, Remote Config template and 32 Cloud Functions for admin access with an authenticator, config publishing, push, fee records, PRO checks (App Store, Google Play, Stripe, crypto) and promo codes.
• Swap fee presets from Free to 2 % on 0x and 1inch routes, paid on-chain to your wallet.
• Fee wallet and prices ship empty; you set them in the admin.

Migration: none, first release.

03How to update

Keep the original package and your changes apart from day one, so a new version is a merge, not a rewrite:

cd superwallet               # the folder with crypto_wallet/ and crypto_wallet_admin/
git init
git add .
git commit -m "SUPER WALLET 1.0.0 (original)"
git branch vendor            # untouched copy of the original

1. Back upAdmin → Publish Config → Save Version Snapshot; commit your work.
2. Download the new versionCodeCanyon → your account → Downloads → SUPER WALLET → All files & documentation.
3. Unpack the new version on the vendor branch

   git checkout vendor
   # delete the old files (not .git), unzip the new version here
   git add -A
   git commit -m "SUPER WALLET <new version> (original)"
   git checkout main
   git merge vendor

4. Resolve conflictsUsually only in files you rebranded. Keep your values, take the new code.
5. Redeploy the backendRules, indexes and functions — not Remote Config, unless the entry says so.

   cd crypto_wallet
   firebase deploy --only firestore:rules,firestore:indexes,functions

6. Release the appRaise the build number, build, upload. For an important fix, set Minimum App Version in Admin → Remote Config once the new version is live.

Versions follow major.minor.patch: a patch fixes bugs, a minor adds features with safe defaults, a major may need migration steps, which are always listed here.