I felt that this was a really good explanation of BIP110 game theory from a BIP110 supporter. He concludes it has failed, and does a very thoughtful breakdown of why he doesn't think the hard fork is right at this time. https://www.youtube.com/live/4rZoo1PJi2A

I'm broadcasting notes on mobile too much xD

#BIP110 didn't fail because of "corrupt" miners, nor did it fail due to miners "colluding" with one another. Although I do agree that miner centralization could pose a risk, I don't think that the bippers are correct in calling the miners corrupt over the failure of BIP110 to activate. The failure to activate was a due to a lack consesus among the broader node community. I'm a pleb. I'm not a cryptographer, nor am I a software developer in any way. This post is mostly just testing and articulating my understanding of the Bitcoin network. If I'm correct in my understanding of the #WhitePaper and how the #Bitcoin network operates, then the following is true: 1. Nodes provide the rules for the Bitcoin network through reaching an independent agreement (consensus) of what is and isn't allowed. They communicate these rules to the miners. 2. Miners try to brute force guess the magic number to mine the next block for the timechain. They also create templates for what information they want to put into the block. Generally being monetary transactions based on fees, but also "spam" or other inscriptions (“The Times 03/Jan/2009 Chancellor on brink of second bailout for banks” inscribed by Satoshi). Miners can also choose not to include transactions, spam, or inscriptions based on their own criteria. Which is why controlling enough hash to assure your transactions get through is important. 3. If 51% or more of the nodes are in agreement of what the rules of the network are, they have consensus. 4. A miner who tries to submit a block that violates the consensus will have that block rejected by the nodes with consensus, and therefore rejected by the Bitcoin network. If there are nodes that would otherwise accept that block, the minority nodes fork off. Or vice versa, the majority network with consensus accepts a block, while the minority nodes may reject a block, causing the minority to fork off. BIP110 forked off because they didn't have majority node consensus. They composed a minority consensus with one another rejected a block that was considered acceptable to the majority of nodes, and forked off. I don't think changing the #PoW (proof of work) of #BTC is the correct solution. For BIP110 (or any other BIP) to succeed, I think they need to: 1. Acquire majority consensus with the nodes all signaling for an upcoming rule change. 2. After acquiring consensus through signaling for the change, they need to put out a specific block height for the change to go effective, and broadcast it to as many node runners signaling for the BIP as possible. 3. After step two they should notify the miners of an upcoming consensus rule change, and warn them (miners) that blocks submissions that are not compliant with the new consensus will be rejected by the network after the specified block height. Is that all correct? #AskNostr #AskBTC

This is the exact reaction I had when I found out the Bippers want to change the proof of work for Bitcoin.

I was taught that six block confirmations of an on chain transaction solidify it.

Tick tock next block.

This Coinkite failure has seriously left my faith in hardware wallets in a shaken mess. I don't even know where to start over. Back to analysis paralysis.

I guess #Aqua is down because #Boltz is down. This is the second near miss for me. I had a small amount of Sats on Aqua to use for fun money, however I moved it on chain last week because I wasn't sure what would happen to those Sats in the event of the impending fork.

My heart is heavy for all those who lost any of their precious time and energy to the ColdCard entropy failure. It's devastating to see people talking about losing the entirety of their time and energy from the past X years - long before I found the Bitcoin space. So many pioneers that forged the path ahead and built amazing educational platforms and spaces. They provided me with all the tools necessary to enter into the Bitcoin space with such a strong conviction in the future of what Bitcoin could bring to society. This is my first Bear Market. The falling USD price hasn't really bothered me. Thanks to the amazing Bitcoin Pioneers' tales of how bad things had been in the past Bear Markets combined with the lack of changes in the fundamentals of Bitcoin. I have stayed grounded in "∞/21M" and, to paraphrase @hodl, leverage won't magically make you an OG." This current ColdCard debacle is the first time I've been extremely uncomfortable to be a part of the Bitcoin community. To preface the next part: I have zero, zip, zilch, prior experience in cryptography, coding, or other software skills. I, like many others, spent a significant time trying to educate myself on different hardware wallets before we took our Sats off an exchange. To be honest though, much of the technical jargon was lost on me. One thing did stand out to me though, ColdCard seemed to have the best (anecdotal) hardware wallet. I particularly liked the Q for it's QR scanner and full QWER keyboard. Knowing that most Sats are lost due to user error, I felt the Q provided ample tools to help verify, send, and receive Bitcoin transactions while minimizing user error. We're all told, "Don't trust. Verify." I did the best I felt I could, short of learning how to code myself to review CoinKite's code. I reviewed as much as I could on the reputation of the devices and feedback from people that had used them. For all intensive purposes, the Q felt like it would provide the best user experience for my wife or heirs if something happened to me, and give them the highest chance of success. I did not expect that I'd see ColdCard have a failure so catastrophic as to screw up the single most important part of the security, generating a secure 128bit private key. When I saw the warning go out from some of my fellow Nostriches that there was a vulnerability in the MK3 series my heart started racing. Did it go beyond the MK3? Were my wife and I affected? I started reading as much information as I could. Keeping up with every detail as more and more UTXOs were drained and more info was breaking. Then I saw it, MK4, MK5, and Q were all sub 128bits of entropy. I had accidentally exposed my wife and I, and all our future generations, to the vulnerability. To say my heart dropped into my stomach would be an understatement. I didn't know how long it would be before the hostile attackers were finished with all the MK3 wallets and started on the MK4/5/Q. I did know that I needed to update things quickly but smoothly. A problem quickly arose as I realized our security setup was so difficult to access in the event of a true emergency, like this, that I may not be able to move a single sat in time. The amount of time from the initial incident to when I was first able to even look at the public addresses of our sats took far too long. I felt more and more sick the more time passed without knowing if we'd already been rugged. When I was finally able to check our UTXOs, there was not a Sat out of place. Not yet anyways. I knew we weren't out the woods yet. Even though I'd accessed our Xpubs for the Sats, it would still take quite some time before I could gain access to our keys. The only things keeping me calm was that we had used a passphrase (that I later learned was too weak), and my wife. As soon as I had access to our private keys, I wrote out a checklist. The checklist provided myself a step-by-step guide to make sure that I did things as cleanly and orderly as possible, to minimize potential missteps in a complete migration to new keys. I rolled 100 independent dice to generate our new wallet. It took me 32hrs from the time I learned of the vulnerability to the time I was actually capable of accessing my cold storage and generating the new seeds to sweep our sats to. The only reason I managed to do it in 32hrs was that my emergency contact was able to meet me half way. Without the emergency contact, our sats would've been exposed for at least another 12hrs. I'm incredibly humbled and grateful that our sats are safe. I understand how incredibly fortunate we are to have been able to keep what small amount of Sats we've been able to stack, because it may not be a lot to most people, but it is a lot to us. I feel like I'd prepared for all the attack vectors, but I never expected that the entropy of a non-tampered with hww would be the one that got closest to compromising our sat stack. What a sobering and panick inducing experience. As a pleb without a background in cryptography or technology, I really took the generation of seed phases for granted. Never again. Rolling my own entropy, and diversifying our hww from now on. Which will be difficult, because the Q was a big purchase, one I thought would be worth the investment. Oh how wrong I was.

Rockin a new NIP-05.

Updated to this one. Thank you! 🐂

Let's go!! Nip-05 inbound. 🐮

Wonderful selection method!

Here comes the "Bitcoin was hacked" fud.

Audio is missing for some reason. Playing fine on the device I uploaded it from, but not in the nostr client. Luke (forward) makes a face when the other guy mentions changing the proof of work for the Bitcoin network. https://youtu.be/rHKXKR-jXPg?t=5061

Primal seems to see it. Amethyst not so much.

Have you talked to about your BullishMarket?

Thanks, , I had already moved it off though. I wasn't sure what happens to Sats on layer twos during a chain split, so I figured it was best to just move it on chain to a hot wallet. If I understand aqua properly, it is a fediment of signers forming a multi-jurisdictional multi-sig. They run a side chain to Bitcoin, and issue liquid Bitcoin as a 1-1 peg per Bitcoin in their fediment. So not really my keys, not really my choice in a chain split. Right?

Happy anniversary, ! I love you. We've been married seven years now, a little more than a quarter of my life. I can't imagine life without you. We've accomplished so much together, we've grown together, and you've helped me grow as an individual. It feels like we've lived a lifetime together, and in some ways we have. I am incredibly blessed that I have had the opportunity to share these past seven years with you. Through all the hardships and happiness. I wouldn't want to do it with anyone but you. Earlier today, our eighteen month old son ripped off his shorts and diaper during nap time, and flung his poop outside his crib. While also getting poop all over everything in his crib - including all over himself. I cleaned the poop covered child, and you took care of the room and crib. We worked together as a team, jumping into our respective roles as if we'd done it a thousand times. That is the strength of our relationship, that we always lean on eachother for support. I felt that the poop incident was a pretty good allegory of our marriage. A little something like this: Life is beautiful. In the middle of what should be a calm moment, life goes to shit. We see the shit, we lean on eachother to clean the shit up. Then life is beautiful again. Thank you for always being there to enjoy the good times with me, and also for working to clean up the shit life throws at us as well. I love you now, and forever.