What are endorsements? Do you have a NIP or some ref docs I can look at. Attestations are kind agnostic.

@Tim Bouma will be using it for #safebox. @arkinox for @Fanfares. @BTC Map for Proof of Place. I think it works really well for @Zapstore too. Hell, we can even define what Nostr is itself by using the NIP NIP @Alex Gleason has created.

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.

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. 🤔

Yes, it's kind of the same concept. I still have to read it more carefully, but maybe we could implement some parts of the nip, not all of it:

btc_remnant

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

Yeah, I guess we could use part of the NIP...