Nostr Zapstore: The Attack on Apple & Google's App Store Monopoly

Software is today's gateway to the world. But who controls which software you're allowed to install on your phone? For over a decade we've been living inside a global duopoly. Apple (iOS) and Google (Android) act as the de-facto wardens of our digital prisons — often euphemistically called "Walled Gardens."

They decide what gets censored, they take up to 30 percent as "taxes" on innovation, and they dictate what digital sovereignty is allowed to mean. But resistance is stirring. The Nostr protocol, originally launched as a Twitter alternative, has built a weapon against this monopoly: the Nostr Zapstore.

We're going to look at how this system works, why Apple is afraid of it, and whether it's actually secure.

1. The Architecture of Control: Why We Need an Alternative

To understand why the Zapstore matters, we need to name the problem. The power of Apple and Google rests on three pillars: gatekeeping, economic extraction, and data centralization.

Gatekeeping as a Power Tool

Every app must pass through corporate review. What officially goes by "security" is often political or economic censorship. A textbook example is the conflict between Apple and the Nostr app Damus.

"Apple threatened to remove Damus from the App Store because users could send each other 'Zaps' (Bitcoin via Lightning) for posts. Apple wanted such payments to go through Apple's In-App Purchase system (up to 30% cut). But since Zaps run peer-to-peer, this model doesn't technically fit cleanly. The result: Apple forced Damus to cripple the feature."

This makes it clear: real peer-to-peer economics are unwelcome in closed stores. Anyone threatening the gatekeepers' business model gets thrown out.

The Illusion of Security

The argument "only the App Store is safe" is fragile. Centralized authorities are a single point of failure. Remember the scandal around "Web of Trust" (WOT): a centralized tool that promised security, but was quietly passing user data to third parties in the background. When the guardian is corrupt or gets hacked, all users are affected simultaneously.

2. The Nostr Zapstore: A Technical Breakdown

The "Zapstore" is not a central company and not a central server. It's a protocol. It's built on several Nostr standards (NIPs) that together form a decentralized infrastructure.

The Foundation: App Events (Kind 32267) & Releases (NIP-51)

How do you find an app without Google? Via Nostr events. Developers publish a signed app event (kind:32267, NIP-82) to the Nostr network. It contains name, icon, tags, and references to releases. Releases are modeled as "Release Artifact Sets" (kind:30063, NIP-51) and reference file metadata (kind:1063, NIP-94) including download URL and hash. It's a decentralized app manifest. Nobody can stop a developer from sending this event. It's permissionless.

Blossom: Decentralized Storage

Nostr relays typically store text, not large files. That's where Blossom comes in. Files are not stored under a name, but under their cryptographic fingerprint (hash).

• Integrity: Change a single bit in the file and the hash changes. Tampering is immediately obvious.
• Censorship resistance: Since a file is only retrieved by its hash, it can be mirrored across many servers. For apps that only the Zapstore's indexer has listed, however, the file comes from the developer's download address.

Cryptographic Identity

In the Zapstore there are no accounts with email addresses. Developers identify themselves via their public key. Release and update metadata are signed with the private key. Your phone checks: "Does this update really come from the same developer as before?" Many apps, however, are listed by the Zapstore indexer, which points to the release on GitHub, for example. Then the indexer signs the Nostr entry, not the developer. The APK itself still carries the developer's signature. Who stands behind a key is only proven by an identity proof. That's supply-chain security at Linux level, made usable for end users.

3. Value Proposition: Freedom & Money Streaming

Why go through the effort? Because the economic model is genuinely different.

Value4Value (V4V) Instead of a 30% Tax

In the Zapstore there is no central platform fee. When you buy an app or send money to a developer, it happens via Bitcoin Lightning. The money flows directly from you to the developer. This enables microtransactions (e.g. 10 cents for a feature) that were impossible in the old system due to fees.

Web of Trust Instead of Algorithm

In Google's Play Store you see what spends the most on ads. In the Zapstore you see what your network recommends. If a security researcher you trust "zaps" or recommends an app, that carries more weight than anonymous 5-star reviews that are often bought by bots.

4. Decentralization vs. Security: A Critical Look

Without a gatekeeper, anyone can upload apps — including malware. How does the Zapstore protect us?

Protection in the Zapstore is based on transparency and reputation. An app from an unknown key is marked as "unverified." Also: on Android, apps run in a sandbox. Even a malicious app from the Zapstore cannot access your contacts or location data without the corresponding permissions. The operating system's security is the last line of defense.

5. In Practice: Does This Actually Work?

Android: The Happy Path

On Android, the Zapstore already works surprisingly well today. You just need to allow installation from "unknown sources" once. After that it feels like an F-Droid store with social features. Since version 1.1, automatic background updates can be turned on (profile → "Data Management" → "Background auto-updates"). They only run on unmetered networks and with sufficient battery charge, and hash and signature are checked. Without asking, the Zapstore only installs apps it installed itself. The zsp tool lets developers push updates directly from their development environment (e.g. CI pipelines like GitHub Actions) to the world — no waiting, no review.

iOS: Sovereignty Denied

There is no iOS version so far. It was announced for the third quarter of 2026, and by early October 2026 it had not appeared. With version 1.1, the project dropped Linux and macOS as platforms. Outside the EU (and Japan), Apple does not allow real sideloading anyway. In the EU (and Japan), Apple does permit alternative app marketplaces and web distribution, but only under strict Apple rules; real, free sideloading remains heavily restricted. This makes it clear: anyone who wants digital freedom hits a hard wall with Apple.

6. Alien Verdict: A Crack in the Wall

The Nostr Zapstore isn't ready for mass adoption yet. It doesn't pass the "grandma test." But it's proof that it's technically possible to distribute software globally without asking a corporation for permission and without paying up to 30 percent protection money.

It's a return to the principles of the open internet — combined with hard money (Bitcoin) and hard cryptography. For developers it's a lifeboat. For users it's a tool for self-defense.