Local Chain Block Mining Trigger

WHAT IT DOES

Local Chain Block Mining Trigger is a read-only developer tool that simulates block mining in local fork environments. It reads the current chain state (block number and timestamp), calculates the effect of mining multiple blocks with configurable time offsets, and generates ready-to-use mining commands for Hardhat and Anvil/Foundry. The tool helps developers test block-dependent contract logic (e.g., block number-based rewards, time-locked withdrawals, epoch-based systems) without waiting for real blocks to be mined. It is essential for developers testing smart contracts that rely on block numbers, timestamps, and transaction ordering in local development environments.

HOW TO USE

Connect your EVM-compatible wallet via the BGWallet bridge and select the network where your local fork is running. Enter the number of blocks to mine (1-100) and optionally a time offset per block in seconds (e.g., 12 for Ethereum's average block time). Click "Simulate Block Mining" to calculate the new chain state and generate mining commands. Results include the start and end block numbers, timestamps before and after mining, total time advanced, a detailed block timeline, and ready-to-use commands for Hardhat (evm_mine with evm_increaseTime) and Anvil/Foundry (evm_mine with evm_increaseTime). The tool also provides a visual progress bar showing mining progress. All analysis is read-only—no signatures or transactions are submitted.

TECHNICAL MECHANISM

The tool uses ethers.js v5.7.2 to fetch the current block number and timestamp via provider.getBlock('latest'). The user-provided blocks to mine and time offset per block are used to calculate the new block number and timestamp. The tool generates mining commands using the EVM's built-in RPC methods: evm_mine (which mines a new block) and optionally evm_increaseTime (which advances the block timestamp). For Hardhat, the commands are formatted as JavaScript with hre.network.provider.send(). For Anvil/Foundry, the commands are formatted as cast rpc calls. The tool provides a block timeline showing each mined block's number and timestamp, and a visual progress bar indicating mining progress. The simulation does not actually mine blocks—it only calculates and presents the commands for the user to run in their local fork environment. The tool handles up to 100 blocks per simulation and validates user inputs to ensure they are within acceptable ranges.

WHAT IT CANNOT SEE

This tool has fundamental limitations that users must understand. It cannot actually mine blocks—the tool is a simulation only and does not execute evm_mine or evm_increaseTime RPC calls. It requires a local fork environment (Hardhat, Anvil, or Ganache) with the appropriate RPC methods enabled. It cannot guarantee that mining will work consistently across all fork tools—different tools may implement mining differently or have different RPC method names. It cannot control the exact contents of mined blocks—the tool does not manage mempool transactions or block composition. It cannot predict the exact gas usage or ordering of transactions in the mined block—the tool only simulates block numbers and timestamps. It cannot mine blocks on live networks—block mining is only possible in local fork environments. It cannot customize block parameters (e.g., gas limit, base fee) without manual intervention—the tool only generates basic mining commands. It cannot handle mining with custom block timestamps beyond basic evm_increaseTime functionality. It cannot detect or handle transactions that may fail when mined. The tool's commands are templates and must be manually executed in the appropriate environment.

PLEASE NOTE

This tool only supports EVM-compatible blockchains (Ethereum, Polygon, BSC, Avalanche C-Chain, Optimism, Arbitrum, and their testnets). Solana, Tron, Starknet, SUI, TON, Aptos, Bitcoin, Cosmos, and XRP are not supported. The tool is free, open-source, requires no API keys, and uses the wallet's native provider for all read operations. Block mining is a powerful testing feature—always verify contract behavior at multiple block numbers to ensure correctness.