Nostr Web Client

One point of confusion between Nostr and Pubky is that Nostr signs individual events (the post-it notes) while Pubky just signs the pkDNS (the board where the post-it notes are stuck on).

On Pubky you could build a client that signs the post-it notes and not just the board. It's just that if you can sign the board then there's less of a need to sign the individual post-it notes, hence the demo client shies away from that.

Garbage nsec 5mo ago

To add to that, for atproto what's signed is the content Identifier (commit) of the new merkle search tree root, and not individual posts. So you sign off on changes of state to your entire history (which could represent the additional of a single post, but not limited to that).

Summary:

Nostr - Sign the note itself

Pubky - Sign DNS beforehand (and the note itself too if you want, but that might be seen as unnecessary)

Atproto - Sign the new state of your personal history

Farcaster - Sign the note itself (except unlike Nostr the "signers" are delegated)

Feels like something nostr:npub1h0uj825jgcr9lzxyp37ehasuenq070707pj63je07n8mkcsg3u0qnsrwx8 would make a good diagram for.

Reply to this note

Please Login to reply.

Discussion

Keychat 5mo ago

I might not have kept up with your discussion. The core of Keychat is the seed phrase , which can derive public-private key pairs for different elliptic curves.

Garbage nsec 5mo ago

I'm just joking cause you make those graphs

Keychat 5mo ago

I thought you wanted Keychat to derive the Pubky key.🤔

Garbage nsec 5mo ago

No no, just comparing what exactly gets signed on the different protocols. Like you compare different L2 networks and such.