Overview
This node generates Ethereum transaction data ready to be signed and sent. It is useful for preparing raw transactions on various Ethereum-compatible blockchains, including mainnets and testnets. The node supports sending native cryptocurrency (ETH or equivalent) and invoking smart contract methods by encoding the call data according to a provided ABI.
Typical use cases include:
- Preparing ETH transfers to recipient addresses.
- Building transactions that call smart contract functions with specified arguments.
- Generating signed transaction payloads for later broadcasting or inspection.
For example, you can build a transaction to send 0.1 ETH to a wallet address on the Ethereum Sepolia testnet, or prepare a contract method call on Arbitrum mainnet by specifying the contract ABI, method name, and parameters.
Properties
| Name | Meaning |
|---|---|
| Blockchain | Target blockchain network. Options include Ethereum Mainnet, Ethereum Sepolia, Ethereum Holesky, Arbitrum Mainnet, Arbitrum Sepolia, Optimism Mainnet, Optimism Sepolia, Base Mainnet, Base Sepolia, Linea Mainnet, Linea Sepolia, BNB Chain Mainnet, BNB Chain Testnet, or Custom RPC endpoint. Default is Ethereum Sepolia testnet. |
| Custom RPC | Custom blockchain RPC endpoint URL. Required if "Custom" blockchain option is selected. |
| Recipient Address | The address of the transaction recipient. For ETH transfers, this is the destination wallet; for contract calls, this is typically the contract address unless overridden in additional fields. |
| Value | Amount of ETH (or native token) to send with the transaction, specified as a number with up to 8 decimal places. |
| Additional Fields | Optional extra parameters: |
| - ABI | JSON array representing the smart contract's ABI. Must include the method signature and optionally error types. Used to encode contract method calls. |
| - Smart Contract Address | Address of the smart contract to interact with. |
| - Smart Contract Method | Name of the smart contract method to invoke. |
| - Smart Contract Method Arguments | List of argument values for the contract method call. The order and number must match the ABI definition. |
Output
The node outputs an array with one item per input. Each output item contains a json object with the following fields:
recipient: The recipient address of the transaction.signature: The signed transaction serialized as a hex string, ready to be broadcasted to the network.nonce: The transaction nonce used for this account.data: The encoded transaction data payload. This is either empty for simple ETH transfers or contains the encoded smart contract method call.value: The amount of ETH (or native token) to send.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential providing access to an Ethereum-compatible blockchain node (RPC provider).
- Uses the
etherslibrary for transaction building, signing, and encoding. - The node internally creates a wallet instance from the private key in the credentials to sign transactions.
- The default RPC endpoints are highly throttled; users are encouraged to provide custom RPC URLs for better reliability.
Troubleshooting
- Invalid RPC endpoint or network errors: Ensure the selected blockchain or custom RPC URL is correct and accessible.
- Incorrect private key or missing credentials: The node requires a valid private key credential to sign transactions.
- ABI encoding errors: If the ABI, method name, or arguments do not match, encoding will fail. Verify the ABI JSON and method signature carefully.
- Nonce issues: Nonce is fetched automatically but may cause conflicts if multiple transactions are sent rapidly. Consider managing nonces externally if needed.
- Value parsing errors: The value must be a valid number convertible to Ether units; otherwise, parsing will fail.