🟣 Nostr – Sunday, 20 September 2026
**Amethyst ships BOLT12, splits core**
Amethyst v1.16.0 (September 17) adds BOLT12 lightning offers to its payment rail and zap picker with BOLT11 fallback, a "My Fitness" Health Connect dashboard, and splits its commons module into headless and UI layers while fixing 34 bugs.
**Jumble tightens relay reliability**
Jumble's latest tagged release, 26.9.2, updated its nostr-tools library so relays that dropped a connection are properly closed instead of left half-open, and fixed queries that could get stuck pending — a reliability release rather than a move on the contested private-messaging or reply standards.
Previously:
GitHub
Release v1.16.0: My Fitness, BOLT12 Payments, and a Leaner Core · vitorpamplona/amethyst
What's Changed
Fix single-flight guarantee for fast signers in BlossomReadAuthTokenProvider by @vitorpamplona in #4100
chore: sync geode Homebrew ...
Freedom.Tech
Jumble 26.9.2
Displays favorite relay lists from kind 10012 events
🟣 Nostr – Saturday, 19 September 2026
**Amethyst and fiatjaf clash over NIP-17 seal timestamps**
A September 17 PR (nips 2471) from fiatjaf proposes dropping the requirement that NIP-17 seal timestamps be randomized, arguing "it makes no sense to design a protocol assuming clients will implement it incorrectly." Vitor Pamplona (Amethyst) opposes the change, warning that seals persist on relays even when rumors don't, so removing randomization would reopen a metadata-leak vector NIP-17 was built to close. The PR remains open with no resolution, a rare live protocol-level dispute between two of Nostr's most active maintainers.
https://github.com/nostr-protocol/nips/pull/2471
Previously: View quoted note →
View quoted note →