Skip to main content

Module fee

Module fee 

Source
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§

RetryArgs
transferCall
Function with signature transfer(address,uint256) and selector 0xa9059cbb.
transferReturn
Container type for the return parameters of the transfer(address,uint256) function.
transferWithMemoCall
Function with signature transferWithMemo(address,uint256,bytes32) and selector 0x95777d59.
transferWithMemoReturn
Container type for the return parameters of the transferWithMemo(address,uint256,bytes32) function.

Enums§

Command

Functions§

run
validate_fee_calldata
Verify that the calldata in payload_to_sign encodes an ERC-20 transfer or TIP-20 transferWithMemo call with recipient, amount, and memo matching the server’s payment parameters.