View article → Nostr Relays

Show Notes: - Nostr is built on a simple promise: no single entity can control the network because no single entity controls the relays - In practice, users gravitate to familiar relays, developers default to known endpoints, and the network coalesces around a handful of large hubs - If everyone routes their notes through the same five relays, censorship resistance is lost because pressuring five operators becomes trivial - Centralization in Nostr does not happen because the protocol forces it; it happens because humans are lazy and networks have gravity - Default relay lists in clients create path dependence: once a few relays become default, they become self-reinforcing - The result is a power-law distribution where a small number of relays handle the vast majority of traffic - If the five largest relays are hosted in the same jurisdiction, a government can pressure them all simultaneously - If they are operated by the same small group, social pressure can silence them - If they rely on the same cloud provider, a technical failure can take them all down - The protocol does not prevent this. The protocol cannot prevent this. The network is what we make it. - NIP-65 gives users a way to declare their chosen relays, enabling the outbox model where content is found by querying the relays a user publishes to - If users only declare the same five relays, NIP-65 does nothing to decentralize the network - NIP-11 lets relays advertise their policies, uptime, and supported features, enabling informed choice - If users never read relay information documents, the information is irrelevant - NIP-66 provides a way to find new relays beyond default lists - If discovery tools themselves become centralized, we have only moved the centralization problem up one layer - NIP-29 and NIP-72 provide frameworks for relay-based groups and moderated communities - If these groups are built on the same few large relays, they are not independent—they are tenants - A user with a default client has theoretical freedom to choose any relay, but theoretical freedom is not practical freedom - Most users do not want to manage relay lists, evaluate uptime statistics, or consider jurisdictional implications - The danger is that the network becomes centralized by default, with new relays unable to gain traction - The protocol enables decentralization but does not ensure it - Not all centralization is bad. Some centralization is intentional, purposeful, and aligned with community values - A Bitcoin-only merchant relay serves a community of Bitcoin businesses who want a space where everyone shares their values - Public relays are noisy, filled with irrelevant content, and subject to moderation policies that may not align with the community - A private relay for Bitcoin merchants is centralized in operation but does not threaten the wider network because the wider network does not depend on it - Its users also publish to other relays. Their content is distributed. Their community is focused. - Economic alignment matters: when a relay serves a community of merchants, incentives align with the community's interests - This model scales: relays can exist for Bitcoin developers, Lightning node operators, privacy advocates, journalists, artists, and any community with shared values - Pyramid is a relay implementation that introduces hierarchical membership, where members invite other members and the invitation tree defines the community - The root member invites a small number of trusted people, who invite others, and the tree grows - Each member is responsible for their invited descendants. If someone misbehaves, their inviter can remove them. - This is centralization with accountability. Membership is distributed across a tree of trust. - For a Bitcoin merchant community, the root member might be a well-known business that invites trusted partners, who invite their trusted partners - The invite tree grows along lines of existing relationships: supply chains, business partnerships, industry associations - The invite tree creates natural accountability: a merchant who invites a bad actor is responsible and can be held accountable by the community - This is stronger than platform moderation because it is personal, not algorithmic - NIP-85 defines trusted assertions: signed statements that a pubkey is trustworthy, an event is authentic, or a relay is reliable - In a world of community relays, trusted assertions become the currency of reputation - A Bitcoin merchant relay can use NIP-85 to attest that a member is a legitimate business - The assertion is signed by the relay operator or a trusted community member and can be published to other relays - This decentralizes reputation: endorsement carries weight because the community has built trust over time, and the endorsement is verifiable, signed, and portable - NIP-85 also allows for negative assertions, enabling communities to warn the network about known bad actors - Trusted assertions bridge community relays to the wider network, creating a web of trust across multiple communities - Running a relay costs $5 to $20 per month for a server - Community relays pool resources: fifty Bitcoin merchants can easily cover the cost of a relay, making it trivial per person - Lightning payments support relay operations through NIP-57 zaps and NIP-75 zap goals, allowing communities to tip or crowdfund relay costs - Pyramid adds the option of invite fees: a new member pays a small Bitcoin fee to join, supporting the relay and creating a barrier to entry that deters spam - Monoculture is when the entire network depends on a small set of relays, operators, and jurisdictions - Monoculture is the failure of decentralization - Monoculture happens when convenience wins, default lists go unchallenged, and users never choose - The NIPs provide tools to combat monoculture, but tools are not enough - The community must value resilience over convenience - The alternative is a mesh of thousands of small nodes, each serving a community of shared interest - Every user publishes to a personal relay, a community relay, and a few public relays - Content is discovered through NIP-65, not through default lists - The network has no large hubs, only many small nodes - The hardware costs are trivial: $5 per month VPS, Raspberry Pi at home - The barrier is social, not technical: the willingness to take responsibility and build - The most important thing any user can do is run their own relay - A personal relay gives you sovereignty: a place to publish that no one else controls - Form communities that share your values, run a relay for that community, use Pyramid to build an invite tree - Join multiple communities and publish to all of them - Use NIP-65 to declare your relays so the network knows where to find you - Zap relay operators and set up recurring payments to make relay operation sustainable - Build better discovery tools, reputation systems, and ways to find communities that match your values - Value resilience over convenience - Nostr does not guarantee decentralization. It enables it. The difference is everything. - If we let default lists define the network and cluster around a handful of relays, we have not escaped centralization—we have just moved it - The same five relays become the new platform. The same pressures apply. The same vulnerabilities exist. - If we choose to run relays, form communities, and use the tools the NIPs provide, we can create a network that is truly distributed - A network where no single entity controls the flow of information - A network where censorship resistance is not a promise, but a property - The Bitcoin merchant relay is a model. Pyramid is a tool. NIP-65, NIP-66, NIP-85, NIP-29 are enablers. - The network is what we make it. Make it resilient.

Show Notes: The Sovereign Library Goals and Strategies for the Librarian Architecture of Curation - Move from mere collection to a functional system of knowledge. - Implement the Core-Satellite Model: maintain a base of 50 to 100 essential books supported by a rotating set of niche research texts. - Apply the Feynman Filter: a book is only truly owned once its thesis can be explained simply to a peer. Distribution via Pyramid Relay - Use fiatjafs Pyramid Relay to move beyond the noise of public squares. - Establish Gated Gardens where only verified librarians can publish book events and metadata. - Transform the relay into a high-signal distribution point that facilitates sovereign peer-to-peer discovery. The Biliterate Mandate - Maintain both digital and physical formats to balance velocity with veracity. - Utilize Digital for the engineers workflow: instant searchability, portability, and global distribution via Nostr, Arweave and IPFS. - Retain Physical for cognitive depth and censorship resistance: paper is the ultimate cold storage that cannot be remotely deleted or edited. The Ten Year Investment Horizon - Treat high-value books as a form of Proof of Work rather than a quick flip. - Commit to active stewardship: climate control and provenance research are required to maintain value. - Recognize books as illiquid assets that require at least a decade to realize their scarcity premium and cultural Lindy effect. Ten Principles of the Noetic Librarian - Own the keys to both digital encrypted files and physical bookshelves. - Verify the hashes of digital editions against original first edition checksums. - Run your own relay to host niche community knowledge. - Convert digital gains into physical anchors that outlive the current tech cycle. - Focus on curation over quantity: a small library of truth outweighs a giant library of noise. #Books #Memphis

You’ve got a prayer in Memphis

Show Notes: The Pyramid Guild Reborn Goals and Strategies for the Sovereign Nostr Bookstore Establishing Noetic Discovery Shift from algorithmic Top 10 lists to Web-of-Trust (WoT) curation. Utilize niche authority and librarian boosts to surface high-value knowledge over high-volume filler. Transform the bookstore from a retail site into a Cultural Outpost for specific intellectual communities. Building the Library of the Spirit Merge the act of selling with the mission of Preservation. Utilize NIP-23 (Long-Form Content) and NIP-94 (File Metadata) to create permanent, hash-verified records of human thought. Ensure digital content remains Atomic and independent of the platform that hosts it. Implementing High-Signal Curation via Pyramid Relay Use fiatjaf’s Pyramid Relay to create Librarian-Only submission gates. Apply the Relay as a Filter strategy: only signed events from verified curators are broadcast, effectively scrubbing the noise. Migrate from passive data pipes to active Institutional Libraries. Architecting Sovereign Infrastructure Organize Reading Rooms and specialized collections via Private Groups to protect sensitive or controversial texts. Leverage Censorship Resistance: treat relays as distributed Distribution Points that cannot be centrally lobotomized or un-sold. Empower the Sovereign Individual to own their metadata, their reviews, and their relationship with the reader. Financial and Intellectual Circularity Integrate Bitcoin/Lightning (Zaps) for instant, peer-to-peer micro-payments, bypassing traditional 70 percent publisher taxes. Enable Permissionless Publishing: removing the need for centralized licenses or Library of Congress approval. Foster an Infinite Game where the bookstore’s value is built on its Lindy Effect (longevity and trust) within the decentralized web. #Memphis

The UTXO Model and the Physics of Sovereign Value

Nothing special, just another sunrise

Sat here for an hour. Made a list of the things I'm grateful for and why they hold value to me. #Gratitude

Elisavetpol Pashalik

Eyes of Elisavetpol

Caspian Pashalik

Wherostr,Freeform,Freerse

Relays stronger than bombs

Hopefully I can get outbox relay feed up today

Value determined by peer urgency not production

Ultimate Disaster

Barry Deen and Fiatjaf . Top tier devs on Nostr

Running Algol by Barry Deen

Can someone help me setup outbox-feed-relay by bitvora? Been 6.5 hours and nothing is working #asknostr

Freemarkets using Bitcoin via Nostr Relays