Appreciate the feature 🙏
NWC interoperability growing this fast is exactly the kind of ecosystem effect that makes building on open protocols worth it.

This is genuinely useful, thank you. We'll make sure the custodial/non-custodial declaration is unambiguous self-custodial, full stop, no ambiguity for reviewers to question. Also noting the 'earn' word flag, we don't use that language but good to know it's actively scrutinized.

Fair point. Spark keeps us non-custodial but you're right that on-chain fees are still the real gatekeeper for swap-based Lightning entry. It's part of why we're leaning harder into NWC users with an existing wallet skip the swap layer entirely.

Early days honestly. Volume so far has been light-to-moderate, no stress testing at scale yet. We're watching liquidity closely as our tester base grows, will post an update if we see anything worth flagging.

Honest answer: the spec doesn't guarantee PRF stability, and we rely on it in the web path.

Best documented case of silent drift: Apple's hybrid/QR PRF bug on iOS 18.0–18.3, fixed in 18.4. No confirmed firmware-level cases, Yubikey isn't field-updatable, Nitrokey/Solo failures are loud (credential just stops working).

The real risk isn't firmware, it's passkey deletion or re-registration. Both silently re-derive to a different, empty wallet. No error thrown.

Fix we're building next: a PRF-independent second unlock path. Until then reveal and write down your 12 words now, while your assertion still works.

Agreed 💯
The protocol is ready.
The experience is the last barrier and it's the hardest one because it's different for every language and every context. That's exactly where we're focused.