Basics guide

Which on-chain events are worth an alert (and which are noise)

Almost anything that happens on-chain can become an alert, which is exactly the problem: alert on everything and you stop reading them. This article goes through the on-chain events that are worth a message on your phone, shows the real alert each one sends, and names the ones that are mostly noise. Everything here works today on Ethereum mainnet, with alerts delivered on Telegram.

Just want the alert? See all alert types

8 min read

Why alerts beat refreshing Etherscan

A block explorer answers a question you already thought to ask. You open the address, scroll the latest transactions and decide whether anything changed. That works for one wallet you check once a day. It falls apart when you care about a few wallets, a collection and a contract, or when the moment you need to know about is the moment you're not looking.

An alert turns that around: you describe once what to watch and when to speak up, and the message finds you. Alerts arrive within seconds of the transaction being confirmed. Pending (mempool) transactions are not alerted. One message is sent per transaction per rule, and its first line is written to make sense in a phone's notification preview.

The hard part is choosing what deserves a message. The rest of this article is that list.

Example alert
WalletExample

Received 1.2 ETH from 0x7099…79C8

Wallet 0xf39f…2266 · Rule: Incoming ETH

Ethereum · View on Etherscan09:41

Money in and out of your own wallet

The first alert worth having is on your own wallet: ETH or tokens arriving, and ETH or tokens leaving. Incoming transfers tell you a payment, a deposit or a withdrawal from an exchange has landed. Outgoing transfers are the ones you want to hear about even more, because an outgoing transfer you didn't make is the first sign something is wrong.

The Protect my wallet template alerts on every transfer in or out. If the wallet is busy, Incoming payments and Treasury outflows split the two directions, and Big moves only keeps transfers at or above a minimum you set, in the asset's own units. Known exchanges and protocols are named in the alert, and other addresses are shortened.

Example alert
TokenExample

Received 2,500 USDC from Binance 14

Wallet 0xf39f…2266 · Rule: Incoming payments

Ethereum · View on Etherscan09:41

Unlimited token approvals

An approval lets another address spend a token from your wallet. Apps need them, but an unlimited approval to the wrong spender is one of the most common ways wallets are drained: the spender can move the whole balance later, without asking again.

The Token approvals template watches a token's contract for Approval events, and the alert flags unlimited allowances with a warning line. Add the condition owner is your wallet to hear only about your own approvals. Approvals across every token a wallet holds are coming with Premium; today you set it up per token.

Example alert
TokenExample

0x3f5c…e0b7 approved 0x9f2c…9a71 to spend unlimited USDC

  • ⚠️ Unlimited allowance: the spender can move the whole balance

Contract USDC (0xa0b8…eb48) · Rule: Token approvals

Ethereum · View on Etherscan09:41

NFT mints of a collection

When a collection mints, you either want to be early or you want to know who got in. A mint is a transfer from the zero address, and the NFT mints template watches the collection's contract for exactly that, on ERC-721 and ERC-1155. Several tokens minted in one transaction arrive as one message with a line per token.

Set the rule up as soon as the contract is deployed, before the mint opens, and nothing is missed while you look for the address.

Example alert
NFTExample

NFT Bored Ape Yacht Club #8817 minted to 0x7099…79C8

Contract Bored Ape Yacht Club (0xbc4c…f13d) · Rule: BAYC mints

Ethereum · View on Etherscan09:41

NFTs leaving a wallet

For your own NFTs, the moment that matters is a token leaving the wallet: a sale going through, a transfer you made yourself, or one you didn't. The NFT received / sent template puts two rules on a wallet, NFT received and NFT sent, so you can send outgoing NFTs to your private chat and keep incoming ones quieter.

To follow one collection instead of one wallet, the NFT activity template watches the collection's contract and alerts on every token that changes hands, like the example below. Add the condition from is one of your wallets to keep only the tokens leaving them.

Example alert
NFTExample

NFT #4412 moved from 0x3f5c…e0b7 to 0x9f2c…9a71

Contract 0x5af0…7a3c · Rule: Collection activity

Ethereum · View on Etherscan09:41

Large transfers of a token

Big movements of a token are worth a message; small ones usually aren't. The Whale transfers template watches a popular token's contract and only alerts above a threshold set per token, in token units, not USD: for example 1,000,000 USDT, 1,000,000 USDC or 500 WETH.

The alert below comes from the Token transfers template, which sends every transfer of a token. Whale transfers sends the same message, only for transfers at or above the threshold.

Example alert
TokenExample

250,000 USDT moved from 0x3f5c…e0b7 to 0x9f2c…9a71

Contract USDT (0xdac1…1ec7) · Rule: USDT transfers

Ethereum · View on Etherscan09:41

Contract admin and governance events

Contracts announce the changes that matter most: ownership transferred, the contract paused, a new proposal created in a DAO. These events are rare, so an alert on them costs almost nothing in noise, and when one does fire it is usually worth reading straight away.

Watch a contract you depend on with an event rule on OwnershipTransferred or Paused, or use Admin method called for a contract you operate. For a Governor-style DAO, the New proposals template alerts on every ProposalCreated.

Source

Contract

0x87b1…4e2a

Rule

Admin method called

pause()

Telegram alert
ContractExample

0x3f5c…e0b7 paused the contract

Contract 0x87b1…4e2a · Rule: Admin method called

Ethereum · View on Etherscan09:41
Example alert
ContractExample

Ownership moved from 0x3f5c…e0b7 to 0x9f2c…9a71

Contract 0x87b1…4e2a · Rule: Everything on the contract

Ethereum · View on Etherscan09:41

What is noise

Some alerts look useful when you set them up and become wallpaper after a day. Two common ones:

  • Every transfer of a busy contract. A rule with no conditions on a popular token or a large collection sends a message for every transfer, all day. Narrow it with a threshold, a counterparty or your own address, or use Whale transfers instead.
  • Every Seaport order on the free plan. Seaport settles sales for a large share of NFT marketplaces, so a rule on it sees every filled order. An event is one transaction seen on one watched address. It counts once, whether it matches none, one or several of your rules and however many channels it fans out to. An alert is sent only when a rule matches. Conditions decide which orders alert you; they don't reduce what is counted. A Seaport rule would use up the Beta plan's 100 events a month quickly, and when events run out, alerts pause until the period resets. For one collection, watch the collection's contract instead.
  • A good test for any rule: if you wouldn't open the transaction when the alert arrives, the rule is too wide.

Set one up in two minutes

Every event above has a template in the dashboard, so setting one up is mostly pasting an address. The steps further down walk through it, from sign-in to your first alert. Start with your own wallet: it takes the least thought and catches the most important event on the list.

Honest limits

Before you rely on alerts, these are the edges today:

  • Ethereum mainnet only. More networks are planned, but none is live yet.
  • Telegram is the only live channel. Discord, Slack, email and webhooks are coming.
  • Alerts on Chain is read-only. It watches public addresses and never asks for a private key or a seed phrase.
  • No USD values, sale prices or floor prices in alerts yet. They are coming with Premium; thresholds are in token units.
  • Alerts report activity after confirmation. They can't block or reverse a transaction.

Which event do you wish you'd had an alert for?

Everyone who has spent time on-chain has one: a transfer they noticed too late, an approval they forgot, a mint they missed. If yours isn't on this list, it's probably the one worth setting up first, and we'd like to hear what it was.

For a closer look at each kind of alert, start from the alert types or one of the guides below.

Set it up step by step

From sign-in to your first alert, in the actual dashboard.

  1. 1
    Sign in at alertsonchain.com with Google or with your wallet. A wallet sign-in is a signed message, not a transaction, so it costs no gas.
  2. 2
    Open the Channels tab and connect Telegram: start a chat with @alertsonchain_com_bot, send /start, and paste the 8-character code it replies with.
  3. 3
    Pick a template on the Rules tab: Protect my wallet for your own wallet, Token approvals, NFT mints or another one from this list.
  4. 4
    Paste the wallet or contract address you want to watch, and pick the Telegram chat the rule sends to.
  5. Click Create rule. The rule is active straight away, and the next matching transaction sends a Telegram message.

Frequently asked questions

  • Which on-chain alert should I set up first?

    An alert on your own wallet, with the Protect my wallet template. It tells you when anything moves in or out, including a transfer you didn't make.

  • Why does a rule on a busy contract use so many events?

    An event is one transaction seen on one watched address. It counts once, whether it matches none, one or several of your rules and however many channels it fans out to. An alert is sent only when a rule matches.

  • Can I set thresholds in dollars?

    Not yet. Thresholds are in the asset's own units, such as 2 ETH or 5,000 USDC. USD values are coming with Premium.

  • Are these alerts free?

    The free Beta plan needs no card and includes 1 wallet, 1 contract and 100 events a month. Paid tiers go from 5,000 to 2,000,000 events a month.