![]() Also, in a case where a transaction consistently fails to be mined, Defender may replace it by a no-op (a transaction with no value or data) in order to advance the sender account nonce. This means that, if you monitor your transaction only via getTransactionReceipt(tx.hash) calls to a node, you may not get the latest info if it was replaced.ĭefender may replace a transaction by increasing its gas price if it has not been mined for a period of time, and the gas price costs have increased since the transaction was originally submitted. The query function is important to monitor the transaction status, since Defender may choose to resubmit the transaction with a different gas price, effectively changing its hash. The transaction information will be stored for 30 days. sendTransaction ( ) ĭefender will update the transaction status every minute, marking it as confirmed after 12 confirmations. Then use them to create a new Relayer instance in your code:Ĭonst tx = await relayer. Start by creating a new relayer using either the Defender console or API for a network of your choice. This library also includes an ethers.js signer and a web3.js provider, that uses the Relay to sign and broadcast its transactions. ![]() You can send transactions via your relayers by POSTing to the Defender HTTP API, or using this library. Each relayer has its own secure private key, and a set of API keys. Relay Signerĭefender Relay Signer lets you send transactions to any supported network using private relayers. This can be fetched via the listKeys method above and is also available in the response on key creation.ĭeletion of a relayer (not just a key) is only available via the Defender console. Note: second argument to deleteKey is the keyId (contains hyphens), not the apiKey.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |