[Nostr] - New nip proof of account

nip-proof-of-account.md

NIP-XX

Proof of account protocol

draft mandatory

1. Users can prove they own some accounts by publishing an event to the relays proof:<{pubkey}, {type}, {url}>

• {pubkey} is a pubkey, as a hex string
• {type} is a string with a single letter, which can be:
  • "t" : for twitter
  • "g" : for github
• {url} is the url of the proof

Example : proof:{"pubkey":"19f....5dg", "type":"t", "url":"https://twitter.com/xxx/status/xxxxxxx"}

2. Relay store the proof.

3. Relay send back the the result to the client. Client has to validate the proof.

Proof content : TODO

We cannot expect relays to validate anything. We can say they should validate, but ultimately the client must validate it by itself or ignore these proofs.

We cannot expect relays to validate anything. We can say they should validate, but ultimately the client must validate it by itself or ignore these proofs.

I'm agree with that. I'll remove it. I'm just afraid on one thing. Client will have a lot of queries to do to validate the proof. But it should be ok

It's not very ok, I think, but some clients may still choose to do it. Or they may choose to only do it with people they're browsing specifically and directly.

Also it's much easier to do this if you're doing it from a native client instead of a web client. Maybe it's not even possible to do it from a web client depending on what you want to verify.

Another thing that could be done is clients that come bundled with a special server (not a relay) that helps them do these expensive operations and keeps verification states and other goodies (of course, all trusted).