Replying to Avatar Gzuuus

Wow, I was just playing around with the new version of nak by nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 , with it you can create your bunker in seconds to sign remotely on any client that supports nip-46. Just download the utility from the https://github.com/fiatjaf/nak repository, there you will find instructions on how to run it, once installed use the command `nak bunker --prompt-sec wss://` to start the bunker with the relay of your choice as coordinator, then once it has run it will ask you to set your nsec, after that you are all set to sign messages remotely using your own bunker!

I have recorded a short demo

https://media.nostr.build/av/1f14384e94665125e13524471899962d456c69114dc4f09d3c97dae0daf37300.webm

This is great! going to try it also. nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 I see the connection string is a bit different than I remember when integrating Pablo’s version, does it work the same or is this a different spec?

Reply to this note

Please Login to reply.

Discussion

Same spec, just change the prefix from nsecbunker to just bunker

It's the same. We must agree on a connection string. I think people like the "bunker://" notation, so we must convince nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft to implement it.

But we should also implement the NIP-05 custodial flow he is working on. I am not sure what are the necessary changes, but should be minimal.