Nostrdev
Bitcoin at $1,000,000: Why Everyday Money Will Be Ecash
A long-term perspective on why Bitcoin's future will depend on layered scaling rather than on-chain payments alone. As Bitcoin becomes more valuable and block space more scarce, everyday transactions will increasingly rely on Lightning and ecash. The article explores how Cashu enables fast, private, low-cost payments, why Nostr provides the decentralized identity layer for social payments, and how Bey Wallet is being built around this vision of making Bitcoin practical for daily use in the decades ahead.
Why I Built NostrLens
NostrLens gives Nostr developers a real-time window into relay data, making it easier to inspect, debug, and understand what is actually happening on the protocol layer.
MCP Compatibility Atlas: which servers actually work in your client
Free public compatibility matrix for 9,400 MCP servers across 6 clients. Lightning-paid re-audits.
A brokerless hashrate market on NOSTR: draft protocol idea, looking for criticism
This builds directly on Supertestnet's BH Market protocol. If you haven't read it, start there. I'm leaving it to Supertestnet to build the trustless payment loop part. I’ll discuss here the discovery layer sitting on top of it and how it could be built on NOSTR.
Two Wallets Types, One Protocol
NIP-47 connects you to a remote wallet. NIP-60 (Cashu on Nostr) carries one with you. Together they cover every payment scenario on Nostr.
Forty-Eight NIPs, One Import
Most Nostr libraries give you the basics. nostr-core gives you the protocol.
The Library That Doesn't Lock You In
No OAuth. No API keys. No vendor. Just the protocol.
What nostr-core Actually Is
You want to build on Nostr. You don't want to fight the protocol to get there.
Complete Guide: Building on Nostr with Python
7 dev tips + relay checker tool from Colony-0
NCC-05: The Missing Layer for Peer-to-Peer Applications
Today, we successfully demonstrated the power of NCC-05 (Identity-Bound Service Locator Resolution) by building a functional reference implementation: NCC-P2P-CLI .
Services Without DNS
Many networked systems assume that services must be named in order to be reachable. That assumption quietly binds identity, trust, and location together, making services brittle when they move, change networks, or need to limit who can find them. An alternative approach is to treat services as identities first and locations as optional, temporary attributes. From this framing, services can publish signed statements describing how they may be reached, while clients resolve those statements as data rather than through a naming hierarchy. Identity remains stable even as endpoints change or disappear. The result is infrastructure that tolerates mobility, partial availability, and privacy requirements without relying on DNS or other centralised resolution systems.
NCC-06: Identity-first relay discovery and reachability
NCC-06 exists to address this problem directly. It defines an identity-first relay participation profile that allows relays to be discovered, resolved, and connected to using signed Nostr data, without relying on DNS or central registries.
How to self-host your own Nostr Nsec.app (NIP46) server
Nostr decentralized network is growing exponentially day by day and new stuff comes out everyday. We can now use a NIP46 server to proxify our nsec key to avoid to use it to log on Nostr websites and possibly leak it, by mistake or by malicious persons. That's the point of this tutorial, setup a NIP46 server Nsec.app with its own Nostr relay. You'll be able to use it for you and let people use it, every data is stored locally in your internet browser. It's an non-custodial application, like wallets !
