How DoneRoad gets its prices

Every asset class is polled every minute, on its own scheduled job. Each reading is written to a one-minute price history, and that history is what a percentage-change rule is measured against — so "up 5% in the last 15 minutes" compares the current reading with the reading recorded fifteen minutes earlier, not with an average.

One-minute history is kept for 40 days and then deleted. That is the longest look-back window any rule can use.

A minute is the floor on how quickly an alert can fire. If a price spikes and returns within the same minute, no reading captures it and no alert fires. This is a deliberate trade: minute resolution across every asset is what keeps the service free.

A rule is one or more conditions. Each condition compares a value — a price, a percentage change over a window, or an indicator such as a moving average — against a threshold you set, using a comparison operator.

Conditions can be combined with AND (every condition must hold at the same moment) or OR (any one of them is enough). A rule is checked on every price reading, so at most once a minute per asset.

Comparisons are strictly greater-than or less-than, with or without "or equal". There is deliberately no "equals" operator: a price sampled once a minute almost never lands exactly on a round number, so a rule written that way would look correct and never fire. Measured against real BTC data, a price crossing a given level jumps over a ±0.05% band 13% of the time. The operator guide walks through a worked example.

Three kinds of value, all computed from the same one-minute history described above — nothing is fetched from a separate analytics provider:

• Price, either as an absolute level or as a percentage change over a window you choose.
• Simple moving averages — SMA 20, 50 and 200. The unweighted mean of the last N readings.
• Exponential moving averages — EMA 9, 12, 20, 50 and 200. Weighted toward recent readings, so they turn sooner than the SMA of the same length.
• Volume, where the upstream source reports it. Not every asset class does, and a rule on volume is only as good as that source.

A long average needs a long history. An EMA 200 on minute data needs 200 readings, so an asset added minutes ago cannot answer it yet. Until the history is deep enough the condition simply does not hold, rather than firing on a partial average — an alert on an average computed from 12 readings instead of 200 would be worse than no alert.

Four channels: Telegram, Discord, Email and browser push notifications. You choose per alert, and an alert can use more than one.

Delivery depends on the channel's own service. A Telegram or Discord message that their API rejects is retried; email lands or bounces on the receiving provider's terms. DoneRoad can tell you it sent a notification. It cannot guarantee your phone was on, your inbox accepted it, or you read it in time to act.

• Prices come from third-party sources and are passed on as received. If an upstream source is wrong, delayed, or unreachable, DoneRoad is wrong, delayed, or silent with it. Nothing here is an exchange feed and nothing here is guaranteed to match the price you can actually trade at.
• Minute resolution, not tick resolution. Movement inside a minute is invisible to the system.
• Alerts are notifications, not orders. DoneRoad never places, routes or executes a trade, and never holds funds.
• This is not financial advice. An alert reports that a number you chose crossed a threshold you set. It is not a recommendation to buy, sell or hold anything, and no part of this service assesses whether a trade is suitable for you. See the full disclaimer.

If a price on this site looks wrong, tell us and we will say what the upstream source returned and when. Write to [email protected] or use the contact page.

This page describes the system as it runs today. It is updated when the sources, the cadence or the retention window change.