Configuration
one document you host.

01Two places, one rule

02Your domain (TIDE_HOST)

Default: the placeholder app.example.com, which is not a real site. Pass your own host (no https://) on every run and build:

flutter run -d chrome --dart-define=TIDE_HOST=app.example.com
flutter build web --release --dart-define=TIDE_HOST=app.example.com

If you set Website, Terms URL or Privacy URL in the operator panel, the app uses those and ignores the derived value. The support address defaults to support@<TIDE_HOST>; set Support email in the panel (and so in your hosted file) to use another one. If your host has no /terms or /privacy page, build with --dart-define=TIDE_TERMS_URL=… and --dart-define=TIDE_PRIVACY_URL=…; --dart-define=TIDE_SUPPORT_EMAIL= (empty) shows no support address at all. tool/build_web_demo.sh uses all three for the public demo.

03The layers

Weakest first. The strongest layer that supplies a value wins that value, leaf by leaf (lib/core/config/config_layers.dart). A hosted value always outranks a value stored on a device.

Operator panel → In force right now lists every value the app is running on and which layer it came from.

04The document

This is the full shape, with the shipped defaults. Operator panel → Copy as JSON gives you the same shape with your values (only the ones you changed).

{
  "config_version": 1,
  "app_name": "TIDE",
  "tagline": "Swap on Solana. See what other wallets did.",
  "support_email": "",
  "website_url": "",
  "terms_url": "",
  "privacy_url": "",
  "announcement": "",
  "min_app_version": "",
  "default_slippage_pct": 1.0,
  "admin_locked": false,
  "flags": {
    "swap_enabled": true,
    "feed_enabled": true,
    "watchlist_enabled": true,
    "profiles_enabled": true,
    "realised_standings_enabled": false,
    "push_enabled": false,
    "evm_chain_enabled": false,
    "copy_execution_enabled": false
  },
  "fee": {
    "fee_enabled": false,
    "fee_bps": 0,
    "min_fee_usd": 0,
    "solana_fee_wallet": "",
    "evm_fee_wallet": ""
  },
  "keys": {
    "helius_api_key": "",
    "zerox_api_key": "",
    "solana_rpc_url": "",
    "evm_rpc_url": ""
  },
  "extra_restricted_regions": []
}

An unknown flag key is ignored. A region code that is not two letters is dropped. Every rate is clamped to its code cap on the way in (caps).

05Feature switches

06Endpoints and keys

07Publishing your configuration

Your users' builds have no operator panel. They read one file you host. No code change is needed.

1. Make your operator buildflutter run -d chrome --dart-define=TIDE_OPERATOR_PASSCODE=choose-your-own (Operator panel).
2. Set everythingIn the operator panel, then press Copy as JSON.
3. Host itSave the text as a file, for example tide-config.json, on any HTTPS static host you control (your host's fees apply). Only https URLs are accepted.
4. Build the user app with the URL

   flutter build appbundle --release \
     --dart-define=TIDE_HOST=app.yourdomain.com \
     --dart-define=TIDE_CONFIG_URL=https://app.yourdomain.com/tide-config.json

   The same two defines go on flutter build ipa and flutter build web. Do not pass TIDE_OPERATOR_PASSCODE here.
5. Change settings laterEdit in your operator build, Copy as JSON, replace the hosted file. Every install reads it on its next start and caches the last good copy.

Optional: "admin_locked": true in the hosted file makes the panel of an operator build read-only and ignores its stored values, which is useful when several people hold operator builds. Firestore or Remote Config can replace the file: pass your own fetchRemote to AdminConfigService in lib/main.dart (see docs/FIREBASE-SETUP.md in the source).

08Push notifications and Firebase (optional)

TIDE works without Firebase and ships no Firebase files. Push is a keyless hook: PushNotificationService in lib/core/notifications/push_notification_service.dart accepts a tokenProvider you supply. To use Firebase: create your own project, add the firebase_core and firebase_messaging packages, run flutterfire configure, initialise Firebase in lib/main.dart, and pass tokenProvider: () => FirebaseMessaging.instance.getToken(). Sending pushes needs a server or the Firebase console; TIDE includes none. These steps are from docs/FIREBASE-SETUP.md and were not run for these docs.

If you store config in Firestore, keep it read-only for clients and never store anything that links a person or device to a wallet address.

09Where data is stored

There is no server and no database. Nothing is uploaded.