Create Wallet Alert

WHAT IT DOES

This tool lets you create in-memory alerts for your connected wallet. You can set conditions for native balance (above or below a threshold) or transaction count (above a threshold). The tool polls the blockchain at your specified interval and displays a visual notification in the browser when the condition is met. Alerts are shown as triggered events in the panel, with the condition that caused the trigger and the time it occurred.

HOW TO USE

Connect your MetaMask wallet using the Connect button. Give your alert a name, select a condition (Balance Above, Balance Below, or Transaction Count Above), and set a threshold value. Choose how often to check the condition (5-300 seconds). Click "Create Alert" to start monitoring. Active alerts appear in the list below. When a condition is met, the alert moves to the "Triggered" section with a timestamp. Use the "Remove" button to delete an alert, or "Clear" to remove all alerts.

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 checks the connected wallet address and reads the current state from the blockchain using provider.getBalance() for native balance alerts or provider.getTransactionCount() for transaction count alerts. The fetched value is compared against the configured threshold. If the condition evaluates to true, the alert is marked as triggered and displayed in the triggered list. All alert configurations and state are stored in-memory variables — no data is persisted to disk. When the page is reloaded, all alerts are cleared.

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 monitor wallet activity in real-time without continuous polling — there is always a delay between the interval ticks. It cannot detect transaction failures or reverts without parsing receipts. It cannot alert on events that occurred before the alert was created. It cannot monitor wallets other than the currently connected wallet. It cannot detect token balance changes, only native currency balances and transaction counts. It cannot trigger alerts based on transaction content (e.g., who sent what amount). It cannot detect smart contract events without additional ABI configuration.

PLEASE NOTE

This tool works only with EVM-compatible wallets connected via the BGWallet bridge. Alerts are in-memory only and will be lost when the page is refreshed or closed. The polling frequency is limited by the RPC provider's rate limits — frequent checks (e.g., every 5 seconds) may hit rate limits on public RPCs. The tool does not store or transmit any data — all processing occurs in your browser. This tool is provided as a lightweight wallet monitoring utility and should not be used as a critical alerting system. For persistent monitoring, consider using dedicated wallet tracking services with push notifications.