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.