2026-05-10T17:14:15Z https://njump.cloud.vinney.xyz lukedewolf https://njump.cloud.vinney.xyz/npub1fk8h6g8zhftw8c7pga2zjd84p2z949up5lc3qdchm9v4m0q7mwws7jcwld https://blossom.primal.net/741de5ab4158f5ddc79b6082bcb492e605ec0f85f7abe754bcd1e22c9d4922cf.jpg https://blossom.primal.net/741de5ab4158f5ddc79b6082bcb492e605ec0f85f7abe754bcd1e22c9d4922cf.jpg https://njump.cloud.vinney.xyz/nevent1qqspk4gxtwvytywjz5agzqkvq8q3ea7uswfzcy5082nmdrz7985zyyqzypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde69vnkcj I&#39;ve taken a bit of a step back since BIP-110 activation day, both to collect my thoughts and to just take a break after an exhausting few months. Here&#39;s an update on me and many of my thoughts. <br/><br/>TL;DR: I&#39;m taking a bit of a step back. I&#39;m not forking off. <br/><br/>BIP-110<br/><br/>It&#39;s done now. I&#39;m not moving to the new fork. Enough said about that. <br/><br/>My support was almost entirely around avoiding chaos, uncertainty, and fracturing the community. I&#39;m sad to see many bitcoiners I respect losing faith in the project. <br/><br/>I have to admit, I&#39;ve had to rethink a few things about how Bitcoin works. <br/><br/>One thing we definitely learned is that the popular narrative about 2017 was wrong. The UASF provided enough leverage to push SegWit over the line. It wasn&#39;t a minority of plebs forcing a change on their own. Those who insisted that 110 would play out the same was as 2017 were categorically wrong. <br/><br/>I also want to note, for the record, that I doubted that things would play out the way Luke, Mechanic, and others predicted, and I have receipts. Hindsight is 20/20. I chose to push for the possibility that wouldn&#39;t result in a hard fork away. It didn&#39;t play out like that. <br/><br/>I now understand that the &#34;economic weight&#34; metric is completely real. That&#39;s the only way a node actually plays any direct role on the network. At the same time, running a node is still important for you. Your node enables your self-sovereignty. Nothing is lost by a minority of nodes being unable to force changes through on the network. <br/><br/>At the same time, I truly believe that 110 wasn&#39;t a sybil attack, at least not entirely. Real users had and have real grievances over Bitcoin&#39;s development. I don&#39;t excuse the choices that Core have made, nor the behavior of many on the 110 opposition side. There were opportunities to compromise, lower the temperature, and keep the community from fracturing. Then again, Luke also refused opportunities to compromise. It takes two. Maybe a hard fork was inevitable. <br/><br/>My position was mine. My own. The whole time. I was not mislead. I wasn&#39;t duped into anything. I listened to people saying very different things, and I made my own choices. I&#39;ll live with them. <br/><br/>Where I Go From Here<br/><br/>I&#39;m taking a step back from many of my Bitcoin activities, partially but not entirely because my second child is due next month. I&#39;m also hard at work pulling the final details together for BTCHEL (which I might not even get to attend, depending on my coming baby&#39;s world-entry preferences!). I&#39;m excited to see many of my friends in the community in my home city one more time. <br/><br/>Then, I&#39;m still confirmed to speak at the Plan B Forum in Lugano in October. After that, I have no plans to attend conferences for the foreseeable future. <br/><br/>Similarly, I&#39;ve also officially stepped away from the Bitcoin Infinity Show. I&#39;m no longer editing or producing episodes. I&#39;m still going to help Knut and team maintain continuity and advising on future direction, but I&#39;m not involved in the show itself anymore. We still have the Bitcoin Infinity Store and help friends in the space to publish books. I still enjoy that work, and I&#39;m happy to do it. <br/><br/>I&#39;m happy with what I was able to produce with Defending Bitcoin. I&#39;m glad to make that Bitcoin cybersecurity resource available for free, and I appreciate any support by buying a physical copy. That book, unfortunately, is already quite out of date. That&#39;s what happens in fast-moving fields. I&#39;ll aim to carve out some time to update key chapters, especially relating to the effects of AI. I might make some quick changes to certain recommendations on the web version. In any case, I hope the book is still helpful to those who want to learn more about Bitcoin cybersecurity. <br/><br/>I largely plan to stay out of debates about Bitcoin&#39;s governance and future. It would be too strong to say that I don&#39;t care at all about those things, but I&#39;ll largely leave those things to the development community. Things like covenants are totally fine by me, in principle. BIP-54 is probably OK too, although it contains a similar edge confiscation risk as 110. If standards were applied consistently, BIP-54 would need to resolve that confiscation risk. But, I&#39;m not going to play the contrarian and stand in opposition. I hope nobody wants to touch the 21 million cap any time soon. I&#39;ll lose interest if that ever happens, to put it mildly. <br/><br/>I&#39;m happy for those who contribute to Bitcoin in their own way to continue to do so. I&#39;m saddened by any personal conflicts that have arisen over the last months and years. I&#39;m willing to put those issues behind me. Toxicity doesn&#39;t suit me. I&#39;ll leave that to others. <br/><br/>I would be lying if I said my enthusiasm for Bitcoin is as high as it was a few months ago. I&#39;m definitely rethinking the effort I&#39;m putting into the space. We&#39;ll see how long this break turns out to be. For the next months, at least, I&#39;m focusing on my family. When I&#39;ve regained some energy, maybe I&#39;ll put my focus back towards contributing more to the Bitcoin security space, and on adoption and education in general. I&#39;ll still be around, here on X. But I likely won&#39;t be so active for the foreseeable future. <br/><br/>I&#39;m still excited to see everyone coming to Helsinki! We just finished the schedule, and I&#39;m just as excited as last year. Maybe even more! At the same time, I&#39;m looking forward to getting to the other side, and finally taking a break. <br/><br/>See you all out there. Take care. 2026-08-27T08:58:58Z https://njump.cloud.vinney.xyz/nevent1qqsrprey7vj367prp58crhvf8mkpvuq3p3v26zlqpzvdu46e822r0lszypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde6pc806a My final thoughts on BIP-110: <br/><br/>TL;DR: I believe BIP-110 activating smoothly is preferable to and less disruptive than a hard fork away from the network. I hope 110 activates smoothly in the coming days, but I will not follow a hard fork away from Bitcoin if it fails. I will remove BIP-110 from my handle, admit I was wrong, and move on.<br/><br/>I also advise everyone not to submit transactions that are likely to be mined in the blocks immediately after activation to minimize the potential for disruption or undesired outcomes.<br/><br/>I went from supporting 110 to opposing it, back to supporting again. Here&#39;s why:<br/><br/>I&#39;ve always seen something wrong with arbitrary data on Bitcoin, and I&#39;ve been intuitively against the need to grow adoption through new use cases. At the same time, I really felt that Bitcoin Core overstepped their mandate by changing the OP_RETURN default in v30, and I largely agree with Hodlonaut&#39;s assessment of that saga in his article series on the topic.<br/><br/>BIP-110 felt like a real way to influence the network back towards one that repudiates arbitrary data and doesn&#39;t leave node developers free reign to make changes to the protocol as long as there is no change to consensus code. I was involved in early discussions on the soft fork, and started running the client when it became available on Start9. <br/><br/>Still, I never felt that 110 was perfect. I thought it was incongruous for every limit to be set at 256 bytes except for OP_RETURN itself, and that it would be more consistent to apply a 256 byte limit there, also. Banning OP_IF and therefore breaking some functionalities of Miniscript also never seemed ideal, and I would have preferred finding a way to avoid that. Still, a fix to avoid OP_IF in Tapscript has been produced, so it&#39;s completely possible to avoid that disruption. Compromise and attempting to better achieve consensus would have been preferable to me.<br/><br/>I had conversations with many people, supporters and opponents, for months. I realized that much of my position came from my industrial cybersecurity experience, and the idea for my Bitcoin cybersecurity book, Defending Bitcoin, was born. I spent 6 months writing that book, and I&#39;m proud of it. I just released it for free as a response to the Coldcard hack. I firmly believe in the importance of Bitcoin security education, and I hope my contribution is valuable to the space. For me, no matter what happens, this book was born from 110, and I&#39;m glad it exists.<br/><br/>In the process of writing Defending Bitcoin, I evaluated the consequences of forks and chain splits on Bitcoin, and what these events look like from a risk perspective. These events are chaotic, messy, and potentially disruptive. Avoiding a chain split at all costs became my overriding position.<br/><br/>At the same time, I saw that consensus wasn&#39;t forming. Multiple groups of opposition have formed. One is technical, objecting to disruptions to applications using the restricted functions and to the limits on scriptability. Another is more philosophical, arguing that any restriction on &#34;valid transactions&#34; would constitute censorship. Yet another group was concerned mostly about the implications for Bitcoin&#39;s governance, what it would mean if a minority can force a change to Bitcoin.<br/><br/>I currently push back against all of those categories of objections, which I&#39;ll get to in a moment, but the bottom line is that I saw serious opposition emerging. Certainly not consensus. I was writing a book on risk analysis where I argue that a chain split or a fork without consensus is chaotic, messy, and risky. That&#39;s where I pulled my support for 110, and began advocating against following it. Bitcoin Mechanic said at one point that either 110 would succeed spectacularly or it would fizzle out quickly. I saw fizzling out quickly to be more likely and less disruptive than a prolonged fork scenario.<br/><br/>Still, my &#34;opposition&#34; was somewhat half-hearted. I still agreed with the goals of 110, and I disagree with many of the arguments against it. I never stopped running Knots with 110, mostly out of inertia. But, publicly, I did not support 110. I focused on finishing my book, and I got to have conversations with many 110 opponents with perhaps more clarity and willingness than if I were a 110 supporter.<br/><br/>After my book launched, however, I turned back towards the 110 debate and discussion. I re-evaluated the situation, and, just as there was staunch opposition, there were staunch proponents. Just as I spoke to opponents over the preceding few months, I also met many plebs who were running 110 for one reason or another. BIP-110 wasn&#39;t going anywhere, and that realization changed my thinking.<br/><br/>My Current Game Theory View<br/><br/>The entire proposition of 110 is that the miners will be compelled to signal by nodes threatening to throw away their blocks. One option involves risk of wipeout, and the other doesn&#39;t. That&#39;s the choice miners are faced with.<br/><br/>There also isn&#39;t any opposition in code. No URSF doesn&#39;t mean there&#39;s no opposition, or that there is consensus for 110. But it means that miners have no side saying &#34;I&#39;m going to reject your blocks if you signal for 110&#34;.<br/>Therefore, either the nodes enforcing 110 with the economic weight backing them is enough to convince the miners to signal and comply, or it isn&#39;t. BIP-110 will still either succeed or fail spectacularly and quickly. It will never catch up if it falls behind. Bitcoin isn&#39;t the longest chain. It&#39;s the longest chain of valid, accumulated proof-of-work. If the non-110 chain takes the lead and has majority hashrate, it&#39;s never giving it up.<br/><br/>Meanwhile, now there is talk of a proof-of-work change and a forced hard fork if 110 doesn&#39;t succeed in activating and becoming the longest chain. In the category of potential disruptions, I put that above all else.<br/><br/>Why A Hard Fork Would Be Bad<br/><br/>A hard fork off of Bitcoin would be terrible for the network. It would be centralizing in all possible metrics.<br/><br/>All nodes that follow the fork or turn off would be a loss for the Bitcoin network. That&#39;s a centralizing factor.<br/><br/>All plebs would had been mining and building their own blocks who choose to follow the fork or simply stop mining will no longer be mining on Bitcoin. That&#39;s a centralizing factor.<br/><br/>And, finally, all the monetary maximalists who believe Bitcoin&#39;s monetary properties need to be defended against use-case creep and crypto affinity scams who either follow the fork or decide to otherwise stop participating in Bitcoin would give up Bitcoin&#39;s governance to David Bailey, Michael Saylor, and the Core-industrial complex. That&#39;s a centralizing factor.<br/><br/>For all these reasons, I believe a hard fork is a bad outcome, and, therefore, 110&#39;s smooth activation is preferable.<br/><br/>Arguments Against Arguments Against 110<br/><br/>I said above that I disagree with most arguments against 110. I&#39;ll briefly state my counterpoints, just for the record.<br/><br/>First, the technical objections. Largely, these consist of opposition to &#34;breaking&#34; Miniscript, and opposition to limits on data embedding for scripting purposes. As mentioned, there&#39;s a fix to the Miniscript problem. Scripting limits is a more meta question and a bit of a philosophical difference.<br/><br/>Many of the developers I&#39;ve spoken with want a large explore space to discover potential use-cases for Bitcoin. Murch recently described the situation as (light paraphrasing) &#34;if Bitcoin is exciting to develop cool smart contracts, there has to be data embedding&#34;. In my view, and many others in the pro-110 camp, Bitcoin doesn&#39;t need to be &#34;exciting&#34; for developers. It needs to be functional money.<br/><br/>I attended Bitcoin++ in Vienna and was on a panel with Seedor Chris, Knut Svanholm, Matt Corallo, and Tiero, where we agreed that the vast majority of users just want to take their Bitcoin into self-custody and use it to pay for things. There is plenty of work to do to make taking self-custody easier, as we saw with the recent, massive Coldcard breach, and make medium-of-exchange better, as we saw with the shutdown of Boltz.<br/><br/>So, I don&#39;t agree that Bitcoin needs massive explore space on the base layer. Furthermore, I believe that practical limits are a positive security control to reduce attack surface and to reduce the viability of arbitrary-data embedding on Bitcoin. Ultimately, all security requires tradeoffs. It might become slightly more difficult to create &#34;exciting smart contracts&#34; on Bitcoin with BIP-110&#39;s rules, but those limits would serve other purposes.<br/><br/>Regarding the objection that BIP-110 threatens Bitcoin&#39;s censorship-resistance and permissionlessness, I believe that this is a total red herring.<br/><br/>BIP-110 doesn&#39;t prevent anyone from transacting, from moving UTXOs from one address to another. BIP-110 also does not introduce a third party you ask permission from in order to transact. In fact, Bitcoin&#39;s permissionlessness is a bit misleading. While it&#39;s true that you don&#39;t ask permission of anyone to transact on the network, you absolutely ask permission of the nodes to accept your transaction, and you ask permission of the miners to include your transaction in a valid block.<br/>In other words, you always have to follow the rules of the protocol. And, if the network chooses to adjust those rules so that certain transaction patterns aren&#39;t allowed, you need to follow those rules in the future.<br/><br/>There&#39;s also a security angle here. If Bitcoin cannot roll back or restrict any &#34;currently valid&#34; transaction type, Bitcoin will eventually be killed by the unforeseen consequences of some future upgrade. Taproot has been in place for over 5 years, and its negative consequences were apparently after less than 2 years. More than 99% of Taproot outputs are dust. The outcome of Taproot is clear: it&#39;s primarily being used for data embedding activity that has nothing to do with Bitcoin&#39;s monetary purpose. Rolling back some of the unrestricted data embedding capability of Taproot is a perfectly valid security response, especially after multiple years.<br/><br/>Finally, addressing the governance question: this is the objection that convinced me the most in preceding months. Voices like Giacomo Zucco and Samson Mow have argued that the precedent set by BIP-110 would be bad for Bitcoin in the long term. That a minority being able to change the network without widespread consensus would be viewed negatively.<br/>My response and pushback here is that users are running software. If some minority percentage of nodes running new software is enough to convince the miners to signal and comply with the new rules, then that&#39;s Bitcoin&#39;s consensus mechanism working as designed. The precedent might not seem nice, but it was entirely within the realm of possibility.<br/><br/>Put another way, if BIP-110 succeeds, we&#39;ll learn that there is some threshold of nodes with some amount of economic weight that is enough to get miners to comply with their new rules. If there are future soft-fork proposals that portions of the network disagree with, they&#39;ll need to object in code and run a URSF.<br/><br/>What If 110 Fails?<br/><br/>I fully acknowledge that it&#39;s possible for the miners to simply not signal. BIP-110 will be dead in the water if it maintains the current signaling past the activation point.<br/><br/>A large part of the argument that 110 will succeed is based on the precedent from the block size wars, where BIP-148 succeeded in compelling miners to activate SegWit. But, if 110 doesn&#39;t succeed, we will have learned that the lesson from 2017 was something different.<br/>In 2017, the miners tried to force a block size increase on the nodes, agreeing to adopt SegWit, but only if paired with a 2x block increase. The nodes, through BIP-148, rejected that increase, and insisted on SegWit&#39;s activation regardless. SegWit has broad consensus at that point, even with miners. Later, Bitcoin Cash implemented the block size increase and forked off from Bitcoin. The nodes rejected the change, they didn&#39;t necessarily force a change themselves.<br/><br/>If 110 fails, it will be because the miners can reject a change proposed by a minority of nodes. 110 proponents will need to similarly conduct their own hard fork and form a new chain if they want to enforce their rules into the future.<br/><br/>Bitcoin will have proven its resistance to change, again. And that, I believe, is the only silver lining here.<br/><br/>However, I won&#39;t be happy to see many bitcoiners I respect choosing to abandon Bitcoin and follow a hard fork off the network. Many of them say that it&#39;s the rest of the chain forking off. I reject that framing. A minority changing the rules to get rid of the proof-of-work algorithm and reject all the ASICs currently mining Bitcoin is a new chain. They can say that it&#39;s more true to Bitcoin&#39;s purpose, but it won&#39;t be the canonical Bitcoin. I don&#39;t think there&#39;s any value in pretending that the outside world will view the fork as Bitcoin&#39;s successor. Engage honestly with reality.<br/><br/>I won&#39;t be following a hard fork away from Bitcoin. I don&#39;t know that I&#39;ll have the same enthusiasm to engage with Bitcoin from that point forward, especially if many people from the space that I respect choose to leave.<br/><br/>This is another reason why I&#39;m happy that I produced Defending Bitcoin when I did. I hope that contribution ends up being valuable to bitcoiners regardless of the outcome of this fork. Even if I step back from contributing to Bitcoin education or adoption, that book will be out there.<br/><br/>What To Do At Activation Day<br/><br/>My concrete advice is to avoid transacting leading up to the activation height and through until we have clarity. I don&#39;t believe that clarity will take long. Either 110 will get overwhelming, essentially unanimous support immediately, or it will maintain its current level of hashrate and be dead in the water. That&#39;s a prediction. It&#39;s possible it takes longer to resolve. But I believe it will be quick. <br/><br/>Then, once we know the outcome either way, move on. Transact as normal. Either BIP-110 is in effect for a year, or it isn&#39;t. I will be turning my attention 100% to BTCHEL just around the corner, and after that, who knows? BIP-110&#39;s outcome will likely have a lot to do with my plans going forward. <br/><br/>Regardless of anything else, I&#39;m going to be glad for this all to be over. 2026-08-07T12:21:32Z https://njump.cloud.vinney.xyz/nevent1qqsxna4ahqz0ecms964yee6479qtnma3g64u0zv7fejzhhel79lkn7szypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde6lqfszs In reply to <a href='/nevent1qqsz66nsayypxsp4ds4u3u00cv9ra8nv06w83l07twq5ws5qtyljqaq5h5l2d'>nevent1q…5l2d</a><br/>_________________________<br/><br/>It&#39;s not quite at that level of detail. It&#39;s recommendations of what to do, not how to do it at low level. I&#39;ll probably add more guides to the website, but there are plenty of resources for &#34;how to&#34; do everything in the book. 2026-08-06T06:51:48Z https://njump.cloud.vinney.xyz/nevent1qqsx0klehfkqely9mstt99wj7jennhaek7cm62yug52460az07qnj7szypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde660f8gx In reply to <a href='/nevent1qqszw0z4hf37m749jkfwhsfjaqfhttepevautkxljpj8yh05tqv0t3gh2nlld'>nevent1q…nlld</a><br/>_________________________<br/><br/>I said &#34;neglected&#34; ;) <br/><br/> 2026-08-05T12:23:43Z https://njump.cloud.vinney.xyz/nevent1qqsw6cac6uzygznacwycn5rgz9ql6yuw3n4gj7lyhtz6pwsx0gd7ncczypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde66vug4m As a response to the ongoing Coldcard hack and other AI-related issues going on, I&#39;ve decided to make Defending Bitcoin available entirely for free on https://<br/>defendingbitcoin.com/reader<br/><br/>It was always in the plan to create a sort of &#34;reader companion&#34;, and I&#39;ll be adding more features to cross-link the contents of the book with useful information on how to improve your Bitcoin security. But, for now, the entire text of Defending Bitcoin is readable from your browser. <br/><br/>AND we&#39;ve finally added it to the Bitcoin Infinity Store at https://<br/>bitcoininfinitystore.com, along with Max Hillebrand&#39;s Praxeology of Privacy (also freely available on Max&#39;s website). If you want to support either of us, you can now do so with Bitcoin. <br/><br/>I also plan to update the chapter on AI Risks. I honestly hadn&#39;t anticipated quite how brutally AI attacks would hit, and, like most others, I certainly didn&#39;t expect one of the most widely-recommended hardware wallet manufacturers had simply neglected to implement such a fundamental feature as secure seed generation. In hindsight, I should have emphasized the risk of AI attack capabilities more strongly. <br/><br/>I hope Defending Bitcoin can be useful to anyone looking to improve their Bitcoin security. Let me know what you think, and stay secure out there. 2026-08-05T12:01:45Z https://njump.cloud.vinney.xyz/nevent1qqsvdh43ek7xeg0z3ekuh6869z2wa4hntsdzte7khfe23eh5dk3w9hczypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde6c05uk9 In reply to <a href='/nevent1qqst0lzxyxdutz66k0a5x0svtfwh4qulkcjsdl3tkspzg8nxlt09cpcw4c58f'>nevent1q…c58f</a><br/>_________________________<br/><br/>Legit, credit to Nifty for letting him speak on the topic. <br/><br/> 2026-07-24T19:04:59Z https://njump.cloud.vinney.xyz/nevent1qqs839nhxp8ysk3sf8ztt7zwhh8g584nru5f9ljmzcq5fvas0ccd9xqzypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde682u506 In reply to <a href='/nevent1qqsrrzrr6qs5rkruy23ctarz9m6ax696wnrnw8kq4m2v38k772kwy0gz0edwm'>nevent1q…edwm</a><br/>_________________________<br/><br/>Yes... Because it&#39;s our podcast. Not his. <br/><br/> 2026-07-23T06:57:22Z https://njump.cloud.vinney.xyz/nevent1qqs0rzmnvlzg2rathd5seldez2wd84s30f2ylp9ydq0a4gf0eu5ljvczypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde6gzjzal In reply to <a href='/nevent1qqsgzp5rdr8r62c7a2h2knfj6dfnwtdd7hy947nve95cxcsz3py5kpq5s9dcc'>nevent1q…9dcc</a><br/>_________________________<br/><br/>I don&#39;t work for Knut. <br/><br/> 2026-07-23T06:43:42Z https://njump.cloud.vinney.xyz/nevent1qqstkgd5mqwem9s8q6thxkr6hdhhzj4zw302vqum4e6fjqav8k5yg5czypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde6m5etx4 In reply to <a href='/nevent1qqsf0zvenahz9z0rz0qp5q27nsx3lq60rcearf9jjf03kf66xkfj90sp72fu5'>nevent1q…2fu5</a><br/>_________________________<br/><br/>I draw the line at personal insults. You do that, you&#39;re just a troll. GTFO. <br/><br/> 2026-07-23T06:07:28Z https://njump.cloud.vinney.xyz/nevent1qqsgdd5sx7e8x3ucvjfu3ap2ptlzz0800grc968qe5c8akcawgq95hszypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde62tsxg6 In reply to <a href='/nevent1qqsy79u4ufzfgacrgmuvwfk7fl5nsz62833hv74y5p3m8cy4uhwaplsc287rc'>nevent1q…87rc</a><br/>_________________________<br/><br/>Fuck off, troll. <br/><br/> 2026-07-23T05:47:56Z https://njump.cloud.vinney.xyz/nevent1qqsdtr0l9wg4cd8kk6zddd82hg584xk2045mzn2fmte7c0t7stunljgzypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde6lm577h In reply to <a href='/nevent1qqs0gsdky8zh0pyd640x8wsujc0lemhu3w02dxldwfrr2yjhjgq9nwse6kq06'>nevent1q…kq06</a><br/>_________________________<br/><br/>I see zero actual harms from 110. A couple of niche use cases will need redeveloping. No risk to being able to self custody or send Bitcoin for normal users. <br/><br/> 2026-07-23T03:24:42Z https://njump.cloud.vinney.xyz/nevent1qqs0amq74ly8xnv93n5yt9aup229lusuntlp4qg9yr6xtc8jd9p5fuczypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde6m0unex In reply to <a href='/nevent1qqsdxvxuk66vl0lvzn23t23esnsa3jczemhnhhkvr05nlsrvw5huvvsa84knz'>nevent1q…4knz</a><br/>_________________________<br/><br/>It was more inertia than anything. I had my node running the 110 client, and I knew I could always change versions later. To a certain extent, I was just waiting and watching. <br/><br/>Then my node actually stopped responding, and I needed to wipe and reinstall to get it back up. That took longer than I expected, and by the end of it I had reasoned my way back to 110 support.<br/><br/>Sorry for any offense, it wasn&#39;t intentional. It was more of an anecdote that I had never turned the signal button off. <br/><br/> 2026-07-22T18:48:03Z https://njump.cloud.vinney.xyz/nevent1qqsxh5mdwe5vxjlearvseacfd2rp8m6m74mawuushsm7w3kycfkyeaszypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde659vwvc In reply to <a href='/nevent1qqs2ew2t6zxd3gwctnttvznu0nl5hcyxu8eygmkv4yrz988g9xce9zqcqt5t8'>nevent1q…t5t8</a><br/>_________________________<br/><br/>This is taking &#34;value is subjective&#34; to an absurd place. Bitcoin isn&#39;t for everyone&#39;s meaning. It&#39;s for money. The protocol already has rules. More rules is fine. <br/><br/> 2026-07-22T12:49:36Z https://njump.cloud.vinney.xyz/nevent1qqsfrr37j2xk9506vz5htdh4k3ypzx55q6x3xrtjqxnsdkn9t5ah4nqzypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde6qjvtd2 In reply to <a href='/nevent1qqswnfrzht30zgylmxd55nrkkl9sp8vsm0qu039xrqql7dvzpf6uz9qknmayv'>nevent1q…mayv</a><br/>_________________________<br/><br/>Yes :) <br/><br/> 2026-07-22T12:43:34Z https://njump.cloud.vinney.xyz/nevent1qqsyhs6lf0n27etqvvctx0nhh850jwl8luzlud9kl9uhut437gpw0ngzypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde6en5w56 I&#39;m live on Stacker News right now! <br/><br/><a href="https://stacker.news/items/1524157">https://stacker.news/items/1524157</a><br/><br/>Ask me about Bitcoin cybersecurity, BTCHEL, BIP-110, or anything else! 2026-07-13T17:05:49Z https://njump.cloud.vinney.xyz/nevent1qqsz9cw5k96lvxx7zq6psdafp6jxjyhn4p9mn9t5jxc78m79h9dvpsqzypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde6a35k7l Join me in a few hours and AMA! <br/><blockquote class="border-l-05rem border-l-strongpink border-solid"><div class="-ml-4 bg-gradient-to-r from-gray-100 dark:from-zinc-800 to-transparent mr-0 mt-0 mb-4 pl-4 pr-2 py-2">quoting <br/><span itemprop="mentions" itemscope itemtype="https://schema.org/Article"><a itemprop="url" href="/nevent1qqsxtdcf2tuaqkutvlg9ny7mlt834yslhhjh8k8x6tn68na9d5tkz3qzyp684huwjqmw67950m98v2lcp0zp4u6d7md8h4zgwm8j6flxklwkgqcyqqqqqqgzvruw0" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1">nevent1q…ruw0</a></span> </div> TODAY: Stacker News AMA with <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/nprofile1qyv8wumn8ghj7enfd36x2u3wdehhxarj9emkjmn99uqsuamnwvaz7tmwdaejumr0dshsqgzd3a7jpc462m378s282s5nfag2s3df0qd87ygrw97et9wmc8kmn564se08" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>lukedewolf</span> (<span class="italic">nprofile…se08</span>)</a></span>, author of Defending Bitcoin! <br/><br/>Bring your questions about Bitcoin, security, and BIP 110!<br/><br/>🗓️ Monday, 13 July 2026<br/>⏰ 1PM CDT / 1800 UTC<br/>📍 stacker.news/~AMA<br/><br/> <img src="https://blossom.primal.net/dcfe31d57bb84913d687783caf3829cbe171824c05960af961194db5d5cad087.jpg"> </blockquote> 2026-07-13T14:26:29Z https://njump.cloud.vinney.xyz/nevent1qqstezy52lra93ga05spt3pmcmv8nlzh0yd6lnhrmrxtymvf2w5e2uczypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde6fch27z In reply to <a href='/nevent1qqs227sssuy3lxz6am7j7rjz92x3rxp0mjjryc3nzsphunyunjks7pcqmjvtc'>nevent1q…jvtc</a><br/>_________________________<br/><br/>Tldr since the Guy interview: I find 110 activating smoothly to be the least risky and least chaotic scenario. I was getting the game theory steps a bit wrong. Something longer coming when I have time to write everything down. Also a few more pods. <br/><br/> 2026-07-08T03:43:52Z https://njump.cloud.vinney.xyz/nevent1qqs2h33vnp85sac2nnahlfnyrphm8kgr6h0pj7nvcentrrxxlrlmrrgzypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde6jha95x In reply to <a href='/nevent1qqsdg2zymq8ktulkc6dzhugtu6rk247kuzxua7387c84x5x3qke999sxgjr70'>nevent1q…jr70</a><br/>_________________________<br/><br/>Apparently you haven&#39;t kept up with my X. I should really make an update on both platforms. <br/><br/> 2026-07-07T14:32:47Z https://njump.cloud.vinney.xyz/nevent1qqsv3ymev3za6aw0rn2etrc3afmfmyuzmn3rqfgk60lk0w5x5r4wccgzypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde6ewkhss In reply to <a href='/nevent1qqsp058anqly3lvnycwfv8rwz7emmjtsumgg9mt7vceedsmp7pxwdcsrjc007'>nevent1q…c007</a><br/>_________________________<br/><br/>There is no reason for this. 2026-06-21T17:53:56Z https://njump.cloud.vinney.xyz/nevent1qqswy36cmtwvcsfflz8xx3fgre8g576qjj0cc42vsdeleegnwr4q6pczypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde6s9hm2p In reply to <a href='/nevent1qqsvqgu75r8rap4v927fgkntlzxughncd5rc0ec76kndtzdq0ajuhvgehsgf8'>nevent1q…sgf8</a><br/>_________________________<br/><br/>I mostly see Luke as committing to forking off to an altcoin if 110 doesn&#39;t work. That profoundly saddens me. This all-or-nothing talk is part of the problem. <br/><br/>I will be happy if 110 succeeds but I just don&#39;t see it happening. I believe now that the incentives are the inverse of what they should be. And the result will be that a large portion of the monetary maximalists leave Bitcoin. And maybe there&#39;s even a protracted chain split and a competing coin. <br/><br/>I can&#39;t support that outcome. Maybe I&#39;m overvaluing the tail risk, but that&#39;s sort of my job. If I&#39;m wrong, I&#39;m wrong. <br/><br/> 2026-06-21T16:46:54Z https://njump.cloud.vinney.xyz/nevent1qqswuyuzu8092kcx75uh5khzay2sfwhfys69ngn9wqg927dpa43p3zszypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde678aq5c In reply to <a href='/nevent1qqs84ew9r5zgwwmjfgrcu4xh9728qmzgm46aqqxqaafeajkdetmg9cg507x39'>nevent1q…7x39</a><br/>_________________________<br/><br/>Knots on StartOS, mining with OCEAN using DATUM. 2026-06-21T10:49:24Z https://njump.cloud.vinney.xyz/nevent1qqszzxwlhtnzy09n03aqyq3sqqcxtp8mt0jrjkz9lkzy8swkg3hwwegzypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde6qecf3y In reply to <a href='/nevent1qqs035c5lv2g7jq8m92uf4wpw0n63tjymw2qdqdd75rwphrnvx47udgp99mhxue69uhhyetvv9ujuumpw3kxzmn5d9eju6t09au8ycte94kkj6m994ax2mnfw35qfrcn9r'>nevent1q…cn9r</a><br/>_________________________<br/><br/>Apparently the IBD has been improved significantly in recent Core releases. Not just assumevalid. <br/><br/> 2026-06-21T06:22:00Z https://njump.cloud.vinney.xyz/nevent1qqs0lhuxnhlm3a3n3cnga2qq5hf74v3xd8ztw5feymjhkl53mzll88czypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde6vw2qlc In reply to <a href='/nevent1qqsg68lsmrmj48vskf6d65h54gegddyrr40ylfv3nsfu7vnjspfhlpsqzmvn9'>nevent1q…mvn9</a><br/>_________________________<br/><br/>This bot account is a deranged moron who apparently thinks I&#39;m pro spam. GTFO. <br/><br/> 2026-06-20T14:15:00Z https://njump.cloud.vinney.xyz/nevent1qqs87t62avxrnatq275npccpdqyzrddz68ve5f6pqr3hf5ulfjjv8fszypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde698tupp In reply to <a href='/nevent1qqsdsccdsg874dqmmg3dlada8pvjelzj5synfnjn5udfzf8ve3l4zss20m4pw'>nevent1q…m4pw</a><br/>_________________________<br/><br/>You&#39;ve given me lots of food for thought. I&#39;m not saying I&#39;ll change my position. But if I do, it will be final. Still a little ways to go yet. <br/><br/> 2026-06-20T13:36:44Z https://njump.cloud.vinney.xyz/nevent1qqs9z6cdtvrr0nr7775qm6t5et6mgdqkx8evll72vrlp9afferrghgqzypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde68rpjvm In reply to <a href='/nevent1qqs0eheu6qx9q3gnah7w8z9e4vkk4sfhxvc0f46st2gkxss5xnr2t4sev75v0'>nevent1q…75v0</a><br/>_________________________<br/><br/>The vast majority of Bitcoin users have no idea BIP110 is even happening. Disruptions to the ability to use Bitcoin as money should be avoided. <br/><br/> 2026-06-20T06:48:50Z https://njump.cloud.vinney.xyz/nevent1qqsq83c3j0d07nwtall25388zurjpkdmnc498tsmx98j4llfr3x8c5gzypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde6rnmjc0 In reply to <a href='/nevent1qqsg2kkk5u25ndc2x8mlrfm8s5qax9jug5lsw505chzjhxznr879tdcz6x8sx'>nevent1q…x8sx</a><br/>_________________________<br/><br/>This fellow is reply-guying me elsewhere too. Seems to have a specific issue with me. Oh well! 2026-06-20T03:11:04Z https://njump.cloud.vinney.xyz/nevent1qqs83ztfjmgrf7rfrlum2hutr532jdd2lvv48z7wrqyujama5qtg3tszypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde6c0faqq In reply to <a href='/nevent1qqsxpahpf0nenswrugqtc7v6njyfcar5xlvx8s294f8k64affvpesjg07cdv3'>nevent1q…cdv3</a><br/>_________________________<br/><br/>No, idiot. A perfectly valid transaction could be mined by a non-110-signalling block and then it&#39;s in limbo. If it gets mined by the BIP-110 chain, it will be in a totally separate block with separate history, which may have downstream effects. But the BIP-110 side could also get RBF&#39;d, permitting a double-spend. <br/><br/>Think things through before posting. 2026-06-20T03:02:50Z https://njump.cloud.vinney.xyz/nevent1qqsykwq39wxxtqwz9anukr6wk3yrlarla62nv3wc20urmnwqlut6fagzypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde6st346p In reply to <a href='/nevent1qqsxf5hpamd8dg08vlhl2902x2eyg3k73dvdgrrgwukzyn5e2sszjyg3l49y4'>nevent1q…49y4</a><br/>_________________________<br/><br/>I content myself knowing that you&#39;re completely wrong. Feel free to point out why you think my book is &#34;AI slop&#34;. If you don&#39;t want to do that, kindly fuck off. 2026-06-20T02:59:58Z https://njump.cloud.vinney.xyz/nevent1qqs8vfd07lm22jdqty6l2wxhs2mksppyh3uf5z9ztdseavnpgxcpf2gzypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde652vpj3 In reply to <a href='/nevent1qqsxsyjfaqqxtlsngyrxay69j46qv4lmlcqc9dkzns0p42z0dws0p9s8qq7dn'>nevent1q…q7dn</a><br/>_________________________<br/><br/>Thanks for the feedback! I&#39;m actively considering my position on BIP-110. If forced to pick between &#34;pro&#34; and &#34;anti&#34;, I&#39;m currently &#34;anti&#34;, but there&#39;s a lot more nuance. I&#39;m mostly focusing on the downside tail risks. Maybe I&#39;m overweighting that scenario. 2026-06-20T02:57:52Z https://njump.cloud.vinney.xyz/nevent1qqs2428chprx60a8czawhm3gnpuadt9aw6w05qv8qcltumcp498c2aczypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde6hnpspe In reply to <a href='/nevent1qqsy6pfr3kac060w2z7x85aw2yrp3zz55u0wppy0yuwwxyus437n3wcm7l52q'>nevent1q…l52q</a><br/>_________________________<br/><br/>Disagree. If a user&#39;s transaction gets mined in a non-compliant block, that transaction will be in conflict. Double spending will be possible on the margins. <br/><br/> 2026-06-20T01:38:50Z https://njump.cloud.vinney.xyz/nevent1qqswusk7em4p5hhpfpenm59xq5dag3nf7a5wgjzss85wkw7dt7vrq9szypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde64k9xjs In reply to <a href='/nevent1qqspgjujyp0qyykjz6vw3vlyg8lkvzles7cask9syzjzpfch2j29d6cpydmhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtmnd9jhyunp945hvmmj0ygjthdk'>nevent1q…thdk</a><br/>_________________________<br/><br/>Thanks, I appreciate that! <br/><br/>I came to my position through writing Defending Bitcoin. I wrote a risk management book. I evaluate the risk of profoundly negative outcomes if BIP-110 causes a chain split to be too high. <br/><br/>Frankly, my real position might be that I support it after all (because I still mostly support the changes, I have specific technical objections that aren&#39;t direction ally important), but only if those signaling/enforcing drop it immediately if it looks like it&#39;s going to end up with a tiny minority of hash rate and just fork off. <br/><br/>In other words, try it, see what the outcome is, but don&#39;t cling to a dead-on-arrival fork if that&#39;s the result. <br/><br/>I believe Bitcoin will survive with or without BIP-110. The &#34;with&#34; scenario would be truly positive in my view. A user-activated rebuke of both arbitrary data and the prevailing governance structure. I&#39;m all for that. <br/><br/>The &#34;without&#34; scenario is what I&#39;m worried about. I don&#39;t want all the monetary maximalists to leave if this soft fork fails to activate and become the longest chain. I don&#39;t think making this an all-or-nothing effort is right. And, in the case of failure, there will be much gloating from on high and ridiculing of those who prefer less arbitrary data on Bitcoin and are uncomfortable with Core&#39;s governance. <br/><br/>In Defending Bitcoin itself, I don&#39;t even say &#34;don&#39;t support BIP-110.&#34; I highlight the potential risks of a chain split, and say DYOR. Know what you&#39;re getting into.<br/><br/>At this point, I see that the momentum for BIP-110 is absolutely there. Almost half the plebs I met at BTC Prague said they were pro-110 or considering supporting it. The only opposition I heard was from devs. But there are also smart people in the space who support its goals but don&#39;t think it will activate. I&#39;m in that camp too. <br/><br/>I don&#39;t know how to square these positions. My internal schelling point landed on not supporting BIP-110, but I&#39;m not sure that&#39;s totally accurate anymore.<br/><br/>Perhaps more accurate would be that I support trying, but giving up quickly if it fails. The problem is that we&#39;re dealing with individuals. I have a feeling or even know that many people will either continue to support the minority chain or just give up on Bitcoin entirely. <br/><br/>This is kind of a chicken and egg problem now. If it&#39;s going to happen anyway, does my support or non-support make any real difference? <br/><br/>Either way, come August 7th, I&#39;m still going to be here. And dealing with the fallout of BIP-110 being unsuccessful, if that&#39;s the case. <br/><br/>I don&#39;t know if that clarified anything for either of us. But those are my thoughts. Take them as you like. <br/><br/> 2026-06-20T01:36:35Z https://njump.cloud.vinney.xyz/nevent1qqsdlaqdw6x4hqaphx9ul90z2lm90gtfnng7y6vfe02crk6xc0jxphqzypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde6tah84m In reply to <a href='/nevent1qqsru4qfsn6j6l40a60nj3vz52ztx40y3rkatw3eep368w3jnkdaxagyz7frx'>nevent1q…7frx</a><br/>_________________________<br/><br/>See here. <br/><blockquote class="border-l-05rem border-l-strongpink border-solid"><div class="-ml-4 bg-gradient-to-r from-gray-100 dark:from-zinc-800 to-transparent mr-0 mt-0 mb-4 pl-4 pr-2 py-2">quoting <br/><span itemprop="mentions" itemscope itemtype="https://schema.org/Article"><a itemprop="url" href="/nevent1qqsxt398y5sfcdetp5gfr8wnsulh7sf4utvxlfsthj0nseqzct9069qwzmjyj" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1">nevent1q…mjyj</a></span> </div> Look at any of my highlighted X posts, listen to any of my recent podcast appearances, or any Bitcoin Infinity Show / Feeedom Footprint Show from about the middle of 2023.<br/><br/>But this is good enough to show I've been anti-spam since the beginning: <a href="https://x.com/i/status/1766696720572830088">https://x.com/i/status/1766696720572830088</a> <br/><br/> </blockquote> 2026-06-20T01:21:09Z https://njump.cloud.vinney.xyz/nevent1qqsxt398y5sfcdetp5gfr8wnsulh7sf4utvxlfsthj0nseqzct9069qzypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde6w9k2ae In reply to <a href='/nevent1qqsgsre22qurua95aypj7fanzt8x3gx324c6nmj45hk0s8569wg5utc8pw63z'>nevent1q…w63z</a><br/>_________________________<br/><br/>Look at any of my highlighted X posts, listen to any of my recent podcast appearances, or any Bitcoin Infinity Show / Feeedom Footprint Show from about the middle of 2023.<br/><br/>But this is good enough to show I&#39;ve been anti-spam since the beginning: <a href="https://x.com/i/status/1766696720572830088">https://x.com/i/status/1766696720572830088</a> <br/><br/> 2026-06-20T01:20:39Z https://njump.cloud.vinney.xyz/nevent1qqsdxwgquhtscyesly5lw0565exum8smeh9u83wy4kumg73gzk2gaaczypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde6uus64f In reply to <a href='/nevent1qqsp2g26ulc34fq0kpjs0m6zhwvhqtd30qc9vtw8r3wna6dfn8j2zpqpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgsuqtjl'>nevent1q…qtjl</a><br/>_________________________<br/><br/>I don&#39;t believe the &#34;good&#34; outcome is likely. That&#39;s why I&#39;m not supporting at this point. <br/><br/> 2026-06-18T15:01:56Z https://njump.cloud.vinney.xyz/nevent1qqs2hew5un52zj6rpqtjtdnxp3u3v877syjarxanncfuhpf8c09gwjqzypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde6v2jces In reply to <a href='/nevent1qqsfkh5juarvjd6u2fhcgaunk2ajnruwav0k66eh7mr57wek9rvgungj8hxdm'>nevent1q…hxdm</a><br/>_________________________<br/><br/>Care to tell me why you think that? Did you read it? <br/><br/> 2026-06-18T12:11:06Z https://njump.cloud.vinney.xyz/nevent1qqsgyz3f05zmdhx8p3a84e29xt07ulmv98gnwevzy4zj9eg4euw0gsczypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde6f2ndq3 In reply to <a href='/nevent1qqsfkh5juarvjd6u2fhcgaunk2ajnruwav0k66eh7mr57wek9rvgungj8hxdm'>nevent1q…hxdm</a><br/>_________________________<br/><br/>Care to tell me why you think that? Did you read it? <br/><br/> 2026-06-18T12:10:51Z https://njump.cloud.vinney.xyz/nevent1qqsva092ruvyu6v654va7mgzhej9xk0qfrcekdrpesdvmqt8nntsm7qzypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde6qfum77 In reply to <a href='/nevent1qqs9lh3sx33ja4u7s2s6gm9xklppgv3mhme47pwaz7ez7564qy95gtqdgtp5a'>nevent1q…tp5a</a><br/>_________________________<br/><br/>Thanks so much for your support, Jeff! <br/><br/> 2026-06-18T10:56:28Z https://njump.cloud.vinney.xyz/nevent1qqs8qcy842gqr4pz95nw4d9gkw9dq6yw5j6lpaey0rryumenet9exmgzypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde6tc9pkc In reply to <a href='/nevent1qqs2dckumu390efwmkw2gppaa69t2t9ngewj2fr5aju0dzhnra65gqqku5ghv'>nevent1q…5ghv</a><br/>_________________________<br/><br/>I&#39;m extremely anti-spam. I don&#39;t believe a soft fork that has consensus is the solution. I believe it will do more harm than good. I have receipts. <br/><br/> 2026-06-16T20:03:13Z https://njump.cloud.vinney.xyz/nevent1qqsyn42ekzw9lgapp9dy8cs5lhc3epvpxgn67twvykedeuzxaehsqzgzypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde6v8sea9 In reply to <a href='/nevent1qqspwf55tcc0jkgcu4m96n4wvw4flzaask70923fcy0usy5ca5s3ryg9l4d5h'>nevent1q…4d5h</a><br/>_________________________<br/><br/>See my recent pod with Guy Swann for the best explanation. Or any of my other pod appearances. <br/><br/> 2026-06-15T14:50:53Z https://njump.cloud.vinney.xyz/nevent1qqsxslxglwsxp6d90pex9c3xcx9tjta8grt5e4hw7d47l4zct4yhjhszypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde6f6u8dr In reply to <a href='/nevent1qqsyw7glnj9c503yu7lfnh0ltc83ecd0xvhsvz8qg7u0c360m66zdxs0zt99g'>nevent1q…t99g</a><br/>_________________________<br/><br/>Soon! We&#39;ve actually never done ebook on our website but we can figure that out. 2026-06-15T11:14:53Z https://njump.cloud.vinney.xyz/nevent1qqsfn78ad9rl28mls50jhp9lky8dghxpaxf2jp48netxkmarq4ynlyczypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde637yqmp In reply to <a href='/nevent1qqsq9qj2n4f33j4f4ezt2m7p95epke030pgrcxjumv7lg4y7252ltygfuuh2s'>nevent1q…uh2s</a><br/>_________________________<br/><br/>Coming soon! 2026-06-15T11:14:25Z https://njump.cloud.vinney.xyz/nevent1qqs9xygmptvuaszemxf0qr88222srqm40kvydlm596cfl903qqtracczypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde67jxph5 In reply to <a href='/nevent1qqsy2cqsgu830gfzvmhmwgw0vcl4fxnjvad837qaw0lj49lwzzgjyfsdum6vm'>nevent1q…m6vm</a><br/>_________________________<br/><br/>Haven&#39;t been for a while. <br/><br/> 2026-06-15T09:40:58Z https://njump.cloud.vinney.xyz/nevent1qqs9gj5mymnjv7a93jwa3d5fg0jvdd4slg7336gw9yp66lysfwmjt9qzypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde6mnz0q4 In reply to <a href='/nevent1qqsgfrug5pj3lz0wvxz52tufpry9jnn6jg73n5ped3slvtdc8dx50pg77ja7t'>nevent1q…ja7t</a><br/>_________________________<br/><br/>🧡 2026-06-15T08:32:35Z https://njump.cloud.vinney.xyz/nevent1qqsyl28v929j3k77kkfm8wfu8c0vzq8yn3smphlv720xynw8qhpctsczypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde65l6tf8 In reply to <a href='/nevent1qqsw7y206cw9ps99g86wycnd69tj0dq0xvzgrkkj24acxw6ppvj9v8sr0j0gd'>nevent1q…j0gd</a><br/>_________________________<br/><br/>Thanks for the support! I hope you enjoy and that it&#39;s useful to you! 2026-06-15T06:32:25Z https://njump.cloud.vinney.xyz/nevent1qqs0zue87fml32kdgrd606q0cf0mj3xdtnuevl0ne6782kfen5h7nsczypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde6zj7dpt Defending Bitcoin is out! <br/><br/>It&#39;s available now on Amazon in paperback, hardcover, and ebook editions. Pick up your copy today! <br/><br/>This is Bitcoin cybersecurity through the industrial lens I&#39;ve spent the last decade working in. Defense for your Bitcoin and defense for the network. From custodial failures to quantum computing, the full threat landscape is here.<br/><br/>Huge thank you to everyone who helped with this massive project. I couldn&#39;t have done it without you!<br/><br/> <img src="https://blossom.primal.net/678ab8b5ca6800770239bcce042d3fcbcd19e431cc144c599f5d379c2c149e4f.png"> 2026-06-15T06:21:14Z https://njump.cloud.vinney.xyz/nevent1qqsx0pgacjdrk09pf79pmnfgkunm0u3km5qrm57nkmdtpn6dmrz24ugzypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde6a9874n I had a great time telling Daniel all about Defending Bitcoin. Give it a listen to find out more about the book! We also cover the BIP-110 situation in quite a bit of deal, with my current reasoning made abundantly clear. <br/><blockquote class="border-l-05rem border-l-strongpink border-solid"><div class="-ml-4 bg-gradient-to-r from-gray-100 dark:from-zinc-800 to-transparent mr-0 mt-0 mb-4 pl-4 pr-2 py-2">quoting <br/><span itemprop="mentions" itemscope itemtype="https://schema.org/Article"><a itemprop="url" href="/nevent1qvzqqqqqqypzpw3089yrxevywh53dq9cnrumurcas5qkd34g88d7ppxsye4ddcs2qy88wumn8ghj7mn0wvhxcmmv9uq3wamnwvaz7tmjv4kxz7fwwpexjmtpdshxuet59uqzpfzrvwa4xrxsdhz7wzsh7vxh7k8nm08w396ka339f2hm7ug37we6ez3hac" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1">nevent1q…3hac</a></span> </div> The latest episode of Once Bitten has just dropped<br/><span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/nprofile1qyv8wumn8ghj7enfd36x2u3wdehhxarj9emkjmn99uqsuamnwvaz7tmwdaejumr0dshsqgzd3a7jpc462m378s282s5nfag2s3df0qd87ygrw97et9wmc8kmn564se08" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>lukedewolf</span> (<span class="italic">nprofile…se08</span>)</a></span> discusses his new book Defending Bitcoin, drawing parallels between industrial control systems and the Bitcoin network.<br/><br/>Full audio and video on <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/nprofile1qyxhwumn8ghj7mn0wvhxcmmvqyv8wumn8ghj7urjv4kkjatd9ec8y6tdv9kzumn9wsqzqefcjf0tldnp7svd337swjlw96906au8q8wcjpcv9k5nd4t3u4wr0u5gem" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>fountain_app</span> (<span class="italic">nprofile…5gem</span>)</a></span> <br/><br/><a href="https://fountain.fm/episode/aqtC0b3XKHZQtMtiuD6y">https://fountain.fm/episode/aqtC0b3XKHZQtMtiuD6y</a><br/> </blockquote> 2026-05-29T12:44:37Z https://njump.cloud.vinney.xyz/nevent1qqstcqlq5422yzjawz6dhjatzy035ld49p9l8e2sh2e06lm6f73ugwszypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde6cjqynp In reply to <a href='/nevent1qqsxppxh79ypgudwz02y7s5zqq4le06lgqlpe3qv2tqef8hwsh2c6gsdwtkd5'>nevent1q…tkd5</a><br/>_________________________<br/><br/>Cheers Roger, it looks great! 2026-05-21T17:55:22Z https://njump.cloud.vinney.xyz/nevent1qqs9jj3n8wtay9hf35y54ydpxnl5pst07f95vrqy4y205k2u29tkxqqzypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde6f6vkuz In reply to <a href='/nevent1qqs8cqhx9w45aql56scyudyqxhwma2vlfnv7m0zx2ekt5sct9h2hv3qpzemhxue69uhhyetvv9ujuerfw36x7tnsw43z73nk73s'>nevent1q…k73s</a><br/>_________________________<br/><br/>At least I hope it&#39;s interesting! <br/><br/> 2026-05-21T02:58:49Z https://njump.cloud.vinney.xyz/nevent1qqstexas729wyv3jxgs0epg2j4lvf5k6nvjhv75k7u600xp8p52ejhszypxc7lfqu2a9dclrc9r4g2f5759ggk5hsxnlzyphzlv4jhdurmde60nkrh5 I want to talk about Defending Bitcoin on as many podcasts as possible and get the word out. Who would you recommend I talk to? Any Bitcoin podcasters here who would like to have me on? <br/><blockquote class="border-l-05rem border-l-strongpink border-solid"><div class="-ml-4 bg-gradient-to-r from-gray-100 dark:from-zinc-800 to-transparent mr-0 mt-0 mb-4 pl-4 pr-2 py-2">quoting <br/><span itemprop="mentions" itemscope itemtype="https://schema.org/Article"><a itemprop="url" href="/nevent1qvzqqqqqqypzqnv005sw9wjku03uz3659y602z5yt2tcrfl3zqm30k2etk7pakuaqyghwumn8ghj7mn0wd68ytnvv9hxgtcpzdmhxue69uhhqatjwpkx2urpvuhx2ue0qqsxtzvqlj9a7m8f987uxzfa3mm7hya2uf7g0gjdfsn25rr6mf8nl7s54435q" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1">nevent1q…435q</a></span> </div> I've been a bit absent from Nostr for the last little while, but that's about to change. For the past few months, I started focusing on a new project, and I'm finally ready to announce what I've been up to. <br/><br/>I've written a book. Defending Bitcoin: Industrial-Grade Cybersecurity for the Monetary Grid. <br/><br/>6 months ago, I realized how I could apply my cybersecurity background to Bitcoin, with a perspective grounded in the world of critical infrastructure and industrial control systems. <br/><br/>In Defending Bitcoin, I make the case that Bitcoin is critical infrastructure, and I mean that technically. Critical infrastructure is everything essential for the modern world to run the way it does, and I assert that Bitcoin meets the threshold of that definition. <br/><br/>Defending Bitcoin is grounded in the industrial cybersecurity principles that I use on a daily basis. The framework I've built is based on ISA/IEC 62443, the most widespread industry standard for industrial cybersecurity, and applies universal cybersecurity principles such as defense-in-depth, risk management, and threat modeling. And in all cases, there's always something you can do to improve your security or that of the network as a whole. <br/><br/>I wrote the book for two audiences at once. The first is bitcoiners who want to improve their security posture. The second is technical professionals who may be skeptical about Bitcoin and want to understand it better. I build a base of vocabulary for both sides to understand each other, then cover the threat landscape over the course of 10 chapters.<br/><br/>Launching today is the accompanying website, <a href="https://defendingbitcoin.com/">https://defendingbitcoin.com/</a> where you can get a preview of the book, read endorsements from Mikko Hyppönen (the foreword writer), <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/nprofile1qy2hwumn8ghj7etyv4hzumn0wd68ytnvv9hxgqgdwaehxw309ahx7uewd3hkcqpqs05p3ha7en49dv8429tkk07nnfa9pcwczkf5x5qrdraqshxdje9sgew2ua" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>Jeff Booth</span> (<span class="italic">nprofile…w2ua</span>)</a></span> , <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/nprofile1qy2hwumn8ghj7mn0wd68ytndv9kxjm3wdahxcqg5waehxw309ahx7um5wfekzarkvyhxuet5qqsw4v882mfjhq9u63j08kzyhqzqxqc8tgf740p4nxnk9jdv02u37ncdhu7e3" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>LynAlden</span> (<span class="italic">nprofile…u7e3</span>)</a></span> , <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/nprofile1qqsxc56ajk5xtxerf4dqspgrfa0s5elrcr80lnz9nasldq87j3zzf0cc5h4hk" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>nprofile1qqsxc56ajk5xtxerf4dqspgrfa0s5elrcr80lnz9nasldq87j3zzf0cc5h4hk</span> (<span class="italic">nprofile…h4hk</span>)</a></span> , <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq3wamnwvaz7tmjv4kxz7fwv9a85ctdduhxuet59uqzpdlddzcx9hntfgfw28749pwpu8sw6rj39rx6jw43rdq4pd276vhu7r8p0e" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>Max</span> (<span class="italic">nprofile…8p0e</span>)</a></span> , and <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/nprofile1qyt8wumn8ghj7cnfw33k76twv4ezuum0vd5kzmqprpmhxue69uhkc6t8dp6xu6twvaex2mrp0yhxxmmdqqspv7zt4kqm0wpptmjvag9d7pre82af4qmxppujcccpp67w6lgcfjq6ecqdh" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>V4BTC</span> (<span class="italic">nprofile…cqdh</span>)</a></span> . I've also built a threat modeling tool where you can check how the book applies to you (fully local, we don't collect any data except your email address, if you want updates). <br/><br/>Defending Bitcoin will be available for purchase online on June 15th, right after <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/nprofile1qqsd0f68dvf98gvs9am9dp0lu0f4r7xzu2k89rm9tt448axf5tu6wlgphpy4c" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>BTCPrague</span> (<span class="italic">nprofile…py4c</span>)</a></span> where I'll be debuting the book physically. Use code DEFENDINGBITCOIN for your ticket, and come see me in Prague to get your signed copy! <br/><br/>I'm thrilled to be releasing this book because it's truly the best possible contribution to the space that I can make. I managed to find a way to bridge the two worlds I live in, those of my day job in cybersecurity and Bitcoin. I hope you find the book to be a helpful guide to improving your security, and that it makes a positive impact for Bitcoin as a whole. <br/><br/>I'll be posting more often about the Bitcoin cybersecurity topic, and hopefully that's valuable as well. <br/><br/>I'm looking forward to hearing what you think! <br/><br/> <img src="https://blossom.primal.net/678ab8b5ca6800770239bcce042d3fcbcd19e431cc144c599f5d379c2c149e4f.png"> </blockquote> 2026-05-20T19:42:27Z