Nuclear Pulse

Contact

The single public contact channel for Nuclear Pulse is the author's Nostr identifier:

henkypenky@huszonegy.world (NIP-05 verified handle)

• Nostr npub (resolved via NIP-05): npub1h0h4pyaajj5r7zu4jn0mx22vkw94avffzpd7hdarjkx56ufzskfqjrtf8e
• Profile URL (npub-based, reliably cached): njump.me/npub1h0h4pyaajj5r7zu4jn0mx22vkw94avffzpd7hdarjkx56ufzskfqjrtf8e
• NIP-05 verification endpoint: https://huszonegy.world/.well-known/nostr.json?name=henkypenky
• DM format: NIP-04 or NIP-44 encrypted DM only (plaintext DMs are ignored)
• Response SLA: none — typically a few days, not guaranteed

There is no email, no Mastodon, no Matrix, no Discord, no GitHub issues, no Twitter DMs. The Nostr handle is the only channel.

Use the npub directly in any Nostr client, or follow the npub-based njump.me link above. (Public NIP-05 web look-ups via the handle, like njump.me/<handle>, are not yet cached for this domain.)

Why only Nostr?

Nuclear Pulse is an independent compilation effort with a deliberately small surface area. The reasons for keeping contact to a single Nostr npub are:

• Editorial integrity — Nostr DMs are end-to-end encrypted and do not feed into any centralized moderation queue. Every issue reads the same regardless of who writes in.
• Privacy — Nostr's pubkey-based identity is pseudonymous by default. There is no email address, phone number, or corporate identity attached to the npub. This matches the privacy posture of the briefing itself.
• Capacity — the briefing is produced on a personal schedule. There is no team available to triage email, tickets, or chat platforms.
• Verification — every claim in Nuclear Pulse is sourced. If a source is wrong, the correction is published in the next issue, not in a private message reply.

What if I have a correction?

If you spot a factual error in a past issue, the most effective path is to:

1. Identify the issue date and the numbered source (e.g., "Issue 2026-08-23, source #18")
2. Check whether the underlying source publication has issued a correction (most reputable industry publications maintain a corrections page)
3. Send an encrypted Nostr DM with the issue date, source number, and the corrected information
4. Wait for the next issue — recurring factual patterns get caught and corrected within 1-2 weekly cycles

Nuclear Pulse does not maintain a public errata page because corrections are infrequent and are integrated into subsequent issues' source notes.

What if I want to subscribe?

There is no subscription mechanism because there is no contact channel. To follow Nuclear Pulse:

• Bookmark index.html — the latest issue is always at this URL
• Check archive.html periodically for the running archive
• Read llms.txt programmatically if you maintain an AI agent
• Fetch sitemap.xml if you want to track new issues via RSS-like tooling

Press and licensing inquiries

For re-licensing Nuclear Pulse content into a third-party publication, the CC BY-SA 4.0 license applies automatically — no permission needed, attribution required. For commercial re-use at scale, see the license text at creativecommons.org/licenses/by-sa/4.0/.

Security disclosures

If you have discovered a security vulnerability in this site, send an encrypted Nostr DM to the npub above. There is no bug bounty program.