Arbitrary Transaction Submission
Submit raw EVM transactions with explicit calldata to any supported chain.
JSON Format
{
"to": "0x...",
"data": "0x...",
"value": "0",
"chainId": 8453
}
| Field |
Type |
Description |
to |
string |
Target contract address (0x + 40 hex chars) |
data |
string |
Calldata to execute (0x + hex string) |
value |
string |
Amount in wei (e.g., "0", "1000000000000000000") |
chainId |
number |
Target chain ID |
Supported Chains
| Chain |
Chain ID |
| Ethereum |
1 |
| Polygon |
137 |
| Base |
8453 |
| Unichain |
130 |
Prompt Examples
Submit a raw transaction:
Submit this transaction:
{
"to": "0x1234567890abcdef1234567890abcdef12345678",
"data": "0xa9059cbb000000000000000000000000recipient00000000000000000000000000000000000000000000000000000000000f4240",
"value": "0",
"chainId": 8453
}
Execute calldata on a contract:
Execute this calldata on Base:
{
"to": "0x833589fcd6edb6e08f4c7c32d4f71b54bda02913",
"data": "0x095ea7b30000000000000000000000007a250d5630b4cf539739df2c5dacb4c659f2488dffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff",
"value": "0",
"chainId": 8453
}
Send ETH with calldata:
Submit transaction with value:
{
"to": "0xRecipientAddress...",
"data": "0x",
"value": "1000000000000000000",
"chainId": 1
}
Validation Rules
| Field |
Validation |
to |
Must be 0x followed by exactly 40 hex characters |
data |
Must start with 0x, can be "0x" for empty calldata |
value |
Wei amount as string, use "0" for no value transfer |
chainId |
Must be a supported chain ID |
Common Issues
| Issue |
Resolution |
| Unsupported chain |
Use chainId 1, 137, 8453, or 130 |
| Invalid address |
Ensure 0x + 40 hex chars |
| Invalid calldata |
Ensure proper hex encoding with 0x prefix |
| Transaction reverted |
Check calldata encoding and contract state |
| Insufficient funds |
Ensure wallet has enough ETH/MATIC for gas + value |
