Router Contract Trust Explainer

WHAT IT DOES

Router Contract Trust Explainer is a read-only tool that evaluates the trustworthiness of router contracts (e.g., DEX routers), generating AI-powered plain-language explanations of trust levels and recommendations. It reads router contract address, router bytecode, router implementation, factory address, pair creation history, liquidity pool addresses, router owner, proxy pattern detection, upgradeable status, event logs, transaction history, privileged function signatures, known router signatures (Uniswap, Sushiswap, etc.), verified status, and audit history. The tool then presents this data alongside an AI-generated evaluation of the router's trustworthiness, analyzing its implementation, ownership, upgradeability, factory pair history, and on-chain behavior — helping you decide whether to use the router for swaps or liquidity operations.

HOW TO USE

Connect your wallet using the BGWallet bridge and select your target network. Enter the router contract address you want to evaluate. Optionally enter a router name for reference. Click "Evaluate router trust" to read on-chain router data. The tool displays the router address, name, implementation, factory address, and trust level (Trusted/Caution/Danger). Detailed information includes proxy pattern, upgradeable status, owner, pair count, verified status, audit history, known signature, privileged functions, and recent event count. A recommendation box provides specific guidance. An AI explanation appears below the on-chain data, evaluating the trustworthiness of the router contract by analyzing its implementation, ownership, upgradeability, and on-chain behavior, flagging suspicious patterns or risks, and recommending whether you should use the router for swaps or liquidity operations before you interact with it. The wallet's own signature step still protects you — this explanation is informational only and does not replace reviewing what you approve in your wallet.

TECHNICAL MECHANISM

The tool uses ethers.js v5.7.2 with the provider from the BGWallet bridge to read on-chain contract data. No hardcoded contract addresses are used — you are always in control of which contract you trust. When evaluating router trust, the tool reads the router contract address from the user input, reads router bytecode via provider.getCode(router), detects router implementation by analyzing the bytecode and any proxy patterns, reads factory address from the router's storage or bytecode, reads pair creation history by scanning event logs (e.g., PairCreated), reads liquidity pool addresses from the factory, reads router owner via the router's owner() function or storage slot, detects proxy patterns by scanning for known proxy opcode patterns and storage slots, detects upgradeable status by checking for proxy patterns and upgrade functions, reads event logs by scanning for router-related events, reads transaction history via provider.getTransactionCount(router), reads privileged function signatures by analyzing function selectors, checks known router signatures against a database of known routers (e.g., Uniswap V2, Sushiswap), reads verified status from block explorer metadata, and reads audit history from the contract metadata. The tool fetches event logs by walking backwards in chunks and halving chunk size on failure, ensuring logs are properly read despite varying RPC limitations. The data is formatted and passed to the AI bridge via BGAI.generate() with a structured prompt that includes all the on-chain data read. The AI is instructed to evaluate the trustworthiness of the router contract by analyzing its implementation, ownership, upgradeability, factory pair history, and on-chain behavior, flag suspicious patterns or risks, and recommend whether to use the router for swaps or liquidity operations — while stating plainly that it cannot detect router risks that involve off-chain governance processes or social engineering, cannot guarantee that a router's behavior matches its claimed implementation, and cannot detect malicious intent in router code beyond bytecode analysis. The AI response is capped at 1,024 tokens to ensure concise, focused router trust assessments. All computed values are guarded against negative numbers — if a pair count or event count appears invalid, the tool flags it rather than displaying nonsensical values.

WHAT IT CANNOT SEE

This tool cannot detect router risks that involve off-chain governance processes or social engineering. It cannot guarantee that a router's behavior matches its claimed implementation. It cannot detect malicious intent in router code beyond bytecode analysis. It cannot detect front-running or sandwich attack risks that depend on mempool conditions. The AI explanation is generated from on-chain data only and cannot detect off-chain governance decisions, hidden implementation details, or social engineering attacks. It cannot predict whether a router will be upgraded maliciously in the future. The tool does not continuously monitor router trust; each analysis is a snapshot at the time of the lookup. It cannot detect delayed attacks, hidden router functions, or off-chain factors. The tool does not store any data persistently; all state is in-memory and resets on reload. The AI explanation is informational and does not constitute financial advice, legal advice, or a guarantee of router safety or protection against router vulnerabilities.

PLEASE NOTE

Router Contract Trust Explainer works exclusively with EVM-compatible chains. It requires a Web3 wallet (MetaMask or similar) and the BGWallet bridge. Explanations are AI-generated from data the app reads on-chain — always review what you are actually signing in your wallet before approving it. Router contracts carry significant risk including malicious upgrades, fund theft, and unexpected behavior. Use this tool as a guide only; always cross-check with independent sources and contract audits for critical decisions. This is experimental software; use at your own risk.