Could we all agree to a temporary soft fork that only suspends the Witness Discount and limits Op_Return to 83 bytes for 18 months? Is that doable? Still a big concession from the Knots/Pro-Filter crowd since it doesn’t invalidate TapScript.

Satoshi and the early Devs built Bitcoin as a well fortified monetary protocol within finite dimensional limits on the Internet. After Satoshi left, creeping relaxation of filters & limits started. 42, then 83 bytes conceded for Op_Return Then we increased the block size via the witness discount and introduced new scripts without sufficient datacarrier limits and other constraints on SegWit & Taproot. We have to get Bitcoin confined and protected with narrow data limits to narrow its focus on Money.

Spam Mitigation = Good for Bitcoin Spam Facilitation = Bad for Bitcoin Spam Proliferation = Bad for Bitcoin If you know, you Knots. Datacarrier = 0. Filters up.✊🏼

It would be preferable if there was pent up monetary demand for a change to Bitcoin so that any new design space or surface that gets introduced is filled up quickly with positive sum monetary activity vs. zero pent up demand that creates a void for Spammers to fill (see Taproot). Run Knots. Filters up.

Fake pubkeys and other forms of advanced steganography have not been mass weaponized against Bitcoin to the same degree as Inscriptions were. Why? Because it’s more expensive to the Spammer and harder to mass Weaponize. Pro-Spam people are shitty Byzantine Generals.

Bitcoin won’t defend us from Fiat Inflation or Dollar Slavery if we don’t try to defend Bitcoin and our full nodes by mitigating Spamflation on chain. The Fiat Money Printer is a Spam Printer. If you know, you Knots. Filters up.✊🏼🫡

Cold storage isn’t enough… the full node is the foundational bedrock of Bitcoin’s security & resilience. True Bitcoin self custody and true solo mining are not possible unless you’re using your own full node/creating your own block template. Yes, you need to get your coins off the exchange… but you can’t truly resist censorship unless you’re running your own full node. Spam Filters help you use Bitcoin as censorship resistant money. View quoted note →

The Cloudflare issue is just another reason why every Bitcoin user needs to keep leveling up their Self-Sovereignty game. It is impossible to verify Bitcoin and use it without permission to resist censorship unless you run your own Full Node. If you know, you Knots. Filters up. ✊🏼🫡

People have been warning about a Cyber Pandemic for a while. Is the Internet Outage on the same day as the Epstein Vote and Repo Madness worries growing a coincidence? I don’t think we can believe in coincidence anymore.

Today, large websites on the Internet are down to a Cloudflare issue. Beginning of the Cyber Pandemic? Seems like a possible next Black Swan crisis given the tandem of Epstein & Repo Madness in the headlines. I hope I’m wrong. But either way Bitcoin remains the Dominant Strategy. Fortune favors the HOLD.

The risks of Spam/CSAM on Bitcoin transcend legal risks. The economic, ethical, technical, reputational, brand, and mission creep risks of all Spam on Bitcoin are sufficient to oppose increasing Bitcoin’s Spam surface, even if there were no legal risks. The Truth > Fiat Law

Op_Codes gave Satoshi problems and concerns because they increased Bitcoin’s risk surface, so Satoshi disabled certain Op_Codes, including Op_Return. Interestingly, Op_Codes are at the heart of the Spam debate today. We should be wary of these Bitcoin Op_Codes. Filters up.✊🏼

Maximize Bitcoin’s Monetary Sats/vByte signal to Arbitrary Sats/vByte noise ratio. If you know, you Knots. Filters up.✊🏼🫡

Spam doesn’t make your Bitcoin fee estimation better. Spam distorts your Bitcoin fee estimation and increases your propensity to overpay for block space when you need to use Bitcoin’s monetary channel. Maximize the monetary signal to arbitrary noise ratio. Run Knots.✊🏼🫡

Given that Lightning is heavily dependent on Bitcoin users being able to run full nodes on L1, it seems we should avoid stuffing unnecessary data in Op_Codes to run Lightning channels so that as many people can run a Bitcoin Full Node + a Lightning node, all things being equal. The Lightning White Paper even emphasizes the importance of a healthy Bitcoin full node layer on L1.

Spam increases the propensity to overpay for Bitcoin block space, all things being equal. Filters up. ✊🏼🫡

90%+ of us were minding our own fuckin business stacking and trying to amplify the Bitcoin signal until Peter ReTodd and Core declared war on the policy layer. Nobody asked for 100kb Op_Returns! Op_Returns at 83 bytes removes huge risks from Bitcoin’s path!! Filters up.✊🏼

Spam makes fee estimation on Bitcoin worse. All things being equal, Spam increases the propensity to overpay for block space. 2nd and 3rd order malinvestment effects of Spam are not appreciated. For a higher quality Bitcoin experience, run Knots. Datacarrier = 0 Filters up.✊🏼

There’s a shitstorm coming and it’s currently at Bitcoin’s gates. It rhymes with Shitrea and ShitVM. Call bullshit when you see it. “Compute anything on Bitcoin” and Go, Chess, and Poker on Bitcoin is not The Way. If you know, you Knots. Bitcoin is Money. Filters up.✊🏼🫡

Afaict, BIP 444 UASF mitigates risks of Spam and upgrades Bitcoin’s monetary quality, presenting all Bitcoiners with more purchasing power upside. Core v.30 prioritizes special interests and opens up new Pandora’s Boxes on Bitcoin. Run Knots, Ocean, and DATUM. Filters up.✊🏼🫡