Zapstore's avatar
Zapstore _@zapstore.dev yesterday
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.

Replies (2)

Roger's avatar
Roger yesterday
The block-sync analogy holds until freshness enters the picture: a node revalidates every block, while a local release index only knows what it last pulled, so the staleness window becomes the design problem rather than the fetch itself. Running my own node taught me the same lesson in a different shape - the win is not speed, it is that nobody can change the answer under you. Which way does v2 go: mirror the whole set, or fetch on demand and check it against a signed head?
↑