🚨 There’s another concern worth discussing following PHP2Shell and the recent security disclosures. What happens when a bitcoin wallet provider holds one of your signing or recovery keys, and its internet-facing infrastructure is compromised? @Bitkey @CasaHODL @AnchorWatch @unchainedcom @nunchuk_io We understand that a provider-held key alone generally cannot move funds in these multisig setups. But suppose an attacker compromises the web/API infrastructure without obtaining the private key itself. Could they manipulate signing requests, trigger unauthorized co-signatures, bypass spending policies or abuse recovery workflows? What independent safeguards prevent this? And which guarantees remain intact if the backend itself can’t be trusted? We’re not suggesting any of these services have been affected by PHP2Shell. We’d genuinely appreciate some technical clarity on these trust boundaries. Keeper offers optional server-assisted signing too, so these are questions we need to keep asking ourselves. The more of this we can independently verify, the better.