\u201cGovernment agents are not active in Bitcoin developer and influencer circles.\u201d<\/em><\/p>\n As the war for global monetary supremacy wages on, you have to assume that the state is actively operating information warfare. This means that the state is operating and acting in order to preserve and expand it\u2019s own power. For that reason, it is sane and reasonable to assume that state operators are in the trenches of Bitcoin attempting to influence public perception, developer activity, and overall bitcoin adoption. If you think this is not happening then you are naive or you\u2019re incentivized to act against bitcoin in a different way. The sabotage of Bitcoin is not some tin foil hat conspiracy, the sabotage of Bitcoin is actively playing out in real time, but the big question is where the sabotage is taking place and what can you do to identify and act to counter the sabotage?<\/p>\n So let\u2019s zoom into Bitcoin of today, where conversation is happening around the future of Bitcoin in regards to dealing with Ordinals, or spam (if you are part of that camp)1<\/a>. The rise of Ordinals last year and the pressure they have caused on blockspace demand has surfaced new rivalries within the bitcoin maximalist community as memetic warfare is waged on what bitcoin is and how it should be used. The purpose of this article is not<\/strong> to make a political stand in this fight, but to point out <\/strong>places in Bitcoin that are prone to sabotage and where active sabotage campaigns might be actively waged. Seeing this division in a once divided front is enough to make one pause and consider what external forces are at work.<\/p>\n As we consider the infighting happening within Bitcoin, it is important to understand the different parties within bitcoin and how each of the powers balance each other out. In 2019, Nic Carter illustrated Bitcoin\u2019s Power Balance Model. This model shows the key roles in Bitcoin and the relationship between each one. You can see the circular feedback loop between Miners -> Devs -> Economic Nodes. In a vacuum these three roles would perpetually pump each other with nothing to keep them in check. At the heart of the model are the Users who keep Devs and Economic nodes in check.<\/p>\n Bitcoin\u2019s Power Balance Model by Nic Carter source<\/a>.<\/p>\n The one factor in the power model that touches each of the player in the model is the software of code. The software touches each of the roles in one way or another and this is probably the largest threat vector to all of Bitcoin. The simple activity of running code is how Bitcoin is eating the monetary world, so it is probably worth understanding the development process.<\/p>\n Let\u2019s now dig into the Bitcoin development process. As you know, making changes to Bitcoin is a slow and deliberate process. This is a big change from the \u201cmove fast and break things\u201d mentality of Silicon Valley. Many argue that this slow methodical process is actually one of Bitcoin\u2019s greatest strengths. In 2011, Gwern published \u201cBitcoin Is Worse Is Better\u201d<\/a> where he says \u201cHowever, in an example of \u2018Worse is Better\u2019, the ugly inefficient prototype of Bitcoin successfully created a secure decentralized digital currency, which can wait indefinitely for success, and this was enough to eventually lead to adoption, improvement, and growth into a secure global digital currency.\u201d This ugly inefficient code has gotten us here today, 15 years later, and in that time the slow methodical approach to Bitcoin development has been and will probably continue to be a part of the developer ethos.<\/p>\n The development process has even been formally documented in BIP 2<\/a> (Bitcoin Improvement Proposal). Here are the general steps in the BIP activation process:<\/p>\n Drafting the BIP<\/strong>: The first step is to draft a BIP following the template outlined in BIP2. This includes writing a detailed document or white paper that outlines the proposed changes. The BIP should be comprehensive, covering motivation, technical specifications, and rationale.Discussion and Feedback<\/strong>: Once the BIP is drafted, it\u2019s shared with the Bitcoin community for discussion and feedback and usually happens on platforms like the Bitcoin Dev mailing list, GitHub, and even Twitter. The purpose is to solicit feedback, refine the proposal, and begin to build consensus around it.Assigning a BIP Number<\/strong>: If the BIP is deemed to have potential and is unique, it\u2019s assigned a BIP number by a BIP editor<\/strong>. This is a formal acknowledgment that the BIP is under consideration.Formal Review<\/strong>: After the BIP is assigned a number, it enters a formal review phase. During this time, the BIP is scrutinized for technical soundness, feasibility, and compatibility with the Bitcoin protocol. This is where the devs try to break the bip and poke holes in the proposal.Revisions<\/strong>: Based on feedback and review, the BIP may undergo several revisions.Implementation<\/strong>: Once consensus is reached, the BIP is implemented in the Bitcoin Core codebase. This step involves actual coding and rigorous testing to ensure that the changes work as intended without introducing new vulnerabilities.Reaching Consensus<\/strong>: For a BIP to move forward, it needs to reach consensus among the Bitcoin development community. This is often the most challenging part, as Bitcoin\u2019s decentralized nature means that a wide range of stakeholders (developers, miners, users, etc.) need to agree on the change.Deployment<\/strong>: After implementation & consensus, the new version of Bitcoin Core including the BIP is released. Depending on the nature of the BIP, it might require a majority of miners or nodes to upgrade to the new version for the changes to take full effect.Activation<\/strong>: Finally, once the required threshold of network participants has adopted the new version, the changes proposed in the BIP are activated on the Bitcoin network.<\/p>\n Reading through this is incredibly helpful in understanding how change happens to Bitcoin. The problem I see is where are the single point of failures in this process and who the gatekeepers2<\/a> are for each step. Conversations happening in channels now are surfacing weak points or non documented parts of the development cycle. For example, Bitcoin Inquisition. This is the in space between steps 2 and 3.<\/p>\n Bitcoin Inquisition<\/a> is a non-documented part of the Bitcoin development process. It was proposed by and administered by AJ Towns in 2022. Here is a very brief summary of why and what it is.<\/p>\n \u201cI think the weakest link in that [bitcoin development] loop is the first one: what if we did activate soft forks on the default signet prior to the code being merged into core? To that end, I\u2019m proposing a fork of core that I\u2019m calling \u201cbitcoin-inquisition\u201d<\/strong>, with the idea that it branches from stable releases of core and adds support for proposed changes to consensus (CTV, ANYPREVOUT, TLUV, OP_CAT, etc\u2026) and potentially also relay policy (relay changes are often implied by consensus changes, but also potentially things like package relay).\u201d<\/em><\/p>\n \u2013 AJ Towns on Bitcoin Inquisition<\/em><\/p>\n The reality is that the Bitcoin Inquisition is live and well. AJ runs a special separate fork of Bitcoin core and acts as the sole admin for testing BIP\u2019s. This is not documented in BIP-2, but has just been accepted as process by core devs. This is a curious development of how tribal devs can make changes how they see fit, without documentation.<\/p>\n At this point we\u2019ve run through the roles in Bitcoin, the steps in the development process, and even identified a glaring hole in the development process. Let\u2019s now dig into what is sabotage.<\/p>\n Sabotage. (noun) \/\u02c8s\u00e6b.\u0259.t\u0251\u02d0\u0292\/<\/p>\n Definition: The deliberate destruction, damage, or obstruction of something, typically for political or military advantage. Sabotage is often carried out covertly and with the intention of hindering operations, activities, or plans of an opponent or competitor.<\/p>\n Verb Form:<\/strong> Sabotage (sabotaging, sabotaged)<\/p>\n Usage in a Sentence:<\/strong> \u201cThe bridge collapse was found to be the result of sabotage by enemy agents.\u201d<\/p>\n For purpose of this article, let\u2019s frame sabotage specifically in relation to Bitcoin Sabotage. Bitcoin Sabotage is the deliberate destruction of Bitcoin, or obstruction of Bitcoin development or adoption, for political advantage.<\/strong> This is the frame. This is what we are up against. With that in mind let\u2019s now dig into how sabotage is waged. Conveniently our very own CIA is masters at sabotage and have been waging sabotage tactics in warfare for over a century.<\/p>\n In the 1940\u2019s, the CIA shipped a field manual called Simple Sabotage Field Manual. The purpose of this was to distribute to operators a practical manual on how to conduct sabotage operations behind enemy lines. While this manual is 80 years old, it reveals some classical tactics in the art of sabotage.<\/p>\nBitcoin\u2019s Power Balance<\/h2>\n
Bitcoin Development Process<\/h2>\n
Bitcoin Inquisition<\/h3>\n
The Bitcoin Sabotage<\/h2>\n
Simple Sabotage Field Manual<\/h3>\n