32: Nostrology w/ WhisperHash — No Solutions

"No Solutions, do the homework."

WhisperHash came to Sovereign Engineering by following breadcrumbs: Bitcoin first, then small solo miners, then Nostr, then No Solutions, then the strange realization that the protocol was not just another social network. After losing a valuable Instagram handle to platform control, the idea of cryptographic identity stopped being abstract. If you do not hold the keys, you do not own the thing.

The mining part of the walk starts with NerdMiner and ESP32 tinkering, moves into BitAxe and open-source ASICs, and lands on the dream of a quiet fanless home miner that can coexist with humans. The Nostr part starts with a data question: how many people are actually here, how many sats are moving, and which numbers should anyone trust?

That question became Nostrology, an ecosystem observatory for Nostr data. But making data visible is not neutral. DAU, MAU, relay lists, zaps, Nutzaps, and follow history all exist somewhere in the event graph, but packaging them into convenient datasets changes the trade-off. Some data wants to be useful. Some data probably wants to rot.

The deeper thread is about primitives. Blossom, FIPS, Zapstore, Nostr identities, Parquet files, and ContextVM all show up as ways to compose small pieces into larger systems without pretending there is one global application. If the abstractions are right, things stack. If the abstractions leak, you get a different kind of centralization with better branding.

In this dialogue:

how WhisperHash found Bitcoin, dismissed Nostr as "decentralized social," and then got pulled back in by ownership, identity, and curiosity
why losing a valuable Instagram handle made platform ownership feel concrete
how a data-science background turned into a search for something useful to build in Bitcoin
why NerdMiner, ESP32 boards, BitAxe, OSMU, and solo mining made mining tangible again
what changes when a miner is something you live with, tune, cool, and hear
why fanless home mining is partly a hardware problem and partly a co-living problem
how Nostr became interesting once WhisperHash started asking basic measurement questions
why active-user counts on Nostr are harder, messier, and more political than they look
how No Solutions served as a strange curriculum for catching up on Sovereign Engineering and Nostr culture
why demo day failure is acceptable, but opting out and showing slides are not
how Blossom, FIPS, Zapstore, and Nostr identities feel like primitives that are finally starting to compose
why Zapstore is a natural fit for Nostr and a glimpse of a different Android distribution model
how app stores, agents, GitHub releases, signatures, and social trust start to blur together
why durable formats matter if you want software and data to survive beyond the current wave
how Silicon Valley, London, Hong Kong, and SEC-08 all shaped WhisperHash's sense of software culture
what Nostrology is trying to observe across relays, lightning, Zapstore, and Nutzaps
why publishing small numbers can help builders, hurt momentum, or do both at once
why Parquet is a practical format for large Nostr datasets even if the events themselves remain the source
how Blossom, storage providers, and ContextVM point toward Nostr-native access without replicating terabytes everywhere
where data ethics, bit rot, public events, and easy aggregation start to collide
why the right next step is not a grand platform, but a tracer bullet that proves someone can consume the data end to end

Related dialogues:

People mentioned:

Projects & tech mentioned:

Recorded at 959,604.