Alerts Web3 Block for Svelte

Each kind has a typed series of 168 hourly samples: a sample ether price, a base fee in gwei and the largest transfer in the hour. A rule fires each time its condition starts to hold, meaning the sample crosses the threshold and the hour before did not. Turning a rule on or off changes the history band but not its own count.

Price fires above the threshold in USD, Gas fires below it in gwei, and Whale transfer fires above it in USD. The direction follows the kind, so the form states it in the field's name, and the threshold must be in range or the field says what the range is.

Everything. Rules live in the tab, the channel is a label, and nothing is delivered. In your app save rules per user, evaluate them on the server against your price, fee and transfer feeds, send through your own email or push service, and keep the dry run: it is how people learn what a threshold means.

Remove deletes the rule and the foot offers one level of Undo. With no rules left, the list shows an empty state that points at New alert. The list keeps its height either way.

Yes. The dialog traps focus, returns it to New alert and closes with Escape; every switch and remove button names its rule; errors in the form are read out and tied to the field.

Rows stay on three lines with the switch at the start and Remove at the end, the header button drops under the sentence, and the dialog scrolls inside the screen.