pull down to refresh

FIrst off, taproot wizards are nothing but a bunch of parasites and middlemen.

This was an interesting podcast , just try block out all the wizard shilling and everything else, just focus on the important stuff. It gave insight into activation methods and Bitcoin consensus.
The Bitcoin Improvement Proposal (BIP) process is a method for proposing changes and improvements to the Bitcoin network, currently overseen by Lukewarm Jr. He is the gatekeeper in the numbering of BIPs. You are unable to test out proposals on testnet, if the BIP you are interested in doesn't have a number. The Ordinals BIP and I imagine many others, is not being assigned a number.
No matter your views on the people discussing this or your opinion on changes to Bitcoin (I side with someone like John Carvalho, in that any change should be looked at as an attack on BItcoin before being implemented), the BIP system and consensus changes and activation seems to be a flaw in a decentralized protocol. I have seen from nostr that fiatjaf (creator of nostr) dislikes their NIP implementation and inefficiencies in the process.

Anyway, here is a summary of the podcast for those unable to listen -
01:00:00 The early history of Bitcoin soft forks, which included changes made by Satoshi Nakamoto and subsequent developers with minimal controversy. Casey mentions a few soft forks, such as pay to script hash and Segregated Witness (Segwit), with Segwit being the first controversial one. During the early days of Bitcoin, the community was tight-knit, and changes were made with minimal controversy since Bitcoin had little value. However, as Bitcoin gained value and larger mining operations emerged, stakeholders began to have different interests, leading to more strategic arguments and a breaking apart of camps. The speaker notes that before Segwit, there were several small soft forks, such as Pay to Script Hash (CSV), and Check Sequence Verify (CSV), which felt relatively insignificant compared to Segwit.
01:05:00 The Segwit upgrade as a significant breaking point in Bitcoin's history, leaving emotional baggage and division within the community. Guest mentions the discovery of Covert ASIC Boost, which led to disagreements and inefficiencies in the Bitcoin Improvement Proposals (BIPs) process. The BIP numbering scheme was criticized for being unnecessarily inefficient and a source of power aggregation, leading to roadblocks and delays in critical upgrades. They compare this process to the bureaucracy of government and finds it ironic that Luke-jr, a BIP editor, is known for his Byzantine behavior.
01:10:00 Bitcoin Improvement Proposal (BIP). The ideal state of a BIP begins with an idea posted to a Bitcoin mailing list for discussion. Once the document, called a BIP, is written and opened as a pull request on GitHub, the BIP editor reviews it for style and relevance to Bitcoin. If approved, the BIP is given a number and merged into the repository. The purpose of a BIP number is to identify the document among others. Some BIPs serve as technical documentation, while others involve consensus changes to Bitcoin. After acceptance, the consensus process begins, and people decide whether to implement the change. This process is fraught with uncertainty and disagreement, and some influential figures in Bitcoin, such as Peter Willy and Greg Maxwell, are no longer actively driving changes. Instead, the community is encouraged to come to consensus, and Bitcoin Core implements the changes. The ideal upgrade process involves proposing changes through the BIP process, with someone else writing the implementation, and a fork of Bitcoin CL activating the change. However, they believe this ideal may not be achievable.
01:15:00 Current state of Bitcoin development and the challenges of reaching consensus on changes to the network. The speaker notes that the Bitcoin Core team no longer holds the same political power they once did, and the new maintainers are hesitant to make risky changes without clear consensus from the community. The speaker argues that it is now the responsibility of the wider Bitcoin community to make it clear that a proposed change has consensus and is not a hard choice for the maintainers. The speaker also shares a story of Jeremy, who followed the BIP (Bitcoin Improvement Proposal) process to propose a change but faced opposition from Blockstream, ultimately resulting in the proposed change being killed. The speaker questions how consensus is decided and pokes fun at the process, suggesting that it is not as simple as a Twitter poll or the Bitcoin Core maintainers' algorithmic feed.
01:20:00 Complexity of determining consensus in the Bitcoin community, particularly through the lens of social media platforms like Twitter. He argues that consensus should not be based on Twitter opinions alone, as many Bitcoin users are not active on the platform. Instead, consensus should be determined through the involvement of key stakeholders, such as developers and miners. The speaker also explains the process of activating Bitcoin upgrades, which involves both developer and miner consensus, and the importance of miners understanding the technical aspects of the changes they are implementing. Despite the challenges, the speaker remains optimistic that the Bitcoin network can reach consensus and continue to evolve.
01:25:00 The role of miners in activating a soft fork in the Bitcoin network. Unlike social media consensus, where individuals may seek the opinions of their peers before making decisions, Bitcoin's soft fork activation process relies on miners. Miners are not asked for approval but are instead asked to enforce the new rules. If only a minority of miners activate the soft fork, upgraded nodes will follow them, while unupgraded nodes will follow the majority hash rate. This process ensures the safety and continuity of the network, despite potential misconceptions or misunderstandings about the role of miners in the consensus-building process.
01:30:00 The concept of a "lock-in timeout" in the context of Bitcoin upgrades. This timeout refers to a point in time when nodes will begin enforcing an upgrade regardless of whether all participants have signaled for it. Miners who have not upgraded may produce invalid blocks, resulting in lost rewards and fees. The speaker also explains different activation methods, including "speedy trial," which allows miners to activate an upgrade early if they signal for it, and "lot true," which requires a consensus among all nodes for activation. The speaker expresses a preference for "lot false" and "speedy trial," but acknowledges the importance of the checks and balances system in Bitcoin development. The debate over Bitcoin activation methods is compared to the metaphor of building a nuclear power plant and a bike shed, with the latter becoming the focus of more discussion due to its more relatable nature.
01:35:00 Inefficiencies and power struggles within the Bitcoin development process, using the example of the Opcat protocol and the need for a BIP (Bitcoin Improvement Proposal) number. The speaker expresses frustration with the current system, where a small group of individuals, including Luke Jr, have control over the merging of new features into the Bitcoin core. The speaker argues that the process is unnecessarily inefficient and calls for a more democratic approach, suggesting the elimination of BIP numbers or allowing multiple repositories. The speaker also reflects on the changing dynamics of the Bitcoin community, with the old guard stepping back and leaving the current group to navigate the development process.
01:40:00 Bitcoin's community and the absence of dominant figures or entities trying to push their agendas. He mentions the presence of various groups such as the "laser eyes," "ordinals camp," and "sandwiches," each with their unique visions for Bitcoin. The speaker also notes the departure of the "big blockers" and the potential need for new ways to build consensus among stakeholders. He expresses his support for the CTV proposal due to its simplicity and the ability to allow experimentation without forcing adoption on those who don't want it. The speaker also touches upon the origins of Bitcoin and the opcat concept.
01:45:00 Removal of the OP_CAT operation from Bitcoin's codebase. OP_CAT is a stack operation that combines two strings on the stack into one, but its naive implementation led to a potential issue where the stack size could double each time it was used, leading to a risk of running out of memory and crashing the computer. The speaker speculates that Satoshi Nakamoto, Bitcoin's creator, may have removed it due to this issue, but there was also a stack size limit in Bitcoin that may have played a role. The speaker also mentions that OP_CAT was removed along with 12 other opcodes in a PR called "Misschanges" with no comments, and expresses a belief that Bitcoin needs more fun and excitement to move forward.
01:50:00 Potential of Opcat and the desire for innovations like covenants, vaults, and a trustless bridge in Bitcoin. He believes that Opcat has the potential to bring these innovations back to Bitcoin and that the community should focus on implementing them instead of debating. The speaker also mentions the concept of Taproot Wizards, which aims to educate Bitcoin users about potential improvements and create a contingency of informed individuals. Despite the controversy surrounding Opcat, the speaker sees it as a neutral addition to Bitcoin education and progress.
Thanks for this write up.
ā€˜ No matter your views on the people discussing this or your opinion on changes to Bitcoin (I side with someone like John Carvalho, in that any change should be looked at as an attack on BItcoin before being implemented), this BIP system seems an inherent flaw in a decentralized protocol. Nothing but a walled garden. ā€˜
reply
thanks! I have since edited the original sentence you quoted but I prefer this, so appreciate you reposting it!
No matter your views on the people discussing this or your opinion on changes to Bitcoin (I side with someone like John Carvalho, in that any change should be looked at as an attack on BItcoin before being implemented), this BIP system seems an inherent flaw in a decentralized protocol. Nothing but a walled garden.
221 sats \ 1 reply \ @oomahq 16 Mar
You are unable to test out proposals on testnet, if the BIP you are interested in doesn't have a number.
This is a non-issue. No one needs permission to start his own signet network with whatever consensus rules they want and do any kind of test on a persistent network that mimicks mainnet even better than testnet.
Additional context: signet is a new kind of testnet introduced in 2020 that is meant to address testnet's shortcomings. Testnet sometimes doesn't see any new blocks for hours, or hundreds of blocks come in at once, leading to huge chain reorganizations. This is no good at all to test real life scenarios.
In comparison signet doesn't use proof of work to validate new blocks. Blocks are simply accepted if they come signed with the private key of the entity who bootstrapped the network. And that entity can "mine" (rather issue) new blocks at whatever rate they want (usually every 10 minutes).
There is an default/official Bitcoin signet which Bitcoin Core connects to when started in signet mode, but this mode is designed to be used by anyone who wants. E.g. the Mutiny Wallet team runs their own signet blockchain.
The Ordinals BIP and I imagine many others, is not being assigned a number.
Ordinal theory doesn't need a BIP because it's doesn't really have anything to do with Bitcoin and it's a scam, not an improvement.
Additional context: Ordinal theory claims to be able to differentiate the different "1's" inside number 4, and assign them an identifier. And further claims that when you do math like 4-1 you're able to tell which number 1 you removed from the number 4. It really is just a scam to separate fools from their sats.
I'd consider the BIP review process compromised if a draft for such nonsense got accepted and assigned a BIP number.
reply
fair points. thanks
reply
Yes, Ordinals has exposed how utterly retarded Bitcoin has become. We used to fix exploits routinely, now we have countless complete whoppers arguing that Bitcoin is a data storage system, captured Core devs shutting down discussions about BIPS to patch the exploits being used and arguing that the only important thing is what miners want, and progress halted as a result of the scams being built on Bitcoin because of the obvious correlation between spam wankers and promoters of the various OP codes currently being talked about.
So, if you want your favourite scaling proposal to be merged, get on board with stopping the spam first. You don't scale before you fix bugs, otherwise you just scale the bugs!
reply
SegWit was a mistake. Not enough brain power was spent on considering the ramifications.
I was also a massive hypocrisy because it was an effective block size increase implemented by the same people who fought against increasing the block size.
I'm honestly losing faith in the core dev team.
reply
The speaker questions how consensus is decided and pokes fun at the process, suggesting that it is not as simple as a Twitter poll or the Bitcoin Core maintainers' algorithmic feed.
And this is why Bitcoin Core innovation has been steadily stagnating.
One can follow the meticulous process for submitting a BIP and gathering feedback, but all it takes is an angry hornets nest on X/Twitter to simply post that they don't want it (or in the case of removing something, want it), then the media and Youtubers pick up on the story, spreading the flames everywhere. And then that's the end of that.
Actual, productive discussion on the mailing list and Github is drowned out by the torrent of angry tweets.
It is also the reason why they can't remove Ordinals.
reply