Oddbean

I cannot recommend any one. Each one have its own use case and is nice that Alby is offering these various options for backend funding. LND - I would run it in neutrino mode (no need for full bitcoin core) so it can run on a simple linux machine with Alby Hub. This is more stable as a node and you have more options to expand. LDK - I would run it with own Esplora server. The default setup is going to use Blockstream public Esplora server, and is quite slow and heavy used (it could cause sync issues for your LDK node). That means you would need to do additional steps to install Alby Hub. PhoenixD - the simplest and quickest one, no need for channel management, can run very easily on any linux machine. The only downsize is that you are charged the Acinq fees and you are in a walled garden of liquidity with unique LSP. But for some nostrr zaps is just fine. Ecash - simplest, fast, custodial, no option (yet) to backup tokens. If you need a quick disposable Alby Hub setup, this is a nice solution. Greenlight - you need an API invitation code BreezSDK - you need also a API invitation code

Default and the most simple one to use is LDK. (Alby runs an optimized Esplora server so it's not depending on blockstream's public server) Out of the box everything should just work If you already have an Umbrel, Start9, RaspiBlitz, or some LND setup then LND is a good option. You need to take care of your LND node then PhoenixD has the advantage to use Acinq's LSP the rest I would not recommend much at this point actually. Ecash is fun.

Thanks, I managed to set everything up automatically, I also updated Alby Hub to version 1.8.0 Instead, for the opening of the channel I asked for help from nostr:nprofile1qqs0h7ec2h2scduxdtcqfp9xgangpts79lcye6uamzfkge0hp5u32zcpp4mhxue69uhhjctzw5hx6egpp4mhxue69uhkummn9ekx7mqpz3mhxue69uhhyetvv9ujuerpd46hxtnfdu46puj5 who was really kind 🙏

oh thanks. that needs to be updated: https://github.com/getAlby/hub/blob/63cd230159c26ee5bad00d538fb29241cdd8bb5a/config/models.go#L28 we run this and also have some optimizations in there, e.g. for fee estimates to mitigate unexpected channel closure potential. we also try to use internal tools where possible that users by default only (if not chosen otherwise) interact with us.