Skip to main content

Module escalate

Module escalate 

Source
Expand description

taskfast escalate — the poster’s on-chain dispute path (taskfast#2044).

After a Tier 1 or Tier 2 remedy fails, the dispute moves to the poster’s own wallet: TaskFast holds no key that can sign dispute(bytes32).

  • escalate reject-remedy <task_id> → POST /tasks/{id}/dispute/reject-remedy moves a dispute with a failed remedy to “awaiting the poster’s signature”.
  • escalate sign <task_id> → GET /tasks/{id}/dispute/signing-params, then signs and broadcasts ArbitratedEscrow.dispute(escrowId) from the poster’s keystore. Every value comes from the server; the CLI computes none.

The dispute counts as signed only when the server’s reconciler sees the finalized EscrowDisputed log, so output says “submitted”, never “disputed”. The CLI never compares its own clock with escalation_deadline: with lapse_pending true it warns and still sends, because the server accepts a signature until it records the lapse.

Refuse-to-sign guards (all before any transaction; signing safety is the CLI’s one unique job, so these deliberately do not trust the server blindly):

  1. keystore address ≠ a non-nil poster_wallet_address;
  2. chain_id ≠ the configured network’s chain id, or ≠ the RPC node’s;
  3. task_escrow_contract / escrow_id malformed, or the contract is zero;
  4. keystore address ≠ --wallet-address / configured wallet address.

--dry-run runs guards 1–4 except the node check (it opens no RPC).

escalate timeout-resolve <task_id> is the worker’s fallback when the arbitrator never rules: once disputedAt + DISPUTE_TIMEOUT (120 days) has passed on a Disputed escrow, anyone may send timeoutResolveDispute. Inputs are the task’s own escrow_id + settlement_domain (party-gated, so the worker can read them; venue-scoped, so a zone escrow is addressed correctly, gh#111) and the chain itself: escrow state, disputedAt, DISPUTE_TIMEOUT and the latest block time, which is what the contract compares, never the local clock. It refuses, sending nothing, on a wrong chain, a non-Disputed escrow, or a deadline still ahead. --dry-run makes read-only RPC calls so it can evaluate those refusals. The CLI does not say who gets paid (the contract decides by who raised the dispute) and writes nothing to the server: the reconciler mirrors the EscrowDisputeTimedOut log.

Structs§

RejectRemedyArgs
SignArgs
TimeoutResolveArgs
Same wallet/RPC flags as SignArgs; the task must be one you are a party to.

Enums§

Command

Functions§

run