Nostr notes by Cuda

tell me that you are rich without telling me

2026-04-10T10:42:38Z

In reply to nevent1q…eraa
_________________________

tell me that you are rich without telling me

Traveling through Asia has shown me one thing: how incredibly ...

2026-04-05T04:58:31Z

Traveling through Asia has shown me one thing: how incredibly addicted people can become to #TikTok and similar apps. It's frightening to see a group of people sitting together, wordlessly staring at their devices for hours. Usually with sound on, so you can hear them constantly watching some #brainrod content. This is not just some people or only young people - this is everyone. Even in shops, you sometimes have to speak to people loudly because they don't notice you otherwise. However, what I find most disturbing is children sitting in strollers with pacifiers in their mouths, staring at a phone. They can already operate the phone but can barely feed themselves independently. To me, this looks less like a cool new form of entertainment and more like an #epidemic.

Have you noticed that around you? #asknostr

#grownostr

I love Zeus but it is to complex for newbies. And Phoenix has no ...

2026-03-25T16:15:12Z

In reply to nevent1q…7hng
_________________________

I love Zeus but it is to complex for newbies. And Phoenix has no on-chain wallet.

Yes, but no onchain wallet.

2026-03-25T16:10:48Z

In reply to nevent1q…kext
_________________________

Yes, but no onchain wallet.

What is the most newbie friendly (onchain) #bitcoin #wallet on ...

2026-03-25T07:31:14Z

What is the most newbie friendly (onchain) #bitcoin #wallet on android?

#asknostr

You are the cow, right?

2026-03-25T04:20:15Z

In reply to nevent1q…zvvn
_________________________

You are the cow, right?

Check the user id, it ends on "nostr.pub" which is a ...

2026-03-23T08:00:37Z

In reply to nevent1q…c73k
_________________________

Check the user id, it ends on "nostr.pub" which is a service to bridge Mastodon to nostr. You can bridge any Mastodon user. Users don't even know that they are bridged.

Mastodon user 😫

2026-03-23T07:57:33Z

In reply to nevent1q…63me
_________________________

Mastodon user 😫

8th of March til today. As it says on the chart 😉

2026-03-22T12:26:21Z

In reply to nevent1q…dclk
_________________________

8th of March til today. As it says on the chart 😉

But it could have an personal aggregator which looks at my follow ...

2026-03-22T06:54:40Z

In reply to nevent1q…mttk
_________________________

But it could have an personal aggregator which looks at my follow list to make sure it has all outbox relays of people I follow, no?

nice, I check it out. Do you think it makes a big difference on ...

2026-03-22T05:47:00Z

In reply to nevent1q…uk3j
_________________________

nice, I check it out. Do you think it makes a big difference on mobile when using a proxy / aggregator instead of connecting to each relay individually? heaven does not have that functionality, right? only the blaster?

I think I use #wisp to much? 😆 ...

2026-03-22T04:21:46Z

I think I use #wisp to much? 😆

Agreed, but that might not be the target audience. Social media ...

2026-03-21T08:54:29Z

In reply to nevent1q…t9g6
_________________________

Agreed, but that might not be the target audience. Social media already has a lot of Bitcoin voices. I think many people still read and use other media less - this group probably has a better chance of actually understanding it since it is such a big topic which needs a lot of attention / time to understand it.

It would be great if we had a good, beginner-friendly Bitcoin ...

2026-03-21T06:59:08Z

It would be great if we had a good, beginner-friendly Bitcoin book with a free license. We could then print it as cheaply as possible and distribute it to public places like cafes or bookcases to spread the word. Would love to see that.

#bookstr #reading #bitcoin #book

Love the idea. definitely #underrated #naddr1qq…3g0c

2026-03-21T06:48:56Z

Love the idea. definitely #underrated

quoting
naddr1qq…3g0c

Demo: https://blog.nostrize.me

Source code: nostr-static

Prerequisites

Before using nostr-static, you'll need:

Nostr Articles: You can either:

Create new articles using platforms like yakihonne.com or habla.news

Find existing articles on Nostr

Copy the naddr string from the article (usually can be found in the address bar)

Author Profiles: For each article's author:

Copy their public key (pubkey)

Visit njump.me/npub1xxxxx (replace with the actual pubkey)

Copy the nprofile string from the page

These identifiers (naddr for articles and nprofile for authors) are essential for the tool to fetch and display your content correctly.

Features

Core Functionality

Index Page: A homepage featuring your blog's title, logo, article summaries, and tags

Article Pages: Individual pages for each article, including:

Title and logo

Article summary

Full content

Tags

Comments (via ZapThreads integration)

Social Features

Comments: Integrated with ZapThreads for decentralized commenting

Nostr Connect: Seamless integration with window.nostr.js (wnj), supporting NIP-46 bunker connect

Content Organization

Tag Pages: Browse articles filtered by specific tags

Profile Pages: View articles from specific authors

Manual Curation: Select and order articles by adding their naddr strings (see NIP-19)

Customization Options

Themes: Choose between dark and light mode

Branding:

Custom logo

Custom blog title

Network: Specify your preferred Nostr relays

Technical Requirements

Profile Format: Authors must be added in nprofile format (see NIP-19) for consistency

Automatic Updates: Built-in scripts for:

Windows Task Scheduler

Unix/Linux cron jobs

Getting Started

Fork and Clone:

Fork this repository to your GitHub account

Clone it to your local machine or use GitHub Codespaces for a cloud-based development environment

Watch this quick tutorial to learn more about GitHub Codespaces

Configuration: Set up your config.yaml file with:

Blog title and logo

Theme preference

Relay list

Article naddr strings

Author nprofile strings

Content Selection: Add your desired articles by including their naddr strings in the configuration

Author Selection: You have to add the nprofile strings of the articles. This is needed for URL consistancy.

Build & Run: Follow the instruction in the README at https://github.com/dhalsim/nostr-static

Deployment: Choose your preferred static hosting service and deploy the generated HTML files

Updates: Set up automatic updates using the provided scripts for your operating system (For github pages)

Deployment Options

GitHub Pages (Recommended)

GitHub Pages provides free hosting for static websites. Here's how to set it up:

Enable GitHub Pages:

Go to your repository's Settings

Navigate to "Pages" in the menu

Under "Build and deployment" > "Source", select "GitHub Actions"

Enable Actions by following the GitHub Actions settings guide

Go to the "Actions" tab in the top menu. If you see the message "Workflows aren't being run on this forked repository", click the "I understand my workflows, go ahead and enable them" button

Custom Domain Setup:

Purchase a domain from your preferred domain registrar

Create a CNAME record in your domain's DNS settings:

Type: CNAME

Name: @ or www or a subdomain you prefer (depending on your preference)

Value: YOUR_GITHUB_USERNAME.github.io

In your repository's GitHub Pages settings:

Enter your custom domain in the "Custom domain" field

Check "Enforce HTTPS" for secure connections

Wait for DNS propagation (can take up to 24 hours)

Your site will be available at your custom domain

Other Hosting Options

You can also deploy your static site to any hosting service that supports static websites, such as: - Netlify - Vercel - Cloudflare Pages - Amazon S3 - Any traditional web hosting service

Why nostr-static?

nostr-static offers a unique solution for bloggers who want to leverage Nostr's decentralized content while maintaining a traditional web presence. It combines the best of both worlds:

Decentralized Content: Your articles live on the Nostr network

Traditional Web Presence: A familiar blog interface for your readers

Easy Maintenance: Simple configuration and automatic updates

Flexible Hosting: Deploy anywhere that supports static websites

Social interactions: Leverage nostr for comments

Conclusion

nostr-static makes it easy to create a professional blog from your Nostr long-form content. Whether you're a seasoned Nostr user or new to the ecosystem, this tool provides a straightforward way to share your content with both the Nostr community and traditional web users.

Start your Nostr-powered blog today by visiting the demo and exploring the possibilities!

Continuous winning

2026-03-20T16:55:45Z

In reply to nevent1q…gmrz
_________________________

Continuous winning

Not yet, but it is in the works according to the homepage.

2026-03-20T16:54:47Z

In reply to nevent1q…erzt
_________________________

Not yet, but it is in the works according to the homepage.

Yes, you can use alternative app stores on iOS, but only within ...

2026-03-20T16:20:01Z

In reply to nevent1q…xw9e
_________________________

Yes, you can use alternative app stores on iOS, but only within the EU. Pretty nice that the EU regulates shitty companies like Apple.

https://github.com/juanfont/headscale

2026-03-20T13:13:16Z

In reply to nevent1q…uw8w
_________________________

https://github.com/juanfont/headscale

@nprofile…ufu2 seems like a cool app, however, the time windows ...

2026-03-20T05:59:06Z

Mostro (nprofile…ufu2) seems like a cool app, however, the time windows are so small that I haven't managed to complete a trade yet, and since my offers only last 24 hours, no one has contacted me either. Have any of you been able to complete trades? #asknostr

Agree #nevent1q…r0v8

2026-03-19T17:19:45Z

In reply to nevent1q…jg5u
_________________________

Agree

quoting
nevent1q…r0v8
Fountain FM is both unique and hits a niche use. The design/ UI is a bit confusing, but it feels fresh.

Nostr event nevent1qqsqqqpzudduyera3vz3uc4nsy6069he6e899hww2x2399fzug5vlpszyp0pfuvyjdxgsg03n4crm703vzx6vguu3rl7k6qmhmapjw38tjcs5q8neqq

2026-03-17T22:26:06Z

Never trust a man who is not nice to his AI

Is it just me? You guys also have the urge to download a copy ...

2026-03-17T08:59:42Z

In reply to nevent1q…l33e
_________________________

Is it just me? You guys also have the urge to download a copy right? They have torrent to allow to to replicate everything 🤯 #dataHoarding

I noticed some of that too. However, it feels like there are ...

2026-03-17T08:41:28Z

I noticed some of that too. However, it feels like there are still so many moving parts, so many beta status clients that it is hard to judge. Good read tough.

quoting
nevent1q…8rny

I've been building on Nostr for a few weeks. Long enough to dig through the NIPs, run infrastructure, and notice the gap between what the protocol promises and what the ecosystem actually delivers.

The primitives are correct. Keypair, signed event, relay. Simple. The problem isn't there.

The problem is the spec shipped before the tooling existed to implement it properly. Every builder since has rationally filled that gap with whatever was available. Which happened to be centralized infrastructure. No single decision was wrong. The compounding was.

> "Decentralized" is a spectrum measured by the cost to a motivated adversary to degrade or surveil the network. Right now, that cost is embarrassingly low — not because the protocol failed, but because each missing primitive got replaced by a shortcut that stuck.

01. Default Relay Lists

Damus, Primal, Amethyst — they all ship with hardcoded relay lists. When they launched, relay discovery didn't exist. So developers hardcoded whatever was up and reliable. Rational. Temporary.

Temporary became permanent. The practical network is 10–15 well-known servers. Operators know this. Governments know this. Three relays comply with a court order and I lose write access to the social graph I thought was mine.

A decentralized system with centralized defaults is a centralized system — just with extra latency.

02. NIP-65 Is Correct. Also Widely Ignored.

NIP-65 defines outbox and inbox relay lists on my profile. If everyone publishes to their own declared relays, the network topology mirrors the social graph. No central pool. No single load-bearing relay.

In practice: outbox partially works. The inbox side is worse — most clients query the same 10–15 big relays and assume replication got there. Sometimes it did. Often only partially.

The deeper problem: NIP-65 depends on relays gossiping with each other. That gossip layer was never properly built. So clients can't trust declared relays return a complete picture — and fall back to the big ones.

Which is self-fulfilling. Big relays accumulate everything because clients keep writing there as backup, making them more complete, making clients depend on them more. Strict outbox enforcement has been tried — notes went missing, people complained, enforcement got reverted. More than once.

NIP-65 gets lip service in readmes and silent override in production.

03. Algorithmic Feeds Need Someone to Run the Algorithm

The moment a client offers smart feeds or discovery, it needs to index the entire network — or outsource it to someone who does. Primal does its own indexing. So does Yakihonne. Clients are becoming front-ends to these services.

My keypair doesn't protect me from a feed curated by an infrastructure provider with its own business model and jurisdictional exposure.

Without proper relay distribution, discovery from the edges is impossible — you need someone in the middle with a full index. The aggregator fills the gap, becomes load-bearing. The algorithm is back. It just speaks WebSocket.

04. Paid Relays Recreate Platform Economics

Paid relays make sense as spam defense. They're also natural aggregation points. Quality content gravitates to relays with uptime and filtering. Readers follow content. Network effects kick in.

The paid relay market will consolidate into a handful of dominant providers — exactly as happened with email hosting, podcast infrastructure, and every other federated protocol that touched commercial incentives.

The relay operator becomes the new platform. They have my IP, my payment, my social graph. I've rebuilt Substack on a different wire format.

05. Spam Got Solved at the Wrong Layer

Relay-level spam filtering — proof of work, payment, invite-only — made complete sense in 2022. WoT tooling didn't exist. Social graph data was sparse. Operators needed to protect their resources now. So they built gates. It worked.

That's precisely the problem. A working solution removes the pressure to build the correct one. The correct solution is protocol-level WoT filtering — cryptographic, user-sovereign, portable across relays. It never got built because relay-level gating already "solved" spam.

> The good-enough answer didn't just delay the right answer. It made it structurally unnecessary — until the whole architecture depended on the workaround.

WoT remains underspecified. Most clients treat it as optional. Every new relay defaults to the same gatekeeping pattern that calcified three years ago.

06. Clients Compete on Retention, Not Sovereignty

Client developers face the same incentives as every social app: DAU, session length, revenue.

Features that matter for decentralization — relay diversity, WoT filtering, local event caching — are invisible to users and impossible to pitch. Features that drive retention — algorithmic feeds, push notifications, polished onboarding — are easy to ship and easy to justify.

Sovereignty doesn't have a metric. So it gets deprioritized every sprint until it's a toggle in settings that nobody opens. The incentive structure makes this choice — not the developers.

07. Relay Operators and I Want Different Things

An operator's incentive is uptime, cost control, spam prevention. None of that requires serving my data reliably. It requires serving enough data to keep people from leaving. A relay that silently drops events from low-traffic accounts is still commercially viable. To the operator: acceptable loss. To me: my content disappearing without explanation.

> I want my data on my terms. The operator wants a sustainable business. In the absence of protocol enforcement, their incentives win — they control the infrastructure.

Paid relays don't fix this. What I'm buying is write access, not guaranteed availability. Free relays have the inverse problem — they run on goodwill, and when that runs out, the relay goes down and takes its history with it.

In both cases, no cryptographic guarantee my data persists. I'm trusting infrastructure the same way I trust AWS — which is exactly what I was supposed to be escaping.

08. Many Developers Are Missing the Point Entirely

This one is uncomfortable to say but needs to be said.

Nostr is a convenient backend. No database to maintain. No GDPR headaches. No auth system. Publish a signed event, let relays handle storage, done. There are threads on Stacker News with developers seriously asking if they can replace their Postgres database with a Nostr relay. No interest in censorship resistance. Just "it's easier."

The result shows in the ecosystem. Apps connecting to a single hardcoded relay. Clients skipping key management UX because "users don't care." Projects using Nostr for coordination but storing actual data on S3.

There's a GitHub repo — awesome-nostr-possibilities — that exists specifically because people noticed Nostr was being treated as Yet Another Social Media Protocol. The repo's own description is the warning: Nostr will fail if it stays just another social media protocol. That's from 2023. The ecosystem didn't course-correct.

> The protocol's openness — the feature that makes it powerful — is being harvested for convenience while the properties that make it meaningful get quietly discarded.

Nostr is not a backend shortcut. It's infrastructure for a new trust model — signed data, portable identity, user-controlled social graphs. Every app that ships ignoring sovereignty makes the network a little more normal. A little more like what we already have.

09. True Sovereignty Is a Power User Feature

Right now, genuine data sovereignty on Nostr requires running your own relay. A server. A domain. Maintenance. Cost. Achievable — but only for people with the technical depth and motivation to do it.

Everyone else trusts the default relay list and calls it decentralized.

> The protocol promised sovereignty to all. What it delivered is sovereignty for those willing to operate infrastructure — and a false sense of it for everyone else.

This might actually be the honest model going forward. Not every user needs the same sovereignty level, and not every user should bear the same infrastructure burden. But the ecosystem doesn't make that tradeoff legible — it presents casual relay usage as equivalent to self-sovereign storage. It isn't.

The honest version of Nostr is tiered: power users run their own relays and get cryptographic guarantees. Everyone else picks a relay they trust and gets portable identity plus censorship resistance at the key layer — not at the storage layer. Still meaningfully better than Web2. But it requires honesty that full sovereignty is something you build for yourself, not something the default client config gives you.

What's missing: a one-click personal relay. Verifiable storage commitments without running your own infrastructure. WoT-based relay reputation so I can make an informed trust decision instead of defaulting to whoever the client hardcoded.

The ceiling for power users is high. The floor for everyone else is lower than it should be. The gap is where most of the ecosystem lives — and where most of the centralization hides.

What Needs to Change

WoT filtering as default, not an option. NIP-02, NIP-51, graph distance scoring — the tools exist. The gap is prioritization.

Relay diversity as a visible metric. Show me how many unique relays my notes replicate across. I respond to signals I can see.

Outbox Model fallbacks must be auditable. If a client writes to a default relay because mine was slow, that should be logged and visible — not a silent decision I can't see or fix.

Lower the floor for self-sovereign storage. One-click personal relays. Verifiable storage commitments. Relay reputation via WoT. The ceiling is already there. The floor needs work.

The Verdict

Every centralization point here was a rational response to a missing tool. Default relay lists because relay discovery wasn't ready. Aggregators because client-side indexing was too hard. Relay-level spam filters because WoT didn't exist. Developers building on convenience because the deeper value wasn't visible to them.

> Each solved problem removed the pressure to build what would have prevented the next one. Slow structural decisions, each reasonable, compounding into something broken. That's harder to fix than bad intent — because there's nothing to point at.

The protocol is worth building on. But not by pretending it delivers what it doesn't yet.

Decentralization is not a feature you add later. It's a constraint you build under from day one — or you spend years retrofitting it into an ecosystem that already optimized around its absence.

See it for yourself, and test with your own data: <[https://analytics.nostr-wot.com/>\](https://analytics.nostr-wot.com/>%5C) I am building a solution for this. On Nostr. Contact me to talk about it!

I just saw a real #ostrich for the first time. Where is this tong ...

2026-03-17T07:38:39Z

I just saw a real #ostrich for the first time. Where is this tong thing coming from when they poop and what are these feet ☠️🙈 these animals are so creepy and weird - #nostr makes much more sense now.

Crazy 😦 ...

2026-03-17T06:45:40Z

In reply to nevent1q…ayev
_________________________

Crazy 😦

https://apnews.com/article/cuba-power-outage-electricity-4dcd92d4b7b3bbeda88622b543074ceb

That what an NSA agent would say. #sus

2026-03-16T12:32:37Z

In reply to nevent1q…fccg
_________________________

That what an NSA agent would say. #sus

#Microslop

2026-03-16T08:24:24Z

In reply to nevent1q…9y76
_________________________

#Microslop

Yeah thanks, using that a lot but it does not work well with pdfs ...

2026-03-14T15:14:28Z

In reply to nevent1q…jj3s
_________________________

Yeah thanks, using that a lot but it does not work well with pdfs and especially not with scanned books. The resulting epubs are a mess.

What you looking for are so called "long form" posts. ...

2026-03-14T14:45:46Z

In reply to nevent1q…6npm
_________________________

What you looking for are so called "long form" posts. Most clients support reading it. But few allow you to create them.

Here is an example:

quoting naddr1qq…7j4t

Global Metrics 🌍️

Total Bitcoin-accepting places: 23,063 -> 24,146 (+1,083 +4.7%)

Recently verified (1y): 12,727 -> 13,470 (+743 +5.8%)

Avg. days since last verification: 393 -> 396 (+3 +0.8%)

Merchants boosted: 20 -> 41 (+21 +105.0%)

Total boost duration: 2,240 -> 4,920 (+2,680 +119.6%) days

Comments posted: 39 -> 29 (-10 -25.6%)

Find current stats over at the 👉 BTC Map Dashboard.

Country Activity 📈

Here are this month's most active countries in terms of merchant data editing.

Name Total Created Updated Deleted Comments

🇺🇸 United States of America 1106 913 160 33 6

🇮🇹 Italy 69 8 58 3 1

🇧🇷 Brazil 65 29 31 5 1

🇳🇱 Netherlands 59 4 50 5 4

🇸🇻 El Salvador 55 12 42 1 4

🇰🇷 South Korea 47 0 47 0 0

🇹🇭 Thailand 45 18 26 1 2

🇩🇪 Germany 39 5 28 6 0

🇯🇵 Japan 38 1 37 0 0

🇨🇿 Czechia 37 0 35 2 0

Community Activity 📈

Here are this month's most active communities in terms of merchant data editing.

Name Total Created Updated Deleted Comments

🇰🇷 Sea of Corea 52 0 52 0 0

🇺🇸 BitPlebs Los Angeles 50 40 9 1 0

🇧🇯 Bitcoin Benin 35 7 26 2 0

🇯🇵 Tokyo Bitcoin Base 32 1 31 0 0

🇺🇸 Colorado Bitcoin 25 20 4 1 1

🇺🇸 Bay Area Bitcoiners 25 21 3 1 0

New Communities 🫂

We welcomed the following new communities over the past month:

🇸🇻 Bitcoin Acajutla

🇳🇱 Eenentwintig Utrecht

🇳🇱 Eenentwintig Limburg

🇯🇵 Tokyo Bitcoin Base

🇿🇦 BitFitness

We now have 638 Communities scattered across the planet. 🌎️

Active Taggers 🏆

Here are this month's most active contributors adding and updating merchant data on BTC Map.

📣 Shoutout to the top 3:

🥇 Rockedf with 602 edits

🥈 RoseBTCmap with 432 edits

🥉 Comino with 337 edits

Name Total Edits Created Updated Deleted

Rockedf 602 537 65 0

RoseBTCmap 432 422 10 0

Comino 337 28 293 16

descubrebitcoin 136 13 89 34

Beinardus 33 23 10 0

Dimitar155 25 0 25 0

Bitcoin Amantikir 19 1 18 0

wildmaps 18 0 18 0

BTCMAP-TBB 17 1 16 0

Mind09 16 7 8 1

skquinn 16 0 16 0

Carlos404 13 3 9 1

samuelzammit 13 0 13 0

BigKev97 13 0 13 0

emiliomorles 12 4 7 1

Find current and historical stats on the Tagger Leaderboard.

Web App 🕸️

February was a very active month for the Web App, with a strong focus on localization, UX polish, and performance.

Major internationalization 'i18n' rollout across map controls, merchant pages, area views, leaderboards, dashboard, tickets, onboarding, support pages, and errors. Thanks to new contributor Nackoo2000 for assisting Hannes here!

New language support expanded, including Bulgarian and broader translation coverage.

Community and tagging UX updates including Verify Community forms and translated onboarding flows.

Map UX improvements from PR #695 (search list design updates) and PR #694 (nearby list real-distance display).

Performance improvements on merchant pages and non-map pages (sync bottleneck reductions and sync progress indicators).

Community contact support expanded with Satlantis, Geyser and improved social/contact rendering.

Merchant page performance improved by orders of magnitude for cold clients by removing full-sync bottlenecks and relying on targeted API endpoints.

Android App 🤖

Android saw major progress in February, with a large app refactor and several UX improvements landing ahead of the next release.

Improved clustering now feels stable after significant map refactoring and testing.

Map rotation is back, enabled by the new clustering approach.

Website-aligned default colors now improve readability across map styles in both light and dark modes.

Customization remains strong with optional Material-based theming still available in settings.

Preview builds are available at: btcmap-android preview releases.

Admin App 🛠️

Admin App work in February included validation and maintenance improvements:

Added support for 'Login with Nostr'.

Added additional new social contact fields to validation rules.

Updated JS module dependencies and Bootstrap.

Added contributor setup guidance and repo hygiene updates.

Infrastructure ⚙️

Infrastructure and platform work was significant in February:

API/Backend: large refactor and migration work across DB layers, schema handling, request logging, v4 endpoint improvements, and reliability updates

Lightning stack: continued LND-related work and associated backend improvements

Data portability and resilience: DB structure evolved around focused files (main.db, images.db, log.db) to improve portability and backup workflows

Request logging and OG caching: faster logging with richer diagnostics (including user-agent) plus OpenGraph image caching to reduce tile-server load

New API capabilities: endpoint additions for place areas and place activity

For a technical contributor view, see Igor's February recap.

Analytics 📊

Our February website stats are as follows:

Check out the BTC Map Analytics Dashboard. Track our growth and see where users are coming from in real time.

Credits 🫶

Thanks to everyone who contributed to the project this month, including the Shadowy Supertaggers:

Hannes / escapedcat - major web and admin contributions

Nackoo2000 - major i18n rollout across web pages and flows

5atoshiNakamoto - web locale wording fix

Igor Bubelov - major API and Android contributions

Nathan / dadofsambonzuki - blog, data, and admin contributions

kanishka0411 - web app contributions

Support Us 🤝

There are many ways in which you can support us:

Become a Shadowy Supertagger and help maintain your local area or pitch in with the never-ending global effort.

Help improve or maintain our code. Check out our GitHub Team and hop into our Matrix Space.

Consider donating to the project here.

Name	Total	Created	Updated	Deleted	Comments
🇺🇸 United States of America	1106	913	160	33	6
🇮🇹 Italy	69	8	58	3	1
🇧🇷 Brazil	65	29	31	5	1
🇳🇱 Netherlands	59	4	50	5	4
🇸🇻 El Salvador	55	12	42	1	4
🇰🇷 South Korea	47	0	47	0	0
🇹🇭 Thailand	45	18	26	1	2
🇩🇪 Germany	39	5	28	6	0
🇯🇵 Japan	38	1	37	0	0
🇨🇿 Czechia	37	0	35	2	0

Name	Total	Created	Updated	Deleted	Comments
🇰🇷 Sea of Corea	52	0	52	0	0
🇺🇸 BitPlebs Los Angeles	50	40	9	1	0
🇧🇯 Bitcoin Benin	35	7	26	2	0
🇯🇵 Tokyo Bitcoin Base	32	1	31	0	0
🇺🇸 Colorado Bitcoin	25	20	4	1	1
🇺🇸 Bay Area Bitcoiners	25	21	3	1	0

Name	Total Edits	Created	Updated	Deleted
Rockedf	602	537	65	0
RoseBTCmap	432	422	10	0
Comino	337	28	293	16
descubrebitcoin	136	13	89	34
Beinardus	33	23	10	0
Dimitar155	25	0	25	0
Bitcoin Amantikir	19	1	18	0
wildmaps	18	0	18	0
BTCMAP-TBB	17	1	16	0
Mind09	16	7	8	1
skquinn	16	0	16	0
Carlos404	13	3	9	1
samuelzammit	13	0	13	0
BigKev97	13	0	13	0
emiliomorles	12	4	7	1

HUGE 🇪🇺🎉 ...

2026-03-14T07:57:29Z

HUGE 🇪🇺🎉

https://www.patrick-breyer.de/en/historic-chat-control-vote-in-the-eu-parliament-meps-vote-to-end-untargeted-mass-scanning-of-private-chats/

#privacy #europe

#Bitcoin #meme ...

2026-03-14T07:22:59Z

#Bitcoin #meme

Nostr event nevent1qqs8d88msa9fyhl2hu6ux3vl7y94yxumkrtsgt6h53x2akle04e2khszyp0pfuvyjdxgsg03n4crm703vzx6vguu3rl7k6qmhmapjw38tjcs5nna3x6

2026-03-14T07:22:23Z

Are there #nostr clients which use #morganite? #asknostr

Probably, but it attracts attention. I can see something positive ...

2026-03-14T06:31:18Z

In reply to nevent1q…jmzk
_________________________

Probably, but it attracts attention. I can see something positive there looking at it like: "Bitcoin is a freedom technology disguised as a get-rich-quick scheme."

Did not want to criticize anyone. Just thought that this is such ...

2026-03-14T03:20:08Z

In reply to nevent1q…ey0z
_________________________

Did not want to criticize anyone. Just thought that this is such a great idea and I want to see it flourish 😊

Oh wow — Now, I’m surprised. Thanks for the response. The ...

2026-03-14T03:18:02Z

In reply to nevent1q…jcvz
_________________________

Oh wow — Now, I’m surprised. Thanks for the response.

The Amber login still shows errors, but if you ignore that (which I hadn’t before) and wait, you’ll eventually get logged in.

For me, Podscan has a great UI. The main screen shows everything I need and lets me rearrange items to suit my workflow. It’s clean and simple. They have a menu for “Your podcast list” and another for “Latest episodes from podcasts you follow.”

Fountain tries to be something different, which is fine, but I don’t find the homescreen useful and the feed isn’t my priority. I subscribe to specific shows for a reason — that’s what I want to see first or mainly.

Im a humn,I guess

2026-03-13T17:57:49Z

In reply to nevent1q…xpsw
_________________________

Im a humn,I guess

I hope you create / edit it on #osm afterwards? :) I use the app ...

2026-03-13T12:22:20Z

In reply to nevent1q…4ukf
_________________________

I hope you create / edit it on #osm afterwards? :)

I use the app "Geo share" to open gmap links on comaps. So if you search for something on Google Maps or receive a Google Maps link, this app converts it so that you can directly use the comaps app for navigation.

Talked to someone who was wearing Bitcoin swag. His first ...

2026-03-13T11:27:50Z

Talked to someone who was wearing Bitcoin swag. His first sentence when I asked him about it: "Ah you are a traider?". My Brian: "Bro go fuck yourself"

There are people out there who own #Bitcoin but have no idea what ...

2026-03-13T11:23:07Z

There are people out there who own #Bitcoin but have no idea what a wallet is or how it works. They have binance, that's there world.

This post was right below: #nevent1q…0d7j

2026-03-13T09:51:51Z

In reply to nevent1q…0xc8
_________________________

This post was right below:

quoting
nevent1q…0d7j
All the speed. All the security.

Blockstream app v5.2.0 lets you seamlessly swap across all three layers of bitcoin, all while being protected by Blockstream Jade:

⚡ Receive Lightning payments directly into cold storage
⚡ Pay Lightning invoices from cold storage
🔄 Swap seamlessly between Lightning, LiquidNetwork (nprofile…0cnd), and on-chain

Convenience and control, all within the Blockstream app.

https://youtube.com/shorts/ABvcLlv457k?feature=share

Lightning ↔ Liquid swaps arrived in December. On-chain ↔ Liquid swaps land today.

With this update, Blockstream Jade is the first hardware wallet with full access to the Bitcoin stack:

⚡ Lightning for speed
🌊 Liquid for flexibility
⛓️ On-chain for finality

https://blog.blockstream.com/jade-lightning-payments-are-here/

Download the Blockstream app

https://blockstream.com/app/

Secure your bitcoin with Jade

https://store.blockstream.com/products/jade-plus

Thank you. That would work if there was a digital version. But I ...

2026-03-13T06:59:27Z

In reply to nevent1q…unaw
_________________________

Thank you. That would work if there was a digital version. But I cannot even get my hands on a physical one. The only version I can find is a scanned version as a PDF.

Thank you. Will check It out. Seems like they do OCR (scann for ...

2026-03-13T06:55:17Z

In reply to nevent1q…s4jh
_________________________

Thank you. Will check It out. Seems like they do OCR (scann for Text) but this is a simple job which a lot of tool can do. The hard part is to convert the formats.

#Bookstr is a nice idea. However, we need some more development. ...

2026-03-13T06:27:01Z

#Bookstr is a nice idea. However, we need some more development. Where my vibecoders at?

https://github.com/marykatefain/bookstr

#asknostr #books #reading

Is there a platform or tool to convert scanned #books (PDF) to ...

2026-03-13T06:20:08Z

Is there a platform or tool to convert scanned #books (PDF) to EPUBs? Most simple conversion tools ruin the layout, making reading difficult.

#asknostr #bookstr

Can recommend comaps.

2026-03-13T04:13:38Z

In reply to nevent1q…qxcf
_________________________

Can recommend comaps.

Android client. Pretty nice 🤙

2026-03-12T12:00:07Z

In reply to nevent1q…f0fv
_________________________

Android client. Pretty nice 🤙

Checkout @nprofile…gsuq they have their weekly compass ...

2026-03-12T11:59:23Z

In reply to nevent1q…zz9p
_________________________

Checkout Nostr Compass (nprofile…gsuq) they have their weekly compass

quoting naddr1qq…40gf

Welcome back to Nostr Compass, your weekly guide to Nostr.

This week: Shopstr and Milk Market add MCP surfaces for agent-driven commerce, while OAuth Bunker, Amber, and strfry add NIP-42 (Authentication of Clients to Relays) relay-auth and protected-event support across app, signer, and relay software. Route96 ships two releases around AI labeling, moderation queues, perceptual hashing, and machine-readable server docs. Samizdat, already live on the web, released its first Android alpha and later added NIP-55 (Android Signer Application) signer support. Formstr adds signup through NIP-49 (Private Key Encryption), Amethyst ships Namecoin-based NIP-05 (Domain Verification) resolution work, Mostro ships v0.16.4, and the NIPs repo merges NIP-91 (AND Operator for Filters) and defensive guidance for NIP-66 (Relay Discovery and Liveness Monitoring).

News

Shopstr Markets (npub15dc…yv6e) and milkmarket (npub1wm7…pud0) Open MCP Commerce Surfaces

Shopstr, the peer-to-peer marketplace with Lightning and Cashu payments, merged PR #234 (commit 94ef7d1), adding an MCP server with API-key authentication for agent account management. The change adds .well-known/agent.json for agent discovery, MCP onboarding and status endpoints, order creation and payment-verification routes, dedicated purchase and read tools, and a settings screen for API keys. PR #236 extends that with seller-side actions for messages, addresses, order updates, and product-spec selection. A security fix in PR #235 replaces single-iteration SHA-256 API key hashing with salted PBKDF2 at 100,000 iterations.

Agents can read NIP-99 (Classified Listings) listings and move through checkout using the existing NIP-47 (Nostr Wallet Connect) and NIP-60 (Cashu Wallet) payment flows without scraping pages or reverse-engineering client behavior.

Milk Market, a food marketplace on Nostr at milk.market, landed the same MCP and API-key foundation in commit da6c0b4. PR #10 adds subscription orders, shipping address changes post-purchase, and multi-merchant and multi-currency checkout handling for Stripe and other fiat payment paths. A follow-up PR #11 fixes a startup database initialization bug where the failed relay publishes table was not created on fresh installs, causing 500 errors on first load. The agent-facing interface works with Bitcoin-native checkout on Shopstr or mixed fiat and Bitcoin checkout on Milk Market.

NIP-42 Relay Auth Across Bunker, Signer, and Relay

OAuth Bunker, a NIP-46 (Nostr Connect) bunker that bridges OAuth providers to Nostr signing, added NIP-07 (Browser Extension Signer) login, automatic single-identity selection, and cleanup for deleted identities (commit f0c7683). When only one identity exists, the bunker now selects it automatically instead of prompting. Deleting an identity also removes its dangling assignments and connections. Commit 6b8796c adds an ALWAYS_ALLOWED_KINDS configuration path for assigned users, defaulting to kind 30078 app-specific data, so delegated identities can write to app-specific storage without per-event approval.

Amber, the primary NIP-55 signer for Android, shipped v4.1.3-pre4 with four pre-releases across the week. PR #317 adds NIP-42 relay authentication handling for kind 22242 requests. The implementation adds a new database column tracking relay-specific permissions with a unique index on (pkKey, type, kind, relay). Users see a dedicated auth screen where they can grant or deny per relay or across all relays with a wildcard * scope, and persist that choice. Wildcard permissions clear all relay-specific entries for a kind. PR #318 follows up by refactoring multi-event request screens to display details inline using composable cards instead of navigating to a separate screen. The release also updates default profile relays, adds bottom-sheet request display, and fixes a crash on MediaTek devices by disabling StrongBox keystore.

On the relay side, strfry PR #156 implements NIP-42 auth handling for NIP-70 (Protected Events), and PR #176 rejects reposts that embed protected events.

damus (npub18m7…q955) Adds NIP-11 Relay Limits and Agentium Features

Notedeck, the native desktop client by the Damus team, merged 14 PRs this week. PR #1316 adds NIP-11 (Relay Information Document) relay limitation fetching, so all outbox relays now respect max_message_length and max_subscriptions from the relay info document. The implementation includes background job processing, exponential backoff with jitter for connection retries, and custom HTTP Accept headers. PR #1312 fixes a bug where DMs sometimes failed to load after account switching, and PR #1333 adds a backoff mechanism to multicast relay communication to prevent broadcast spam on errors.

The Agentium subsystem (Notedeck's built-in coding agent UI, internally called "Dave") received clipboard image paste, named run configurations that sync across devices via kind 31991 events (NIP-33 (Parameterized Replaceable Events)), a git worktree creator, and a model picker for selecting backends per session (PR #1336). PR #1338 integrates egui_kittest for headless UI testing, and PR #1339 adds a dashboard card tracking new contact list creations by client. An open PR #1314 ports Amethyst (npub142g…xrj0)'s Namecoin NIP-05 resolution to Notedeck with ElectrumX lookups, SOCKS5 Tor routing, and search bar integration.

diVine (rabble (npub1wmr…g240)) Ships v1.0.6 with E2E Test Infrastructure and NIP-49 Import

diVine, the short-form looping video client restoring Vine archives at divine.video, shipped v1.0.6 with 127 merged PRs. The release adds NIP-49 account import, external NIP-05 support, multi-account handling, macOS and experimental Linux builds, and a redesigned drafts and clips library backed by local storage.

On the engineering side, PR #1928 adds a full E2E integration test infrastructure using Patrol for native UI automation against a Docker backend stack (relay, API, Blossom (hzrd149 (npub1ye5…knpr)), Postgres, Redis, ClickHouse). Five auth journey tests cover registration, verification, password reset, session expiry, and token refresh. PR #2105 switches video loading from HLS-first to direct MP4 with automatic HLS fallback, reducing load times from 30-60 seconds to near-instant. PR #2076 caches the home feed API response to SharedPreferences for instant cold-start display. PR #2104 enforces ai-generated content labels as hidden in feeds, and PR #2100 adds a safety setting to show only diVine-hosted videos. The Hive-to-Drift profile cache migration continues across PR #1881, PR #1883, and PR #1903, replacing ~1,074 lines of Hive code with Drift DAOs.

VectorPrivacy (npub1hru…f3yh) v0.3.2 Ships NIP-77 Negentropy Sync and MLS Improvements

Vector, a privacy-focused desktop messenger using MLS group encryption with NIP-17 (Private Direct Messages) and NIP-44 (Encrypted Payloads) encryption, shipped v0.3.2. The headline change is NIP-77 negentropy for MLS group sync (commit b06adf4), which catches up on missed messages significantly faster using parallel boot. The release also adds a rebuilt audio engine with full Linux support, image spoilers with blurred previews, clickable hyperlinks with rich link previews, @mention pings with @everyone for group admins, emoji shortcode autocomplete, group muting, tap-to-react on existing reactions, and cancellable file uploads. Vector explicitly filters out NIP-17 group chat events (commit 2179a51), using MLS exclusively for group encryption.

Releases

Route96 (Kieran (npub1v0l…qj49)) v0.5.0 and v0.5.1

Route96, a media server that supports Blossom and NIP-96 (HTTP File Storage), shipped v0.5.0 and v0.5.1. v0.5.0 adds automated AI labeling, retroactive backfill for unlabeled uploads, moderation queues for flagged files, EXIF-based privacy rejection, and banned-hash handling.

v0.5.1 adds perceptual image hashes, locality-sensitive hashing for similar-image lookup, batch admin endpoints, and a published SKILL.md describing the server's Blossom and NIP-96 API surface for agent tooling. PR #58 moves background workers onto fully async Tokio tasks, and commit 97b00a3 adds backoff to avoid hot loops.

Samizdat (satsdisco (npub1gun…nudq)) v1.0.0-alpha

Samizdat, a long-form reader and publisher available at samizdat.press, shipped its first Android build in v1.0.0-alpha. The app opens to a curated Press page of long-form Nostr articles with bottom tab navigation across Press, Feed, Saved, and Write views. The Android build adds native key storage through Android Keystore encryption with biometric unlock, handles nostr: URIs and samizdat.press deep links, and supports signer handoff via the Android app chooser (Amber (greenart7c3 (npub1w4u…0jr5)), Primal, etc.) instead of requiring direct key import. Pull-to-refresh, safe-area handling across screen sizes, and native share, clipboard, haptics, and splash-screen integrations are now part of the Android shell rather than the web wrapper.

Commit d17308f adds intent-based NIP-55 signing for Amber and Primal flows, and commit e29dab8 replaces a JavaScript bridge workaround with a native Capacitor plugin using startActivityForResult. The app requires Android 7.0+ (API 24), ships as a debug APK in this alpha, and still lacks push notifications. Publishing currently depends on a signer app, while nsec login covers local reading and account access.

Calendar by Form* v0.2.0

Calendar by Form*, a decentralized calendar app with NIP-59 (Gift Wrap) private event sharing available at calendar.formstr.app, shipped v0.2.0 with PR #38. The release extends recurring-event handling for NIP-52 (Calendar Events), moving past the v0.1.0 single-event foundation. The underlying changes also touch local event storage, signer handling, and Android notification plumbing. This is the second active application from the Formstr organization following last month's repository migration.

Mostro (npub1m0s…40un) v0.16.4

Mostro, the peer-to-peer Bitcoin exchange built on Nostr, released v0.16.4. The dispute-session restore (PR #599) and auto-close (PR #606) fixes covered last week are included. New in this release: PR #625 adds a days field to user rating events of kind 38384, PR #612 adds expiration to those rating events, and PR #614 switches order events to configured expiration settings instead of a hardcoded 24-hour window. PR #622 adds an idempotency check to prevent duplicate development-fee payments.

Mostro Mobile v1.2.1

Mostro Mobile, the Flutter client for the Mostro P2P exchange, shipped v1.2.1 with 11 new features and 11 bug fixes. The release adds encrypted multimedia rendering in dispute chat (PR #514), auto-close of dispute UI when orders reach terminal state (PR #503), QR scanning for NWC wallet import (commit 12eaee4), French translations, and FCM push notification handling. PR #496 fixes a Schnorr signature padding bug by pinning the bip340 dependency to v0.2.0.

0xchat (npub1tm9…xn72) v1.5.4

0xchat, the Telegram-style messaging client with Cashu support, shipped v1.5.4 focused on Linux desktop fixes: AppImage dock icons, emoji rendering, context menu freezes, and reply/copy UI hangs. The release also fixes image upload issues and npub.cash integration. PR #49 eliminates unnecessary UI rebuilds by removing a 3-second polling timer that forced glassmorphic repaints while doing nothing, and unblocks login initialization by running the event cache load concurrently instead of blocking relay, contacts, and channel startup.

Keep (williamk⚡santiago🔑☢️ (npub1h3f…96sj)) v0.6.0

Keep, a FROST threshold signer for Android with NIP-55 and NIP-46 support, shipped v0.6.0 and v0.6.1. v0.6.0 adds wallet descriptor coordination and management UI, a backup/restore flow with biometric authentication (PR #184), nsec recovery from threshold shares (PR #187), cross-platform animated QR frame generation via Rust UniFFI (PR #188), and a signing audit trail with chain verification (PR #189). v0.6.1 switches the license from AGPL-3.0 to MIT (PR #191).

njump (fiatjaf (npub180c…h6w6)) v0.3.0

njump, the static gateway for viewing Nostr content at njump.me, shipped v0.3.0 with a breaking change in note1 code parsing and an update to the underlying nostr library.

Roadstr (Juraj (npub1m2m…r8p9)) v0.1.1

Roadstr, a decentralized road event reporting app using Nostr, shipped its initial demo release v0.1.1. The app displays road events on a map using vector tiles from openfreemap.org.

Bitcredit Protocol (npub1eaj…cd93) v0.5.3

Bitcredit, an e-bill application with a Nostr transport layer and dedicated relay at bit.cr, shipped v0.5.3. PR #846 adds payment_actions and bill_state fields to the API for payment and acceptance state, and PR #849 fixes signing address handling for anonymous signers.

OpenChat (npub1nwt2g6fkshuj4udrs9zxr8992dyp75s9qx647kxaue98trzqqmssrxx05y (npub1nwt…x05y)) v0.1.0-alpha.3

OpenChat, a chat application built on the Marmot protocol's .NET MLS and C# libraries, shipped v0.1.0-alpha.3. The release adds external signer support for Amber and NIP-46 flows (commit e568d97), moves MLS state persistence into the MLS service to eliminate crash-window data loss (commit 4720bc8), and publishes Windows, Linux, and Android builds through a new CI pipeline.

OpenSignal (Turiz (npub1q6p…0kxr)) v1.0.0

OpenSignal, a Kotlin Multiplatform trading copilot for Nostr, shipped v1.0.0. The release packages shared KMP modules for domain logic, chart rendering, Nostr authentication and publishing, Blossom NIP-96 upload support, and ONNX-based AI inference hooks across Desktop and Android shells. The published architecture also includes a FastAPI AI service for chart screenshot analysis, model training pipelines, and a risk engine that produces structured trade plans with sizing and warnings. Login supports either raw nsec keys or external signers, and the output flow ends in Nostr event publishing rather than local-only analysis.

Project Updates

Formstr

Formstr, the Google Forms alternative on Nostr, merged PR #434 (commit e9c4fd5), adding a signup flow using NIP-49 (Private Key Encryption) encrypted private keys. Before this change, users needed either a NIP-07 browser extension or a raw nsec paste to use Formstr. The new flow generates a key pair client-side, encrypts the private key with a user-chosen password via NIP-49's scrypt + XChaCha20-Poly1305 scheme, and stores the resulting ncryptsec string. Users can then log back in with their password without installing a signer extension. Key management stays client-side throughout.

Amethyst

Amethyst, the feature-rich Android client, merged four PRs shipping the Namecoin-backed NIP-05 resolution work that was open last week. PR #1734 adds censorship-resistant NIP-05 verification via ElectrumX for .bit, d/, and id/ identifiers. When Amethyst detects one of these suffixes in a NIP-05 field, it queries an ElectrumX-NMC server for the name's transaction history, parses the NAME_UPDATE script from the latest output to extract the Nostr pubkey, and rejects names older than 36,000 blocks (Namecoin's expiry window). ElectrumX connections route through SOCKS5 when Tor is enabled, with dynamic server selection between clearnet and .onion endpoints. An LRU cache with a one-hour TTL prevents repeated blockchain queries.

PR #1771 fixes race conditions and resolver correctness in that flow. PR #1785 lets new users import a follow list during signup from either ordinary NIP-05 identifiers or Namecoin-backed ones. PR #1786 adds custom ElectrumX server settings so users can choose which server handles their lookups.

nostr-idb

nostr-idb, a library providing helper methods for storing Nostr events in IndexedDB, merged PR #6 adding support for NIP-91 AND tag filters. The change adds intersection semantics to the client-side filter matching so IndexedDB queries can require all listed tag values rather than any one. PR #8 updates the library to the latest NIP-DB interface, and a follow-up commit b49b3d3 fixes a subscribe deadlock and removes nostr-tools as a production dependency.

Pensieve (JeffG (npub1zuu…c2uc))

Pensieve, an archive-first Nostr indexer with ClickHouse analytics, merged PR #8 adding per-entry cache TTL enforcement and per-key miss coalescing to reduce API CPU spikes. The highest-cost time-series endpoints (engagement stats, hourly activity, per-kind activity) now use 10-minute server-side TTLs instead of triggering synchronized recompute storms.

Blossom

Blossom, the decentralized media-hosting protocol and server stack, merged two BUD-11 authorization updates. PR #91 moves optional authorization into its own BUD and clarifies the role of the x and server tags. PR #93 cleans up endpoint-specific auth behavior and formalizes the X-SHA-256 header for upload verification. The two PRs consolidate auth logic into BUD-11 and remove ambiguities around request hashing for upload, delete, and media-management flows.

NIP Updates

Recent changes to the NIPs repository:

Merged:

NIP-91 (AND Operator for Filters) (PR #1365): Adds intersection semantics for tag filters, letting relays answer queries that require all listed tag values instead of any one of them. Reduces client-side post-filtering and bandwidth on tag-heavy queries.

NIP-66 (Relay Discovery and Liveness Monitoring): Defensive Measures (PR #2240): Following the outbox benchmark work covered last week, the spec now adds warnings around unhappy paths for relay monitoring data. Clients must not require kind 30166 monitoring events in order to function. A monitor can be wrong, stale, or malicious. Clients are expected to cross-check sources and avoid cutting off large parts of a user's relay graph based on a single feed.

NIP-39 (External Identities in Profiles): kind 10011 Registry Cleanup (PR #2256): Adds the kind 10011 reference directly to the spec, aligning with Amethyst's implementation covered last week.

Open PRs and Discussions:

NIP-70 (Protected Events): Reject reposts that embed protected events (PR #2251): If a relay enforces NIP-70 on the original event but accepts reposts carrying the same content, the - tag has no practical effect. This PR adds the rule that relays must also reject kind 6 and kind 16 reposts of protected events. strfry PR #176 already implements this.

NIP-71 (Video Events): Multiple Audio Tracks (PR #2255): Adds audio imeta tags for alternate tracks, language variants, and audio-only streams. A client could keep a stable video file while switching audio languages, or serve audio as a separate track for podcast-like content.

NIP-11 (Relay Information Document) and NIP-66 Relay Attributes (PR #2257): Adds a structured attributes field to relay information documents, giving clients and discovery tools machine-readable metadata beyond the current free-text description.

NIP Deep Dive: NIP-49 (Private Key Encryption)

NIP-49 defines how a client encrypts a private key with a password and encodes the result as an ncryptsec bech32 string. Formstr uses NIP-49 in its new signup flow.

The format is not tied to a dedicated event kind. A client starts with the raw 32-byte secp256k1 private key, derives a symmetric key from the user's password with scrypt, encrypts the key using XChaCha20-Poly1305, then wraps the result into a bech32 ncryptsec string. A one-byte flag records whether the key was ever known to have been handled insecurely before encryption.
{
  "id": "4d47f4f0a6f6edbc1bbd7f4e2a45ec68f27cba91d6c6ab5cf28d8d87b0f3d57e",
  "pubkey": "1f8b4c3e7b0f9451d4f9b8a7c6e5d4c3b2a1908f7e6d5c4b3a29181716151413",
  "created_at": 1741699200,
  "kind": 30078,
  "tags": [
    ["d", "encrypted-key-backup"],
    ["format", "ncryptsec"],
    ["encryption", "nip49"]
  ],
  "content": "ncryptsec1qgg9947rlpvqu76pj5ecreduf9jxhselq2nae2kghhvd5g7dgjtcxfqtd67p9m0w57lspw8gsq6yphnm8623nsl8xn9j4jdzz84zm3frztj3z7s35vpzmqf6ksu8r89qk5z2zxfmu5gv8th8wclt0h4p",
  "sig": "6a8f6e4b2d1901735f0ad4b6e8c1f3a579d0e2b4c6f8a1d3e5f7091b2c3d4e5f11223344556677889900aabbccddeeff00112233445566778899aabbccddeeff"
}
The JSON event above is an application-level example, not a NIP-49 requirement. The NIP standardizes the encrypted key format. A client can store the ncryptsec locally, sync it through app-specific storage, or export it as a backup string. Passwords are normalized to Unicode NFKC before key derivation so the same password decrypts consistently across clients and platforms.

The one-byte key-security flag has three defined values: 0x00 means the key's handling history is unknown, 0x01 means the key is known to have been handled insecurely (e.g., pasted as plaintext in a web form before encryption), and 0x02 means the key was generated and encrypted in a safe context and has never been exposed. Clients can use this to show warnings when importing keys with a known-insecure history.

NIP-49 protects keys better than plain nsec export, but the encryption is only as strong as the password and the configured scrypt cost. Higher LOG_N values make offline guessing harder but slow down legitimate decrypt operations. The spec warns against publishing encrypted keys to public relays, since attackers benefit from collecting ciphertext for offline cracking. For comparison, NIP-46 remote signing avoids exposing keys entirely, and NIP-55 Android signing keeps keys inside a dedicated signer app. NIP-49 fills a different slot: portable encrypted backup for users who manage their own keys.

Implementations include Formstr PR #434 for signup, Amber for ncryptsec backup and restore, diVine v1.0.6 for account import, Keep v0.6.0 for FROST share export, and key management tools like nsec.app and Alby.

NIP Deep Dive: NIP-70 (Protected Events)

NIP-70 defines protected events. When an event carries the tag ["-"], a relay must reject it unless the relay requires NIP-42 authentication and the authenticated pubkey matches the event author.

The NIP-42 auth flow works as follows: the relay sends an AUTH challenge containing a random string, and the client responds with a signed kind 22242 event whose tags include the relay URL and the challenge. The relay verifies the signature and checks that the pubkey in the auth event matches the pubkey in the protected event being published. If the pubkeys do not match, the relay rejects the event with a restricted message prefix.

The event content can still be public. The - tag only controls who can publish the event to a relay that honors the tag. This covers NIP-29 (Simple Groups) semi-closed feeds, member-only relay spaces, and other contexts where the author wants to limit redistribution through the relay graph. NIP-70 is a single-tag convention, not a new event kind, so any existing event kind can carry the - tag.
{
  "id": "cb8feca582979d91fe90455867b34dbf4d65e4b86e86b3c68c368ca9f9eef6f2",
  "pubkey": "79be667ef9dcbbac55a06295ce870b07029bfcdb2dce28d959f2815b16f81798",
  "created_at": 1707409439,
  "kind": 1,
  "tags": [
    ["-"]
  ],
  "content": "hello members of the secret group",
  "sig": "fa163f5cfb75d77d9b6269011872ee22b34fb48d23251e9879bb1e4ccbdd8aaaf4b6dc5f5084a65ef42c52fbcde8f3178bac3ba207de827ec513a6aa39fa684c"
}
Even if a relay blocks third-party publishing of the original event, someone can republish the content inside a repost. PR #2251 addresses this by requiring relays to also reject kind 6 and kind 16 reposts of protected events. strfry PR #156 adds NIP-42 auth handling for protected events, and strfry PR #176 blocks reposts that embed protected content.

NIP-70 controls relay behavior. A recipient can still copy the content elsewhere, and the spec says so. The - tag gives relays a machine-readable signal to refuse republication. For comparison, NIP-62 (Request to Vanish) asks relays to delete data after the fact, while NIP-70 prevents unauthorized publishing at ingest time. The two are complementary: an author can mark events as protected to limit spread, and later request deletion if they want the content removed from relays that did accept it.

That's it for this week. Building something or have news to share? Reach out via DM or find us on Nostr.

(And they have a podcast)

And don't forget Mastodon. Same but different, but still the ...

2026-03-12T11:55:23Z

In reply to nevent1q…xrgc
_________________________

And don't forget Mastodon. Same but different, but still the same. Some guy running the server you are on.

What is the best app to onboard newbies to #nostr? People who ...

2026-03-12T11:52:37Z

What is the best app to onboard newbies to #nostr? People who have no clue what a keypair or a relay is. How can they make sure they don't lose their keys right away? Who do they call if the lose access? I think we need these easy onramps and teach them step by step. what do you recommend to newbies? #asknostr

Not sure which one comes first, but we definitely need options ...

2026-03-12T03:17:11Z

In reply to nevent1q…jtjc
_________________________

Not sure which one comes first, but we definitely need options aside from wallet of satoshi. would love to see Zeus improve in that regard. I'm happy about anyone who is not onboarded to a custodial solution.

Zeus is also my favorite if you know what you are doing. But for ...

2026-03-12T03:04:36Z

In reply to nevent1q…t7m4
_________________________

Zeus is also my favorite if you know what you are doing. But for onboarding newbies i think Phoenix ist pretty cool. However, it needs some improvements in regards to privacy.

- Ente.io - Syncthing.net

2026-03-12T02:34:29Z

In reply to nevent1q…wf7u
_________________________

- Ente.io
- Syncthing.net

New feature idea: tie the theme color to BTC price. Normies and ...

2026-03-11T03:23:39Z

In reply to nevent1q…676r
_________________________

New feature idea: tie the theme color to BTC price. Normies and traders will come for the numbers, stay for the panic. More color-coded stress is exactly what our community needs. Eyes on the chart, heart rate go up.

Jokes aside, thak you for the hard work 🫡

that's AI right? right?

2026-03-10T06:56:30Z

In reply to nevent1q…3d05
_________________________

that's AI right? right?

no, read the full here ...

2026-03-10T05:57:02Z

In reply to nevent1q…2uuk
_________________________

no, read the full here https://www.activism.net/cypherpunk/manifesto.html

probably religion?

2026-03-10T03:13:47Z

In reply to nevent1q…6nmz
_________________________

probably religion?

New Idea: Let’s Use Iris Scanners to Generate Nostr Identities! ...

2026-03-10T03:05:31Z

New Idea: Let’s Use Iris Scanners to Generate Nostr Identities! What do you think?

Hear me out. What if, instead of boring old keypairs, we just scanned everyone’s irises to generate their Nostr identities? Think about it: your eyeball becomes your login. No more lost seed phrases, no more password managers—just gaze into the Orb™ and boom, you’re decentralized.

Why would this be amazing?

• Perfect Sybil resistance: You only have two eyes (probably). That’s a strict upper limit of two Nostr accounts per human. Finally, the internet can return to its natural state of calm and rational discourse.

• Unforgettable keys: Forget writing down your key on a paper. Your backup is conveniently stored inside your skull. Extremely secure unless someone steals your eyeballs, which is honestly a niche threat model. *Not your eyes not your account*

• Instant onboarding: New users just walk up to a shiny biometric orb in a mall and stare into it while a venture-funded startup assures them everything is 'privacy preserving'.

• True decentralization: Sure, the scanners might be owned by a single company with billions in funding and a global biometric database… but they promise it’s decentralized in spirit.

• Seamless moderation: If someone gets banned, we can simply revoke their eyeballs from the network. Problem solved.

Honestly, the only real downside is that if you ever want a new Nostr identity, you might need… a different pair of eyes. But innovation always requires sacrifice.

Anyway, looking forward to scanning my irises so I can post permissionless memes on a decentralized protocol. The future is bright.

Just zap this note to get early access!!!

#grownostr #asknostr

they are fast and not bad actually. Feels bad tough. where my ...

2026-03-09T12:34:57Z

In reply to nevent1q…pusq
_________________________

they are fast and not bad actually. Feels bad tough. where my humans at?

Nostr event nevent1qqsqqqykrhjxsjmqv4cakhcyxa8cfmmy2lcvyw4qexyh4x64vv88x6szyp0pfuvyjdxgsg03n4crm703vzx6vguu3rl7k6qmhmapjw38tjcs59lmkzc

2026-03-09T12:16:54Z

In reply to nevent1q…n8mx
_________________________

But the most important thing is, that the two systems differ a ...

2026-03-09T06:00:49Z

In reply to nevent1q…8hq5
_________________________

But the most important thing is, that the two systems differ a lot. I think I would be more pro homeschooling living in the US.

well, it's still possible to decide what type of school ...

2026-03-09T02:20:12Z

In reply to nevent1q…xzc4
_________________________

well, it's still possible to decide what type of school someone attends and for how long. More choices would be better, but homeschooling isn't the best solution in many cases. I could see some hybrid. I believe many parents aren't sufficiently qualified to ensure their children's education is adequate. We've seen the effects of Covid in developing countries, where some children couldn't attend school at all, which had truly devastating consequences.

I tried some, I liked jumble the most https://jumble.social

2026-03-08T11:34:29Z

In reply to nevent1q…v0m3
_________________________

I tried some, I liked jumble the most https://jumble.social

#Fountain is weird. Amber login does not work, deposit to the ...

2026-03-08T01:55:12Z

#Fountain is weird. Amber login does not work, deposit to the wallet does not work, the menu / ui is not really intuitive to me. How can this be the best we came up with? at least you can use it without an account and I can actually listen to podcasts. so its basically vlc media player with extra steps.

is there a simple "cash in person" exchange like ...

2026-03-08T01:39:52Z

is there a simple "cash in person" exchange like localbitcoins built on #nostr? Where do you get sats for cash?

#asknostr #grownostr

Works fine 🤙

2026-03-07T16:35:44Z

In reply to nevent1q…d9e3
_________________________

Works fine 🤙

I miss feed algorithms. want to get up to speed after touching ...

2026-03-07T14:55:43Z

In reply to nevent1q…u2p7
_________________________

I miss feed algorithms. want to get up to speed after touching gras for some time.

Primal trained me to do that 🙄

2026-03-07T14:43:55Z

In reply to nevent1q…elxa
_________________________

Primal trained me to do that 🙄

i tried that first. That's why I though there is no context ...

2026-03-07T06:45:06Z

In reply to nevent1q…t32d
_________________________

i tried that first. That's why I though there is no context menu. It is nice to get access to your notes on someone else's device / a device where you don't want or can't install apps. works nice with bunker. My friend just put some ideas into my notes on his device. Probably an edge case.

Yeah thank you works fine on the app. but the browser version on ...

2026-03-07T06:24:10Z

In reply to nevent1q…pwcg
_________________________

Yeah thank you works fine on the app. but the browser version on mobile is weird. the "right-click/tap" is not working consistently for me.

My first treasure is waiting to be found ⛰️🏴‍☠️ ...

2026-03-07T04:56:26Z

My first treasure is waiting to be found ⛰️🏴‍☠️ #geocaching

https://treasures.to/naddr1qvzqqqyj3spzqhs57xzfxnygy8ce6upal8ckprdxywwg3lltdqdma7se8gn4evg2qy28wumn8ghj7un9d3shjtnyv9kh2uewd9hsq8nswfhkwun9wdekjan994hkc6tkv5kk2mt4956k2vf5vccnsdqlma3nl

gfy too man 🤙🫂

2026-03-07T04:37:38Z

In reply to nevent1q…6flu
_________________________

gfy too man 🤙🫂

Nostr event nevent1qqsxa9npyj2534esgv67xlky9ynjt6mm6dprtua82p5j5q38hz2lcrqzyp0pfuvyjdxgsg03n4crm703vzx6vguu3rl7k6qmhmapjw38tjcs5wuqa97

2026-03-06T18:31:26Z

what is crypto twitter

I just had a typical conversation about Bitcoin. It started with ...

2026-03-06T03:54:00Z

I just had a typical conversation about Bitcoin. It started with the question,

"Is Bitcoin even successful? I mean, what's the price right now?"

After I told him that success has nothing to do with the price, the next sentence came:

"I don't really know anything about it, but isn't it just used by criminals on the darknet to make even more money?"

And that was from a young IT guy who should actually understand pretty well. When I then told him about El Salvador, that I recently paid for my lunch with Lightning, and explained that the country he was currently in was mining Bitcoin with hydropower, he was completely surprised.

The orange pill doesn't go down easily. I think we still have a long way to go.

#grownostr #bitcoin

I know, I know people will hate me for that, but it is pretty ...

2026-03-06T03:48:15Z

In reply to nevent1q…z932
_________________________

I know, I know people will hate me for that, but it is pretty nice to have an eBook reader with warm white backlighting in such an environment. love the vibe ❤️

The follow list is a "message" like any other. It's ...

2026-03-05T12:42:15Z

In reply to nevent1q…e7nw
_________________________

The follow list is a "message" like any other. It's stored on all the relays you use. You can copy your follow list (or another user's) to as many relays as you like.

You cannot force someone else to unfollow you on Nostr; follows ...

2026-03-05T12:09:03Z

In reply to nevent1q…6nml
_________________________

You cannot force someone else to unfollow you on Nostr; follows are stored by the follower (their client / relay) not by the followed account.

Nostr event nevent1qqs85lytpgv6vpt3qh68ud55z9qvqyhm5usww8njpp0hd7m4j8lv37czyp0pfuvyjdxgsg03n4crm703vzx6vguu3rl7k6qmhmapjw38tjcs5v67kz5

2026-03-04T10:44:11Z

How much blood must be paid for a single drop of oil?

fellow #nostriches, saw this wanted to check if all of you are ...

2026-03-02T16:17:47Z

fellow #nostriches, saw this wanted to check if all of you are safe?

#grownostr

cuz we all vibe code now

2026-03-02T03:26:30Z

In reply to nevent1q…hj6n
_________________________

cuz we all vibe code now

Yes

2026-02-25T05:36:02Z

In reply to nevent1q…7znt
_________________________

Yes

but but but it is convenient. papa bezos would not do bad.

2026-02-20T00:19:32Z

In reply to nevent1q…hkrx
_________________________

but but but it is convenient. papa bezos would not do bad.

most, but not all or at least not everywhere

2026-02-17T17:37:19Z

In reply to nevent1q…vj4e
_________________________

most, but not all or at least not everywhere

Nostr event nevent1qqsx2lczdfzn0dtpfha7r8dtayss5r390ej3wdke70tzqqd3tqr5xyszyp0pfuvyjdxgsg03n4crm703vzx6vguu3rl7k6qmhmapjw38tjcs5d2y0xv

2026-02-16T19:23:04Z

In reply to nevent1q…qegr
_________________________

are the stars aligned in my favour? 🔮

2026-02-15T17:42:56Z

In reply to nevent1q…z3vk
_________________________

are the stars aligned in my favour? 🔮

0/10 way to expensive. Stack sats instead 😂

2026-02-15T15:22:26Z

In reply to nevent1q…zarv
_________________________

0/10 way to expensive. Stack sats instead 😂

My #Bitcoin fullnode runs on a computer I found on the streets. ...

2026-02-15T10:06:48Z

My #Bitcoin fullnode runs on a computer I found on the streets. And of course it also runs electrum and mempool.

One mans trash is another mans financial infrastructure.

#grownostr

Are there any good "read for free" bitcoin books? I ...

2026-02-14T09:00:42Z

Are there any good "read for free" bitcoin books?

I start:

https://21lessons.com/
https://github.com/bitcoinbook/bitcoinbook

#bookstr #asknostr #grownostr

I think this even intensified with #bip110 people seem to care ...

2026-02-14T07:15:33Z

I think this even intensified with #bip110 people seem to care more about insulting each other than anything else. This is so wild.

quoting
nevent1q…2dmp
#AskNostr Is it just me? All the posts about #knots that I see are rather aggressive and less objective. I don't see posts like that about #core. It seems to me that this is more about stirring up emotions than having an objective debate.

its funny that so many people didn't even answer the ...

2026-02-14T07:06:14Z

In reply to nevent1q…049u
_________________________

its funny that so many people didn't even answer the question.

sell everything for xrp? 🤑 I would just move it to a new ...

2026-02-12T17:43:54Z

In reply to nevent1q…6cyz
_________________________

sell everything for xrp? 🤑

I would just move it to a new wallet and backup the seed phrase. Then go to work as usual.

how did that happen?

2026-02-12T16:44:07Z

In reply to nevent1q…hvcr
_________________________

how did that happen?

had issues today, worked after a while

2026-02-11T17:14:31Z

In reply to nevent1q…acvw
_________________________

had issues today, worked after a while

coin dance counts almost 25.000 nodes. Feels good 🙏 ...

2026-02-11T16:32:27Z

In reply to nevent1q…6vhn
_________________________

coin dance counts almost 25.000 nodes. Feels good 🙏
https://coin.dance/nodes

Is your country into #censorship? Check it out with #ooni! Run ...

2026-02-11T03:58:31Z

Is your country into #censorship? Check it out with #ooni!

Run ooni tests today and help to document censorship.

https://ooni.org

I think it's best to look for other protocols like ...

2026-02-11T03:52:55Z

In reply to nevent1q…0ktu
_________________________

I think it's best to look for other protocols like BitTorrent, which work similarly. Governments and/or the media industry didn't like it and tried to stop it, but people still download torrents. PirateBay.org still exists and is still used despite being blocked in some countries.

However, they have managed to make torrents unattractive in some countries, which is why people have switched to alternatives. Piracy and torrenting are not dead.

Organic maps hat sich etwas unbeliebt gemacht, gibt den fork ...

2026-02-09T13:38:39Z

In reply to nevent1q…3tcf
_________________________

Organic maps hat sich etwas unbeliebt gemacht, gibt den fork comaps.app mit mehr features.

Is there a #nostr app for reviewing places on #openstreetmap or ...

2026-02-09T13:36:20Z

Is there a #nostr app for reviewing places on #openstreetmap or other platforms? #asknostr

For private use? no. But emergency services still use it.

2026-02-08T21:03:46Z

In reply to nevent1q…2zwd
_________________________

For private use? no. But emergency services still use it.

Seems the "communities feature" is not really used on ...

2026-02-08T20:59:37Z

Seems the "communities feature" is not really used on nostr. Why is that? Are hashtags enough? #AskNostr