nostr:npub1az9xj85cmxv8e9j9y80lvqp97crsqdu2fpu3srwthd99qfu9qsgstam8y8 What about a "Nostr nsec" option for BIP85 menu? It could also show you which is the corresponding npub to crosscheck it in the client.

Reply to this note

Please Login to reply.

Discussion

You can use the 32 bytes hex for now. To create a nsec we need to make some changes but only available on edge release.

Yes, this is what I did here in this other note. Works great! Just thought that being able to see the npub would help making sure everything went right. Cool for edge!

nostr:nevent1qqsttzq5fsknw00yug8qpgay8mdgrydmqlgjlc0waa8tw5dq9wwd2agpzpmhxue69uhkummnw3ezumt0d5hsygpyud7pukcv3w5dmcn4f08lcca4k2vlspj037uj308nzkuuf9jl8vpsgqqqqqqsdyn683

npub are created the same way Taproot addresses are generated.

wow can you explain what you did there. looks cool!

Having a seed in a Coldcard Q, I derived —using a BIP85 index— a deterministic 32-byte-hex. That's a private key for Nostr.

I asked Q to show it as a QR, and then I scanned it with a Nostr client. Thats it.

If I lose my phone or logout from client, I can always derive it again using the same seed and index with a CC Q 🙂

Can you do the same with JADE and create a QR ?

No idea 🫤

I will ask

Nobody but you knows what that means

Does that only work with the ColdCard Q?

thank you for explaining 🙏🙏