The most recent high profile physical attack on a bitcoiner that took place in Toronto this past week has made me once again examine my physical security and my Bitcoin security. I use multi-vendor, geographically distributed multisig. If you kidnap me, you've got to bring me to at 3 different places which are open and public places. This could take over 24 hours time. It's probably not worth the risk of you getting caught in the process.
But what about kidnapping me (or worse one of my family members) and holding me/them in a secret location until someone ELSE gathers the keys? THIS seems plausible.
We need to be able to timelock our Bitcoin to prevent this type of attack. I know that timelocking is currently possible (see Liana wallet), but I believe that you have to create a new on-chain transaction to "reset" the timelock for every expiry. This isn't practical or efficient in the long term.
So my question: what type of upgrades are needed to the Bitcoin code in order to timelock a UTXO upon the signing of a new transaction? In other words, I sign a transaction for a ransom, but it doesn't send for a certain number of blocks. It is also reversible with an additional signature. And this is all verifiable before the signing even occurs to deter the transaction in the first place.
Tagging some big names to get a discussion on the topic: nostr:nprofile1qqstnem9g6aqv3tw6vqaneftcj06frns56lj9q470gdww228vysz8hqpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqg6waehxw309ahx7um5wghx7unpdenk2urfd3kzuer9wcq3wamnwvaz7tmjv4kxz7fwvd6hyun9de6zuenedyvu6425 nostr:nprofile1qqsw4v882mfjhq9u63j08kzyhqzqxqc8tgf740p4nxnk9jdv02u37ncpz4mhxue69uhhyetvv9uju6mpd4czuumfw3jsz9nhwden5te0wfjkccte9ec8y6tdv9kzumn9wsq3yamnwvaz7tmsw4e8qmr9wpskwtn9wvql3tqm nostr:nprofile1qqsg2zqd8wkhpnxu6lm5c2dyfa2mhpwte57apjae2ldp6g2mmwf3ypqpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhs50xuq8 nostr:nprofile1qqsve2jcud7fnjzmchn4gq52wx9agey9uhfukv69dy0v4wpuw4w53nqpr9mhxue69uhhyetvv9ujuumwdae8gtnnda3kjctv9uk3h9ux nostr:nprofile1qqs2auxkkgfgylem580xrztp8ek5sf83s86k0vfq2feuz6y4lkhskgcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhs4rzw8c nostr:nprofile1qqs0w2xeumnsfq6cuuynpaw2vjcfwacdnzwvmp59flnp3mdfez3czpspz4mhxue69uhhyetvv9ujuerpd46hxtnfduhspu30gj nostr:nprofile1qqsw3znfr6vdnxrujezjrhlkqqjlvpcqx79ys7gcph9mkjjsy7zsgygpr9mhxue69uhhqatjv9mxjerp9ehx7um5wghxcctwvsq3samnwvaz7tmjv4kxz7fwdehhxarjd93kztnrdaksz9thwden5te0wfjkccte9ekk7um5wgh8qatz7tvu4p nostr:nprofile1qqs9pk20ctv9srrg9vr354p03v0rrgsqkpggh2u45va77zz4mu5p6ccpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9thwden5te0dehhxarj9ehhsarj9ejx2a30qyg8wumn8ghj7mn0wd68ytnddakj7xph5zr nostr:nprofile1qqsdv8emcke7k3qqaldwv956tstu40ejg663gdsaayuuujs6pknw7jspp4mhxue69uhkummn9ekx7mqpr3mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmqpzfmhxue69uhhqatjwpkx2urpvuhx2uc86mqq0 nostr:nprofile1qqsqfjg4mth7uwp307nng3z2em3ep2pxnljczzezg8j7dhf58ha7ejgpz4mhxue69uhkummnw3ex2mrfw3jhxtn0wfnszynhwden5te0wahhgtn4w3ux7tn0dejszxthwden5te0wdjkuerfwshxummnvekxzun99e3k7mgrcp7e2 nostr:nprofile1qqs8fl79rnpsz5x00xmvkvtd8g2u7ve2k2dr3lkfadyy4v24r4k3s4sppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qg4waehxw309aex2mrp0yhxummnw3ezucn89ur9eu8h nostr:nprofile1qqsxu35yyt0mwjjh8pcz4zprhxegz69t4wr9t74vk6zne58wzh0waycpz9mhxue69uhkummnw3ezuamfdejj7qg4waehxw309ahx7um5wghx77r5wghxgetk9uq3samnwvaz7tmxd9k8getj9ehx7um5wgh8w6twv5hsj7hdd2
Oddbean new post about login | logout