Ethereum: Transaction executor icon

Ethereum: Transaction executor

Execute Ethereum transaction
Join our community

Overview

This node executes Ethereum blockchain transactions by sending signed transactions to a specified network. It is useful for automating interactions with Ethereum or compatible blockchains, such as transferring ETH, calling smart contract functions, or submitting custom calldata. Practical examples include:

  • Sending ETH payments programmatically.
  • Invoking smart contract methods with specific calldata and signatures.
  • Automating nonce management and gas limit settings for transaction submission.

Properties

Name Meaning
Blockchain Target blockchain network. Options include Ethereum Mainnet, various testnets (Sepolia, Holesky), Arbitrum, Optimism, Base, Linea, BNB Chain, and a Custom option. Default is Ethereum Sepolia testnet.
Custom RPC URL of a custom blockchain RPC endpoint. Required if "Custom" blockchain is selected.
Recipient Address The address that will receive the transaction.
Value Amount of ETH to send in the transaction, specified as a number with up to 8 decimal places.
Nonce Transaction nonce, used to order transactions from the sender's account.
Calldata Hexadecimal string representing the transaction calldata (e.g., encoded smart contract function call).
Signature Signature string authorizing the transaction.
Gas Limit Maximum amount of gas units the transaction can consume. Default is 21000.

Output

The node outputs an array of JSON objects, each containing a receipt field. This receipt holds the transaction receipt returned by the blockchain after the transaction is mined and confirmed. The receipt includes details such as transaction hash, status, gas used, logs, and block information.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential providing access to an Ethereum-compatible wallet private key.
  • Uses the ethers library to interact with the blockchain.
  • Connects to blockchain networks via default or custom RPC endpoints.
  • The user must configure appropriate credentials and optionally provide a custom RPC URL for better performance or reliability.

Troubleshooting

  • Common issues:
    • Incorrect or missing private key credential will cause authentication failures.
    • Using an invalid recipient address or malformed calldata may result in transaction rejection.
    • Insufficient funds or incorrect nonce values can cause the transaction to fail.
    • Default RPC endpoints are highly throttled; consider using a custom RPC URL to avoid rate limits.
  • Error messages:
    • Errors related to "invalid signature" indicate problems with the provided signature string.
    • "Nonce too low" or "replacement transaction underpriced" errors suggest nonce conflicts; ensure nonce is correctly managed.
    • "Insufficient funds" errors mean the wallet balance is too low to cover value plus gas fees.
  • To resolve these, verify all input parameters, ensure the private key has sufficient funds, and use reliable RPC endpoints.

Links and References

Discussion