❤ View quoted note →

Rug the spammers! Run Bitcoin Knots and support BIP110 and The Cat 🤙 Because Bitcoin is Freedom Money, NOT a shitcoin for jpegs. View quoted note → View quoted note →

Fucking Legend! Maybe its time for Costa Rica to consider #Bitcoin Freedom Money?

Based! Also remind yourself that there are no shitcoins in El Salvador. Only Bitcoin Freedom Money 🤙

Majority of Core devs are not only compromised but their so called arguments have been complete bullshit. We already know that but now raw data from the blockchain proves it. It really shows when they (Citrea and their cucks) are trying to turn Bitcoin into an Ethereum like shitcoin. Core's V30 is a malware and an attack on Bitcoin. Spam on Bitcoin is just disgusting. Run Bitcoin Knots and support BIP110 because Bitcoin is Freedom Money. "The “blocks must be full” belief fails on (at least) three independent grounds: Empirically: Spam doesn’t meaningfully contribute to security budget. 36% of block space produces 1% of revenue. Fees are at 3.5-year lows despite massive increase in non-financial usage."

Issue #4 - The "Blocks Must Be Full" Myth

Data, queuing theory, and the case for healthy headroom

True, Bitcoin in self-custody is The Only Freedom Sovereign Money. View quoted note →

Satoshi sends his regards. #Bitcoin is THE Global Most Secure Decentralized Unconfiscatable Peer-to-Peer Scarce Hard Sovereign Freedom Money, The Greatest Store of Value and The Strongest Hope for Humanity.

View quoted note →

Sorry Dave, I’m afraid I can’t do that! PCs refuse to shut down after Microsoft patch

Patch Tuesday update makes Windows PCs refuse to shut down

: Microsoft claims it's a Secure Launch bug

Truth! Run Bitcoin Knots and support

BIP-110

BIP-110: Reduced Data Temporary Softfork

Temporarily limit the size of data fields at the consensus level to protect Bitcoin

because Bitcoin is Freedom Money. Fuck spam. View quoted note →

Bitcoin separates money from state. View quoted note →

Based! View quoted note →

Winds of change. View quoted note →

Compromised Core devs fucked up with their malware Core V30. From @secsovereign on X "INDEPENDENT POST-MORTEM ANALYSIS: Bitcoin Core v30 Wallet Deletion Bug Bitcoin Core had "dangerous" code that could cause the complete loss of wallet data that existed in the code for 3+ years but was unreachable due to an earlier failure. In 2022, migration cleanup code used fs::remove_all() which could delete the entire /wallets/ directory. However, before 2025, the bug couldn't actually execute because the backup restore step would fail early before reaching the dangerous fs::remove_all() call. In 2024, maintainer ryanofsky explicitly warned in a code review that this pattern "could wipe out a lot of other data" and suggested a followup PR. As far as I can tell, no followup was created. Then in 2025, PR #32273 changed backup locations, which removed the early failure that was hiding the bug. Now the dangerous cleanup code could actually execute, and users lost all their wallets when migration failed. The fix came 18 days after the bug report, but the dangerous pattern should have been addressed when warned. Using fs::remove_all() on user data directories is a fundamental software development anti-pattern that should never have been merged. The original "dangerous" pattern in PR #19602 was submitted and self-merged by achow101 2 years later with basically zero review. The second PR #32273 that enabled the bug was submitted by a contributor, the situation was explicitly noted by ryanofsky "if migration fails the wallet directories are deleted and recreated" but it was not flagged as dangerous, and then it was merged by achow101 ~3.5 months later. There were also earlier concerns. Contributor furszy reported partial data loss in 2022, and maintainer laanwj expressed concern about wallet deletion in 2021, but only ryanofsky's 2024 code review warning identified the exact bug pattern that caused complete directory deletion. A maintainer explicitly warned about the exact bug pattern that would cause complete data loss, suggested a followup PR to fix it, and then nothing happened for 2 years until users actually lost all their wallets. The warning was clear, saying it "could wipe out a lot of other data" and recommended moving away from fs::remove_all(). Despite this, no followup was created, no fix was implemented, and the dangerous code remained until it executed and deleted users' wallets. This is a governance failure because maintainer warnings about data loss risks need tracking and followup. This shows a complete failure of the followup tracking process for critical warnings about catastrophic risks. Jan 12, 2026 · 8:58 PM UTC"

As of today 16 January 2025 Bitcoin indexes directory is 62GB This directory is created when you enable txindex=1 option in bitcoin.conf which gives you the ability to inspect all transactions using bitcoin-cli getrawtransaction command.

Volume to the max to feel the golden years of music Vanila Ice - Ice Ice Baby

🚀 Got #Bitcoin? View quoted note →

BIP110 makes Bitcoin stronger against spammers and abusers. Bitcoin is Freedom Money, not jpegs.

Fuck Epstein's banker Jamie Dimon!