Multisig_Transactions_Destroy_2
Removes the queued but not executed multi-signature transaction associated with the given Safe transaction hash. Only the proposer or the delegate who proposed the transaction can delete it. If the transaction was proposed by a delegate, it must still be a valid delegate for the transaction proposer. An EOA is required to sign the following EIP-712 data: ```python { "types": { "EIP712Domain": [ {"name": "name", "type": "string"}, {"name": "version", "type": "string"}, {"name": "chainId", "type": "uint256"}, {"name": "verifyingContract", "type": "address"}, ], "DeleteRequest": [ {"name": "safeTxHash", "type": "bytes32"}, {"name": "totp", "type": "uint256"}, ], }, "primaryType": "DeleteRequest", "domain": { "name": "Safe Transaction Service", "version": "1.0", "chainId": chain_id, "verifyingContract": safe_address, }, "message": { "safeTxHash": safe_tx_hash, "totp": totp, }, } ``` `totp` parameter is calculated with `T0=0` and `Tx=3600`. `totp` is calculated by taking the Unix UTC epoch time (no milliseconds) and dividing by 3600 (natural division, no decimals)
Multisig_Transactions_Destroy_2 is an example object payload from Safe (Gnosis Safe), with 8 top-level fields. It illustrates the shape of data this provider's APIs accept or return.