Hi nostr:nprofile1qqsgeksa4tajm7x673gq2v7t56dkgkh6pjhhzdhrgxlpke4za8jmmkqpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqgjwaehxw309ac82unsd3jhqct89ejhxqgkwaehxw309aex2mrp0yhxummnw3ezucnpdejqetk0p4 I'm trying Bitkit and I like it too much, really a good sovreign lightning experience. I have some question I cant find answers in docs:

- Is a sort of "channel rebalamcing feature" planned? Cause open channels with multiple LSPs become very tedious if then I cant receive/pay specifically to/from a particular channel.

- Does Bitkit implement an automated full punishment system to react if our LSP is trying to cheat on us? Is, practically, all automatic, tested and secure to use?

- Are backups encrypted with our seed, like in phoenix wallet? In the docs its stated that "backup material is not sensible data", but it is: old channel states can be broadcasted and used to steal funds to users. It all should be encrypted, I think.

- Is the "automated channel created with Blocktank when we receive to lightning without enough inbound liquidity" trustless? Or do we need to trust blocktank until confirmation?

Is the channel creation started with user-onchian-funds trustless?

- Are bolt-12 and splicing support planned?

Thanks!

Reply to this note

Please Login to reply.

Discussion

ah also was forgetting, is the backup include all channels, even the ones that are not enstablished with blocktank? And its the wallet able to recover these channel in case of device migration with recovery? And the channels stay open or it recovers and closes them?

also last thing, a feature I miss is the possibility to close a channel directly to an external address... is it planned? Thanks a lot!

Hey, thanks for using Bitkit and for all the questions!

1. Not any time soon. We have discussed ways we could do it, but doing such things is tricky and we have lower hanging fruit.

2. The LDK node does enforce, but only while the app is open, so you need to be using it weekly to have a realistic chance of enforcing.

3. The wallet and channel state is encrypted on the client using the seed. We use AES/GCM which is pretty standard on mobile these days.

4. It’s trust-minimized. The invoice is a HODL invoice which is not claimed until the channel is opened.

5. No plans for BOLT-12, I believe changing payment protocols is disruptive and that it isn't a significant-enough change; we will reconsider if industry organically moves to it. We would love to support splicing, but LDK (Bitkit) and LND (Blocktank) still don't support it.

6. Yes, the backups include all channels, and should restore them in a new Bitkit wallet. However, you need to be very careful not to install the node on two live devices at the same time or it may corrupt the state. It should be noted that we cannot control what third-parties do, so it is possible that a migration could also result in some channel closures.

7. No plans to customize destination addresses for channel closures, but if it becomes something many users want we could revisit the idea.

thanks a lot for your answers! I'm really in love with Bitkit and appreciate the way its build, pretty totally agnostic respect to the LSP and first-party services, without sacrificing UX. Thats the way bitcoin software should be built to maximize user sovreignity. Kudos!!!