What problem does it solve? Internet Computer canisters cannot natively reach Ethereum or other EVM chains, and wiring up individual RPC providers with API keys, consensus handling, and cycle accounting is error-prone. This Skill shows how to use the EVM RPC canister and the evm_rpc_client crate to make consensus-verified JSON-RPC calls from Rust canisters without bridges, oracles, or API keys. ## Core Features & Use Cases - Typed and raw JSON-RPC calls: Query balances, blocks, transaction receipts, and logs using the typed evm_rpc_client API or raw JSON-RPC payloads. - Multi-provider consensus: Fan requests out to providers like Alchemy, Ankr, and PublicNode with configurable threshold consensus to tolerate provider disagreement. - ERC-20 reads and signed transactions: Read token balances via eth_call and broadcast pre-signed transactions with eth_sendRawTransaction. - Use Case: Build a Rust canister that checks a user's ETH balance on mainnet, reads their USDC balance on Arbitrum, and submits a threshold-ECDSA-signed transaction, all through one system canister. ## Quick Start Ask the AI to add an EVM RPC integration to your Rust canister that fetches the latest Ethereum block using the evm_rpc_client crate with threshold consensus.