and then we can maybe talk about retrieving my balance that has disappeared!

When someone give us their lightning address, I realized it is likely we will send sats to that same person again. Let's store the lightning addresses that we have sent money to by default in a contact list. With option to remove them in case we need to. But it would be nice to have a recurrent sender's contact list. This adds another social layer to the app. Having our friends on the list makes us feel more at home when we see them as contacts of our wallet.

I created a lightning address for a sub-wallet. I would like to transfer it to full Alby Account. For that I need to delete it first.

Many jurisdiction impose tax rules based on capital gains. The tax is based on the difference between the acquisition and sale price.
Tracking the acquisition and sale price in Alby Hub would be very useful.
Or a some guidance to create exports and importing it into a spread sheet.

We should be able to toggle off our total balance

You can set a fee when sending via on-chain or withdrawing on-chain funds, but if there is a fee spike and your transaction is time-critical you should be able to have a way to bump the transaction.

I prefer not to switch between apps and wallets all the time: I’d like to manage everything from my Alby Hub & Alby Go.

For on-chain funds going to an offline wallet, I’d like the option to add an xpub for view-only balances and address generation into the Hub. That way I can create new on-chain addresses without having the use the online Hub’s seed. 🔒

This should be something very different than the current onchain balance, it should be a piggy bank section or "your safe offline storage" section, hidden somewhere to avoid confusion and let only advanced users use this.

This does add complexity, but it improves usability and security for advanced users. It shouldn’t be easily accesible or enabled by default, and the flow should be clearly documented, what an xpub is, why you’d use it, so non-advanced users can follow along. 📖🧠.

This safe offline storage can also work for having referal links to exchanges that let you buy bitcoin directly to your onchain offline wallet for exactly safe storage. So it has the potential to help users that are already doing this, but also to assists new users interested on safe offline storage to be able to just view everything from the hub and not having to learn anything else somewhere else. There is also reveneu oportunity on very small comissions for linking bitcoin sellers with those users.

Thanks for considering it.

Lets users instantly check for Address Swaps

Could be nice to see how payments went (through which channels) and where they incurred how much fees and how much was the fee in total.

As a user I might have bought several channels. With the current invoice (Alby - invoice: ALB-5498-xxxx-001 (Lightning Channel)), I don't know for which channel exactly I was billed.

When pressing the red close button, a helpful warning appears that the app needs to keep running for Lightning payments to work.

This is important and good.

Current behavior:
The app can only be minimized to keep running in the background. When minimized, a second window appears on the far right of the Mac Dock (as an additional Alby Hub window). This behavior is disruptive.

My wish is to truly close the app via the red close button. At the same time, I want Swift Quit (Application to handle windows in iOS) to prevent the app from fully terminating, allowing it to continue running in the background—without the annoying additional Dock window.

Problem:
The warning about quitting always shows and cannot be disabled. This interrupts and disturbs the workflow because I actually want to close the app, but effectively it can only be minimized, causing an extra window in the Dock which stays there for ever.

Suggestion:
Please add an option in the Alby Hub settings to disable the quit warning.

This way, when I close the app using the red button, it truly closes, and Swift Quit ensures it continues running in the background—without an extra Dock window always open.

This would enable a clean iOS workflow that allows background operation without disruptive Dock additional App windows.

Would be nice to have an option to have a log in screen with plain albyhub branding rather than the shadowy figures with the quotes about bitcoin.

It has a very "tin foil hat" feel to it and I think it would put a lot of people off Albyhub. I Certainly cringe pretty hard every time I have to unlock my wallet.

A watchtower service, part of the Pro plan to monitor node channels if offline

Since recommended channel sizes at usually 1M sats or more, and multiple channels are needed. Users are expected to be holding non-trivial balances on Alby Hub.

Also the Hub account controls user's nodes.

Thus, Alby Hub should allow users to add 2FA through authenticator apps as a additional security measure.

Channels close because some have a fixed duration or because of low activity. A warning before the channel closes would be useful. Especially if there is a chance to keep it open if payment activity increases.

I came across this Github issue: https://github.com/getAlby/hub/issues/1504 and would like to add this as a feature request here.

The Problem:
Receiving on Lightning is not very private, since all invoices by default include your nodeid. It has been common practice in all LN node implementations (LND, CLN, eclair) to assign a fixed nodeId, which makes it easy to fingerprint you and is bad for privacy.

However, this is not technically necessary. If you are not a routing node (i.e. only have private channel), there is absolutely no need to have a fixed nodeid - it can be randomized each time you generate an invoice (you just have to include route hints in the invoice then).

The Solution:
[Technical details in the linked Github Issue]

tl;dr : generate a random nodeid for each invoice, and add a routing hint - for AlbyHubs using the embedded LDK node with private channels only.

Fyi, This was done already years ago by Simple Bitcoin Wallet and is maintained to this day in its fork. It's a proven technique.

Implementation:
Could be done via optional toggle, experimental settings for the beginning. Once stable, rolled out for GA.

Can we get this in Alby Hub??
This would be a massive upgrade for Lightning privacy!! 🙏

Create a UI that only shows all sending and receiving failures with some information to why so that they can be addressed. Same for any errors when creating invoices for payers. The goal is to get those to zero.

Regarding LDKs long Bolt12 offering strings

Could we make it optional to have blinded paths when using LDK? For example, make the user decide if we would like to have a shorter string, without blinded paths

The problem I'm currently facing is that when I try to sign the message with my Coldcard Q which has a limit on how long the mesage can be, 240 characters. This tells me that the BOLT12-string Alby Hub produces is much longer (more than 240 characters) than the BOLT12-string that Core Lightning produces which makes me not able to use Alby Hub.

Is it possible to get Alby Hub to produce a shorter string so users with a Coldcard Q can sign the message, thus be able to receive Ocean payouts.

Core Lightning Bolt12-string:
"lno1pg7y7s69g98zq5rp09hh2arnypnx7u3qvf3nzutdds682enyvekkcer5dccrswfnx4nhx6rhwp6xu6rhdeunxetjddcrsvnyvdjpvggzc3m2qq87346z6uu4yw3kxk6qt6dvg2mm06vysage7tuh3fe3uers"

Alby Hub Bolt12-string:
"lno1pg7y7s69g98zq5rp09hh2arnypnx7u3qvf3nzutdds682enyvekkcer5dccrswfnx4nhx6rhwp6xu6rhdeunxetjddcrsvnyvdjpp6qr3209v5fwexx69dtcjasl0tu09q96lx9qj2prvrxklufcrd0g3xls9nngzj0vjn64gdmn0qe8h8f7yn3ga9u89mrhw4ym73tjm6zyxk2jqgp95n04qq28xnea6mxem8hs60ef7k0xqls7e3rgr6udsphm3yfu9zsqxw0ryg5wr3nkval9cqsm9l363y86vu7ksfafmj0lgl0lmwjppd0rzgt0q5u2jm7hvzr7w3yl3z629ycfzc4q9t8l6txsz5glk7kv3dyqk846vrpc68ktmkmf50h4884jpgm0f8p3qqk8z20pgtns0r3c63xwn7ngx3dn04v3t5q06thk70mgpfhg6c38qe634j0qr2rh4d0cdz5dl5tzzqeuagfktk504rg4a23ltqw96cfeluuxw48s86zwpxmcplx6dh2kqv"

The BOLT12 offer string is longer because it includes paths . These are blinded paths used for recipient privacy. LDK (the integrated node in Alby Hub) uses these by default.

In the self-hosting/Docker world, it’s common to offer a toggle to disable update notifications.
Some operators prefer to check updates on their own schedule (via GitHub, Docker tags, etc.), especially in locked-down or critical environments.

When swapping from on-chain to lightning, a QR Code, as well the amount and "Copy" show up.

Would be good if the address was also displayed for extra verification.

It would be really helpful to have a way to see past balances, maybe daily or weekly snapshots.

It would be nice if the mempool instance used to refer to on-chain channel related transactions was configurable. I run my own LND based node, with my own instance of the mempool explorer. I would prefer to be able to open channel on-chain transactions in my own explorer for privacy reasons. At the moment, I have to copy the link, and then copy the transaction id from that link to enter into my own explorer.

Currently I can migrate my Hub using a migration file. That works great, but requires to select Alby Cloud on getalby.com/subscription/new and then upload the file during the setup process.
I would like to upgrade with one click by selecting Alby Cloud within my current self-hosted Hub.

Hey Alby team!

First of all, I just want to say I’m a big fan of what you’re building — congrats on such a great product!

I’ve been using Alby Hub as a vault account to receive Lightning deposits via LNURL on wapupay.com (I am the founder), and it’s been working really well. That said, I wanted to share a small suggestion that I think could make a big difference for users like me.

Feature idea:
It would be awesome if sub-account users could receive and withdraw funds from their wallet without needing the Alby Hub admin to intervene.

Why this matters:
I’d love to recommend Alby Go/Zeus to my family and friends as their first Bitcoin wallet. One of the things I value is being able to help them recover access if they mess something up. But there are a couple of common use cases that are tricky right now:

Most people buy bitcoin through an exchange because it supports fiat, but many exchanges only allow on-chain withdrawals.

As they start stacking more sats, they’ll want to withdraw to a hardware wallet eventually.

I know there are third-party services that can help, but that adds friction. For beginners, it would be amazing to offer an all-in-one Bitcoin tool right from the start. Otherwise, they might end up going with custodial wallets like Wallet of Satoshi, Muun, or even staying on exchanges.

This feature would also be super helpful for business use cases. For example, if I had multiple merchants receiving Lightning payments, it’d be great if they could withdraw their funds directly, without needing me (the admin) to take action each time.

Just wanted to share this thought. Thanks again for the great work you’re doing!

Best,
Andy

To have have incoming connections (and channels) we need to be connectable in the internet, but when running at home we usually do not have a fixed IP address, and exposing our public home address is dangerous for several reasons. Having Alby Hub connectable via TOR would solve this problem. We could then increase inbound liquidity without having to pay for it, and even have a public node routing transactions.