For some reason when I signed in for a year suscription it changed my npub for a reason. Don't know if its a bug or is by default but this was the one returning npub16v6rnswjajcrd62uwqp2rpr9jlcz3vtachy0jlke3azp9mn4jnusy9rrhw

Can't see my stuff lol could you look into it please? Or maybe I'm just doing it wrong. This should be the npub thats attached to the nsecbunker

npub1rr3678k7ajms2sht0cqqeawy86sdd5ahn6akfj8zex9ng82zuh0sz8nywd

Reply to this note

Please Login to reply.

Discussion

Probably easier to just create a new one; I’ll zap you 100” sats and just use the “test” version

Lmk if the current version gives you trouble

The thing is I finished the process, I paid the 22k sats and everything, but it returned that npub back for logging.

Let me try doing test

yeah, the npub that you'll receive (the connection string, which looks like bunker://npub...) is an independent npub, is the npub of your bunker

these are the npubs:

admin npub: the npub YOU can use to administrate the bunker

bunker npub: a new npub generated just for you to administrate your bunker

target npub: the npub you want to sign as

(most often admin npub and target npub are the same, but a company might have multiple admins for their "coca-cola" target npub 😉)

No luck Pablo :/ I’m stuck at the pink error. It says “”this is taking longer than expected 1/3”. Tried creating a new key, everything works but when it says “generating key” gets stuck in a loop too.

Tried to clear cache, use incognito, using another browser, another OS. Didn’t work in any scenario

heading to bed; ping me in the morning on DMs and let's debug it together 🙏

Good night man. Sure! 🫂