It seems quite some people don't know about the multi-account features. Do you have any ideas on how to improve this in the extension?
Is it possible that you forgot to to import your existing nostr keys to the extension?
If you want to use a different Alby account you would need to login to the account you want to connect on getalby.com first, and then connect the extension. (we have some improvements coming with the next release that should make things easier for multi-account setups)
Yes, only one nsec per wallet. Do you want to use a different wallet for the other nostr identities?
Otherwise it's also fine to add the same wallet multiple times, and just use different nsecs with each account.
Seems like you clicked "Connect a Wallet".
You need to instead go to the account settings of an existing account. Hover the account you want to edit your keys for and click on the settings icon (see screenshot from before).
Does that work for you?
> but was the other 24k to open a channel?
Exactly. You seem to have paid an LSP to provide you with a channel and some inbound liquidity.
Each profile has it's own keys. You can find them in your Extension Account settings > Key Management (either import your 12 words recovery phrase or an existing nsec via Nostr Settings)
Alby Extension supports having multiple accounts. Is there a reason that doesn't work for you?
nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm I migrated to #AlbyHub a few days ago but now zapping doesn’t work anymore for me. When someone zaps me, the payment will still go through but it’s not shown on the zapping history of my post. Is there any way to fix it? Before migrating to Alby Hub, Alby works perfectly! nostr:note1ntj3mlsz0rjz8svaplyf52mysulvgt7yjwkhgfq9tet6gyn4vszszq2vex
The description of your zap invoices seem to be "LNBits". Where does that come from? Do you mind to share some details about your setup?
Exactly. First you buy inbound liquidity and thereby open your first channel, then you can transfer bitcoin to your Hub via Lightning.
An inbound channel over 250k sats currently is ~10k sats. Not sure how you conclude 180 bucks buy-in?
At what step did you get stuck?
Things look alright on our end. Has this been resolved in the meantime? 🤔
If it hasn't: Do you mind to reach out to support@getalby.com and share some details about your setup?
Paying for coffee in San Salvador with my Alby Hub node in Warsaw connected through nostr:npub19hg5pj5qmd3teumh6ld7drfz49d65sw3n3d5jud8sgz27avkq5dqm7yv9p to Alby Go mobile app https://video.nostr.build/981ee4039560b0027a1afb3b2f82430f28b0222d208e9b097c6dd7795d159340.mp4
Beautiful 😍
I see, we're looking into it. Thanks for reporting!
Did you try to login to your Alby Hub and see if there is anything wrong there?
You can change the relay for your hub via environment variable:
https://github.com/getAlby/hub?tab=readme-ov-file#optional-configuration-parameters
You can't just change the connection string manually, since the hub needs to know which relay to listen to for incoming requests.
Interesting, after Umbrel + nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm hub reboot, I had to unlink and relink my node to my wallet.
Is this a known issue Alby?
Why did you need to relink? Did you see any errors?
Can you give it a try again? We're not yet sure what it was, but for some reason things started to work again with my BTCPay instance...