Topic: The Lightning Network FAQ - page 5. (Read 33783 times)

core lightning v23.08 release candidate 1 has now been announced and it is now time to test new and experimental features before release, such as these:

• taproot address support for core lightning
• introduction of renepay
• splice funds in or out of a live channel

https://community.corelightning.org/c/general-questions/version-23-08-release-candidate-1-tagged
 

Picture this: in a Phoenix (also Breez) scenario, providers have to rebalance the channel that connects users to their hub, for every single user, if needed.

I see. But Blixt, Phoenix and Muun also have such default hubs for all their users. Nevertheless, routing is much worse for these wallets (comparing with LNBits, for example).

Quite obvious. Large lightning nodes which are the default hubs for custodial wallets have respectable part of the network's funds.

When it did exist, yes, but isn't BlueWallet's hub shut down?

Simoultaneously, custodial wallets have no problems with routing.

Using Lightning through BlueWallet does not have "remarkably low fees". It was known that it had hidden fees for each LN transaction that would sometimes cost the user high fees than the average, depending on demand and transaction size.

In my venture to explore the Lightning Network (LN), I opted for the seamless experience provided by BlueWallet. The transactions conducted were solely in BTC, amounting to a mere USD $0.1. The swiftness of these transactions was remarkable, accompanied by remarkably low fees. However, I find myself more inclined towards Bitcoin (segwit) due to familiarity.

For LN, it may be suitable for facilitating sales and purchases at various stores while also introducing the original Bitcoin, highlighting how it is perceived, what is observed, and so forth. As of now, there are no plans to uninstall the game here.

a new version of the blixt wallet has now been released. the new 0.6.8 version includes some fixes as well as the new feature called speedloader
the complete changelog and the download files can be found at the github link below the quote:

https://github.com/hsjoberg/blixt-wallet/releases/tag/v0.6.8

OP, probably good to remove BlueWallet and add Mutiny.

What is Mutiny? It's the first self-custodial lightning wallet that runs on the web! Control your funds on an open standard that does not depend on Apple or Google app stores. No downloads are needed!

We've set out to solve the onboarding problem for Bitcoin no matter who you are, where you live, or what device you are using. And because funds are fully in your control, there's no need to provide identity to a regulated institution. This is what it looks like to make Bitcoin accessible to the 5 billion global internet users with access to a web browser.

https://blog.mutinywallet.com/mutiny-wallet-open-beta/

It says that Blink is unavailable some countries app stores, including the US  
I like that they are supporting Stablesats, USD equivalent that is much better way of holding some kind of stablecoins but without having to deal with shitcoins.
So far I didn't try it but I might give it a go to see how it works, but if I understand correctly this is custodial LN wallet.

Speedloader syncs the wallet's channel database ("channel graph") on startup. This is important for payment pathfinding and will make sure you have an up-to-date database.

I would recommend Blink (formerly BItcoinBeachWallet) available for ios and android and app gallery  https://www.blink.sv/

I haven't, but from the GitHub description it looks basically identical to the rebalance plugin. You still need to manually specify input and output channels, for instance.
What's the benefit over rebalance?

rebalance.go:57 Run: ===================== ATTEMPT 1 =====================
 40516 2023-06-14T05:58:43.347Z DEBUG   plugin-circular: params.go:48 validateLiquidityParameters: validating liquidity parameters
 40517 2023-06-14T05:58:43.348Z DEBUG   plugin-circular: params.go:50 validateLiquidityParameters: refreshing in and out channels
 40518 2023-06-14T05:58:43.348Z DEBUG   plugin-circular: params.go:75 validateLiquidityParameters: liquidity parameters validated
 40519 2023-06-14T05:58:43.349Z DEBUG   plugin-circular: route.go:41 tryRoute: generating route
 40520 2023-06-14T05:58:43.354Z DEBUG   plugin-circular: route.go:19 getRoute: looking for a route from Boltz to SCP-096
 40521 2023-06-14T05:58:43.403Z DEBUG   plugin-circular: time.go:10 TimeTrack: rebalance.getRoute took 64.837ms
 40522 2023-06-14T05:58:43.407Z DEBUG   plugin-circular: route.go:53 tryRoute: Route from: Boltz to: SCP-096
 40523 2023-06-14T05:58:43.407Z DEBUG   plugin-circular: Amount: 300000
 40524 2023-06-14T05:58:43.408Z DEBUG   plugin-circular: Fee: 2267msat
 40525 2023-06-14T05:58:43.408Z DEBUG   plugin-circular: Fee PPM: 7
 40526 2023-06-14T05:58:43.408Z DEBUG   plugin-circular: Hops: 4
 40527 2023-06-14T05:58:43.408Z DEBUG   plugin-circular: Hop  1:                           Crypt04n4rkMoV, fee:    0.000, ppm:     0, scid: 778301x567x0, delay: 408
 40528 2023-06-14T05:58:43.408Z DEBUG   plugin-circular: Hop  2:                                    Boltz, fee:    0.301, ppm:     1, scid: 748535x568x1, delay: 328
 40529 2023-06-14T05:58:43.409Z DEBUG   plugin-circular: Hop  3:                         marburg.ddns.net, fee:    0.166, ppm:     0, scid: 774975x2457x1, delay: 288
 40530 2023-06-14T05:58:43.409Z DEBUG   plugin-circular: Hop  4:                                  SCP-096, fee:    1.800, ppm:     6, scid: 711640x1428x1, delay: 144

Anyone using the plugin called Circular to rebalance channels in Core Lightning v23.0.5??? I think it might be broken after the API changes in Core Lightning.
Wanted to know if anyone can still use this plugin.

    Fixed crash (memory corruption!) in listtransactions (openingd: work harder to intuit OPT_SCID_ALIAS. #6304)
    Don't crash on gossip store deletion fail (gossipd: don't fail on gossip deletion #6297)
    Fix incompatibility with LND which prevented us opening private channels (openingd: work harder to intuit OPT_SCID_ALIAS. #6304)
    Fixed crash in dual-funding. (CI: restore dual-funding tests. #6273)