Bankr Agent - Arbitrary Transactions

Submit raw EVM transactions with validated JSON fields across Ethereum-compatible chains.

80|30|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/BankrBot/claude-plugins --skill bankr-agent-arbitrary-transactions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Bankr Agent - Arbitrary Transactions
Source: https://github.com/BankrBot/claude-plugins/tree/main/bankr-agent/skills/bankr-arbitrary-transaction
Command: npx skills add https://github.com/BankrBot/claude-plugins --skill bankr-agent-arbitrary-transactions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Submitting raw EVM transactions manually is error-prone and slow; this capability provides a programmatic way to craft and send transactions with precise calldata, to addresses, values, and chain IDs.

Core Features & Use Cases

  • Submit raw EVM transactions with explicit to, data, value, and chainId.
  • Cross-chain support across Ethereum, Polygon, Base, and Unichain.
  • Validates input fields to prevent malformed transactions and failures.

Quick Start

Submit a raw transaction by providing a JSON object with to, data, value, and chainId.

Frequently Asked Questions about Bankr Agent - Arbitrary Transactions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I submit raw EVM transactions with custom calldata?

To submit raw EVM transactions, provide a JSON object containing the to address, hex data, wei value, and chainId to execute deterministic calldata interactions on compatible networks.

What is raw transaction submission and when do I need it for smart contracts?

Raw transaction submission is the process of sending EVM transactions by explicitly specifying calldata and target addresses, needed for precise cross-chain contract interactions and deterministic execution.

Can I submit raw transactions across different EVM chains like Polygon and Base?

Yes, cross-chain raw transaction submission supports Ethereum-compatible networks including Ethereum, Polygon, Base, and Unichain by validating the specified chainId parameter.

How do I format calldata and addresses for EVM transaction submission?

Formatting calldata and addresses for EVM transaction submission requires strict hex encoding for data, proper address formatting, and wei-value validation to prevent malformed transactions.

Why does my raw EVM transaction submission fail with invalid inputs?

Raw EVM transaction submission fails when input validation rejects non-hex calldata, improperly formatted addresses, incorrect wei values, or unsupported chain IDs to ensure safe traceable submissions.