Documentation Index
Fetch the complete documentation index at: https://docs.ordsbot.com/llms.txt
Use this file to discover all available pages before exploring further.
Overview
OrdsBot uses a two-layer wallet architecture:- Sign-in wallet — Xverse, Unisat, or Leather — used to authenticate via BIP-322 message signing
- Bidding keys — derived in-memory from your seed phrase, used by the bot to sign bid messages
Authentication (BIP-322)
When you connect your wallet, OrdsBot follows a challenge-response flow:Key Derivation
The bidding bot requires keys in server memory to sign Satflow bid messages. These are derived from your seed phrase using standard Bitcoin derivation paths:| Key | Path | Purpose |
|---|---|---|
| Payment key | BIP84 (m/84’/0’/0’/0/0) | Signs bid messages, receives payments |
| Ordinals key | BIP86 (m/86’/0’/0’/0/0) | Taproot key for inscriptions |
What the bot uses your keys for
- Signing the Satflow bid message string:
- Signing PSBTs for auto-listing inscriptions (Taproot Schnorr signatures)
Bidding Wallet (Multi-sig)
Satflow uses a bidding wallet model where your bid collateral is held in a 2-of-2 or 2-of-3 multi-sig address. This is displayed in Settings after you derive your wallet. Fund this address to activate bidding.Security Notes
- The bot only needs your seed phrase once per server session
- Sessions use secure, signed tokens stored in server memory
- There is no password recovery = if you lose your seed phrase, you lose your wallet