Nostr Web Client

Our existing system is a powerful, specific implementation of what the Attestations NIP aims to generalize. Our "verifications" are a highly specialized form of their "attestations." The NIP is not a replacement for our testing infrastructure but a potential protocol for broadcasting our results. Adopting the NIP could significantly increase the reach and interoperability of our findings within the broader Nostr ecosystem, making WalletScrutiny a foundational "Attestor" for app reproducibility.

We use a sophisticated, automated testing infrastructure to perform reproducible build verifications for cryptocurrency wallets, primarily for Android and hardware wallets. The goal is to determine if the publicly available application binary matches the publicly available source code. The results are published as detailed "Review Pages" on our website.

Attestations NIP: This is a new, generic proposal for making, tracking, and revoking truthfulness claims about any event on Nostr. It is not specific to wallets or reproducible builds. As it's a new proposal, it currently has no widespread adoption, but it aims to be a foundational layer for any "web of trust" application, from fact-checking to reputation systems.

Nathan Day 6mo ago

Would some form of Evidence tag work for your usecase?

An Attestation event could optionally reference your (Release) Verification event in this way.

We refer to the process of arriving at an Attestation state (valid/invalid) as the verification process, but we are silent on what that process is as it's Subject Event - and often Attestor specific - and is down for the WoT to weigh those.

Some form of evidence expectation could optionally be included in the Attestation Request. 🤔

Reply to this note

Please Login to reply.

Discussion

dannybuntu 6mo ago

nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgkwaehxw309aex2mrp0yhxummnw3ezumn9wshsqgqrk5pkms7msfsyxp7pjexjhynyz753cwc3aa6m5m992qv7ndax9gk27w9w could answer that.

btc_remnant 6mo ago

> An Attestation event could optionally reference your (Release) Verification event in this way

Yeah, I guess we could use part of the NIP. Probably not the full one, as I don't see us requesting attestations to other users. Maybe I'm wrong. Also, is this mechanism meant to be implemented by general purpose clients? I mean, I don't expect a lot of clients showing our "verifications" events, so I don't know if any client will show the "request for attestation" to our event kinds.

Nathan Day 6mo ago

No, I don't think it'll be in general clients.

Specific clients will show relevent Attestations base on the kind type of the Subject Event.

e.g. nostr:nprofile1qqsra2ey033mkdwl5w8q0jss9ak69zafh82xsuvhwsaauw3trkq2amgpz9mhxue69uhkummnw3ezuamfdejj7qgcwaehxw309anxjmr5v4ezumn0wd68ytnhd9hx2tck28qzu will show Place Attestations.

Attestation marketplaces will emerge as specialist clients.