A WASM LNbits extension with one BTC/USD price history for the entire instance, private user alerts, and optional daily summaries. Prices use LNbits' configured exchange-rate providers and cache, rounded to USD cents. No external price provider is needed.
Integration pending: this staged revision has its history, chart, alerts, and compiled component ready for review. Automatic activation of the collector and its storage-owner context require the separately proposed core support. The manifest deliberately does not yet declare automatic schedules. Do not install this draft until the collector integration is completed.
The intended collector runs once per minute for the instance, beginning on extension activation without a user visiting the UI. Ordinary users have no start/stop controls. Every user reads the same history; alert and notification settings remain private.
| Resolution | Retention |
|---|---|
| Minute | Last 24 hours |
| Hour | Last 7 days |
| Day | Last 366 days |
| Calendar month | Forever |
A sample exactly on a retention boundary is retained. Each aggregate keeps its open, high, low, close, observation count, and the timestamps of its extrema. Hour/day/month boundaries use UTC. The collector prunes the shorter resolutions on each successful observation; monthly data is stored in calendar-year chunks. Collection downtime leaves gaps. Data is not fabricated or backfilled.
The chart below the current price offers 1D, 1W, 1M, 1Y, and All. Its line follows closing prices and shading shows the recorded low/high range. Dense data is reduced for display while preserving extrema; stored minute observations remain complete. Hover, touch, or keyboard inspection shows prices and timestamps. Longer chart ranges use the retained coarser resolutions. A fresh database shows only observations collected since activation.
Create, edit, disable/enable, or delete up to 50 private alerts. Each includes:
- A name (1–80 characters).
- A positive USD fluctuation threshold.
- A whole-number interval in minutes (at least 10), hours, days, weeks, or months. Alert months mean 30 days; stored monthly aggregates use calendar months.
- One or more notification channels: email, Telegram, Nostr.
An alert triggers when the highest minus lowest recorded price within its rolling window reaches the threshold. A rise followed by a return to the starting price still counts. Confirmed fluctuation can trigger as soon as observations establish it; collecting a complete window is not required. Missing observations are never invented, and checks skip when the newest price is more than two minutes old.
A channel is notified once while the condition remains active. The alert rearms when the recorded fluctuation falls below the threshold. Changing the threshold, interval, channels, or enabled state starts a fresh rule evaluation; renaming alone does not send a duplicate. Successful channel receipts are kept if another channel fails, so the next check retries only unsent channels. Notification bursts are drained over successive minute checks (up to 15 channel attempts per check) to respect WASM limits. Pending channels retain the original event and timestamp even if its window clears before delivery.
Windows up to one day use minute observations; up to seven days use hourly extrema, up to 366 days use daily extrema, and longer windows use monthly extrema. An older aggregate straddling the start of a window cannot reveal every interior price after its finer history expires. To avoid a false notification from an expired peak, only its timestamped open/close/extrema inside the window count toward triggering. Rearming waits until even the entire intersecting aggregate is below the threshold. This can delay triggering or rearming for a partial older bucket.
Configure notification destinations in the user's LNbits account. Pricebot uses the saved settings for each selected channel. A queued message does not guarantee delivery. A process failure between queuing and saving a receipt can cause a repeat; the host does not offer an atomic notification-and-storage transaction.
Saving an alert creates or resumes the user's check-alerts job (* * * * *, UTC).
Saving summary preferences creates or updates daily-summary (0 9 * * *, UTC).
Existing matching jobs are reused without postponing their next run. These user
jobs never collect prices. The optional summary includes the current price and
24-hour change, requires a full-day baseline, and queues once per selected
channel per UTC day during normal operation.
Disabling the extension for a user stops that user's jobs through the host's access checks. The instance collector belongs to the extension, independent of any account. Global extension deactivation prevents its scheduled work.
The fresh schema creates history, preferences, alerts, and state inside
the extension database. No legacy-data conversion is provided.
The collector writes through current owner-scoped storage methods using a dedicated
extension owner. Users read only history through storage.get_public and
storage.get_public_paginated, with an explicit field/source policy. Private
alerts and notification state are not public. No deprecated shared-storage import
or invented shared-storage permission is used.
The pending host integration must start the approved instance schedule on activation/startup and supply the collector's extension storage owner. The existing administrator-owned alternative would require a one-time manual setup and would tie collection to that account.
Use Node.js 22 or newer and the existing pinned @bytecodealliance/jco toolchain.
make check
make buildmake check covers history retention, UTC boundaries, partial-write recovery,
shared reads with isolated alerts, rolling fluctuations, channel retries, and
input validation. make build compiles the guest into wasm/module.wasm using
the WIT contract. Browser files use Vue render functions and native SVG, without
runtime template compilation or an additional chart dependency.
Install through LNbits' installation flow to apply the fresh schema and approve the manifest permissions once the collector integration is completed. A symlink alone does not install storage migrations, approve permissions, or start jobs.