I'm working on WalletScrutiny.com and I'm trying to move all that could be called "attestation" to nostr with several goals:
* WalletScrutiny should not be the only authority on what we attest to. Others should be able to equally chime in and potentially provide alternative opinions.
* In nostr, events are signed by an author, with the signature being verifiable by the visitor.
* The author has followers or otherwise a web of trust which gives the visitor something to go by when judging whose attestation is worth something and whose not.
* Nostr is a protocol. Attestations could be integrated in other apps that ascribe value to them. zap.store for example could show attestations in the app store where available. bitcoinbinary.org could collaborate on these attestations given the very similar focus.
* Nostr is social. Building on nostr, WalletScrutiny might get more visibility, especially if the integration is not disruptive to others.
My question is which nip or nip proposal should I build on? https://github.com/nostr-protocol/nips/pull/1336/files looks relevant but that's only on the per app level and not on the per artifact level. For example build reproducibility is a property of each binary. Which are the kinds we should use for attestations?
franzap (npub1wf4…dgh9) PABLOF7z (npub1l2v…ajft) NVK (npub1az9…m8y8) #askNostr
LeoWandersleb / Leo Wandersleb
npub1gm…78rf6
2024-08-22 21:53:40
Author Public Key
npub1gm7tuvr9atc6u7q3gevjfeyfyvmrlul4y67k7u7hcxztz67ceexs078rf6Published at
2024-08-22 21:53:40Event JSON
{
"id": "0d4980bf542bcfdc1b4927786335ab4662a367b7bd0fb31754e1c46999c0a927",
"pubkey": "46fcbe3065eaf1ae7811465924e48923363ff3f526bd6f73d7c184b16bd8ce4d",
"created_at": 1724363620,
"kind": 1,
"tags": [
[
"t",
"asknostr"
],
[
"p",
"726a1e261cc6474674e8285e3951b3bb139be9a773d1acf49dc868db861a1c11",
"",
"mention"
],
[
"p",
"fa984bd7dbb282f07e16e7ae87b26a2a7b9b90b7246a44771f0cf5ae58018f52",
"",
"mention"
],
[
"p",
"e88a691e98d9987c964521dff60025f60700378a4879180dcbbb4a5027850411",
"",
"mention"
]
],
"content": "I'm working on WalletScrutiny.com and I'm trying to move all that could be called \"attestation\" to nostr with several goals:\n\n* WalletScrutiny should not be the only authority on what we attest to. Others should be able to equally chime in and potentially provide alternative opinions.\n\n* In nostr, events are signed by an author, with the signature being verifiable by the visitor.\n\n* The author has followers or otherwise a web of trust which gives the visitor something to go by when judging whose attestation is worth something and whose not.\n\n* Nostr is a protocol. Attestations could be integrated in other apps that ascribe value to them. zap.store for example could show attestations in the app store where available. bitcoinbinary.org could collaborate on these attestations given the very similar focus.\n\n* Nostr is social. Building on nostr, WalletScrutiny might get more visibility, especially if the integration is not disruptive to others.\n\nMy question is which nip or nip proposal should I build on? https://github.com/nostr-protocol/nips/pull/1336/files looks relevant but that's only on the per app level and not on the per artifact level. For example build reproducibility is a property of each binary. Which are the kinds we should use for attestations?\n\nnostr:npub1wf4pufsucer5va8g9p0rj5dnhvfeh6d8w0g6eayaep5dhps6rsgs43dgh9 nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft nostr:npub1az9xj85cmxv8e9j9y80lvqp97crsqdu2fpu3srwthd99qfu9qsgstam8y8 #askNostr",
"sig": "5f6bbb0aab51ae4b64b5e2697ea07eb9d5b78e2669f621a44545db402ef85cae8fbeeee5f6f8c7baf24e36f8b0383c37b67a9d9a2975adcd61f631d79561f30c"
}