Get notified when a number reaches your threshold

This applies only while your B Cash access is active and its watch is on for the board. Then B Cash owns that board's enabled price alerts. The standalone web widget and desktop alert monitor leave those notifications to it, so one crossing does not produce two deliveries. Funding APR, basis, OI change and multi-condition alerts remain standalone.

The agent establishes a fresh baseline when watching starts or resumes. A price already past the line at that baseline does not notify immediately; it must move from an unmet rule to a met rule in later fresh readings. Agent checks run roughly every 30 seconds and can cover configured saved boards even when their widgets are off screen. Browsers can throttle or suspend the tab, and closing the app stops the watch.

Activity keeps the observed evidence and source link. Notification permission affects delivery, and an unavailable delivery is reported while the signal remains in Activity. Repeated delivery of the same event has a five-minute cooldown; distinct events can notify separately, with at most three notifications per board check. The sections below describe standalone alerts; see Board Agent for its settings and source limits.

Each Alert widget holds one rule: a kind, an asset, a direction and a threshold. A perp alert can add up to two more conditions on the same perp, all of which must hold at once (see Combine conditions). A new alert starts paused, so nothing fires until you arm it.

1. 1

   Add the widget

   Open the Add tab, unfold On the board if it is folded, and click Alert. Or open the command palette with Ctrl K (Cmd K on macOS) and run Add price alert. A widget titled Price alert appears already active, so its controls show.

2. 2

   Choose the kind

   Pick Price, Funding APR, Basis or OI change in the switch along the top of the widget. The four kinds compare different numbers.

3. 3

   Choose the asset

   Open the asset menu, the dropdown that shows a ticker such as BTC. For Price it lists the 48 coins of the catalog. For the perp kinds it lists 12 main Hyperliquid perps and the 12 Solana assets that have a Hyperliquid perp. Basis needs a Solana spot price, so it is offered only for the Solana assets.

4. 4

   Set the threshold

   Choose Above or Below, type the threshold and press Enter. Direction and threshold lists what the box accepts.

5. 5

   Arm it

   Press Arm. The button stays disabled until a live value has loaded for every condition and the thresholds are valid (an OI change condition may still be building its history), and hovering it shows which one is missing: Waiting for a live value, Needs a live value before it can be armed or Fix the threshold first. In a browser this is also the moment the page asks for notification permission. The pill changes from Paused to Armed, or straight to Triggered if the value is already past the threshold.

6. 6

   Pause or remove it

   Press Pause to stop checking and keep the rule. To delete the alert, remove the widget with the trash icon in its header.

A new alert is set to BTC, Above and 100000. The kind, asset, direction and threshold controls show only while the widget is active, and Arm and Pause need an active widget too. A newly added widget starts active. To get back to the controls later, select the widget and then click it again (the hint Click to use this widget appears), double-click it, or press Enter. Esc leaves the widget again.

One widget holds one rule, with up to three conditions on a perp. For a separate rule, add another Alert, or duplicate the first with the copy icon in its header or with Ctrl D (Cmd D on macOS) while it is selected. A duplicate keeps the state of its source, so a copy of an armed alert is armed. The widget reference has a shorter entry under Board tools.

The table shows what each kind compares with your threshold. Funding APR and OI change cover 24 Hyperliquid perps; Basis covers the 12 Solana assets among them.

The perp kinds cover 12 main Hyperliquid perps, BTC, ETH, HYPE, XRP, DOGE, BNB, SUI, AVAX, LINK, LTC, ENA and AAVE, and 12 Solana edge assets, SOL, JUP, WIF, BONK, JTO, POPCAT, FARTCOIN, RENDER, W, MOODENG, ME and USELESS. Basis is offered only for the Solana assets, and choosing a main perp drops a basis condition and pauses the alert. Hyperliquid quotes BONK as the kBONK market, a bundle of 1,000 tokens, so Cashboard divides its price by 1,000 before comparing it with spot. The Solana edge widget reads the same feed, and the glossary explains funding APR and basis.

Hyperliquid reports open interest as a level and keeps no history, so Cashboard samples it once a minute while it checks: in the background on desktop, and while the widget is on screen on the web. An OI change condition stays unjudged, and the widget shows building OI history with how many minutes it has, until the samples cover its window. You can arm it meanwhile. Restarting the app or reloading the page starts the history again.

On desktop, a CoinGecko Demo key saved under Connections is used for price alerts, including the background checks. See Connections.

A perp alert can stack up to three conditions on the same perp, joined by AND. For example: notify me only when HYPE funding APR is below 0 and its open interest is up more than 10% in 1h. Price alerts keep one condition.

1. 1

   Start from a perp kind

   Pick Funding APR, Basis or OI change and the perp, then set the first condition as usual.

2. 2

   Add a condition

   Press Add condition under the first one. A row starting with and appears with its own kind, Above or Below, threshold and, for OI change, window. Adding a condition, or changing its kind, pauses the alert, because the new threshold is only a starting value.

3. 3

   Arm it

   Press Arm. The widget lists every condition with its value now and its gap, and the top right shows how many hold, such as 1/2.

The alert fires once when the last condition falls into place, with every condition true at the same check. It stays quiet while all of them keep holding, and fires again only after at least one stops holding and all hold again. A condition without a value leaves the whole rule unjudged for that check, so a missing feed never fires an alert. The desktop monitor and the web widget evaluate the same rule, with the same 5 minute desktop cooldown.

Remove a condition with the × at the end of its row; that does not pause the alert. Switching the first condition to Price drops the AND conditions. An edge from a Solana edge widget feeds the perp of every condition.

HYPE funding apr + OI change alert
My board: HYPE funding apr below 0.0% at -4.4% and OI change 1h above +10.0% at +12.6%.

Above fires when the value is at or above your threshold, and Below when it is at or below it. Both comparisons include the threshold itself: an Above alert set to 100000 fires at a price of exactly 100000.

Type the threshold in the box and press Enter or click away to apply it. Esc throws away what you typed. Until you apply a new number the old one stays in force, so an armed alert never runs on a half-typed value. The box holds up to 24 characters and cleans up what you paste: $65,000 becomes 65000 and 0,5 becomes 0.5. A price threshold must be above 0 and cannot take a minus sign. Funding APR, basis and OI change thresholds are percentages and may be negative.

A number that cannot be applied shows a message under the box, such as Enter a threshold, Add a digit after the decimal point or Price must be above $0. When the number is fine, the hint states the unit, and for basis it also shows the same figure in basis points. While an edit is waiting, the hint ends with Enter to save.

Changing the kind pauses the alert and resets the threshold to a starting value: 100000 for Price, 50 for Funding APR, 0.5 for Basis and 10 for OI change over 1h. A dollar figure would mean nothing once it became a percentage.

An alert can watch the asset of another widget instead of its own. With the select tool, hover a Price chart, Prices, Watchlist or Solana edge widget and drag from the handle on its right edge to the handle on the left edge of an alert. Prices, Watchlist and Solana edge ask which row to follow when they list more than one. An alert follows one widget at a time, and connecting a second one replaces the first.

• Connecting pauses the alert and replaces its asset picker with a chip such as ← Price chart · SOL and an unlink button. A chart, Prices or Watchlist row offers Price; a Solana edge row offers Funding APR, Basis and OI change, and the threshold resets when the kind has to change.
• When the chart switches asset, the alert pauses and reads Source switched to JUP. Check the threshold, then re-arm. Arming it then watches the new asset.
• When the followed row leaves Prices or Watchlist, the edge turns red and dashed and the alert pauses until you unlink it or add the row back.
• Unlinking keeps the asset the alert last followed and leaves it armed or paused as it was.
• Click an edge and press Delete to remove it. Deleting a connected widget removes its edges in the same undo step.

Edges travel with share links, board exports, board copies and a paste of both connected widgets. Duplicating one widget does not copy its edges. Cashboard Desktop checks a connected alert against the asset of the widget it follows, the same rule the widget shows.

Armed means the alert is switched on and being checked. The setting is saved with the board, so it survives a restart or a page reload. Paused means the rule is kept but never checked and never notifies, and every new alert starts that way. An armed alert shows Triggered while its value is at or past the threshold. You cannot set that state yourself, and firing does not disarm the alert, so it stays ready for the next time the value reaches the threshold.

An alert notifies you once, at the moment its condition changes from not met to met. After that it stays quiet until the value leaves the threshold and reaches it again.

• If the value is already past the threshold when you press Arm, that counts as reaching it. The gap already reads Met before you arm. On the web the notification comes at once. On desktop it comes with the next check, within about 15 seconds.
• A check that cannot read a value, because the source has nothing for that asset or cannot be reached, does not notify. The alert stays armed and tries again at the next check. On the web, a refresh that comes back without a value for the asset also makes the widget forget an earlier notification, so you can be notified again when a value returns past the threshold.
• Alerts compare the values that each check reads. A value that crosses your threshold and comes back between two checks is not seen.

The title names the asset and the kind, such as BTC price alert or SOL basis alert, and the body restates the rule and the value. Prices show two decimals, or four under $1. Funding APR shows one decimal and basis three, both with a sign, as in SOL funding apr above +50.0% at +52.3%. An alert with several conditions names each kind in the title, such as SOL funding apr + OI change alert, and lists every condition with its value in the body. On desktop the body starts with the board name. A browser notification has no board name in front of the body.

BTC price alert
My board: BTC price above $100000.00 at $100123.45.

Cashboard Desktop checks every armed alert on every saved board every 15 seconds while the app window is open or minimised, whether or not the widget or its board is on screen. The check runs in the app itself, not in the widget, so the widget you see and the background check read their values separately.

• It runs while the app window is open or minimised, and it stops when you close the window. On Windows, closing the window quits the app. On macOS the app stays in the Dock but does not check; click its icon to open a window and checking resumes.
• There is no tray icon, no launch at login and no background service, and Cashboard does not keep the computer awake.
• Checking starts together with the window, so an alert that is already past its threshold at launch notifies you within moments.
• An alert you arm or edit is picked up after its board has saved, a moment after the change, and then at the next check. Allow up to about 15 seconds.
• Every armed alert on every board is its own alert, so duplicating a board that holds armed alerts doubles the notifications.

Notifications are native system notifications. A second notification for the same alert inside 5 minutes is dropped, and it is not sent later. The cooldown is counted per alert (board, widget and rule), so it never hides a different alert, and changing the rule starts a fresh count. It is kept in memory, so restarting the app clears it.

Clicking a notification restores and focuses the Cashboard window, but it does not jump to the widget. If the operating system reports that it cannot show notifications, nothing is shown. See Desktop app for installing and running it.

On the web app, the Alert widget does the checking itself, inside the open page, and the browser shows the notification.

• The widget must be on screen. The canvas draws only what is in view, so panning the widget out of view, or opening another board, stops its checks.
• The tab must be visible. A tab that the browser reports as hidden, such as a background tab, is not polled, and checks resume when the tab is visible again.
• Price alerts read every 15 seconds, and funding APR and basis alerts every 20 seconds.
• The browser must allow notifications. Arm asks for permission when it has not been given and shows Notification permission was not granted if you decline. The Enable notifications chip asks too, without arming anything. If you block notifications later, the chip reads Notifications blocked and the note reads can’t notify: allow them in the browser's site settings, then return to the tab.
• There is no cooldown, and a value that hovers around your threshold notifies on every crossing. The widget also forgets that it has notified whenever it leaves the screen. While the value is past the threshold, you are notified again after a reload, after you pan the widget back into view and after you return to its board.
• Changing the threshold or direction of an armed alert while it stays past the threshold does not notify again. Pause and arm it again to be told.

Alert rules travel in share links and in exported board files: the kind, the asset, the direction, the threshold and whether the alert is armed. Nothing about an alert is stripped. The person who opens a link sees a review screen with the board name, the widget types and any external web addresses, not the thresholds. Add to my boards then creates a copy with every alert as you left it.

An armed alert arrives armed. On desktop it starts checking in the background as soon as the copy is saved. In a browser it checks once that board is open with the widget in view. The recipient has to allow notifications in their own browser, and until they do the first trigger shows Browser notification permission is required in the widget.

Run through this once after you arm an alert.

1. Check the pill and the note. Armed with watching is healthy. loading and no value mean there is no value to compare yet, feed delayed means the last refresh failed, and can’t notify means the browser has not allowed notifications.
2. Send yourself a test. Set a threshold the value has already passed, for example Above a number below today's price, then press Arm. The notification arrives straight away in a browser and within about 15 seconds on desktop. On desktop, change the threshold between tests, because pausing and re-arming the same rule inside 5 minutes is silent. Then set the real threshold.
3. Read the header. The line under the title names the source and the pill on the right shows the age of the reading. A price that keeps getting older means the source is not giving Cashboard anything newer.
4. On desktop, keep the app minimised, not closed, and leave the computer awake, because Cashboard does not keep it awake for you.
5. On desktop, check your operating system's notification settings.
6. On the web, keep the tab visible with the widget in view, and look for Notifications on.

For problems outside alerts, see Troubleshooting.