Trending Tags
  • #bitcoin
  • #nostr
  • #Bitcoin
  • #yarnstr
  • #threelaws
Trending Notes
Global
Trending Profiles
  • Silberengel
    @Laeserin
  • Kevin's Bacon
    @Kevin's Bacon
  • The Daniel ⚡️ and 84 sats
    @daniel
  • Brunswick
    @Brunswick
  • makomichi the wolf of weeb street
    @makomichi

Nostr View


hzrd149 @hzrd149 - 6d

Your right the possibilities with key delegation (and by extention rotation) are very powerful however as you mentioned it gets complex and the complexity IS the issue because it scales exponentially and not linearly Generally speaking complexity is bad because it slows adoption and introduces bugs. But its even worse when complexity is required on the edges (clients) because that means that for every user who uses key delegation every other user needs to check the validity of the delegation along with and possible revocatiotion. This would quickly become unmanageable or would cause the network to centralize because of the sheer number of checks required for clients to do. Also having complexity on the edges introduces new attack vectors like users rotating keys every minute or creating more delegations than a client could easily check. I haven't read the link you sent so I don't know if you've made any improves. but in my opinion Nostr succeeded because it did not key delegation or rotation, it was stupid simple which made it get quickly adopted by devs

0
0
3

Showing page 1 of 1 pages