TIDE docs
 v0.1.0
Live 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 pubspec.yaml version 1.0.0+1. First release.

  • Self-custodial Solana wallet for iOS, Android and web: create and import (BIP-39), AES-256-GCM vault in platform secure storage, SOL and SPL balances, send, receive.
  • Jupiter swaps with slippage control and the app fee shown before confirm.
  • Feed of followed wallets (up to 25), classified from on-chain balance changes; profiles; realised standings; local notification centre.
  • Operator panel inside the app with four configuration layers, validation, code caps, Copy as JSON and admin_locked.
  • Swap fee (off by default, max 200 bps), 1–2 tier referral programme, 1–2 band volume cashback, local payout ledger with CSV export.
  • Copy execution module, off by default and region-gated.
  • Light and dark themes.

Known limits

  • Base (EVM) is scaffolded without a quote source: evm_chain_enabled, the EVM fee wallet and the 0x key have no effect.
  • The Helius API key field is stored but not used; use the Solana RPC URL.
  • No QR scanner for addresses and no localisation.
  • On the web build SPL balances need your own RPC endpoint.

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 tide                   # your project folder
git init
git add .
git commit -m "TIDE 1.0.0 (original)"
git branch vendor          # untouched copy of the original
  1. Back upOperator panel → Copy as JSON and keep the file; commit your work.
  2. Download the new versionCodeCanyon → your account → Downloads → TIDE.
  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 "TIDE <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. Check and releaseflutter pub get, flutter analyze, flutter test, then raise the build number and release. For an important fix, set Minimum app version 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.