10 smart contract alert recipes

A new owner can usually upgrade, pause, mint or withdraw. A planned handover is a non-event you already know about. An unplanned one means a key was compromised or a multisig was bypassed. SmartAlert watches OwnershipTransferred and alerts within minutes of the block.

An upgradeable proxy can get new code in one transaction. SmartAlert watches the ERC-1967 events Upgraded and AdminChanged. The message has the new implementation or admin address. Add the proxy address, not the implementation.

A pause stops deposits, withdrawals or transfers for every user. If your guardian paused the contract, the team needs to know now. If someone else did, it is an incident.

On AccessControl contracts, roles like MINTER_ROLE or DEFAULT_ADMIN_ROLE decide who can mint, pause or upgrade. Most teams change roles a few times a year, so each alert is worth reading. The message names the role and the account.

Your Safe holds the keys to the treasury and admin roles. Lowering the signature threshold or adding an owner changes who controls your funds. Every signer should know the moment it happens.

A contract can keep emitting events while a growing share of calls to it fails. SmartAlert fires when, over a window, the share of direct transactions to the contract that reverted is above your threshold. Example: "Revert 30% in an hour at a 2% norm". The alert lists up to the three latest failed transactions.

SmartAlert starts reading receipts of a contract when the first enabled transaction rule appears on it. There is no history before that moment, so the chart appears after one window. The rule is not available on every network. A window with no transactions is not a failure.

Large moves often come before price impact: a treasury moving funds, a whale exiting, or an exploit draining a pool. The limit is in tokens, decimals are applied for you. If the token has history, the form suggests a limit.

A fixed limit on transfer count is noisy at peak hours and silent at night. SmartAlert compares each hour with the same hour on previous days and alerts when activity is far above that norm. The norm needs about 5 days of history.

On Uniswap V2-style pools, removing liquidity emits Burn. A liquidity exit makes swaps expensive for your users and is often the first sign of a rug or a depeg. SmartAlert counts Burn events per hour and alerts when they are far above the usual level for that hour.

Some failures make no noise: a keeper stops, an oracle stops updating, nobody calls the contract. Silence is invisible on a dashboard nobody opens at night. Pick an event your contract should emit regularly, and the rule fires when it stops.

Seven more rules, each on its own page:

• Alert when a wallet balance runs low
• Alert when a keeper wallet has gas for less than N days
• Alert when a balance is low and no top-up came in an hour
• Alert when a treasury falls below $100,000
• Alert on a token transfer above $50,000
• Alert when a contract's paused() returns true
• Alert when a Safe transaction fails (ExecutionFailure)