Chain Reorg Risk Explainer

WHAT IT DOES

Chain Reorg Risk Explainer is a read-only tool that analyzes on-chain data for transactions and blocks to assess chain reorganization risk, generating AI-powered plain-language explanations of reorg vulnerability. It reads chain head history, block depth, fork detection, block confirmations, finality status, unconfirmed transactions, safe block status, finalized block status, validator set, chain reorganization events, block timestamps, block hashes, orphaned blocks, transaction inclusion depth, and L2 finality status. The tool then presents this data alongside an AI-generated explanation of current reorg risk, including depth, confirmation count, finality status, and potential risks — helping you understand transaction security before acting on a confirmation.

HOW TO USE

Connect your wallet using the BGWallet bridge and select your target network (Ethereum Mainnet is recommended for L1 checks, but Arbitrum, Optimism, and Polygon are also supported). Enter a transaction hash or block number you want to analyze. Select the chain type (L1 or L2). Click "Analyze reorg risk" to read on-chain data. The tool displays the transaction or block, chain type, confirmation count, block depth, finality status, and reorg risk level. Detailed information includes safe block status, finalized block status, unconfirmed transaction count, fork detection, orphaned blocks, recent reorg events, active validator set, and L2 finality status. A reorg risk meter visually indicates the overall risk level (Low/Medium/High). An AI explanation appears below the on-chain data, describing the transaction's or block's chain reorganization risk including current depth, confirmation count, finality status, and potential risks if a reorg occurs. 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 data. When analyzing reorg risk, the tool reads chain head history and block depth using provider.getBlock() and provider.getBlockNumber(), calculating how many blocks have been added since the target block. Fork detection is performed by comparing chain head hashes and checking for reorg signals (via getBlock() and getBlockWithTransactions()). Block confirmations are counted as the number of blocks built on top of the target block. Finality status is determined based on confirmation depth (for L1: usually 12-15 confirmations for safety, 30+ for finality; for L2: based on rollup finality or challenge period status). Safe block status is checked against the chain's safe block threshold (typically the last 6 blocks). Finalized block status is checked against the chain's finalized block threshold. Unconfirmed transactions are read from the mempool (simulated). Validator set is read from the consensus layer or validator registry. Chain reorganization events are read from event logs (e.g., ReorgDetected) by walking backwards in chunks and halving chunk size on failure, ensuring logs are properly read despite varying RPC limitations. Orphaned block count is tracked from block history. L2 finality status is read from the rollup contract's finalization state (e.g., getFinalizedBatch(), isFinalized()). 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 explain the transaction's or block's chain reorganization risk including current depth, confirmation count, finality status, and potential risks — while stating plainly that it cannot predict future chain reorganizations, finality failures, or consensus issues, and cannot guarantee that transactions will remain confirmed or that blocks will achieve finality. The AI response is capped at 1,024 tokens to ensure concise, focused risk assessments. All computed values are guarded against negative numbers — if a block depth or risk score appears invalid, the tool flags it rather than displaying nonsensical values.

WHAT IT CANNOT SEE

This tool cannot predict future chain reorganizations, finality failures, or consensus issues. It cannot guarantee that transactions will remain confirmed or that blocks will achieve finality. It cannot detect off-chain consensus problems, validator misbehavior, or network partitions not reflected on-chain. The AI explanation is generated from on-chain data only and cannot detect hidden consensus issues, validator collusion, network latency, or off-chain fork propagation. It cannot predict network congestion, validator downtime, or consensus failures that may occur after the analysis. The tool does not continuously monitor the chain; each analysis is a snapshot at the time of the lookup. It cannot detect delayed finalization, stale blocks, or off-chain data latency. 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 transaction safety or finality.

PLEASE NOTE

Chain Reorg Risk 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. Chain reorganizations carry significant risk including transaction invalidation, double-spending, and loss of funds if a transaction is reorged out of the chain. Use this tool as a guide only; always cross-check with blockchain explorers and independent sources for critical decisions. This is experimental software; use at your own risk.