Hello! Until now I've been using a trezor one. Great device, but the fact that every time I write the passphrase I expose it to keylogs in my computer bothers me. So, I bought a coldcard q and want to share with you my planed set up.
Physical attacks worries me. I don't have much or am public exposed, so the chances of happening are low. However is the only way I see I could lose my funds. I've read a lot about "decoy wallets" but in my opinion they are not useful. Any informed thief would know that simple trick, and he would hit you with his wrench until you open the "true" wallet. I think the only way to prevent or mitigate a physical attacks is to be totally unable to access your funds.
My first thought was to set up a coldcard cosign (CCC) multifirm with a spending policy. In this case, you use one device with two keys to send transactions below a determined amount. In case you need to override that, you'll need a second device with a third key. I could have the first device in my house and second one in a separate location, several hours by car. I think this is a very nice system, but it can be a little difficult to set and operate.
Other option would be to set a spending policy using only one Coldcard device. In that case, if you want to override the policy, you need to enter a PIN. I could store the PIN in that separate location and have a system very similar to the previous one, without the multifirm multidevice things. The only drawback I see is that the thief might think you actually know that pin, and could hit you with his wrench until you enter it.
What do you think, fellow bitcoiners? Thanks in advance.
[link] [comments]
You can get bonuses upto $100 FREE BONUS when you:
π° Install these recommended apps:
π² SocialGood - 100% Crypto Back on Everyday Shopping
π² xPortal - The DeFi For The Next Billion
π² CryptoTab Browser - Lightweight, fast, and ready to mine!
π° Register on these recommended exchanges:
π‘ Binanceπ‘ Bitfinexπ‘ Bitmartπ‘ Bittrexπ‘ Bitget
π‘ CoinExπ‘ Crypto.comπ‘ Gate.ioπ‘ Huobiπ‘ Kucoin.
Comments