10/30/2026, 20 engagements
Zapstore
Download 1.1.2 for Android: https://zapstore.dev/ SHA-256 checksum: 29b7aae256ef567e466c30fac13b8a7794d84a79862162d69f029f61c2ce5dd2 APK certificate hash (for AppVerifier): 99e33b0c2d07e75fcd9df7e40e886646ff667e3aa6648e1a1160b036cf2b9320 Nostr DMs will be ignored, tag us instead.
Getting negative vibes from developers lately
Bare with me in this transition week, I'm doing my best to push v2 across the finish line WHILE making current shit still work
I have no obligation to do a proper migration, please be kind
10/30/2026, 60 engagements
Apps that have no Android keystore ownership proof (signed NIP-C1) are no longer accepted.
The ones without proof already accepted will show no author in the new app. It doesn't matter if that pubkey signed the release events.
The feature was in zsp for months.
10/27/2026, 16 engagements
Developers FYI:
There is no more immediate publishing in the new relay, it takes a few minutes max.
Events are now verified and only then promoted:
- check no broken nostr events, e.g. a single orphan kind 3063
- APK exists and its certificate matches up with the C1 proof
We no longer accept apps if you can't prove they're yours.
We want no more garbage or broken listings.
10/27/2026, 27 engagements
Hotbox 🔥
A secure vault that keeps both your nsec and Android keys, so you can keep a single file and open it for safe agentic use. It goes hand in hand with zsp.
10/27/2026, 12 engagements
zsp v2 - the most agent friendly app store publisher is out
10/27/2026, 12 engagements
First leg of Zapstore v2 released:
1️⃣ Relay v2 with indexer deployed 2️⃣ zsp v2 now available 3️⃣ hotbox is out too!
New app and webapp next week 🤞! The vision for zapstore is becoming reality
10/27/2026, 40 engagements
Many developers creating new npubs just for releasing apps.
In v2 we will be pushing features so that they use their most reputable npub.
Otherwise web of trust is even less helpful.
10/23/2026, 10 engagements
ICYMI: Update now
Loading quoted post…
10/21/2026, 1 engagement
The app is dead. Long live the app!
Loading quoted post…
10/21/2026, 7 engagements
Zapstore 1.1.3 released, update now!
Rolling out Zapstore v2 over the next weeks, this patch release includes compatibility with new relay v2 constraints and the new catalog signing key.
If you stay on 1.1.2 you will notice the experience degraded, though it should still work.
10/20/2026, 8 engagements
Step by step, v2 taking shape 👷


10/16/2026, 1 engagement
Imagination, taste and drive are the limiting factors 🎯
Loading quoted post…
Shower thought turned into an app!
Zaplite is a lightweight client for Zapstore
The app itself is only 1.5 MB. It uses very little storage and bandwidth. Designed to run on low powered devices and old Android versions.
No search by name No browsing No stacks No screenshots No comments, profiles, or zaps No privacy reports or permission lists No settings or Tor No update all No uninstall
Just keeping up to date.
10/10/2026, 2 engagements
Services back online.
Relay should be healthy but please report if you find any issues.
Investigating what happened.
Loading quoted post…
10/10/2026, 4 engagements
We are having issues with our server.
On it. Will post updates here.
10/10/2026, 11 engagements
Despite having the lowest bar for publishing apps ever...
We still have developers lagging behind.
WE GONNA LOWER IT EVEN MORE


10/9/2026, 6 engagements
Replacing our indexing software, so there won't be external updates until tomorrow due to this maintenance operation.
Self-publishing not affected.
We now placed all emphasis on certificates, so if you get another "certificate mismatch" just know it will be the last time.
We picked one stable key per app, and honor rotations. Prioritizing self-signed apps and deprioritizing external builds such as F-Droid.
This is the first step towards v2.
10/6/2026, 8 engagements
Zapstore v2 is becoming almost a full rewrite. The clankers,
and
have been going hard on development (but mostly systems design) for many weeks now.
It is the first time I can say everything actually makes sense. We have a cohesive product story that is reflected in every project that constitutes it.
Including how we communicate it. It's a freedom tech product, not just a nostr one anymore.
This is why I'm quite silent, and why there are no incremental updates. The whole product will be launched at once.
We can finally push features we've been asked for, for ages. I'm particularly excited about the new privacy and security features. Publishing and discovery as well.
The new website is looking hot. Not only way faster but more clear. No more ambiguities around rules for publishing.
I have also taken time to sharpen tools and operations, many are now agent-first (public and internal). And app releases should happen more often.
Fortunately, it seems we won't have many migration or backward-compatibility issues.
Hard work, probably a million decisions taken already to reshape this in the right direction. Excited for what the future holds.
10/3/2026, 57 engagements
Done!
Appears to be a great Google Maps alternative:
Loading quoted post…
10/1/2026, 8 engagements
"Version numbers are strings"
Developers:


9/28/2026, 2 engagements
Trying out new things.
Coming soon to a Zapstore near you.


9/27/2026, 6 engagements
These comments keep me going 💙
Loading quoted post…
9/23/2026, 3 engagements
A Bitcoin node syncs blocks and queries locally.
Organic Maps pulls tiles and queries locally.
Why can't Zapstore pull release bundles and query locally?
At first this sounded crazy.
It turns out it's (almost) the holy grail of privacy and UX.
Initial prototype of v2 is insanely promising.
App written in Kotlin from scratch.
Browsing apps is instant. Search is orders of magnitude better.
For update checks, no need to reveal your installed app set to any remote server.
Tor by default.
And that's just the tip of the iceberg.
More soon.
9/21/2026, 9 engagements
🚨 Please update to Zapstore 1.1.2
It was released last week and contains a fix for a major security bug found in an underlying library, related to nostr event verification.
I don't believe it has been exploited as apps are loaded primarily from relay.zapstore.dev (which properly verifies nostr events) and we haven't heard of any report.
Found by ethicnology, thank you Sir (couldn't find his nostr profile, he deserves some zaps!)
9/4/2026, 4 engagements
Thank y'all for the kind words but also for the bug reports.
I hear you and know many things are suboptimal.
We are designing Zapstore v2 (mainly a new indexer with hard lessons learned, revamped zsp and a new mobile app)
I won't spill the beans yet but I'm excited. Everything starting to make much more sense.
8/28/2026, 5 engagements
Starting to push Zapstore repos to ngit, finally!
8/11/2026, 1 engagement