I’ve been meaning to generate a new key pair and just go through the process on the hosted version, thanks for that link!

Reply to this note

Please Login to reply.

Discussion

Just found this one too! Even more good descriptions.

nostr:note1rf3xwtlehsnas944kh5kekmtg52pc63tdspa757g80c9nj9zgd2saasjjn

does the client need login with nsec bunker or you can also generate an unique nsec for a client that doesn’t have that?

I think the client needs to be nip-46 compatible. So far it seems to be coracle.social and nostr.kiwi. Haven’t found others.

On coracle.social it shows my npub and the “bunker key” which is the delegated nsec for that client. You might be able to plug that nsec into another client, but unless it was nip-46 compliant I think it would just treat it as a normal nsec and be associated with the delegated npub and not your npub.

I’ll have to look into if I can implement it in sideus, or possibly just wait for damus to

Would love to see it! I haven’t heard of altstore or seen sideus yet. Will have to take a look. I locked my Damus version into the last TestFlight version before they removed zaps but now I can’t install TestFlight 😅

what available right now is very close to what you have. it’s about at 1.5(4) TestFlight so maybe you don’t have the alby one tap.

there still 66 days until those builds expire, yours should still live on with out update. no purpose really until then, mostly just to give time to get altstore set up. Hopefully damus has bunker support by then, solves for the trusting who built it.