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.

Replies (4)

Universal, used broadly for signing. Easy to verify signatures. More and more projects use it. You can sign messages in case the website is compromised - trust hooks are the most important, place the key and/or its fingerprint on github, on nostr on the website, let people fetch it for the future, use webarchive to save the fingerprint (time based trusthook). Sign rotated keys with an older key, attach the fingerprint inside the zapstore itself (Putty project does exactly that, attaches the FP inside the binary for yet another trust hook)
We are trying to make cryptographic asset verification easier with Zapstore, GPG has many documented issue. I think less and less projects use it. Kind of pointless on Android too and even more so when we link the keystore to a nostr keypair
↑