TordlWalletProtocols VS bip-efficient-bitcoin-vaults

I really recommend you read a well designed guide for storing bitcoin like The Tordl Wallet Protocols. It gives very helpful guideance on how and why store your bitcoin in certain ways.

I highly recommend you follow a guide like The Tordl Wallet Protocols which are holistic guides to storing your bitcoin. They include guidance on inheritance that will make it so your wife can access your bitcoin - in the worst case scenario with help she is informed to be careful about.

Coldcard works great. Tho I'm pretty disappointed coldcard renegged on having its firmware open source. I might recommend that if you have multiple types of hardware wallets, you might want to consider a multisig wallet that incorporates your ledger and your coldcard. The Tordl Wallet Protocols have holistic guides on how to do that. A ledger+coldcard multisig wallet is far far more secure than a single-sig wallet of any kind.

While you're thinking about ways to level up, you might be interested in reading through some of The Tordl Wallet Protocols, a holistic set of guides for how to securely store your bitcoin. Its got info in there about multisig bitcoin storage, inheritance, and other nice info. Coldcard is nice, but if you really want to elminate all single points of failure, you need to go multisig. If you have more than $5000 in bitcoin, I'd recommend thinking about it.

Muun doesn't seem to have very clear documentation, but it definitely supports Trezor at least. I'd definitely recommend you upgrade your security using a hardware wallet. The Tordl Wallet Protocols are a good resource for that.

First of all, yes, the largest thing you didn't mention is legal transfer of your Bitcoin. I'm many jurisdictions, a holographic will is probably your easiest solution to this (tho not all jurisdictions recognize them, so check). I'd recommend reading the inheritance guidance in the Tordl Wallet Protocols.

You should first study methods that security experts have developed and published. A good resource for everyone is the Tordl wallet protocols: https://github.com/fresheneesz/TordlWalletProtocols

Definitely record where you've put any wallet information where your heirs can access it. Definitely use a metal plate for your seed. Its pretty cheap generally too (eg the blockplate or steelwallet)

You could also go full self-custody by following a guide like The Tordl Wallet Protocols.

I like electrum on desktop (lots of nice featuers and battletested) and Phoenix as a mobile lightning wallet. If you're trying to figure out a good way to self-custody I'd recommend checking out The Tordl Wallet Protocols - holistic guides to how to self-custody your bitcoin.

If you really want to up your security game, I would take a look at The Tordl Wallet Protocols which are holistic guides on how to properly store your bitcoin. It includes info on hardware wallets, backups, inheritance, multisig, and a lot more.

I have the proposal for this opcode up here: https://github.com/fresheneesz/bip-efficient-bitcoin-vaults/blob/main/cd/bip-constraindestination.md. I'd love to hear what people think about it, what problems it might have that I've missed, or other issues or suggestions surrounding this. I'd also appreciate any input that would help me improve the presentation of the opcode.

I guess if pressed, I'd have to define a smart contract as a Bitcoin script involving more than one person. Lightning is one. Another one I'm looking forward to is wallet vaults where you have a third party controlling one key in a multisig like address. The third party can help you recover if you lose all your keys, but can't steal from you (unless, again, you lose all your keys). Also, I created a proposal for a wallet vault where in one transaction you could send money to someone else directly from your wallet vault while still having buffer time to reverse the transaction in the case it was a mistake or theft attempt. If those kinds of things count as smart contracts, they're pretty interesting to me because they could make self custody far easier and more secure.

Who pays the escrow with credit cards? Merchants do. But escrow is basically costless on transactions where they don't have to intervene. You could construct a smart contract that automatically releases money to the recipient after a time lock (eg using this hypothetical opcode), and the escrow only needs to be paid if their intervention is asked for. Who would pay the fee? It's a service for the payer, so the payer should pay that fee. Payers would happily pay a little bit to get their money back i think.

To get wallet vaults, we need covenants. OP_CHECKTEMPLATEVERIFY can do that. However there are limitations. But the benefits are significant enough to make the limitations acceptable. I think we can do better tho, which is why I'm working on this. ​

If you're interested in op_ctv, you might be interested in a sneak preview of a bip draft I wrote.