Pre-Sign Recipient Verifier

WHAT IT DOES

Pre-Sign Recipient Verifier takes any transaction or address and tells you exactly who or what the recipient is before you sign. It reads the recipient address, checks whether it's an externally owned account (EOA), a known protocol, a verified contract, an unverified contract, or a suspicious contract. It analyzes contract bytecode for red flags like self-destruct, ownership functions, proxy patterns, and pause/unpause. It also detects if the recipient has transaction history or is brand new. An AI layer then translates the technical data into plain English—explaining who the recipient is, whether it's a known entity, and whether anything looks suspicious. You get this before your wallet ever asks for a signature, so you know who you're sending funds to.

HOW TO USE

Connect your EVM wallet using the BotGentz wallet bridge. Select the network matching your transaction. Paste a transaction hash to fetch and verify its recipient, or paste a recipient address to inspect it directly. Click "Verify"—the tool fetches the recipient's bytecode, analyzes its type, checks for known labels, flags risks, and generates an AI explanation. Results show you the recipient, its type (EOA, protocol, unverified contract, etc.), value, function call (if any), risk level, flags, and a plain-English explanation of who the recipient is. No transaction is ever submitted—this tool is read-only and free.

TECHNICAL MECHANISM

The app uses the injected BGWallet bridge to access the EVM provider via ethers.js v5.7.2. Transaction hashes are fetched via provider.getTransaction(), returning the full transaction object. Recipient addresses are resolved using provider.getCode() to fetch bytecode. Bytecode analysis detects contract types: EOA (code is 0x or empty), known protocols (matched against a local label database of Uniswap, USDC, BAYC, OpenSea, etc.), proxy patterns (presence of 0x363d9d8b or "delegatecall"), unverified contracts (bytecode present but no known pattern), and suspicious contracts (presence of self-destruct). Additional flag detection checks for ownership transfer functions, pause/unpause, and withdraw functions. A local label database maps known addresses to protocol names. Risk flags are generated based on contract type, detected functions, and value thresholds. The AI bridge (BGAI.generate) receives a prompt with the recipient analysis and returns a plain-English explanation of who the recipient is and whether it's safe to send funds to.

WHAT IT CANNOT SEE

This tool cannot detect malicious intent hidden in contract bytecode—it reads only the bytecode and transaction data visible on-chain. It cannot verify off-chain identity or intent—a known protocol label may not correspond to the actual deployed code. It cannot confirm that the recipient address matches the intended recipient—you must verify the address yourself. It cannot detect front-running or contract impersonation. It cannot tell you if a contract has been audited or if the source code matches the bytecode. The AI explanation is generated from the provided data and may miss nuanced attack patterns.

PLEASE NOTE

Supports EVM-compatible chains only—Ethereum, Sepolia, Polygon, Mumbai, Optimism, Arbitrum, and any network the wallet bridge connects to. Explanations are AI-generated and should be treated as assists, not authoritative audits. Always review the recipient address in your wallet's own signature prompt before approving. The wallet's signature step is the only protection that actually gates any action—this tool is informational and does not replace that safeguard. Free to use, no API keys required.