Can someone help me understand how Zapstore (nprofile…tdq0) works?
First thing I don't understand is where the files live. Do the APKs just live on github and then there is automation to check that the hash of the release matches what the dev publishes to zapstore?
If so, what is actually published to zapstore? Is it just a note from a developer that a release has been made, it's location and hash?
au9913
npub16u…6lra7
2025-01-14 15:19:29
Author Public Key
npub16ux4qzg4qjue95vr3q327fzata4n594c9kgh4jmeyn80v8k54nhqg6lra7Published at
2025-01-14 15:19:29Event JSON
{
"id": "ff8029fdc1ad83e6b3a950c5d41d718737b3299d0411a75909f8988ca7ca9445",
"pubkey": "d70d50091504b992d1838822af245d5f6b3a16b82d917acb7924cef61ed4acee",
"created_at": 1736867969,
"kind": 1,
"tags": [
[
"p",
"78ce6faa72264387284e647ba6938995735ec8c7d5c5a65737e55130f026307d",
"",
"mention"
]
],
"content": "Can someone help me understand how nostr:nprofile1qqs83nn04fezvsu89p8xg7axjwye2u67errat3dx2um725fs7qnrqlgzqtdq0 works? \n\nFirst thing I don't understand is where the files live. Do the APKs just live on github and then there is automation to check that the hash of the release matches what the dev publishes to zapstore?\n\nIf so, what is actually published to zapstore? Is it just a note from a developer that a release has been made, it's location and hash? ",
"sig": "407679e75bc323017bd37b183df968691c55ff5fa9c14aad983489911326e9861d835a8210d66ff1eb4f9169bf41fcb3d266580b674c9491bd976f14068fc518"
}