Expand description
taskfast fee retry — re-attempt a failed submission-fee charge.
Wraps GET /tasks/{id}/retry-fee and POST /tasks/{id}/retry-fee.
Since 2026-11-01 the server requires the poster’s freshly signed fee transfer
(a 0x-hex signed ERC-20 transfer, or the hash of one the poster already broadcast)
in the request body; the original voucher cannot be reused.
When --submission-fee-voucher is omitted, the CLI fetches the payment parameters
(GET /tasks/{id}/retry-fee), validates the network allowlists, verifies that
the calldata matches the payment parameters, signs and broadcasts the payment
using the poster’s keystore wallet under the per-wallet lock, and submits the
transaction hash to the server.
If the broadcast succeeds but the server submission fails, the transaction hash
is persisted in .taskfast/ via StateStore. Re-running the command reuses
the broadcast transaction hash rather than paying twice.
When --submission-fee-voucher is passed, the CLI passes the value through unchanged.
409 retry_not_needed / retry_in_progress / fee_executed_unmatched surface with
their stable codes.
Structs§
- Retry
Args - transfer
Call - Function with signature
transfer(address,uint256)and selector0xa9059cbb. - transfer
Return - Container type for the return parameters of the
transfer(address,uint256)function. - transfer
With Memo Call - Function with signature
transferWithMemo(address,uint256,bytes32)and selector0x95777d59. - transfer
With Memo Return - Container type for the return parameters of the
transferWithMemo(address,uint256,bytes32)function.
Enums§
Functions§
- run
- validate_
fee_ calldata - Verify that the calldata in
payload_to_signencodes an ERC-20transferor TIP-20transferWithMemocall with recipient, amount, and memo matching the server’s payment parameters.