Stats badge (recommended) — countdown, era, and block reward
HTML to copy
<a href="https://why21million.com/" rel="nofollow noopener">
<img src="https://why21million.com/badge-stats.svg"
width="300" height="100"
alt="Bitcoin halving stats — why21million.com" />
</a>
Compact badge — countdown only
<a href="https://why21million.com/" rel="nofollow noopener">
<img src="https://why21million.com/badge.svg"
width="240" height="64"
alt="Next Bitcoin halving — why21million.com" />
</a>
These are static SVG images, not tracking pixels. Hosted images make a request to why21million.com unless served from cache, consume bandwidth, and require your site's CSP img-src policy to allow this host. To self-host, save the image and replace its src with your own URL. Attribution is optional: remove the surrounding <a> and </a> tags to use the image without a link.
Loss-evidence badge — estimates are not proof
HTML to copy
<a href="https://why21million.com/lost-bitcoin/" rel="nofollow noopener">
<img src="https://why21million.com/badge-lost.svg"
width="300" height="100"
alt="Bitcoin loss evidence: lost keys are not directly observable; dormant does not mean lost; estimates are not proof." />
</a>
The optional link points to the loss-evidence reference page, which distinguishes script-level unspendability, address-based inference and dormancy. The badge supplies no numerical loss or liquid-supply estimate; unresolved historical figures on the reference page are labeled unverified.
Why this exists
These badges offer a compact visual aid, not a live data feed. Halving dates are estimates, and static images can become outdated. Hosted assets may be revised, but browser and third-party caches can retain older versions; freshness is not guaranteed. Self-hosted copies do not update automatically. Check the underlying resource before relying on a displayed date or number. A link back is appreciated but not required.