Skip to main content

Wallet Settings

Derive Wallet

Enter your seed phrase (12 or 24 words) to derive your bidding keys in server memory. The server derives:
  • Payment key (BIP84, bc1q…) — signs bid messages
  • Ordinals key (BIP86, bc1p…) — signs listing PSBTs
Your seed phrase is used only to derive keys into RAM. It is never stored. You need to re-enter it after a server restart.
After deriving, you’ll see your:
  • Payment address (bc1q…)
  • Ordinals address (bc1p…)
  • Satflow bidding wallet address

Ordinals Address Override

If you hold inscriptions at a different taproot address (e.g. from a hardware wallet), you can set a custom ordinals address in Settings. This does not affect key derivation.

API Keys

Satflow API Key

Required for all bidding and listing operations. Get yours by opening a ticket on the Satflow Discord. The key is stored encrypted in the database and used for all your task workers.

UniSat API Key

Optional. Required only if you want to use VWAP pricing for Rune tasks (UniSat order book data).

Telegram Notifications

Telegram notifications are coming soon. This section will be updated when the feature goes live.
Once available, you will configure a Telegram bot token and chat ID here to receive real-time alerts for fills, floor crashes, and errors.

Usage & Exposure

The Settings page shows your current usage:
MetricDescription
Active tasksRunning vs plan max
Total exposureSum of all active bid values
Max exposurePlatform limit (5M sats default)