bankr-arbitrary-transaction_skill

Overview

This skill submits raw EVM transactions with explicit calldata to supported chains. It accepts a JSON object containing to, data, value, and chainId fields and forwards the prepared transaction for execution. Use it when you need direct calldata execution, send ETH/ERC20 transfers via calldata, or submit signed transaction payloads programmatically.

How this skill works

You provide a JSON transaction object with the target address (to), calldata (data), value in wei (value), and numeric chainId. The skill validates the address, calldata format, value string, and that the chainId is supported, then constructs and submits the raw EVM transaction to the target chain. If submission fails, it returns validation errors or on-chain revert diagnostics when available.

When to use it

• Submit a raw transaction JSON payload to be executed on-chain
• Execute arbitrary contract calldata (function calls) directly
• Send native token value alongside calldata (ETH, MATIC, etc.)
• Programmatically automate contract interactions across supported chains
• Test calldata encoding or debug transaction reverts

Best practices

• Always validate the to field is 0x + 40 hex characters before submission
• Prefix calldata with 0x; use "0x" for empty calldata
• Provide value as a string in wei (use "0" if none)
• Confirm chainId is one of the supported IDs (1, 137, 8453, 130)
• Ensure the sending wallet has enough native balance for gas + value

Example use cases

• Call an ERC20 transfer method by providing the contract address and encoded transfer calldata
• Approve an allowance by executing approve calldata on a token contract
• Send 1 ETH with empty calldata to a recipient address using chainId 1
• Execute a custom contract function on Base (chainId 8453) with encoded parameters
• Submit transactions from CI/CD scripts or backend services that manage on-chain workflows