Actions11
Overview
This node enables sending raw transactions on an Ethereum Virtual Machine (EVM) compatible blockchain. It allows users to specify the recipient address, amount of native tokens (in Wei), optional data payload (such as encoded contract calls), and gas settings either automatically estimated or manually set. The node supports advanced transaction management options like manual nonce setting, retry attempts, and gas fee boosting for replacement transactions. It also offers the ability to only estimate gas usage without broadcasting the transaction.
Common scenarios where this node is beneficial include:
- Sending ETH or other native tokens directly to another address.
- Executing custom contract calls by providing encoded data.
- Testing gas costs before actual transaction submission.
- Managing complex transaction sending strategies with retries and nonce control.
Practical example:
- A user wants to send 0.1 ETH to a specific address with a custom encoded function call to a smart contract, while manually specifying gas fees and ensuring the transaction nonce is controlled to avoid conflicts.
Properties
| Name | Meaning |
|---|---|
| To Address | The recipient address for the raw transaction. |
| Amount (Wei) | Amount of native token to send in Wei (smallest unit). For example: 1 ETH = 1000000000000000000 Wei. |
| Data | Optional hexadecimal data payload for the transaction. Used for contract calls as the encoded function call. |
| Gas Settings | How gas settings should be determined. Options: - Auto (Estimated): Let the network estimate gas settings. - Manual: Set gas settings manually. |
| Gas Limit | Gas limit for the transaction (required if Gas Settings is Manual). |
| Max Fee Per Gas (Gwei) | Maximum fee per gas in Gwei (required if Gas Settings is Manual). |
| Max Priority Fee Per Gas (Gwei) | Maximum priority fee per gas in Gwei (required if Gas Settings is Manual). |
| Estimate Gas Only | Boolean flag to only estimate gas required without sending the transaction. |
| Transaction Management | Advanced transaction options: - Manual Nonce: Specify nonce manually. - Max Attempts: Maximum number of attempts to send the transaction. - Replacement Boost (%): Percentage increase for gas fees when replacing transactions. |
| Wallet Source | Choose which wallet to use: - Credential Wallet: Use wallet from credential settings. - Input Private Key: Provide a private key directly for this transaction. |
| Private Key | The private key to use for this specific transaction (with or without 0x prefix). Required if Wallet Source is "Input Private Key". |
Output
The node outputs JSON data representing the result of the raw transaction operation. This typically includes:
- Transaction hash identifying the submitted transaction.
- Status information about the transaction submission.
- If
Estimate Gas Onlyis enabled, the output will contain the estimated gas cost without sending the transaction. - Any error messages or failure details if the transaction could not be sent.
If binary data were involved (not applicable here), it would summarize the meaning accordingly, but this node focuses on JSON transaction results.
Dependencies
- Requires an EVM-compatible blockchain RPC URL and an API key credential that provides access to the blockchain node.
- Uses the ethers.js library for blockchain interaction.
- Requires a valid private key either from credentials or provided directly for signing transactions.
- No additional external services are explicitly required beyond the blockchain RPC endpoint.
Troubleshooting
- Invalid Private Key Error: If the private key provided is malformed or incorrect, the node throws an error indicating invalid private key. Ensure the key is correct and optionally prefixed with "0x".
- Gas Estimation Failures: When using auto gas estimation, the network might fail to estimate gas if the transaction data is invalid or the recipient address is incorrect. Try switching to manual gas settings with appropriate values.
- Nonce Conflicts: Transactions may fail due to nonce conflicts if multiple transactions are sent simultaneously. Use the manual nonce option or rely on the built-in nonce manager to handle this.
- Insufficient Funds: Transactions will fail if the wallet does not have enough native tokens to cover the amount plus gas fees.
- RPC Connection Issues: Ensure the RPC URL and API key credentials are correctly configured and the node can reach the blockchain network.