Useful notifications, with honest limits.

Best-effort notifications

Notifications can be delayed, duplicated, misclassified, or missed because of node outages, reorganizations, pool-attribution limits, public-service failures, email filtering, or other operational problems. Do not rely on a notification as your only financial or security control.

Bitcoin Block Notifier cannot stop, cancel, replace, reroute, or reverse a transaction. Address notifications describe activity that is already included in a block.

Pool and Coinbase-tag matching

Every pool notification requires a selected mining pool. With no Coinbase tag entered, the notification covers every new block attributed to that pool. With a tag entered, matching is case-insensitive and partial within the extracted miner tag for the selected pool.

Partial matches can produce false positives. The less unique your chosen tag, the more likely it is to match unrelated text. Pool and secondary-tag attribution also depends on the recognizable data available in a block.

Saving a notification with a tag that is not already in the public catalogue may also create a private pending catalogue candidate. The notification is active immediately, but submission alone does not publicly list the tag and does not guarantee that the candidate will be published or retained.

If the exact tag is later confidently observed in a public blockchain block attributed to the selected pool and algorithm, Bitcoin Block Notifier may add it to the public catalogue. Blocks and Coinbase data in the accepted blockchain are inherently public and permanent. A catalogue entry does not identify or publicly link the submitter, account, or email address.

Start heights and milestones

Each block-based notification records the current block height when it is saved. Monitoring begins from that reference point and does not search backward for historical matches. A height notification is sent once when its selected algorithm first reaches or passes the future target.

Price notifications

Price notifications use the service's observed reference price, which can differ from the executable price shown by a particular exchange or wallet. Price notifications may be sent when the observed price is within 2% of your target.

A price notification is one-time. Its status changes from Active to Reached after the target range is entered, and it remains in your account until you remove it. Provider outages, delayed market data, currency-conversion availability, rapid price movement, and email delivery can delay or prevent a notification.

Verified addresses

You may add an address only after producing a supported signed message. That proof shows control at enrollment; it does not prove identity, legal ownership, or continuing control. You are responsible for adding only addresses you are authorized to monitor.

Only newly found blocks after the saved start height are checked. Matches include Coinbase payouts, transaction outputs, and spent-input previous outputs. Mempool activity and earlier blocks are not searched.

During BLAKE2b fallback, whole public blocks may be retrieved from mempool.guide and checked inside the monitoring service. Watched addresses are not sent to that service.

Donations

Donations are voluntary, final Bitcoin payments and do not purchase service, priority, support, or a promise that the service will remain available. Confirm the network and destination before sending; payments cannot be reversed.

Use a wallet compatible with the selected network before sending. Where Lightning is made available, it uses a freshly created invoice.

Fair use and service changes

Do not abuse verification, attempt to evade limits, interfere with the service, or use it to unlawfully monitor another person. Notification limits and features may change to protect reliability, privacy, and operating costs.