Nudges
Being told when a patch stops earning, and the restraint that makes those messages worth reading.
What gets watched
A patch can be watched for four things: falling in the shade, coming back into the sun, approaching an edge, and being emptied. A background job compares every watched patch against the chain every five minutes.
A patch outside its range is not broken and not at risk. It has simply stopped working, and it will go on not working for as long as nobody looks — which is the entire reason this exists.
Why you will not be spammed
Messages are sent on change, not on condition. The last known state of every subscription is stored, and a message goes out only when the state read from the chain differs from it. A patch that stays in the shade for a week produces one message, not two thousand.
Something that notifies on every check is a notification switched off within a day, and after that the nudge that actually matters does not arrive either. That is why the first check on a new subscription sends nothing at all: it records the current state, and you hear from us when that state changes.
Approaching an edge is treated differently, because it is a condition rather than a transition — a price sitting near a boundary would otherwise produce a message every five minutes. It carries a six-hour cooldown per subscription, and the threshold adapts to the width of the range: a range narrower than about twenty percent is always within five percent of one of its own edges, so a flat five percent would mean "always approaching".
Signing in
Nudges are tied to an address, so there is one signature to prove the address is yours. It is a message, not a transaction: it costs nothing, moves nothing, and grants no permission over your funds or your patches. The signed text names this domain, and a signature carrying any other domain is refused — so a signature collected elsewhere cannot be turned into a session here.
The session lasts thirty days and lives in this browser only. Clearing site data ends it. There is no password, no email, and no account.
Where messages go
| Channel | Arrives |
|---|---|
| In this app | When you open the nudges page. A browser notification also appears, but only while a tab is open. |
| Webhook | A POST to a Discord or Slack URL, whether or not you have the site open. The URL must be https and must not point at an internal address. |
| Telegram | A message from the bot to the chat id you provide, whether or not you have the site open. |
They are drawn by the page, so they arrive only while a tab is open. If you want to hear about a patch while the site is closed, use the webhook or Telegram. The interface says this next to the switch as well, because assuming otherwise is the way to miss the one message you wanted.
When delivery fails
A failed send is recorded against that message and retried on later runs, at most three times, after which it is left marked as failed and visible on the nudges page. One dead webhook never blocks anybody else's messages in the same run, and never stops the next check.