Watch types

• Money moves on a wallet and you want to know: Wallet balance changes.
• A price jumps and you want to react: Feed price moves.
• You delegate to a provider and want to know when it stops earning rewards: Provider eligibility changes.
• You never want to run out of credits: Credits balance falls below a limit.
• You run a provider and want reminders for reward signing: Reward signing is pending.
• You run a provider and want full technical monitoring: Provider FSP monitoring.

You enter the network (Flare or Songbird), the wallet address, optionally a token address (empty means the native coin), a threshold in tokens and a direction: any direction, incoming or outgoing. Every check compares the balance with the previous check. If it changed by at least the threshold in the chosen direction, you get an alert. The first check only records the starting balance.

Example: your project treasury holds FLR. A watch with threshold 10,000 and the direction Outgoing tells you as soon as a larger amount leaves the wallet, even when you did not expect the transfer.

You enter a feed symbol such as FLR or BTC, a move threshold in percent and a window between 5 and 1,440 minutes. The watch compares the current price with the oldest price inside the window. It sends at most one alert per window length, and a move of twice the threshold or more is marked critical.

Example: symbol FLR, threshold 5%, window 60 minutes. If FLR falls from 0.0200 to 0.0189 USD within the hour, you get a warning; at a 10% drop the alert is critical.

You enter the network and the provider address. The watch alerts when the provider is no longer registered, or when it was not eligible for rewards in the last closed reward epoch. When both are fine again, you get a recovery notice.

Example: you delegate your WFLR to a provider. If that provider loses eligibility, you earn nothing for that epoch. The alert gives you time to move your delegation before the next epoch.

You enter a limit in credits; the default is 1,000. The watch alerts when your own credit balance falls below it and sends a recovery notice once it reaches or exceeds the limit again. This type is free and needs no slot.

Example: your slots renew automatically from your credits. A limit a little above the renewal price warns you early enough to top up before a renewal fails.

You enter the network and the voter address. That is the provider identity address registered in the EntityManager, not the signing policy address. The watch reminds you when the uptime vote is still unsigned 2 hours after the epoch ended, when the reward data has been published for 2 hours without your signature, and again after 12 hours. It also tells you if a vote concluded without you, and confirms once per epoch when everything is signed.

Example: your automatic signer stopped after a server update. Instead of noticing days later that rewards were lost, you get the first reminder 2 hours after the epoch ended.

You enter the network and the provider identity address. The watch follows commits, reveals, signatures, FDC, Fast Updates, registration, validator, balances and unclaimed rewards of that provider in every voting round. It uses its own provider slot. Everything about it is on Provider Watch.

Example: you run the provider on Flare and Songbird. You create two watches, one per network, and route the critical groups to your team's Telegram group.

• Wallet balance changes: one Standard slot per watch
• Feed price moves: one Standard slot per watch
• Provider eligibility changes: one Standard slot per watch
• Credits balance falls below a limit: free, up to 3 per wallet, no slot needed
• Reward signing is pending: one Standard slot per watch
• Provider FSP monitoring: one Provider slot per watch