Repository navigation
Withdrawal submission safety
The Harvester reserves a withdrawal claim and its rolling-cap charge in SQLite before contacting Kraken. Concurrent execution attempts cannot submit the same proposal twice. A timeout or interrupted audit leaves an unverified claim that blocks further bot withdrawals until an operator reconciles it. Historical failed rows are treated as unverified during migration, and the dashboard shows the hold.
Upgrade and recovery
Back up the harvest and operator databases using SQLite's online backup operation before migration. Reconcile withdrawal claims and approved execute commands against Kraken Funding before restarting the Harvester. The local claim-... and historical failed-... identifiers are not Kraken reference IDs. If reverting to v2.0.12 while any claim is unresolved, keep the Harvester stopped. See the withdrawal incident runbook and changelog.
The source release and GHCR image do not deploy the file-based NAS stack. No real withdrawal was performed during verification.