melvincarvalho on Nostr: Hot take on the #pubky protocol. Bits I like, bits I dont like, bits that involve ...
Hot take on the #pubky protocol. Bits I like, bits I dont like, bits that involve trade-offs. Overall better than I expected. A pubky is basically an npub without a prefix and checksum. The enromously complicated npub checksum afaik is never used and its the "wrong" checksum (segwit vs taproot). Something nostr might be able to learn from. This is one reason why I'm glad there are different innovations in the space. Also nostr and pubky can be easily integrated. Would offer a lot new use cases. And I also like John, who has been often a voice of reason in the community. At this point, I wish them luck.
Published at
2024-10-27 13:40:28Event JSON
{
"id": "65af6973224a0a6e8acac99ad75f40985f22e04b56da07c52859e52f14190561",
"pubkey": "de7ecd1e2976a6adb2ffa5f4db81a7d812c8bb6698aa00dcf1e76adb55efd645",
"created_at": 1730036428,
"kind": 1,
"tags": [
[
"t",
"pubky"
]
],
"content": "Hot take on the #pubky protocol. Bits I like, bits I dont like, bits that involve trade-offs. Overall better than I expected. A pubky is basically an npub without a prefix and checksum. The enromously complicated npub checksum afaik is never used and its the \"wrong\" checksum (segwit vs taproot). Something nostr might be able to learn from. This is one reason why I'm glad there are different innovations in the space. Also nostr and pubky can be easily integrated. Would offer a lot new use cases. And I also like John, who has been often a voice of reason in the community. At this point, I wish them luck.",
"sig": "00d043d003833db2b790fd1a5067c70c6679299fe191aae1077cf41c0f6a22f1d103213494aaee2f8eff2236b91b191e9acfd0d0404c23d4e5682fcdf542dae5"
}
