SUPER WALLET docs
 v1.0.0
Wallet demo Admin demo Get help
● Reference · Versions

Changelog
what changed, when.

Every release, newest first. Read the entry for your target version before you update.

011.0.0 · 2026-09

Current 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.

02How 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. 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
  3. Resolve conflictsUsually only in files you rebranded. Keep your values, take the new code.
  4. 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
  5. 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.