Farcaster: Transaction builder icon

Farcaster: Transaction builder

Generates Farcaster frame transaction object
Join our community

Overview

This node generates a Farcaster frame transaction object for blockchain interactions. It is designed to build transaction data that can be sent to various EVM-compatible blockchains by specifying the chain, recipient address, method, value, and additional transaction details.

Common scenarios where this node is beneficial include:

  • Preparing transactions for smart contract calls on Ethereum or compatible chains.
  • Constructing raw transaction objects for further processing or sending via other nodes or services.
  • Encoding calldata with optional ABI definitions to interact with complex contracts.

Practical example:

  • You want to send ETH or call a smart contract function on Polygon. This node lets you specify the target chain, recipient address, method type, ETH value in WEI, and optionally provide calldata and ABI to encode the transaction properly.

Properties

Name Meaning
Blockchain The target blockchain network identified by its CAIP-2 chain ID. Options include Ethereum, Base, Optimism, Polygon, Gnosis, Zora, Degen, and several testnets.
Recipient The address of the transaction recipient (e.g., a wallet or smart contract address).
Method The method ID to identify the type of transaction request. Default is eth_sendTransaction.
Value The amount of ETH to send with the transaction, represented in WEI (smallest ETH unit).
Additional Fields A collection of optional fields:
- Data: Transaction calldata as a string.
- ABI: JSON array defining the contract ABI including encoded function types and error types.
- Attribution: Boolean flag to include calldata attribution suffix.

Output

The node outputs an array of JSON objects, each representing a transaction object with the following structure:

{
  "chainId": "string",        // Blockchain CAIP-2 chain ID
  "method": "string",         // Method ID for the transaction (e.g., eth_sendTransaction)
  "attribution": true|false,  // Whether calldata attribution suffix is included
  "params": {
    "abi": [],               // JSON ABI array for encoding/decoding
    "to": "string",          // Recipient address
    "data": "string",        // Calldata string
    "value": "string"        // ETH value in WEI
  }
}

This output can be used downstream to submit transactions or further process them.

Dependencies

  • No external API calls or services are made directly by this node.
  • Requires proper configuration of blockchain interaction nodes or services downstream to handle the generated transaction objects.
  • No special environment variables or credentials are required by this node itself, but subsequent nodes submitting transactions will require appropriate blockchain access credentials.

Troubleshooting

  • Invalid recipient address: Ensure the recipient field contains a valid blockchain address format for the selected chain.
  • Incorrect chainId: Using an unsupported or mistyped chain ID may cause issues downstream; verify the CAIP-2 chain ID matches the intended network.
  • Malformed ABI JSON: If providing ABI, ensure it is valid JSON and correctly describes the contract functions and errors.
  • Empty or invalid calldata: If the transaction requires calldata, ensure the data field is correctly encoded.
  • Value format: The value must be a string representing a number in WEI; incorrect formatting may cause transaction failures.

Links and References

Discussion