Recovery and manual commands
Restart with the same deployment, identities, guest, and durable state. Restore infrastructure and inspect the recorded phase before intervening. Do not clear state or run another owner.
Operating modes
Section titled “Operating modes”| Condition | Response |
|---|---|
| Recovery-only mode | Fresh bids pause; committed work continues and may clear the condition. |
| Recorded bond loss | Investigate and acknowledge every loss before resuming bids. |
| Invalid state, nonce invariant, durability failure, or worker panic | Repair the cause before restarting. |
Ethereum ambiguity
Section titled “Ethereum ambiguity”Check canonical receipts and rebroadcast the exact persisted signed bytes through approved private paths. A null receipt, nonce too low, or acknowledgement alone does not resolve the transaction. There is no same-nonce fee bump or cancellation; providers must include valid reverting transactions.
Terminal Monero payments
Section titled “Terminal Monero payments”Ethereum completion does not resolve a possibly relayed Monero payment. Keep its reservation and use normal recovery first.
Exceptional abandonment requires a stopped runner, the exact stored txid, current absence and unspent-input checks, and explicit acceptance of delayed-rebroadcast risk. The solver persists thawing before releasing the reservation.
Command reference
Section titled “Command reference”Pass --config path/to/solver.toml before each subcommand. Stop run before manual commands, including diagnostics. Replace the uppercase identifiers with recorded values.
chainjump-solver command |
Effect |
|---|---|
check-config |
Validate configuration without network access. |
run |
Discover and execute the continuous workflow; can spend funds. |
status SWAP_ID |
Inspect the recorded swap. |
preflight SWAP_ID BID_XMR |
Run mandatory checks without bidding; amount is nominal XMR. |
bid SWAP_ID BID_XMR |
Resume an already signed bid; fresh manual bids are prohibited. |
confirm-award SWAP_ID |
Reconcile the winner and confirmation depth. |
prepare-payment SWAP_ID |
Revalidate the payment reserved before bidding. |
relay-payment SWAP_ID |
Relay the exact prepared payment. |
confirm-payment SWAP_ID |
Reconcile payment inclusion and wallet/daemon data. |
build-witness SWAP_ID |
Build the canonical witness at its managed path. |
settle SWAP_ID |
Sign/recover, broadcast, and confirm settlement. |
resume-bidding --acknowledge-loss SWAP_ID |
Acknowledge an investigated bond loss; all losses must be acknowledged. |
recover-terminal-payment SWAP_ID |
Inspect and recover a terminal payment. |
recover-terminal-payment SWAP_ID --abandon PAYMENT_TXID --acknowledge-delayed-rebroadcast-risk |
Explicit exceptional abandonment after the enforced checks. |
chainjump-prover command |
Effect |
|---|---|
account |
Inspect the configured requester through the network. |
submit SWAP_ID |
Submit/reconcile proof work; can incur a paid request. |
resume SWAP_ID |
Continue proof recovery; can make allowed paid attempts. |
adopt-request SWAP_ID REQUEST_ID |
Associate an existing request after domain checks; does not create a new request. |
Do not use run --deployment-test-hold-after-bid in production operation. It is a harness control that deliberately pauses after bid confirmation.
Durable storage failures
Section titled “Durable storage failures”State replacement uses file and directory fsync. Three exhausted post-rename directory-sync retries poison further access and stop the process. Repair storage first; preserve newer state and unknown artifacts. Reconcile external transactions before restoring any older backup.