1 · Configure your jar
The default jar points at the builder's donation address — replace it with your own prl1… address to collect your own tips.
2 · Live preview — this is the real widget, polling Blockbook now
3 · Copy the snippet
One block: a mount <div>, the jar config as JSON, and the self-contained widget script. No external JS or CSS — only your Blockbook URL is fetched at runtime. Paste it into any HTML page and it works.
4 · Tamper-evident descriptor
The descriptor commits to your exact jar config (SHA-256 of the canonical JSON). Publish it next to your snippet — anyone can re-verify the config against it.
Standalone verifier
Paste any config JSON + descriptor. If a single character was altered after forging, verification loudly refuses.
Listen mode — watch any jar address live
Uses the current wizard config (generate first, or it watches the default jar). Start listening to see the jar fill, confetti on new tips, the tip feed, and totals — plus CSV export of every detected tip.
Honest limits
- Read-only, always. The widget and this page issue GET-only Blockbook reads. Neither can move funds, sign, or broadcast — tipping happens in the visitor's own wallet via the pearl: URI / QR.
- Tips count at 1+ confirmations. Unconfirmed mempool transactions are not shown as tips.
- Dust is not a tip. Outputs below 1,000 grains (0.00001 PRL) are ignored — they're uneconomical to ever spend and would let anyone spam the jar feed for free.
- Polling cadence. Default every 30 seconds, configurable 15–300s. Be courteous to public Blockbook instances: longer intervals on high-traffic pages.
- No background notifications. When the tab or page is closed, polling stops — tips that land while you're away appear on the next poll.
- New-tip detection is per page load. Seen transaction IDs are tracked in page memory. The first successful poll is a silent baseline (existing tips show as history, no confetti); only tips arriving after that get the confetti burst. Reloading the page re-baselines.
- Descriptor ≠ signature. The tipjar:v1: descriptor proves the config wasn't altered after forging; it doesn't prove who forged it.