Create Wallet Activity Alert

WHAT IT DOES

This tool monitors your connected wallet for new transaction activity. You create an alert that watches for incoming, outgoing, or any transactions involving your wallet. The tool polls the blockchain at your specified interval, scanning for new blocks and detecting transactions that involve your address. When activity is detected, the alert triggers and the transaction appears in the activity log. All alert configurations and activity history are stored in-memory — no data is persisted across page reloads.

HOW TO USE

Connect your MetaMask wallet using the Connect button. Give your alert a name, select what to monitor (Incoming, Outgoing, or Any transaction), and set a check interval (5-300 seconds). Click "Create Alert" to start monitoring. Active alerts appear in the list. When a transaction involving your wallet is detected, the alert status changes to "Triggered" and the transaction appears in the Recent Activity log. Click any transaction hash to view it on Etherscan. Use "Remove" to delete an individual alert or "Clear All" to remove all alerts and activity history.

TECHNICAL MECHANISM

The tool uses the BGWallet bridge to access the blockchain provider via ethers.js. For each active alert, it creates a JavaScript interval that runs at the user-specified frequency. On each interval tick, the tool fetches the current block number and compares it against a stored last-checked block number. It then scans for logs involving the wallet address using eth_getLogs. To handle varying RPC limits, the tool implements a chunked scanning strategy — it starts with a chunk size of 500 blocks and halves the chunk size if the RPC returns a "limit exceeded" error, continuing until the scan completes. For each transaction hash found, it fetches the full transaction and receipt, verifies the direction (incoming/outgoing), and records it if it matches the alert type. The tool deduplicates transactions using a Set of seen hashes to avoid duplicate entries.

WHAT IT CANNOT SEE

This tool cannot persist alerts across page reloads because it runs in an opaque-origin sandboxed frame with no storage access. It cannot send push notifications or emails without external services. It cannot detect activity that occurred before the alert was created. It cannot monitor wallets other than the currently connected wallet. It cannot detect pending or failed transactions — only confirmed transactions with status=1. It cannot detect transactions sent from the wallet to itself. It cannot detect token transfers without user-provided token addresses. It cannot detect contract interaction details without ABI. It cannot detect activity on networks other than the connected network. It cannot detect transactions that were included in a block but did not emit a log event.

PLEASE NOTE

This tool works only with EVM-compatible wallets connected via the BGWallet bridge. The chunked scanning ensures compatibility with RPC providers that limit eth_getLogs ranges, but scanning large ranges may take time. Frequent polling (e.g., every 5 seconds) may hit RPC rate limits on public providers. Alerts are in-memory only and will be lost when the page is refreshed or closed. The tool does not store or transmit any data — all processing occurs in your browser. This tool is provided as a lightweight activity monitoring utility and should not be used as a critical alerting system.