Nostr has this too, secp256k1 is an asymmetric signature algorithm. This is redundant buzzword spewing.
> more gobbledegook about homeservers
Once again you have not really addressed what pubky is solving, you have not elaborated any kind of architecture that it is clear would be useful or desirable. All data stored on homeservers introduces new problems of its own, but given that Pubky's only coherent user acquisition strategy seems to be trying to take users from Nostr it is doubtful that it will ever have enough users to find out why its design decisions are laughably atrocious.
> Decentralized discovery ... DHT
DHT-based node discovery is a possible feature for Nostr. I have no idea why I should waste my time propagating yet another public key for a service that has no social graph for it. jb55 (npub1xts…kk5s) has even speculated on implementing it (relevant nevent attached). It's not a bad potential feature but never once have I heard "node discovery" on a list of major struggles users have experienced. Most nevents have node hints attached. If Nostr ever becomes targeted by the authorities enough that DHT for node discovery becomes desirable, it can certainly be tacked on with minimal effort, and doesn't justify the existence of a new protocol.
Pubky is not solving any problems. Its entire existence and strategy makes sense when you just say "Tether is funding this, and it required SMS verification." It all becomes extremely clear what is going on to literally everyone.
quotingi like the idea of dht + gossip as a layer for nodes that are trying to find specific ids after the source relay is down. p2p for eventual consistency...
nevent1q…j4ma