Nostr Web Client

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

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.

Reply to this note

Please Login to reply.

Discussion

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.