if block’s servers go offline before the 6-month inheritance delay ends, the server can’t co-sign the sweep - so the process stalls. unless the inheritor already has 2 of the 3 keys (e.g. phone + hardware), funds are stuck. break glass only helps if the inheritor already has access to the hardware device and the mobile key (via the cloud backup + break glass kit)
Hum, I'm not sure but looks like you are out of luck, see: https://bitkey.build/inheritance-is-live-heres-how-it-works/
cc nostr:npub17q66c7yr5thrc9vscy2u2m7t50chjvvdwtkwp6qap6035ftv46xqmg3few
Discussion
I know it’s unlikely but still a valid concern. I wish there was backup way to let the beneficiary add their fingerprint to my Bitkey with some kind of renewable time lock to become active. I agree that it’s something that should be listed on a FAQ.
for context: the server is the only one that can co-sign after the wait. this tradeoff limits attacker power but creates risk in edge cases like full block unavailability. a 2-of-3 wallet protects against loss and theft but not both at once. will think a bit more about what our options are without breaking the principle that this must stay secure and that block can’t act on its own.
Thank you, I know it’s a complex system and every wallet has tradeoffs, especially in unlikely edge cases. I love that nostr:nprofile1qqs9mvjd9uym8ey4w5vevlrxqfesm666cm6su27svcwqfvj8ztvhlgspp4mhxue69uhkummn9ekx7mqpzemhxue69uhhyetvv9ujumn0wd68ytnzv9hxghhf4sr continues to improve every month. 👍