We need to fix that. You should be able to import your key if you want but it's not necessary for zaps/NWC to work. It only matters if you want to have the same follows/followers show up within coinos. We're planning to let people sync their keys with an external browser extension or signer app like Amber soon so you won't need to provide your secret key directly.
Also, nostr:npub1h2qfjpnxau9k7ja9qkf50043xfpfy8j5v60xsqryef64y44puwnq28w8ch when I go to the settings area there's a Nostr integrations area that has an npub and nsec. So that's obviously different than my nsec and npub I'm using here on Primal / Damus. Below that is an "Import secret key" option. I tried using that and pasting the nsec I'm using here, but it says:
"Something went wrong
Method Not Allowed"
Am I supposed to import the nsec / npub I use here on Primal / Damus or is this a separate thing? I have nip-05 for the npub I'm using here, but I see that my RiddleStyx@coinos.io also has a .well-known/nostr.json?name=RiddleStyx that shows the hex of the npub currently showing in the Nostr integrations area.
I'm just a little confused about what I'm supposed to be using / doing here. The "Support" link just goes to a contact form and the "Documentation" link shows API documentation but doesn't explain how things work.
Any help? Thanks!
Discussion
Oh, ok, thanks nostr:npub1h2qfjpnxau9k7ja9qkf50043xfpfy8j5v60xsqryef64y44puwnq28w8ch! So that's not working correctly just yet or are you saying I should be able to do that now? Also, am I able to put in my existing pub key somewhere so my .well-known/nostr.json?name= entry shows the hex of my existing Nostr npub that I use here on Primal and Damus? I would like to use coinos as my nip-05 verification provider if I can put my same key that I'm using here as the entry. I'm excited about what you guys are building!