I see verified contacts as the most important feature to develop right now. It may not seem revolutionary on its own, but I believe it is a fundamental building block for a resilient P2P network.

- You verify your contact’s identity (npub) in your hardware wallet.

— This is best done offline. You don’t need many contacts, just ones you fully trust.

- When sending an on-chain transaction, you use an address signed by that contact.

— This means you don’t need to check the address on your HWW, just the human-readable name tag.

- The verified contact’s address can be automatically retrieved in the background.

— We tested this using Nostr in our prototype, and it worked well.

- The same approach can be used to verify anything else.

— For example, LN invoices or Ark addresses.

- This could also enable:

— P2P marketplaces

— Social backup

— Trust-based scaling nostr:note174qkw0ujwx3z8867sceg8fd7h9kf0w7j8te6a4a6qd76sap0gksqf7d5y4

Ideally, a high-quality standard would emerge that various HWWs could adopt. This would allow deriving backups for any hot wallets, and verified contacts could be used consistently across all applications.

Reply to this note

Please Login to reply.

Discussion

Kind 0 meta attestations (perhaps more?) I think is all that is needed for that. Could be combined with a new "follow" event, should there be one.

https://github.com/nostr-protocol/nips/blob/a2574814c2b4e01019ec946bc76f40a8c03086a0/xx.md

Thanks. It looks compatible. I was thinking about local storage. Since I don’t need to publish the proofs 🤔