Something erased my entire profile, my pictures and addresses and dang.

I live with three adult women. They're actually all of them accomplished cooks. And I would say that at any time, which is entirely unpredictable, one and a half of them are passionate about cooking, and the other half of them hates it. But I don't really like to cook myself, and I am 25% of the family. So that is how our fractions are going to look throughout the rest of this post. When I do cook, it's kind of hit or miss. There's some things that I make that are magnificent. My hamburger rice is amazing. My hamburger salad is also pretty good. I make a decent lasagna, everything down then I'll throw a bunch of stuff into an instant pot and be like, damn, I know what I'm doing. But they're all busy tonight, so I'm doing some brown food. and brown beverage.

#bitcoin #hodl #coldstorage I am an artist by nature, but I was in IT for a minute or two, and I learned the value of something IT calls a "disaster recovery drill." Every now and then. I carefully put myself in a situation where I have to rebuild my entire cold storage architecture from the ground up. Of course, the first step of this is always to make sure that it is truly a simulation, and I'm not endangering any of my aspects of retrieval. In short, what I do is I'll install a fresh copy of some Linux distribution on an old laptop, "yay - Sy sparrow-wallet" (or whatever package manager goes with whichever distribution I chose), get my physical private keys (or better yet, only two of them as I should have access to my Xpubs, more closely and locally). I like to do this with a hardware signer that can handle ephemeral or stateless keys. I've used a #seedsigner, a #jade, and most recently a #coldcard, which can all work this way. Then I get as much information into Sparrow as I can to make sure that I can recreate a wallet and see all my UTXOs. Finally, I create a transaction, sign it with two of my keys, and sometimes I might broadcast it, but usually I just stop there. Here's the cool thing, though. Every time I do this, I run into some snag. I had a digital backup of part of my information and found out that the file had become corrupted once... that was sobering. And I've also found that over time, both my understanding of best practices and the state of hardware and software lead me to where I can refine my methods. Perhaps even find ways to make them safer and more redundant without adding more risk. And finally I take a moment to tell my loved ones what I've done so they have a slightly better understanding of how all this works. I still have quite a bit of work to do there though. I just wanted to share because I really think this should be a ritual for everyone who holds their own keys. Be careful. Triple check. Don't shoot yourself in the foot. 😁🙏🫎

My text should have read tail emission. But you've got to love Groks aswer eh @Peter Todd? 😁