Server Operator: tidal-server kick

tidal-server kick evaluates and optionally executes kick candidates directly on the server host.

Subcommands

• inspect: explain why candidates are ready, skipped, or deferred
• run: evaluate candidates once and optionally broadcast
• daemon: loop continuously and evaluate on an interval

Common Invocations

Inspect the current shortlist:

tidal-server kick inspect

Run one evaluation pass with explanations:

tidal-server kick run --explain

Broadcast from the server host:

tidal-server kick run --broadcast --sender 0xYourAddress --account wavey3

Run continuously:

tidal-server kick daemon --broadcast --interval-seconds 300 --sender 0xYourAddress --account wavey3

Important Flags

• --source-type
• --source
• --auction
• --limit
• --broadcast
• --verbose
• --explain
• --require-curve-quote and --allow-missing-curve-quote
• --json

The run and daemon subcommands also use the shared wallet flags:

• --sender
• --account
• --keystore
• --password-file

When To Use This Instead Of tidal kick

Use tidal-server kick when:

• the server itself owns the broadcast wallet
• you want a server-local daemonized kicker
• you are debugging shortlist behavior directly against the shared database

For remote human-operated execution against the control plane, prefer tidal kick.