LIVEBTC $84,614 ↗ +5.16%ETH $2,720 ↗ +5.42%SOL $115.83 ↗ +6.90%XRP $1.47 ↗ +6.53%BNB $783.36 ↗ +4.34%HYPE $94.98 ↗ +4.47%ZEC $1,515 ↗ +5.01%STRK $0.05 ↗ +4.06%BTC $84,614 ↗ +5.16%ETH $2,720 ↗ +5.42%SOL $115.83 ↗ +6.90%XRP $1.47 ↗ +6.53%
Monday, September 21, 202610:01 UTC
Newsletter

Daily signal

The day’s most widely covered stories, ranked the way the front page ranks them, with every source link attached.

Sign-ups are not open yetThere is no mailing list behind this site, so the form below is switched off rather than taking an address it cannot save. No issue has been sent to anyone, and no address has been stored. When that changes this page changes with it — a form that shows a green tick and drops the address is worse than no form.

The form

Disabled while there is no list to join. Nothing is submitted and nothing is stored.

What would arrive

Headlines · Every weekday morningPlanned
The day's most widely covered stories, in the order this site ranked them, with the source links attached.
  • ·Overnight price action across the twelve assets tracked here
  • ·Policy and regulatory filings from the last 24 hours
  • ·Every item links to the reporting it came from
The Protocol · WeeklyPlanned
Upgrades, client releases, incidents and the infrastructure stories that do not make the front page.
  • ·Network upgrade and fork tracker
  • ·Disclosed vulnerabilities and post-mortems
  • ·Testnet and mainnet milestones

Both are marked planned because neither has ever been sent. There are no sample issues to link to, and inventing one would be describing a publication that does not exist.

What happens to your address

Nothing, because the form will not accept one. If a provider is connected later, addresses will be held by that provider rather than on this site, used only for the editions chosen, and removable by the unsubscribe link in any issue. The full position is in the privacy notice.

For the site owner

The journey is built and tested end to end — selection, validation, consent, duplicate handling, rate limiting and real error states. It is waiting on credentials, not on code. Set one of these groups and the form goes live on the next deploy:

  • NEWSLETTER_PROVIDER=buttondown BUTTONDOWN_API_KEY=…
  • NEWSLETTER_PROVIDER=resend RESEND_API_KEY=… RESEND_AUDIENCE_ID=…
  • NEWSLETTER_PROVIDER=kit KIT_API_KEY=… KIT_FORM_ID=…

In the meantime

The RSS feed carries stories written here, in full order, and needs no address.