Skip to main content

​
How Bidding Works

The OrdsBot bidding engine runs as a background worker for each active task. Every cycle (default 30 seconds) it:
The bot uses Satflow’s bidding wallet model — your sats are held in a multi-sig address and collateral is locked per bid. When a bid is filled, Satflow transfers the inscription to your ordinals address.

​
Bid Types

​
Collection Bids (default)

Bid on any item in a collection. The floor price for the collection is fetched from Satflow’s API and used as the price reference.

​
Trait Bids

Bid on items with a specific trait (e.g. Background: Gold). Trait bids ignore the collection floor as the reference — instead you set your own fixed or percent range.
Trait bids require fetching the collection’s trait data. OrdsBot caches this automatically when you create a trait task.

​
Supported Asset Types

​
Bid Cycle Frequency

The default cycle interval is 30 seconds. You can customize this per task with loopSeconds. Lower values use more API quota.

​
Bid Expiry

Satflow bids have a configurable expiry. The default is 16 minutes, which means the bot refreshes all bids roughly twice before they expire. You can change the expiry per task.
Short expiry (e.g. 5 min) = more API calls, always fresh prices. Long expiry (e.g. 60 min) = fewer calls, bids may lag the market.