Constant Value Verification Tool

WHAT IT DOES

Constant Value Verification Tool is a read-only tool that verifies constant values in contracts, generating AI-powered plain-language explanations of whether constants are correct, suspicious, or inconsistent. It reads constant variable values, constant declarations, contract bytecode, compiler version, optimization settings, variable types, storage layout (constants are not stored), proxy pattern detection, upgradeable contract status, event logs, transaction history, privileged function signatures, and known constant values from standards. The tool then presents this data alongside an AI-generated analysis of whether the constant values are correct, comparing them against known standards or expected values and flagging suspicious or unexpected constants — helping you understand the contract's fixed configuration before interacting with or relying on it.

HOW TO USE

Connect your wallet using the BGWallet bridge and select your target network. Enter the contract address you want to analyze. Optionally enter a contract name for reference. Click "Verify constants" to read on-chain contract data. The tool displays the contract address, constants found, constant names, constant values, and verification status (Verified/Suspicious/Inconsistent). Detailed information includes compiler version, optimization settings, variable types, expected vs actual comparison, proxy pattern, upgradeable status, known standards, and privileged functions. A verification assessment box provides a summary risk evaluation. An AI explanation appears below the on-chain data, verifying the constant values in the contract, comparing them against known standards or expected values, and flagging suspicious, unexpected, or incorrect constants, explaining the risks of trusting these values before you interact with or rely on the contract. 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 verifying constant values, the tool reads constant variable values from the contract metadata and bytecode, reads constant declarations from the contract's ABI, reads contract bytecode via provider.getCode(contract), reads compiler version from the contract metadata, reads optimization settings from the contract metadata, reads variable types from the ABI or metadata, reads storage layout (constants are not stored in storage) by analyzing the bytecode, detects proxy patterns by scanning for known proxy opcode patterns and storage slots, detects upgradeable contract status by checking for proxy patterns and upgrade functions, reads event logs by scanning for deployment-related events, reads transaction history via provider.getTransactionCount(contract), reads privileged function signatures by analyzing function selectors, and compares constant values against known standards (e.g., ERC20 decimals, max supply patterns) using a database of standard values. 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 verify the constant values in the contract, compare them against known standards or expected values, flag suspicious, unexpected, or incorrect constants, and explain the risks of trusting these values — while stating plainly that it cannot detect constant values that are computed at compile time from off-chain sources, cannot guarantee that a constant value is correct or safe, and cannot detect constants in contracts that use inline assembly or non-standard patterns. The AI response is capped at 1,024 tokens to ensure concise, focused constant verification assessments. All computed values are guarded against negative numbers — if a value or type appears invalid, the tool flags it rather than displaying nonsensical values.

WHAT IT CANNOT SEE

This tool cannot detect constant values that are computed at compile time from off-chain sources. It cannot guarantee that a constant value is correct or safe. It cannot detect constants in contracts that use inline assembly or non-standard patterns. It cannot detect malicious intent behind constant values beyond bytecode analysis. The AI explanation is generated from on-chain data only and cannot detect off-chain computed constants, hidden constants, or social engineering attacks. It cannot predict whether a constant value will cause issues in the future. The tool does not continuously monitor constant values; each analysis is a snapshot at the time of the lookup. It cannot detect delayed issues, hidden constants, 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 constant correctness or contract safety.

PLEASE NOTE

Constant Value Verification Tool 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. Constant values carry significant risk including incorrect decimals, wrong fee rates, mismatched addresses, and other hardcoded values that could lead to loss of funds. 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.