hodlbod
hodlbod
@fiatjaf I have to agree with your critiques. Writing this NIP has taught me that **any** key rotation scheme on nostr is going to come with some *hefty* assumptions and...
Closed in favor of #2137
@arkin0x @pablof7z
Yeah, write a NIP. The whole point of nostr is network effect, and a NIP makes network effect over a feature set possible.
An alternative to edit could be "annotations". In threads on github, it's convention for anything more than a minor edit to be appended to the bottom of a comment with...
I think that only makes things less clear. Having the requirement that the event is immediately available forces us to solve the problem of where to put the events. Anyway,...
> relay.damus.io, nos.lol, relay.primal.net We need something similar to promenade coordinators/signers, or indexer relays like purplepag.es. These are relays whose owners are trusted, and which can be relied upon to...
> Hadn't we softly reserved NIP-41 to be used for this identity migration thing? Renamed > What if the user changes their mind about opting out or lose the key...
> Why can't we just pre-sign the migration event with the old key pointing to the next key This means that the user has to generate the next key eagerly...
> Can we design this NIP from the standpoint of having a vault-like type of client? This is an implementation detail. Nothing in this NIP requires any client to do...