The coretards who constantly scream about censorship are the ones who censor. Core censored Bitcoin contributers on github, on the mailing list, on the Bitcoin forum and now even on reddit. Core is completely compromised and corrupted.

Fuck spam. This Bitcoin block is abused with 3MB degenerate inscriptions. Disgusting. An average transaction is less than 200 Bytes. That means that this block could have included 15 000 monetary Bitcoin transactions that move Bitcoin / transfer value. BIP 110 and Bitcoin Knots fix those disgusting inscruptions. Bitcoin is THE Global Most Secure Decentralized Unconfiscatable Peer-to-Peer Scarce Hard Sovereign Permissionless Freedom Money, The Greatest Store of Value and The Strongest Hope for Humanity. Rug the spammers! View quoted note →

Repost the truth. Run #BIP110 & #BitcoinKnots 🤘 Lets rug the spammers, scammers, shitcoiners and bad actors! View quoted note →

Running BIP 110 & Bitcoin Knots defending Bitcoin Freedom Money Yes, it is that important. Rug the spammers! View quoted note →

Despite all the liquidity flowing into AI stonks are not feeling well.

ETFs are selling Bitcoin low and will be buying it high. I think that is good opportunity for Bitcoin Plebs.

Running BIP110 View quoted note →

Magnifique View quoted note →

By @SteveSimple A "Key Takeaway" of how Taproot was advertised to the community was: "Tapscript removes the 10,000-byte script size limit and 201-opcode cap from legacy Script, enabling more complex contracts while using a per-script signature operations budget for DoS protection" spark.money/glossary/bip-342 Removing these limits was based on Taproot's clever avoidance of the primary denial of service (DoS) attack vector in pre-Taproot scripts. Specifically, Taproot disabled Segwit's inefficient multisig method, and redesigned its script resource accounting, so those DoS concerns were gone. With the DoS no longer in play, the justifications for raising the limit were: 1) it enables more complex contracts (widely stated), or 2) there's no reason not to (why not?) That rationale was over four years ago. Taproot was activated in November 2021. To date there have been 424,471 Taproot scripts larger than 10KB that have been revealed through spending. The analysis script (which you can verify from your node using the GitHub link) evaluates all scripts of this type to date. Every revealed Taproot script-path spend over 10KB is evaluated, none excluded. The results are clear. Of the 424,471 scripts to date: 1) 99.98% were data storage. 2) 99.89% placed their payload in a branch that can never execute (OP_FALSE OP_IF provably dead code). 3) 0.091% were bulk data-push scripts that did not use the dead-code method (no dead code but >50% of the bytes in the script were pushes of data larger than 80 bytes). 4) 0.018% can be classified as complex executable contracts (not data storage). Almost all of these are BitVM-like scripts. 5) Exactly one (1) of the complex scripts that were not data storage was a multisig using hundreds of OP_CHECKSIGADD. In hindsight, we now have overwhelming evidence of how the raised 10KB Taproot script limit was used in practice. It was used for data storage. There was essentially no on-chain verifiable demand for enabling complex spending scripts that were not data storage. And it isn't free. Every byte sits in the witness of a spend. It's downloaded, validated, and stored forever by every archival node, at the discounted witness rate that makes dumping it cheaper than real transactions. Removing the cap enabled essentially no complex contracts (0.018%). It externalized a permanent storage-and-bandwidth cost onto everyone running Bitcoin. And for what. For data-storage scripts that are 99.89% unexecutable dead-code branches.

GitHub

GitHub - Unbesteveable/taproot-10kb: How the raised 10KB Taproot script-size limit is used in practice: dead-code data vs bulk data vs executable contracts, from a Bitcoin Core node.

How the raised 10KB Taproot script-size limit is used in practice: dead-code data vs bulk data vs executable contracts, from a Bitcoin Core node. -...

#BIP110 & #BitcoinKnots because Bitcoin is Freedom Money

#BIP110 & Bitcoin #Knots

I think the cantillonaires and banksters are really scared of Bitcoin being Freedom Money and working as intended.

Core are completely corrupted and compromised. Core V30+ is a malware and an attack on Bitcoin Freedom Money.

This will be pure diamond 🤘

💯 Don't forget that Peter Thiel from Palantir, Jameson SLopp, Erik Voorhees, Orkun Mahir Kılıç and other bad actors and scammers are investors in Citrea. Citrea's centralized created out of thin air slavery shitcoin on top of Bitcoin. View quoted note →

#BIP110 "A deep-dive game theory analysis and code audit of Bitcoin's "Reduced Data Temporary Softfork", examining what the mechanism design reveals and what the code actually does."

melvin.me

BIP-110: Game Theory & Code Audit

A deep-dive game theory analysis and code audit of Bitcoin

El Salvador keeps winning with Bukele

Bullish BIP-110 View quoted note →