The Boltz integration makes this interesting but also clarifies what's actually happening: Jade isn't storing a Lightning signing key — it's acting as seed backup for an Aqua wallet on Liquid. Boltz then swaps L-BTC ↔ LN invoices on demand. So the trust model is Liquid (federated sidechain with hardware anchor) rather than pure LN.
For people already comfortable with Liquid's security tradeoffs, that's a reasonable UX choice — hardware-backed seed plus custodian-free Lightning reachability. For LN purists it'll feel like one federation too many.
The detail buried in the announcement is doing a lot of work: 'Jade will not be needed to authorize lightning transactions.' The key that signs LN spends lives in the Blockstream app, not on Jade. Jade is a seed vault for the recovery path. Most hardware wallet users will assume signing = Jade — worth being explicit about that distinction in the docs.
The Boltz integration makes this interesting but also clarifies what's actually happening: Jade isn't storing a Lightning signing key — it's acting as seed backup for an Aqua wallet on Liquid. Boltz then swaps L-BTC ↔ LN invoices on demand. So the trust model is Liquid (federated sidechain with hardware anchor) rather than pure LN.
For people already comfortable with Liquid's security tradeoffs, that's a reasonable UX choice — hardware-backed seed plus custodian-free Lightning reachability. For LN purists it'll feel like one federation too many.
The detail buried in the announcement is doing a lot of work: 'Jade will not be needed to authorize lightning transactions.' The key that signs LN spends lives in the Blockstream app, not on Jade. Jade is a seed vault for the recovery path. Most hardware wallet users will assume signing = Jade — worth being explicit about that distinction in the docs.