CLI Client: tidal auction

tidal auction prepares and optionally broadcasts direct auction-management actions through the API.

Subcommands

• deploy: create a new auction from the configured factory
• enable-tokens: queue token enable calls for an auction
• settle: resolve an active lot when it is settleable

Common Invocations

Deploy a new auction:

tidal auction deploy \
  --want 0xWant \
  --receiver 0xReceiver \
  --starting-price 1234

Enable discovered tokens for an auction:

tidal auction enable-tokens 0xAuction

Add one extra token explicitly:

tidal auction enable-tokens 0xAuction --extra-token 0xToken

Settle an auction:

tidal auction settle 0xAuction
tidal auction settle 0xAuction --token 0xActiveToken
tidal auction settle 0xAuction --sweep

Broadcast one of those actions:

tidal auction settle 0xAuction --broadcast --sender 0xYourAddress --account wavey3

Important Flags

Shared across the mutating auction commands:

• --broadcast
• --bypass-confirmation
• --sender
• --account
• --keystore
• --password-file
• --json

Subcommand-specific flags:

• deploy: --want, --receiver, --starting-price, optional factory and governance overrides
• enable-tokens: --extra-token
• settle: --token, --sweep

Behavior Notes

These commands use the same prepare and audit model as tidal kick:

1. the API prepares the action and records an audit row
2. the CLI client shows a review panel
3. the CLI client signs and broadcasts locally
4. the CLI client reports the broadcast and receipt back to the API

That means the API owns the action history while the CLI client keeps local control of the wallet.