<unnamed>

🚨 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!)
https://github.com/zapstore/zapstore

2026-08-28 20:29:19 UTC

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.

2026-08-04 21:39:03 UTC

🎯
https://blossom.primal.net/6ce0bb53b832e5d43825090e59fe95ebbdf291508ad799feec9bfb63a5d39b46.jpg

2026-08-03 20:51:58 UTC

Seeing more Certificate Mismatch errors?
Deployed an upgrade to the indexer.
As we deprioritize F-Droid signed releases in favor of developer-signed (as it should be) you may find some new Certificate Mismatch errors.
To keep updating those apps you'll need to reinstall them. Unfortunately there is no other way. (If you have multiple profiles on your device, ensure to remove app from all of them!)
Apologies for the inconvenience, but it's the right move to minimize certificate mismatches in the future!

2026-07-29 19:02:01 UTC

Someone is constantly releasing updates to an app.
It's cool too see how frictionless app publishing can be, on the other hand they live in Latest Releases which takes space away from other projects.
We're going to move away from this dumb REQ approach and work on a smarter feed for discovering new stuff.

2026-07-28 12:39:17 UTC

- reply

Great!

2026-07-27 22:05:29 UTC

- reply

@nprofile…gnen I found the issue. You are not bumping the version code, so Android thinks it's the same version. "1.5.0" means nothing, it's the 2001 that counts.
We may put a guard for this in zsp in the future, but this is standard Android dev.

2026-07-25 21:04:05 UTC

- reply

Yes definitely weird. Will try with 1.4.1 -> 1.5.0

2026-07-25 21:02:53 UTC

- reply

No Google please, hold your keys

2026-07-24 18:43:13 UTC

- reply

I was unable to reproduce but fed the issue to the agent to create a potential fix, curious does this happen with just this app or others? Screenshots?

2026-07-24 16:21:46 UTC

Amazing charts of apps on Zapstore!
https://dev.nostrolo.gy/zapstore

2026-07-24 15:05:20 UTC

- reply

Or maybe a post-install action we can trigger for Amber users? @nprofile…xcpk

2026-07-24 15:03:34 UTC

- reply

Love this idea but it's on the app developer and Amber side.
Zapstore can help with app stacks, unfortunately can't avoid per-app install confirmations enforced by the OS.
Having a one-tap install experience would be wonderful, including a "restore my apps" on a new device just with a Nostr sign in.

2026-07-24 14:57:48 UTC

GM developers
When publishing, don't skip linking your Android keystore/cert to your Nostr identity!
(We need to know that you actually own the app)
Soon, apps without it will show as unclaimed, as any other indexed app regardless of who published the app metadata.

2026-07-24 14:49:26 UTC

- reply

Are you publishing PosterChan nonstop every few hours? It's not wrong but it's always present in latest releases

2026-07-23 20:46:30 UTC

- reply

Done

2026-07-23 19:56:24 UTC

- reply

Thanks. That is a different error. Sorry I should make this more clear in the UI.
What version are you on? Have you installed those apps via another store?
You can now swipe left on those apps to unmanage (prevent Zapstore from checking for updates)

2026-07-23 19:54:28 UTC

- reply

#nevent1q…d0fd

2026-07-23 19:52:15 UTC

- reply

I can't reproduce the error with any of those. It also doesn't make sense as there is no C1 proof for indexed apps (obviously)
Can you share screenshots when that happens?

2026-07-23 19:41:06 UTC

- reply

Unfortunately the publisher signature is broken, I will reach out for them to re-sign

2026-07-20 19:46:46 UTC

🚀 zsp release 0.4.14 :
- Fix bad name and icon extraction regression
- Fix Gitlab parser download path
- Add fastlane as metadata source
- Add Tor fallback for failing requests, retries
- Add default image compression
https://github.com/zapstore/zsp

2026-07-18 14:39:29 UTC

- reply

Sorry, it opens a can of worms and I have many other things to do. It is literally the first time someone asks for wearos

2026-07-18 14:38:01 UTC

- reply

I would like it too, but that will have to wait. I don't have time or even those devices to test with

2026-07-17 22:55:10 UTC

- reply

Against known certs

2026-07-17 21:11:47 UTC

NEW FEATURES
- Background auto updates (opt in)
- Check certificate ownership before installation
- Back up settings, bookmarks, and more to a device key
- Ability to exclude apps from updates
- NIP-56 reporting
- Shareable app dagnostics
- Efficient image loading
#nevent1q…2732

2026-07-17 20:57:07 UTC

Also released new zsp and fixed several issues with apps stuck in the indexer.
Brave, Ironfox, Aurora Store, Flow and others are back!

2026-07-17 20:55:34 UTC

Implemented on the fly image compression for icons, profile pictures and screenshots.
For some images gains are slight and for others up to 30x
Live on the website and on latest zapstore 1.1.0, it should feel way faster!

2026-07-17 20:46:01 UTC

🥏 Zapstore 1.1.0 just dropped
New features and lots of fixes!
https://zapstore.dev/apps/dev.zapstore.app
Update from the app or download at zapstore.dev

2026-07-15 15:33:14 UTC

- reply

Yeah I always liked the language but used Flutter because of my previous experience with it. It's great too but the situation with coding agents now is different.

2026-07-15 15:27:50 UTC

Over the past week I have also been working on a completely new codebase for the Zapstore app, in pure Kotlin.
(A recurrent issue with the current Flutter app is the boilerplate/overhead to interact with native features.)
Things require less code and feel significantly faster, but to be fair it has 10% of the features so far. Promising option for Zapstore v2.