First draft of the BIP for SIGHASH_UNIFIED just dropped:
groups.google.com/g/bitcoin-devel/c/0F1-AFDQMaA
Luke Dashjr
Luke Dashjr is an American software developer known for his long-standing role in the development of Bitcoin Core and for co-founding the Bitcoin mining pool Ocean. More on Wikipedia
-
Luke Dashjr reposted
Kyle 🐆
@kwsantiago
-
Luke Dashjr reposted
privacymatters21m
@privacymatter21
Remember when we were repeatedly told that it was impossible to prevent spam on Bitcoin. Yeah, that was a lie meant to gaslight you into accepting the network's degradation so shysters can profit from it.
-
Luke Dashjr reposted
Extractive Ghost of Unhosted Marcellus 👻
@oomahq
Evergreen meme.
-
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
"The attackers reportedly failed to mine a Bitcoin block during the hijack, meaning no block rewards were collected."
OCEAN advised other miners to send the attackers 0.16202083 BPD ($10,510) after this article was published, at 5:21pm and 10:24pm. At this very moment, OCEAN is still telling their miners to reward 0.08123485 BPD ($5,270) to the attackers, and their website states an intent to reward them another 0.33029017 BPD ($21,400) in the next 24 hours.
OCEAN themselves collected 0.00330655 BPD ($210) profit from the attack, and intends to keep another 0.0066058034 BPD ($440) for a total of nearly 0.01 BPD ($650).
Yes, that's right: OCEAN is profiting from a cyberattack on their own customers, and rewarding the attackers. -
Bitcoin News
@BitcoinNewsCom
🚨 64,000 BITCOIN MINERS HIJACKED IN MASSIVE ATTACK
An estimated 64,000 Bitcoin miners representing 13 EH/s of hashrate were reportedly hijacked overnight, with their mining power redirected to OCEAN mining pool and payouts assigned to an attacker-controlled Bitcoin address.
The attack reportedly began around 8 PM CT on November 14.
OCEAN’s dashboard shows a sharp spike in hashrate, briefly approaching 50 EH/s before falling back toward 40 EH/s.
CoreX Hosting first raised the alarm, reporting that miners were being redirected without authorization.
One affected operator says their entire mining farm was hijacked and identified Luxor’s Commander mining management software as the source of the compromise.
Other operators reported similar unauthorized pool changes several days earlier, potentially pointing to a broader incident.
CoreX later reported that the attack appeared to be over, with the hijacked hashrate falling from 13 EH/s to approximately 100 PH/s.
The attackers reportedly failed to mine a Bitcoin block during the hijack, meaning no block rewards were collected.
However, affected miners permanently lost the opportunity to earn Bitcoin during the attack. That hashing time cannot be recovered.
The full scope of the breach and whether Luxor Commander was compromised have yet to be independently confirmed.CoreX Hosting @CoreX_Hosting
Just a heads up, there is a big miner hack going on as we speak. Miners are being pointed at @ocean_mining with BTC address bc1qphukp9rjfc4rcej7erpm9ae20xmtspw8pcddrr .
Luke Dashjr
@LukeDashjr
"The attackers reportedly failed to mine a Bitcoin block during the hijack, meaning no block rewards were collected."
OCEAN advised other miners to send the attackers 0.16202083 BPD ($10,510) after this article was published, at 5:21pm and 10:24pm. At this very moment, OCEAN is still telling their miners to reward 0.08123485 BPD ($5,270) to the attackers, and their website states an intent to reward them another 0.33029017 BPD ($21,400) in the next 24 hours.
OCEAN themselves collected 0.00330655 BPD ($210) profit from the attack, and intends to keep another 0.0066058034 BPD ($440) for a total of nearly 0.01 BPD ($650).
Yes, that's right: OCEAN is profiting from a cyberattack on their own customers, and rewarding the attackers. -
Luke Dashjr
@LukeDashjr
If you forked off from Bitcoin to defend and enable CSAM distribution (ie, you assert Spamcoin is Bitcoin), you are a bad person. Comment here so I can block you.
-
Luke Dashjr
@LukeDashjr
As requested, you can now optionally re-enable Manifest V2 (for @ublockorigin) also:
github.com/luke-jr/gentoo-overlay-luke-jr-llm/blob/master…
Luke Dashjr
@LukeDashjr
If you want a decently secure web browser, compiled by yourself, I have @ClaudeAI maintaining Chromium ebuilds for @Gentoo here:
github.com/luke-jr/gentoo-overlay-luke-jr-llm
Use at your own risk. Browsers still have daily security issues. Recommend only running it on a separate, untrusted computer. -
Luke Dashjr
@LukeDashjr
First draft of the BIP for Bitcoin's BLAKE2b PoW change just dropped:
groups.google.com/g/bitcoin-devel/c/cArFwXT4m2Q -
Luke Dashjr reposted
Eduardo Prospero @edprospero23
For Bitcoin to maintain its value proposition, nodes would have to be in control.
If miners are in control, and three companies control block creation, Bitcoin is not worth anything.
This shouldn't be controversial. -
Luke Dashjr
@LukeDashjr
With 5* GB of cache, this can now compile (simple) security updates to Chromium in under 15 minutes.
github.com/luke-jr/gentoo-overlay-luke-jr-llm/blob/master…
(* 13 GB on an uncompressed filesystem)
Luke Dashjr
@LukeDashjr
If you want a decently secure web browser, compiled by yourself, I have @ClaudeAI maintaining Chromium ebuilds for @Gentoo here:
github.com/luke-jr/gentoo-overlay-luke-jr-llm
Use at your own risk. Browsers still have daily security issues. Recommend only running it on a separate, untrusted computer. -
Luke Dashjr reposted
The Heretical Liberal 🇨🇦
@Rob_ThaBuilder
This is the kind of headline you read and your mind just refuses to believe it. You assume there must be some exaggeration or misinformation, or some nuanced fact is being exploited to paint an inaccurate picture.
Because surely it cant be this, right? Surely theres no way a 20 y/o man could have his sentence overturned because it wasnt established at his trial whether he "thought he was having consensual sex with a 10 y/o".
But then you read the article (article 🔗'd in reply) and thats literally what it is. This is what makes ppl think our leaders hate us, this is what deligitimizes the Liberal project in many people's minds.
Like many liberal-minded people of my generation, I grew up believing that progressivism promised a better way, a more fair and just world, where people really WERE judged by the content of their character and not the color of their skin.
When I see stuff like this, i cannot help but think something is deeply wrong with the state of the modern Left. After all, to paraphrase the psycho from No Country For Old Men:
"If the liberalism you followed brought you to this....of what use was your liberalism?" -
Luke Dashjr reposted
XBT | Hardfork cguida | ⚡🪢
@cguida6
If your economy consists only of a bunch of people sitting around waiting to get rich, your economy might be a Ponzi scheme
Michelle Weekley
@michelleweekley
One of the hardest things in the world for people to do is nothing.
You just wait.
Your patience will be rewarded.This post is unavailable. See it on X. -
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
A new Bitcoin Development mailing list has also been established:
groups.google.com/g/bitcoin-devel
The former mailing list has been subject to censorship. The new list is intended to provide an open forum for Bitcoin development discussions, including BIP proposals. -
Luke Dashjr
@LukeDashjr
The official Bitcoin Improvement Proposals (BIPs) repository is now located at:
github.com/Bitcoin-specs/BIPsPost not available here, view on X
Luke Dashjr
@LukeDashjr
A new Bitcoin Development mailing list has also been established:
groups.google.com/g/bitcoin-devel
The former mailing list has been subject to censorship. The new list is intended to provide an open forum for Bitcoin development discussions, including BIP proposals.
Luke Dashjr
@LukeDashjr
An amendment to BIP 3 is proposed to formally designate the new list as the BIP development mailing list:
github.com/Bitcoin-specs/BIPs/pull/3
All messages to the new list will be held for moderation until Friday, November 13, 2026, to give devs time to subscribe before discussions resume.
Luke Dashjr
@LukeDashjr
BIP authors and Bitcoin developers are encouraged to subscribe to the new list and continue their work through the official BIP repository.
-
Luke Dashjr reposted
Cyber Security News
@The_Cyber_News
‼️ Google Chrome 0-Day Vulnerability in the Wild to Execute Malicious Code Remotely
Details: cybersecuritynews.com/google-chrome-0-day-exploited/
Google has fixed a Chrome zero-day that attackers are already using. The flaw is tracked as CVE-2026-125350, and it lets a remote attacker run malicious code in the browser.
Google’s Stable channel update moves Chrome to version 157.0.8103.50/.51 for Windows and Mac and 157.0.8103.50 for Linux.
The rollout will reach users over the coming days and weeks. CVE-2026-125350 is a high-severity use-after-free bug in Chrome’s XML component. Google says it is aware that an exploit for this flaw exists in the wild.
#cybersecuritynews -
Luke Dashjr
@LukeDashjr
It's been long enough, and I hear nvk is going around pretending humans couldn't find the Coldcard defect.
So public disclosure time. No clue if Coinkite fixed these after I told them privately. I'm not claiming these can all be weaponised, or that they're definitely all bugs.Post not available here, view on X
Luke Dashjr
@LukeDashjr
8) The fix prevents the PRNG from getting compiled/linked in, but only as a build time tweak. There should probably be a runtime assertion to ensure the real RNG is being utilized properly.
Luke Dashjr
@LukeDashjr
9) If the new rng_get is called from the wrong (not Python exception safe) context, and the RNG times out, mp_raise_OSError could invoke undefined behaviour. Likely a crash, but not necessarily, and even a crash at boot could risk bricking slow devices.
-
Luke Dashjr reposted
XBT | Hardfork cguida | ⚡🪢
@cguida6
Miners aren't in charge
Stop assuming miners are in charge and which chain is the real bitcoin becomes immediately clear
realityblob
@realityblob
> so it pained me when miners simply ignored it.
That’s because you think miners are in charge. If nodes are in charge, nothing happened. Price just got cheaper and new mining algo. -
Luke Dashjr reposted
HardDuke 1 year coinbase maturity
@DukeDukingtonRD
It's been 3 months since sha-256d miners maliciously attempted to hardfork bitcoin, producing an altcoin known as spamcoin.
Here's who's found the blocks since then. Antpool and Foundry are officially gone.
For reference, here's who found the blocks on spamcoin since then. -
Luke Dashjr reposted
Kyle 🐆
@kwsantiago
And we’re not stopping there. We’ll keep rooting out the spamsters wherever they are!
Renaud Cuny
@CunyRenaud
Fake-multisig spam that filled ~75% of BLAKE2b block space in mid-October has nearly vanished.
- Peak ~45 MB/day (Oct 13);
- 0.03–0.3 MB/day since Nov 3, below pre-wave baseline.
Knots 29.4.3 (Oct 28) shipped the coinbase-maturity soft fork alongside a policy rule targeting fake-multisig.
The decline began Oct 25, before the release as pools upgraded ahead of activation. -
Luke Dashjr reposted
Renaud Cuny
@CunyRenaud
Fake-multisig spam that filled ~75% of BLAKE2b block space in mid-October has nearly vanished.
- Peak ~45 MB/day (Oct 13);
- 0.03–0.3 MB/day since Nov 3, below pre-wave baseline.
Knots 29.4.3 (Oct 28) shipped the coinbase-maturity soft fork alongside a policy rule targeting fake-multisig.
The decline began Oct 25, before the release as pools upgraded ahead of activation. -
Luke Dashjr reposted
Taimour AlNeimat @albitcoiner
Majority, majority, majority!
The majority still uses fiat. By Spamcoin folks' logic, we should all stick with it.
We’re here to separate money from the state, even when the majority disagrees.
Bitcoin was never about following the majority.
#xbt is #bitcoin -
Luke Dashjr reposted
Bitcoin Knots
@BitcoinKnots
Bitcoin Knots 29.5.knots20260508 released! 🎉
Be sure to read the release notes and verify your download(s)!
bitcoinknots.org?29.5?twitter -
Luke Dashjr
@LukeDashjr
If you want a decently secure web browser, compiled by yourself, I have @ClaudeAI maintaining Chromium ebuilds for @Gentoo here:
github.com/luke-jr/gentoo-overlay-luke-jr-llm
Use at your own risk. Browsers still have daily security issues. Recommend only running it on a separate, untrusted computer.
Luke Dashjr
@LukeDashjr
Also includes a "hardened" USE flag to add some extra security features from/like @GrapheneOS's Vanadium browser.
Disabling Javascript is best. You can selectively enable it per-site, and can keep JS JIT and/or JS optimization disabled per-site as well.
Luke Dashjr
@LukeDashjr
Additionally, I had Claude write a plugin for @ClawsMail to use Chromium for rendering HTML emails. You can optionally set it up so Claws and its Chromium run in isolated containers, or (with some effort) even separate computers.
github.com/luke-jr/claws-mail-chromium-viewer -
Luke Dashjr reposted
Thomas Massie
@RepThomasMassie
Instead of correcting course, the GOP chose to shoot the messenger and double down on stupid. (This tweet is one year old tomorrow.)
-
Luke Dashjr reposted
Michael Grunwald
@MikeGrunwald
By the way FL voters also passed a crazy property tax referendum that will gut local governments. Wheeeee!🐊💀
-
Luke Dashjr reposted
XBT Motorist
@BitcoinMotorist
There are people calling themselves Bitcoiners who say we should go along with whatever the majority wants.
They're not Bitcoiners, they are fiat maxis -
Luke Dashjr reposted
1-year Coinbase Maturity Dave BIP-110⚡️
@davelund_
"Big Bitcoin" = the Epstein political class.
-
Luke Dashjr
@LukeDashjr
Most things might be unaffected, but apparently using LND (or any Go servers) makes you vulnerable...
Until you can upgrade properly, at least do:
iptables -t raw -I PREROUTING -m u32 --u32 "0>>24&0x0F=6:15" -j DROP
The Hacker News
@TheHackersNews
‼️ Linux kernel TCP flaw rated 9.8 CVSS.
Anthropic demonstrated an exploit that runs commands as root on servers using MPTCP.
Ubuntu and RHEL still lack fixes, while Debian, Oracle and others have released patches for some versions.
Details: thehackernews.com/2026/10/linux-kernel-tcp-flaw-with-98-c… -
Luke Dashjr reposted
Sovereign Retard/ XBT
@BTCtoOblivion
This @BitcoinKnots release is extremely underrated since it doesn't talk much about how @kwsantiago also added some filters with this new version so, you may not see a lot of spam with fake pubkeys anymore.
Thanks to @JasonSopko42 for writing a PR to filters these fake pubkeys spam.
Spammers/scammers will have to find different ways to spam bitcoin timechain now.
Sovereign Retard/ XBT
@BTCtoOblivion
Running PR#468 😎
This post is unavailable. See it on X. -
Luke Dashjr reposted
Kyle 🐆
@kwsantiago
What's new:
- Nodes and miners should upgrade before block 979919
- As the community decided, mining rewards from that block until September 2027 take about 180 days to mature
- Spam filters catch more ways of hiding data in transactions
- Better peer discovery and Tor fixes
Bitcoin Knots
@BitcoinKnots
Bitcoin Knots 29.4.3.knots20260508 released! 🎉
Be sure to read the release notes and verify your download(s)! -
Luke Dashjr reposted
Connor's Lab ⚡️ #BLAKE2b
@ConnorsLabYT
FYI, Knots 29.4.3 lets us reduce Ark send fees by almost 60%!!!
Make sure you upgrade your Paperclip Wallet on Umbrel/StartOS to take advantage
Paperclip Pool
@PaperclipPool
Paperclip Ark Wallet update 0.9.0/0.9.1:
- Smoother UI and ~60% lower recovery allocations for typical Ark sends.
- StartOS: persistent package signing key; downloads use our standard GPG key. Verify before accepting new trust prompts.
ark.paperclip-xbt.xyz/wallet/ -
Luke Dashjr
@LukeDashjr
The community has spoken. 180-day maturity, it is.
Milestone: This is the first version of Knots released by someone other than myself. Congrats @kwsantiago!
Bitcoin Knots
@BitcoinKnots
Bitcoin Knots 29.4.3.knots20260508 released! 🎉
Be sure to read the release notes and verify your download(s)! -
Luke Dashjr reposted
Bitcoin Knots
@BitcoinKnots
Bitcoin Knots 29.4.3.knots20260508 released! 🎉
Be sure to read the release notes and verify your download(s)! -
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
BIP110 was not to fight spam. It was to prevent CSAM attacks.
BLAKE2b wasn't either - it was to restore functionality to the network after the miners attacked it.
Neither was the long maturity - that was to fight Stratum pooling.
Bitcoin fights spam with filters. And it's very effective. From nearly 2 MB of spam per block to 120k is a 94% reduction. And as you notice, Plumb is paving the way to reduce it further.
Spam is still bad, but no longer a serious problem for Bitcoin. -
Post not available here, view on X
Luke Dashjr
@LukeDashjr
BIP110 was not to fight spam. It was to prevent CSAM attacks.
BLAKE2b wasn't either - it was to restore functionality to the network after the miners attacked it.
Neither was the long maturity - that was to fight Stratum pooling.
Bitcoin fights spam with filters. And it's very effective. From nearly 2 MB of spam per block to 120k is a 94% reduction. And as you notice, Plumb is paving the way to reduce it further.
Spam is still bad, but no longer a serious problem for Bitcoin. -
Luke Dashjr reposted
Tallow Twins | Skincare
@Tallowtwins
the more i learn about women’s health, fertility, and the benefits of pregnancy and birth, the more skeptical i become of a system that treats fertility like a disease and motherhood like an inconvenience.
every time i read something like this, i think about how little we’re taught about what our bodies are capable of, how often we’re encouraged to override our natural rhythms, and how rarely women are given the full picture.
they want us to believe our bodies are problems to be managed. meanwhile, our bodies have been doing incredible things for thousands of years.
question everything. learn your biology. take back your autonomy. -
Luke Dashjr reposted
Without Rulers - #BTCB2
@BTCLeukocyte_WR
The last couple of years we found out Bitcoin Core™, Blockstein and the compromised influencer class are irredeemable.
Keep an eye on anything Tether related - the USD state shitcoin.
They fund Plan B and the shitcoiner "maxi" @giacomozucco.
They're now infesting Ocean Mining.
Eli Nagar
@EliNagar
A panelist at the PlanB Forum in Lugano:
"We need to bring back stablecoins on Bitcoin, otherwise we will remain with just Bitcoin"
WHAT??? -
Luke Dashjr reposted
XBT Motorist
@BitcoinMotorist
I thought this meme was about Spamcoin
𝘼𝙣𝙘𝙖𝙥 𝘼𝙞𝙧 🛫
@AncapAir
It do be like that...
-
Luke Dashjr reposted
Ami Hardfork XBT
@MountainHodl21
My worker found a block😍😍 just amazing
-
Luke Dashjr
@LukeDashjr
Just to be perfectly clear: I am against this. I think we should let the long CBM expire in a week and move on, focus on building back what we lost.
But it's not my decision, and the Bitcoin community seems to clearly support it, so I will accept it.
Luke Dashjr
@LukeDashjr
What is there Bitcoin consensus on? (Future proposals like rolling 45-day aside)
THIS IS NOT YOUR OPINION, just what you observe the community at large supporting.
Luke Dashjr
@LukeDashjr
.
-
Luke Dashjr
@LukeDashjr
Some websites are temporarily offline while I patch this.
FBI Cyber Branch
@FBICyberBranch
Two critical vulnerabilities have been identified in PHP, a widely used programming language that powers websites and web applications. These vulnerabilities (CVE-2026-109618 and CVE-2026-109619) could allow malicious cyber actors to remotely execute code in PHP core, potentially compromising sensitive data and networks.
The FBI urges organizations to take the following steps now:
➡️ If an immediate update is not feasible it is recommended that organizations take the system offline until it can be fully mitigated.
➡️ Immediately update affected PHP installations following the guidance on php.net. Inventory where PHP runs in your environment, prioritizing internet-facing systems and vendor products that bundle PHP.
➡️ Monitor web servers for suspicious activity, including PHP processes unexpectedly launching command shells or downloading files. Ensure appropriate process-monitoring capabilities are in place to help identify potential exploitation.
➡️ If you find signs of compromise, isolate affected systems, preserve your web server and PHP logs, and report it to your local FBI field office or www.ic3.gov. Those reports help us identify the actors involved and warn other organizations before they become victims.
For the latest information, follow PHP’s announcement on php.net, CERT-EU Security Advisory 2026-018, and CISA’s Known Exploited Vulnerabilities catalog.
Luke Dashjr
@LukeDashjr
Felipe Daragon
@FelipeDaragon
🚨 UPDATE: A public PoC demonstrates RCE on PHP 8.5.12, even after the October 21 security patches.
The attack is separate from the patched php2shell CVEs and requires specific session configurations and application weaknesses.
Our earlier concerns about PHP session handling remain relevant.
We've updated php2shell-protection with additional hardening guidance.
#php #cybercurity
github.com/syhunt/php2shell-protection -
Luke Dashjr reposted
Vici Tax
@ViciTax
XBT is Bitcoin. Which is why xbtdirectory.com is now live. It’s a free online service for connecting sellers & buyers who exchange XBT for goods and services.
Matthew R. Kratter
@mattkratter
XBT is Bitcoin
-
Luke Dashjr reposted
⊹ damir
@otomir23
a trusted intermediate CA just "leaked" (the private key was 4)
-
Luke Dashjr reposted
AJ Stuyvenberg
@astuyve
private keys from 8 intermediate CA certs have been compromised (eMudhra)
Happy "Update everything" day to all my pager-carrying friends
emudhra.we-have-a-problem.com -
Luke Dashjr
@LukeDashjr
What is there Bitcoin consensus on? (Future proposals like rolling 45-day aside)
THIS IS NOT YOUR OPINION, just what you observe the community at large supporting. -
Luke Dashjr reposted
realityblob
@realityblob
Anyone who was “pro” BIP-110 before the fork and stopped supporting the principles AFTER the fork, never had any principles to begin with.
-
Luke Dashjr reposted
ꓘɨℓσꬺƄℓɑꓘҽ2ƄꓘɳσŦƨ \\ BTC = XBT
@Kilombino_
LND has BOLT12 now too, on Lightning Fork, Paul’s LND fork for the BLAKE2b chain. Native, no side-car: it mints reusable offers, answers invoice requests over onion messages, and can fetch and pay other nodes’ offers.
Docs: github.com/paulscode/lightning-fork/blob/blake2b/docs/bol… -
Luke Dashjr reposted
PepeLapiu - XBT HARDFORK
@LapiuPepe
Just beautiful, isn't it?
-
Luke Dashjr
@LukeDashjr
Unfortunately, this doesn't apply to Spamcoin, because unlike Bcash and 2X, Spamcoin does not aspire to or consider decentralization a real goal. Their success is defined as a CBDC.
Luke Dashjr
@LukeDashjr
Even if 2X were to win, it STILL loses because it would be proving that a decentralised cryptocurrency is a dream that can never become real
-
Luke Dashjr reposted
Ben Zeisloft
@BenZeisloft
There is no difference between murdering your baby to make your crops grow and murdering your baby to earn your college degree.
-
Luke Dashjr reposted
Sovereign Retard/ XBT
@BTCtoOblivion
@Convoy_Mining just crossed @TwhitNub101 in hashrate...!!!!
Let's see if Convoy holds this position for a long time or not (especially after 1 year CBM softfork)
LFG 🚀🚀🚀 -
Luke Dashjr
@LukeDashjr
PSA to Ledger owners. This is apparently larger than just CryptoBills.
If you haven't addressed the Spamcoin airdrop yet, be careful not to lose your bitcoins in a kneejerk attempt to save funds. (ie, don't just send them to some exchange that will rug you!)
Ledger
@Ledger
Update from Ledger Donjon on the CryptoBilis investigation 🔽
@DonjonLedger is investigating Ledger signers sold by CryptoBilis, a reseller in Southeast Asia, that contained an unauthorized hardware implant. Ledger confirmed this on October 10th for one affected user's signer. All confirmed fund losses tied to the incident disclosed on October 9th involve signers sold through CryptoBilis. We have not verified a drain linked to a signer bought elsewhere. CryptoBilis has confirmed it stopped selling Ledger signers while the investigation continues.
Based on the Donjon's analysis of the attack, the implant sits inside the enclosure and reads the data shown on the screen. During setup, the signer displays the 24-word recovery phrase. When the implant detects these screens, its microcontroller decodes the words and transmits them over LTE using a provisioned eSIM. The implant is a separate component. It does not modify the Secure Element or the Ledger operating system, and it does not alter transactions or signatures.
The Donjon will analyze the signers it receives and will share more as the investigation continues.
We have not confirmed the total number of affected users or the total value lost. Figures circulating online come from third parties and Ledger has not fully verified them. If your funds were drained and you have not contacted us, please do so through Ledger Support so we can include your case. We are also reviewing reports of implants in other signers and locations. We will continue to share information as the investigation progresses. Rest assured the Ledger team is going above and beyond to leave no stone unturned to investigate this situation to the strongest possible outcome.
If you bought a Ledger signer from CryptoBilis and have not set it up, do not set it up and contact Ledger Support. If you have set it up, transfer your assets promptly to a new signer with a new recovery phrase. Do not enter or restore any recovery phrase on a signer bought from CryptoBilis. Never enter your recovery phrase into a website, app or form.
If you lost funds or hold a tampered signer, contact Ledger Support at support.ledger.com and file a report with local law enforcement. Do not send the signer to anyone before speaking with Ledger Support or local law enforcement. If you lost funds, coordinate with law enforcement before opening the signer. Researchers and others with relevant information can write to security@ledger.com.
If you did not buy from CryptoBilis and want to inspect the inside of your signer, the guide is at support.ledger.com/article/4404382029329-zd. Use caution and make sure your recovery phrase is backed up first, because opening a signer can damage it.
Ledger will never call you, message you directly, or ask for your 24-word recovery phrase. We will update this post when we verify new information. -
Luke Dashjr
@LukeDashjr
Atheists constantly demand unmistakable miracles as proof, yet they ignore the many times throughout history God gave it to them.
Catholic Drip 💧
@CatholicDrip___
109 years ago today, the sun “danced” at Fatima before tens of thousands.
October 13, 1917. ☀️🇵🇹 -
Luke Dashjr reposted
Key and Chain | Bitcoin Blake2b
@keyandchain21
Blake2b is the real Bitcoin and SHA256 is not (you slept through it) youtu.be/aguU5iVnzwM via @YouTube
-
Luke Dashjr reposted
Down for the Neorenaissance | XBT | blake2b
@NeorenaissanceB
10/10/25
The Day Crypto Crashed
and also...
the day @bitcoincoreorg released its malware version v30
Coincidence?
XBT plebs know.
di
@_btcdi
10/10/25
“one of these things is not like the others” 🎶 -
Luke Dashjr reposted
Rev. Nicolás E. Despósito
@FrDesposito
Sermon: On Feminism, By Rev. Michael DeSaye. youtu.be/tiu3D4ud2Ac via @YouTube
-
Luke Dashjr reposted
CONVOY
@Convoy_Mining
CONVOY is excited to officially re-launch our pool. Originally known as Eligius, and successor to OCEAN, CONVOY continues the decentralization mission.
DATUM Gateway, now under CONVOY's stewardship, has finally released 0.5.0beta, updating it for Bitcoin's new proof-of-work algorithm, and the many features that come with it. 🚀
DATUM is an open-source protocol that lets miners truly solo mine, building their own block templates, while still participating in pooled reward sharing. It’s crucial for mining decentralization, and used by most of the network today.
Download DATUM Gateway v0.5.0beta now in the links below! -
Luke Dashjr reposted
Ned17Flanders Let Freedom Ring
@Ned17Flanders
What has the chance of making new all time highs first?
-
Luke Dashjr
@LukeDashjr
Are you using Bitcoin or Bpedo?
Luke Dashjr
@LukeDashjr
Epstein didn't invent Bitcoin. But let's pretend he did for a moment.
Even then, the concept of Bitcoin is still what matters. We should disregard any future direction from Epstein, stop using his software, and take over / keep Bitcoin going for the good guys. -
Luke Dashjr reposted
Down for the Neorenaissance | XBT | blake2b
@NeorenaissanceB
In 2 days, it will be 1 year since Bitcoin hit ATH.
In 6 days, it will be 1 year since @bitcoincoreorg betrayed the plebs and released v30.
Bitcoin crashed, has never recovered, and is now 85% spam in new blocks.
When is enough enough?
XBT is Bitcoin.
Come back home. -
Luke Dashjr reposted
𝚌𝚕𝚞𝚖𝚙 𝚘𝚏 𝚌𝚎𝚕𝚕𝚜
@ZELLKLUMPEN
Happy Sunday! ⛪️
Pray to end abortion! -
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
Spam is a major problem, but we've been forced to move beyond it. The solution to spam is policy filters.
Core created a bigger problem of CSAM. That's way worse than spam. Solved by BIP110.
Then ex-miners created a bigger problem of CBDC, which defeats the point in another way. Solved by BLAKE2b. -
Post not available here, view on XPost not available here, view on X
Luke Dashjr
@LukeDashjr
Spam is a major problem, but we've been forced to move beyond it. The solution to spam is policy filters.
Core created a bigger problem of CSAM. That's way worse than spam. Solved by BIP110.
Then ex-miners created a bigger problem of CBDC, which defeats the point in another way. Solved by BLAKE2b. -
Luke Dashjr reposted
NEET
@NEETOCRACY
Reminder: you are taxed more heavily than ancient slaves.
-
Luke Dashjr reposted
nomadshiba | XBT
@nomadshiba
many didn't understand bitcoin and rejected it before.
they still dont, they are just attracted to the orange. they are still against bitcoin.
XBT -
Luke Dashjr reposted
HardDuke 1 year coinbase maturity
@DukeDukingtonRD
Spamcoin is a step in the wrong direction from fiat.
It is de facto a CBDC.
Cash dollars are better because they're harder to trace.
A fully KYCed spamcoin network, where all your addresses and transactions are known and permitted/refused by centralized entities, awaits you. -
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
"‘Upon this rock I will build my Church,’ that is, on the faith of his confession." -St. John Chrysostom
"Faith, then, is the foundation of the Church, for it was not said of Peter’s flesh, but of his faith, that the gates of hell should not prevail against it." -St. Ambrose
"This faith it is which is the foundation of the Church; through this faith the gates of hell cannot prevail against her." -St. Hilary of Poitiers
It's not one or the the other, as if they could ever be opposed; it's both St. Peter and his profession of faith, together. -
Post not available here, view on X
Luke Dashjr
@LukeDashjr
"‘Upon this rock I will build my Church,’ that is, on the faith of his confession." -St. John Chrysostom
"Faith, then, is the foundation of the Church, for it was not said of Peter’s flesh, but of his faith, that the gates of hell should not prevail against it." -St. Ambrose
"This faith it is which is the foundation of the Church; through this faith the gates of hell cannot prevail against her." -St. Hilary of Poitiers
It's not one or the the other, as if they could ever be opposed; it's both St. Peter and his profession of faith, together. -
Luke Dashjr reposted
Mirari Vos enjoyer
@PopeGregoryXVI
If God said this instant "screw it everyone here is going to Hell" and in that moment 8 Billion people immediately descended into Hell it would be absolutely just
-
Luke Dashjr reposted
Joshua Blake2B Fortezza
@JoshuaFortezza
The “security budget” idea suggests that miners need a cash flow incentive to support their role as a double spend protector. The logic here assumes miners are not also the users of Bitcoin as money, and instead are simply using their skill to acquire microchip and electricity contracts at size, as the highest bidder, regardless of the users purpose for the silicon and electrons.
This worldview can be seen in all aspects of the fiat world, for example where children are treated as wards of the state and should learn the ways of the world not by their mother and father but instead by state sanctioned strangers of a public school system that assume people can just be programmed to do whatever the state thinks is best for them rather than what would actually be best for the children. And what is best is obviously teaching them (1) securing the means of production of the necessities of life for themselves and their community (ie food water shelter energy and fixed supply money) and (2) securing the means to fulfill their biological necessities (procreation). Instead these things are after thoughts because the state and its corporate interests need instead obedient tax cattle and mindless wage slaves, respectively.
That is certainly one world view, but it is entirely at odds with the underlying world view of Bitcoin, which is that the users of money aught to have the ability to secure the means of their own monetary network as they see fit. And from this world view miners then are not an amoral security budget question but instead are a user driven security question, where the “cash flows” of operations is not derived from block rewards but rather from the monetary soundness of the protocol they enforce. The block rewards are simply a small technical seigniorage solution for the networks bootstrapping. And it is in this light that Andreas Antonopoulos so poetically and famously explained the necessity and equally important the capability of the network to hard fork into a new proof of work should such a circumstance arise requiring such a nuclear option to be executed.
Hard fork Creasy explains the current mental state of the sha256’ers perfectly:
“The emotional and physical investment in btc for years on end will not allow most to see the truth of how bitcoin just defended itself against centralization and executed its only path out of it via monetary maxis.”
And in a recent video post you, JD, illuminated the community sentiment that supports this pow fork, and I’m paraphrasing, your video was fantastic, but if I could distill it down to three primary themes:
(1) we are not here to negotiate, we are here to complete the task of building Bitcoin, a user based monetary network, regardless of the personal sacrifice required because
(2) our eyes are wide open, we fully understand the job which we have taken upon which is the up ending of the fiat worldview, to supplant it with a righteous and just new means of cultural order, thus, obviously, we are going to therefore piss off the most powerful people in the most privileged positions of power as we completely undermine their way of business, namely the disjointed amoral business of treating people as objects for the purpose of generating cash flows for themselves through rent seeking via idea monopolization by the brutal and immoral means of violent coercion, and misguided high time preferenced stupidity. And finally because
(3) the cost of building good things requires self sacrifice, that the quality of the goodness built is equal to the courageousness applied.
And let me tell you something, my brothers, we’ve got a global legion of the most courageous and morally based people on the planet at our sides in this fight, and we won’t quit until the job is done.
Strength and Honor. 🧡🫡 -
Luke Dashjr reposted
Sovereign Retard/ XBT
@BTCtoOblivion
xbt.nomadshiba.me
Check out this website 😎 -
Luke Dashjr reposted
ANTON
@Anton_Bitcoin
I've updated my both nodes to 29.4.2, to support Bitcoin softfork.
Don't forget to go to "Version" settings tab on Umbrel, to actually activate the new version.
Luke Dashjr
@LukeDashjr
Looks like the Bitcoin softfork activation will be earlier than anticipated (this afternoon instead of tomorrow), upgrade ASAP!
Bitcoin Knots
@BitcoinKnots
Bitcoin Knots 29.4.2.knots20260508 released, further mitigating the ongoing attack! 🎉
Be sure to read the release notes and verify your download(s)!
bitcoinknots.org?29.4.2.20260508?twitter -
Luke Dashjr
@LukeDashjr
Time's up, softfork is active.
XBT | Hardfork cguida | ⚡🪢
@cguida6
Softfork to lengthen coinbase maturity to 45 days in 2 blocks! All miners must upgrade to make sure they don't mine any invalid blocks!
Luke Dashjr
@LukeDashjr
(Technically there's another 100 blocks grace period due to the preexisting maturity rule, but don't wait until the last minute!)
-
Luke Dashjr reposted
-
Luke Dashjr
@LukeDashjr
Looks like the Bitcoin softfork activation will be earlier than anticipated (this afternoon instead of tomorrow), upgrade ASAP!
Bitcoin Knots
@BitcoinKnots
Bitcoin Knots 29.4.2.knots20260508 released, further mitigating the ongoing attack! 🎉
Be sure to read the release notes and verify your download(s)!
bitcoinknots.org?29.4.2.20260508?twitter -
Luke Dashjr reposted
HardDuke 1 year coinbase maturity
@DukeDukingtonRD
1/3
There are no bitcoin conferences anymore. Only shitcoin NFT-tether ones.
I've stayed in the shadows for a long time. Now I want to seize this opportunity to kickstart something.
Is there energy for a mid-sized bitcoin (which has blake2b hashing algo) meetup/conference? -
Luke Dashjr reposted
Rory D Fpic
@Rory_D_Fpic
There were exactly 0% nodes running a URSF. Miners ignoring g a UASF with 20% node support is them forking away from node runners. Miners are not in charge of Bitcoin.
-
Luke Dashjr reposted
XBThomemining
@XBThomemining
Something is cooking 💀
-
Luke Dashjr reposted
SpectrGen // XBT
@SpectrGen
The connection people are missing with AlphaPool is QUAI.
AlphaMine isn't some independent pool operator that randomly showed up on XBT. @TwhitNub101 is an official QUAI ambassador, and AlphaMine is part of QUAI's mining infrastructure.
Look at what QUAI has already built.
Their SOAP system recruits SHA256/Scrypt hardware from other PoW ecosystems, captures the parent-chain block subsidies, and uses them to buy QUAI. QUAI literally markets this as:
“daily buy pressure funded by other chains.”
That tells you a lot about the incentives here.
AlphaPool then shows up on XBT, makes it trivial for huge amounts of existing BLAKE2b/Sia hash to point at our chain, and aggregates that hash behind AlphaPool-controlled SV1 templates.
We've been treating this like an oversized mining pool problem, but look at the bigger picture: their ecosystem already has an explicit strategy of aggregating outside PoW resources and turning them into value for QUAI. Now one of its mining operators is fighting for a dominant position in XBT block production.
AlphaPool is not a neutral stakeholder whose incentives we should blindly trust. Their affiliation, their business history, and QUAI's own economic model are public.
XBT should not accept AlphaPool's presence as accepted mining infrastructure.
Keep your hash out of AlphaPool. Build your own blocks with DATUM.
Sources: gist.github.com/SpectrGen1/fd0cec6aed55079e26580627d243ba71 -
Luke Dashjr reposted
Lori Singer Meyer
@Loriss65
Of course AlphaPool is a liar - AlphaPool is a psychopathic asshole seemingly with ties to the CCP and mining farms, based on his advertising for Sia Miners in Hong Kong and China. And I've heard through the grapevine that he is in bed with Udi with specific designs on hurting the Blake2b network so it never has any chance to develop into a sovereign money independent of nation states. The big question is how to protect new attack surfaces that emerged in the years since Satoshi, that Satoshi could not have imagined, and not be so ideologically "pure" that a person would rather have their own network smashed to pebbles under their feet than recognize the changes in an ecosystem that require some real rehtinking of how Bitcoin must be protected so it will not be lost before it has a chance to take root.
XBT | Hardfork cguida | ⚡🪢
@cguida6
Alphamine is a liar
-
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
I've heard some big buyers complain about a lack of liquidity.
There really isn't a lack of liquidity, though. There's 20MBTC out there, much of it with a price.
The real issue they're facing is they want to buy bitcoins on the cheap, below the market price.
Offer $80k/BTC and I think they'd find lots of sellers.
Make it $150k/BTC and I'm sure of it. -
Post not available here, view on X
Luke Dashjr
@LukeDashjr
I've heard some big buyers complain about a lack of liquidity.
There really isn't a lack of liquidity, though. There's 20MBTC out there, much of it with a price.
The real issue they're facing is they want to buy bitcoins on the cheap, below the market price.
Offer $80k/BTC and I think they'd find lots of sellers.
Make it $150k/BTC and I'm sure of it. -
Luke Dashjr reposted
HardDuke 1 year coinbase maturity
@DukeDukingtonRD
Ignoring an unopposed UASF is theoretically exactly equal to implementing a MAHF
Miners have demonstrated that they have the ability to hardfork the network against nodes' wishes
Only clowns with the intellectual capacity of a child and downright grifters are still on corechain
Extractive Ghost of Unhosted Marcellus 👻
@oomahq
It isn't. In the presence of an UASF movement without opposition (URSF) proof of decentralization would be mining nodes freaking out adopting it. The fact that it could be ignored by the pool CEOs proves centralization.
The decentralized way to maintain status quo in the presence of an UASF movement is to launc a competing URSF movement, and if the URSF gets more economic nodes and hashrate behind it the UASF loses fairly.
Node runners and users who really didn't want BIP-110 simply delegated their agency to the pools, and now it's been shown they can set the rules (either to maintain them and reject fixes or to force unwanted changes, it's the same power). -
Luke Dashjr reposted
ScarcityMan 🍴 BLAKE2b Hardfork
@ScarcityMan
Remember how much offense Core supporters took when we called many of them CSAM supporters or pedos because they refused to acknowledge any argument with respect to limiting the ability to put CSAM on chain? All the phony, make-believe outrage and "how dare you call us names like that," and "the reason I don't support your shitfork is because you called us bad names..." Remember all that? And how they claimed no one supported CSAM, but nothing could be done, so *shrug*.
Well, every now and then I get into an argument with one of these "people" (and I use that term loosely), and it turns out, they're a pedo or CSAM supporter. Isn't it interesting?
Not all spam-loving, Core-supporting, BIP-110 opponents are pedos, but all pedos are spam-loving, Core-supporting, BIP-110 opponents. Funny how that works. -
Luke Dashjr
@LukeDashjr
Mined bitcoins are unspendable for their first 100 blocks. There has been proposals to either delay spending them for 4375 blocks (~a month), or to zero the block subsidy for a month (so miners only get paid fees and nothing more).
The motive here is to deter a large batch of hashers who appear to only have profit as their motive, and are attacking Bitcoin's decentralization in the process.
No decisions are final, but you should join the discussion if you have an opinion:
discord.gg/Dkr5eRGxU
Luke Dashjr
@LukeDashjr
To be clear: both proposals are for a temporary change.
-
Luke Dashjr reposted
XBT BLAKE2b LTP
@mpps_x
You're not "mining" unless you're running a node.
Full stop. -
Luke Dashjr
@LukeDashjr
August 8th, Spamcoin forked off from Bitcoin with a contentious hardfork attempt (removing/violating BIP110 rules). Bitcoin continued, albeit maimed by miner abandonment.
August 19th, "Purity" did the same (by removing/replacing the DAA). Bitcoin continued, unfazed.
August 30th, Bitcoin deployed a proof-of-work change to BLAKE2b. It was uncontroversial and unanimously supported by what was left of the network, and carries the original chain forward undisputed. -
Luke Dashjr reposted
Ben Owen
@BlackRifle_Co
-
Luke Dashjr reposted
.
@GrassFedBitcoin
Also - I propose renaming the tiniest unit of SHA256coin to "suits" instead of "sats"
-
Luke Dashjr reposted
Greg Tonoski, BIP-110, Blake2b
@GregTonoski
Bitcoin has withstood the largest, the most expensive attack in the history.
The reference implementation is Bitcoin Knots. It's time to update nodes to version 29.4.1 which includes update of proof-of-work algorithm (Blake2b replaced SHA-256d): github.com/bitcoinknots/bitcoin/releases -
Luke Dashjr reposted
HardDuke 1 year coinbase maturity
@DukeDukingtonRD
All I see are lies on the timeline.
BITCOIN (blake) HAS REPLAY PROTECTION.
SPAMCUCKCOIN DOES NOT.
The users of bitcoin (blake) are protected from accidentally spending spam tokens when using their money.
The users of spam token are not protected from spending bitcoin (blake). -
Luke Dashjr reposted
Billy Binion
@billybinion
CPS said Parkinson was guilty of child abuse and neglect for letting her son walk a half-mile alone. It placed her on the state registry, where she'll remain for 7 years.
Yet the case really hit rock bottom last week when... /4 reason.com/2026/09/02/virginia-mom-gets-6-month-suspended… -
Luke Dashjr
@LukeDashjr
Bitcoin is back online! Scammers in shock.
Bitcoin Knots
@BitcoinKnots
Bitcoin Knots 29.4.1.knots20260508 released, mitigating the ongoing attack! 🎉
Be sure to read the release notes and verify your download(s)!
bitcoinknots.org?29.4.1.20260508?twitter -
Luke Dashjr reposted
Agorist Nexus (Brandon)
@AgoristN
-
Luke Dashjr reposted
XBT | Hardfork cguida | ⚡🪢
@cguida6
First difficulty adjustment dropped! This period will be special because it will be very short, since the last period was much longer than two weeks (started Aug 8)
After this, the block rate should stabilize quickly to 10 minutes per block -
Luke Dashjr reposted
ꓘɨℓσꬺƄℓɑꓘҽ2ƄꓘɳσŦƨ \\ BTC = XBT
@Kilombino_
-
Luke Dashjr reposted
loogart
@loogart
Many precedents have been set since the PoW mining algo change.
1. Miners are not the legislative branch. Individual non-mining nodes are. They decide which rules they are willing to enforce. Miners are the executioners, nothing more. They execute the rules the network accepts.
2. Arbitrary-data demand is not welcome here. We don't treat it as legitimate demand for Bitcoin's scarce blockspace. We don't subscribe to “the fee is the filter,” and we don't want to create a permanent revenue lobby for miners around arbitrary data.
3. The mining constituency is replaceable. We don't have to permanently accommodate miners whose incentives conflict with Bitcoin's monetary purpose.
4. The precedent is simple: the network sets the rules, miners execute them. If the miners won't, replace the miners. Hashrate does not define validity.
This is Bitcoin governance. Not miner governance. -
Luke Dashjr reposted
XBT Motorist
@BitcoinMotorist
RDTS is working better than expected. Not only did it activate but as a bonus we got a number of other bugs fixed, upgraded the algo, and reduced the block size ✊
JUAN
@uanbtc
Message to my RDTS/BIP110 friends:
If you find yourself being or following things that are inconsistent with what you were fighting for just a month ago… question yourself:
Is this rational, or am I following a cult?
That’s it.
What a sad conclusion to the most promising decentralization movement in recent Bitcoin history. It will be hard to replicate, but I won’t lose hope. -
Luke Dashjr reposted
XBT BLAKE2b LTP
@mpps_x
Great to see.
-
Luke Dashjr reposted
Greg Tonoski, BIP-110, Blake2b
@GregTonoski
Reduced Data Temporary Soft-fork (a.k.a. BIP-110) stricter rules for transactions are fully active now (from the block height 961640).
-
Luke Dashjr reposted
Connor's Lab ⚡️ #BLAKE2b
@ConnorsLabYT
To anyone interested in mining the #blake2b mainnet, here’s my tutorial for getting DATUM going with StartOS:
youtu.be/mcmY-UBDGB8 -
Luke Dashjr reposted
Balkan Hodl
@balkanhodl
This guy just mined the latest block. But check out his mining history, goes all the way back to 2011
mempool.guide/mining/pool/kc -
Luke Dashjr reposted
CONVOY
@Convoy_Mining
Running bitcoin
halfin
@halfin
Running bitcoin
-
Luke Dashjr reposted
.
@GrassFedBitcoin
.@Convoy_Mining blocks will be able to pay out hundreds of miners at a time just like the old Eligius blocks. We paid out 903 miners once iirc.
Working around Bitmain firmware was so frustrating.
Luke Dashjr
@LukeDashjr
BLAKE2b is quite a bit better for decentralization than SHA256d...
For starters, we now have the precedent that centralization will result in a PoW change, creating a strong disincentive to do so.
BLAKE2b also doesn't have any known vulnerabilities (like SHA256d's ASICBoost) and is very simple for new ASIC manufacturers to enter the market. There are already 6 or 7.
Since we had to reorganize the header anyway, we also fixed several long-standing issues with it. One of those issues fixed is block withholding attacks. The only way previously to defend against them was incentives and KYC. With the new format, it is possible to defend completely at a technical level.
It also increases the nonce space significantly, avoiding the need for mining hardware to handle Bitcoin internals - often incorrectly, a problem that interferes with generating payouts to miners directly. -
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
BLAKE2b is quite a bit better for decentralization than SHA256d...
For starters, we now have the precedent that centralization will result in a PoW change, creating a strong disincentive to do so.
BLAKE2b also doesn't have any known vulnerabilities (like SHA256d's ASICBoost) and is very simple for new ASIC manufacturers to enter the market. There are already 6 or 7.
Since we had to reorganize the header anyway, we also fixed several long-standing issues with it. One of those issues fixed is block withholding attacks. The only way previously to defend against them was incentives and KYC. With the new format, it is possible to defend completely at a technical level.
It also increases the nonce space significantly, avoiding the need for mining hardware to handle Bitcoin internals - often incorrectly, a problem that interferes with generating payouts to miners directly. -
Post not available here, view on XPost not available here, view on X
Luke Dashjr
@LukeDashjr
BLAKE2b is quite a bit better for decentralization than SHA256d...
For starters, we now have the precedent that centralization will result in a PoW change, creating a strong disincentive to do so.
BLAKE2b also doesn't have any known vulnerabilities (like SHA256d's ASICBoost) and is very simple for new ASIC manufacturers to enter the market. There are already 6 or 7.
Since we had to reorganize the header anyway, we also fixed several long-standing issues with it. One of those issues fixed is block withholding attacks. The only way previously to defend against them was incentives and KYC. With the new format, it is possible to defend completely at a technical level.
It also increases the nonce space significantly, avoiding the need for mining hardware to handle Bitcoin internals - often incorrectly, a problem that interferes with generating payouts to miners directly. -
Luke Dashjr reposted
XBT | Hardfork cguida | ⚡🪢
@cguida6
Feeling more energized than ever to get back to building
Lightning is finally going to become what it was always meant to be, since we don't have to fight against spam and MoE minimalists anymore
Get in touch if you want to help out, we're currently organizing in the Knots discord
We have a lot of work ahead of us, but now we have all the tools we need to win, so it's just a matter of time and focused effort -
Luke Dashjr
@LukeDashjr
-
Luke Dashjr
@LukeDashjr
blake2b_headline=8-30 NYPost Deride And Conquer
-
Luke Dashjr reposted
Matthew R. Kratter
@mattkratter
"If SHA-256 became completely broken, I think we could come to some agreement about what the honest block chain was before the trouble started, lock that in and continue from there with a new hash function."
-
Luke Dashjr reposted
OCEAN
@ocean_mining
OCEAN and Luke Dashjr announce today that, by mutual agreement, Luke Dashjr has separated from OCEAN, resigning as Chairman, Chief Technology Officer, and director.
Link to the joint statement press release here: www.prnewswire.com/news-releases/joint-statement-of-ocean… -
Luke Dashjr reposted
CrabBoss
@CrabBoss_
I have successfully promoted the consensus of bip110-blake2b-btc in China. Everyone is supporting it, so in China, no one will prefer the SHA256 core algorithm for BTC anymore.
-
Luke Dashjr
@LukeDashjr
PSA: Potential Bitcoin PoW change Sunday. SHA2 miners should stop mining Saturday.
- @BitcoinKnots 29.4.1rc4 will be released tomorrow, setup for mainnet rehearsal. This locks-in the final SHA2 block.
- After NYPost updates their Sunday morning print online, I'll post the canonical blake2b_headline parameter.
- If things go perfectly, Knots 29.4.1 final will be released Sep 1 on schedule, keeping the Aug 30 blockchain.
- If there's any issues (unlikely at this point), we address them and reset to the last SHA2 block for rc5.
If you intend to mine from day 1, I recommend getting setup with testnet4 (rc3) _now_ so you're ready for mainnet on Sunday.
Luke Dashjr
@LukeDashjr
Note that contrary to what you might expect, NY Post uploaded Saturday's print paper an hour ago (~1:10am ET). I haven't been watching closely enough to know if this is the norm, but I'm going to plan on staying up Saturday night into Sunday for the kickoff.
-
Luke Dashjr reposted
boozy | XBT
@TheBoozles
😁
-
Luke Dashjr reposted
loogart
@loogart
The chances of recapturing the spamchain and restoring it to Bitcoin's original purpose are far lower than the chances of BLAKE2b Bitcoin succeeding.
BIP-110 supporters who want to “continue fighting” on the CSAM chain need to understand this. -
Luke Dashjr reposted
HardDuke 1 year coinbase maturity
@DukeDukingtonRD
When I re-explained BIP110 and explained the necessary PoW change hardfork to my semi-orange-pilled best friend the other day, he said "how could anyone possibly not support that".
-
Luke Dashjr reposted
Jordan ♱🇻🇦🇺🇲
@regulator062
People need to stop looking at what form of government they feel would be best for themselves, and instead think about what kind of society and government God wants. God wants to save as many souls as possible. All modern governments have been total failures in this regard.
-
Luke Dashjr reposted
FlyTheElephant ₿IP110+₿LAKE2b #BitcoinIsHope
@FlyTheElephant1
Come join the Bitcoin-BLAKE2b Testnet4 RC3 test. Set your headline=Catbus. Today in a couple hours. Bring your datum gateway! test.bitcoinknots.org/~luke-jr/programs/bitcoin/files/bit…
-
Luke Dashjr reposted
Kretch🐸 b2b xbt bitcoin
@kretchino
Replacing bitcoin's sha256 algo with blake2b is like replacing the worn out wipers of your Lambo with new ones of a different brand.
It's still the original Lambo. It's only the necessary maintenance that is being performed 🤗 -
Luke Dashjr reposted
1-year Coinbase Maturity Dave BIP-110⚡️
@davelund_
Bitcoin mainnet can be observed here
mempool.guide -
Luke Dashjr reposted
Ray Blake2b
@M28Ray
Mining does not give Bitcoin its value—it simply finds the next block, which is then verified by every node. Bitcoin’s value comes from people holding the coins, those dollar-cost averaging into it, people buying and selling goods with it, and the thousands of node runners who keep the system decentralized.
SpectrGen // XBT
@SpectrGen
Miners don’t own Bitcoin. They provide proof under rules enforced by users
This BIP-110 PoW proposal makes the fallback explicit: if miners refuse the rules users choose, the network can change the PoW and fire them
Here’s what that would actually entail x.com/i/article/2084750717160652800 -
Luke Dashjr reposted
₿itcoin ₿ombadil
@BitcoinBombadil
To dismiss a PoW Algo Change for Bitcoin is to neutralize its properties of anti-fragility and voluntary association.
Opposing a Bitcoin PoW Algo change is like opposing the 2nd Amendment.
If you know, you Knots2b110.
Filters up!🛡️✊🏼🫡 -
Luke Dashjr reposted
Modus | BIP-110
@MBronens
Look who suddenly just fell in line with with a soft fork that has barely been discussed with the plebs.
orangesurf
@OrangeSurfBTC
You can see that @FoundryServices, @viabtc & @MARA are all mining compatible blocks
-
Luke Dashjr reposted
HarloLabs
@HarloLabs
We keep seeing requests for BLAKE2b miners. Is this something you’d want?
If this post gets enough positive engagement, we’ll look into building BLAKE2b home miners.
Like, repost, and comment if you’re interested! -
Luke Dashjr reposted
1-year Coinbase Maturity Dave BIP-110⚡️
@davelund_
Big Bitcoin never stops producing slop. #bip110
-
Luke Dashjr
@LukeDashjr
Bitcoin IS a "purity test". It doesn't work if people are willing to accept invalid blocks.
-
Luke Dashjr reposted
SpectrGen // XBT
@SpectrGen
One thing people should understand about the proposed BLAKE2b hard fork is how replay protection would work.
After a split, your old coins exist on both chains. With a BLAKE2b-aware wallet, you could opt-in to the new Unified Sighash and spend the BLAKE2b side in a way that the SHA256 chain simply won’t accept, leaving those coins untouched there.
The reverse is intentionally not forced. A normal SHA256 transaction could still be valid on BLAKE2b, because making protection mandatory would mean rejecting transactions Bitcoin has always accepted and breaking compatibility with existing wallets and pre-signed transactions.
So there’s a tradeoff: better compatibility, but users spending from the SHA256 side would still need to be careful about replay.
This is still a draft proposal and has not been merged. You can read the full proposal here: github.com/privkeyio/bitcoin/blob/453b5f9fb051b1b97fce2a9… -
Luke Dashjr reposted
SpectrGen // XBT
@SpectrGen
If Luke is anything, he is a man of his word. A dedicated and honest individual who isn’t afraid to stand on principles. The world needs more people like him.
-
Luke Dashjr reposted
Roughnecks
@Roughnecks110
8/22 NYPost Out of left field📰
Tick tock, next block⛏️ -
Luke Dashjr reposted
Alien Perspective
@WigglyAir
-
Luke Dashjr reposted
Erwan Le Corre
@ErwanLeCorre
Feelings and principles are not the same.
Emotion-based morality isn't morality. -
Luke Dashjr reposted
ꓘɨℓσꬺƄℓɑꓘҽ2ƄꓘɳσŦƨ \\ BTC = XBT
@Kilombino_
Tesnet BLAKE2b live here NOW:
mempool.guide/es/testnet4 -
Luke Dashjr reposted
FlyTheElephant ₿IP110+₿LAKE2b #BitcoinIsHope
@FlyTheElephant1
Come join the Bitcoin-BLAKE2b Testnet4 RC2 test. Set your headline=Totoro. Today in a couple hours. Bring your datum gateway! github.com/bitcoinknots/bitcoin/tree/v29.4.1.knots2026050…
-
Luke Dashjr reposted
BTC Ikigai #BIP-110
@btc2ikigai
Why I'm stepping back from SHA-256 mining (and what that means for Hashrate Autopilot): github.com/rdouma/hashrate-autopilot/discussions/377
-
Luke Dashjr reposted
XBT | Hardfork cguida | ⚡🪢
@cguida6
Bitcoin Blake2b testnet4 is already way more decentralized than suitcoin
-
Luke Dashjr
@LukeDashjr
BTW, Knots 29.4.1rc1 trial run of BLAKE2b PoW change on testnet4 later tonight.
Hop on the Discord to get help setting it up (or maybe people focused on the mining side can reply here with tips).Post not available here, view on X
Luke Dashjr
@LukeDashjr
Well, that was fun. The (completely uncalibrated) difficulty adjustment for the algo change was WAY too low since it started from a testnet4 difficulty. Blocks every second until the first adjustment. And because of a special testnet4 rule, the adjustment went too far in the opposite direction, leaving us with 1 block per 50 days. Will have to address these for rc2 before we can realistically test transactions.
Luke Dashjr
@LukeDashjr
For rc 2, use:
blake2b_headline=Totoro -
Luke Dashjr reposted
Nithu Sezni BIP110 Suit
@nithusezni
Boycotting products of anti BIP110 companies would have saved cold card users 100 million dollars.
Bitcoin Lebowski⚡
@DudeJLebowski
Where is NVK?
Where is that shady dev?
Where are the arrests? -
Luke Dashjr reposted
Roughnecks
@Roughnecks110
Patiently waiting for the Blake2b POW change. Bitcoin is proving its antrifragility despite being written off by fiat maxis and big blockers.
Tick tock, next block -
Luke Dashjr reposted
mastercheese
@mastrchz
If you want to mine on testnet4 today for the dry run, use blake2b_headline=rc1 in your bitcoin.conf
-
Luke Dashjr reposted
SpectrGen // XBT
@SpectrGen
It's invigorating how amped people are to help restart the chain. This community is amazing 🔥
Luis Marcano 🦉 Bitcoin
@MarcanoFilms
I have no asic because it’s everything sold out 🤣😕 but I’m still experimenting with my gpu in the mid time lol it is alive and mining Bitcoin on Blake2b ❤️
-
Luke Dashjr reposted
Connor's Lab ⚡️ #BLAKE2b
@ConnorsLabYT
No other words needed. #blake2b
-
Luke Dashjr reposted
Cato the Youngest
@YoungBTCato
A few days back I was really demoralized about bitcoin.
Now I’m actually super excited about the POW change. A fresh start and clean out of the people who don’t gaf about Bitcoin anyway beyond how they can abuse it/enrich themselves. -
Luke Dashjr reposted
HardDuke 1 year coinbase maturity
@DukeDukingtonRD
The latest from bitcoin influencers is:
"If we need to increase the bitcoin supply less than 1% a year to pay miners, I'll do it".
Demurrage or tail emissions ARE coming on BCache-Saylor'sVision. And you will be viciously mocked for opposing it. -
Luke Dashjr reposted
mastercheese
@mastrchz
Stayed up super late last night getting my own DATUM fork working for BLAKE2b/-sia testing using the draft hardfork PR @LukeDashjr posted the other day, applied to my node
We are hashing, team 🔥 -
Luke Dashjr reposted
SpectrGen // XBT
@SpectrGen
How do BLAKE2b-Sia ASICs compare with Bitcoin SHA256d miners?
Raw TH/s is meaningless across algorithms, so I normalized each miner by its share of network hashrate and expected solo block interval, then matched similar power tiers.
The results are absurd.
Example: a 130W HS BOX at 470 GH/s represents ~0.00651% of Sia’s 7-day hashrate.
The same share of Bitcoin’s 926.98 EH/s is ~60.3 PH/s—about 10,057 Avalon Nano 3S miners drawing ~1.41 MW.
That also gives the same expected solo-block interval: ~107 days for 1 HS BOX on Sia, versus ~107 days for that ~10,057-Nano fleet on Bitcoin.
One Nano 3S by itself is roughly a 2,939-year statistical wait at this network hashrate.
This is NOT saying a BLAKE2b hash does 128,000× the cryptographic work of a SHA256d hash.
It compares each miner’s share of the network it actually competes on.
Both chains target ~10-minute blocks, so equal network share ≈ equal expected block-finding probability.
Across the hardware ladder, the pattern persists: similarly powered Sia ASICs represent vastly more of their current network than similarly powered Bitcoin ASICs represent of Bitcoin.
Full methodology, 22-model table, sources and caveats in the article:
SpectrGen // XBT
@SpectrGen
-
Luke Dashjr reposted
Connor's Lab ⚡️ #BLAKE2b
@ConnorsLabYT
To anyone interested in trying to run DATUM for Bitcoin Blake2b with a regtest node, there is an implementation in the works:
github.com/Maveth/datum_gateway/tree/bip110-pow-v2
I’ve submitted some PRs to address some share rejection issues as well as some general JSON string parsing/handling errors. -
Luke Dashjr reposted
Donal
@DonalDevine
Spamcoin is cooked and Luke won't be there to save it.
-
Luke Dashjr reposted
Bitcoin XBT
@BitcoinXBT_
Miners get paid once. Spammers and VCs cash out. Node operators get lifelong unpaid storage duty. Bitcoin’s "fee market" only rewards the people stuffing the chain never the people forced to carry the garbage forever.
-
Luke Dashjr
@LukeDashjr
-
Luke Dashjr reposted
SpectrGen // XBT
@SpectrGen
₿itcoin-GUS🧡
@Scavacini777
What timeline is this?
Kratter, please brother, stop attacking Bitcoin
Let's go back to the drawing table as a community.
Not take our ball and go home, forking off. Please. -
Luke Dashjr reposted
Joyce Dawn
@BitcoinWifey
Dude! “Bitcoin’s antifragile, so it doesn’t need to be defended” is exactly backwards.
Bitcoin’s antifragility is not some intrinsic magical property in the code that means no one has to defend it.
The entire point is that Bitcoin can take stress, expose weaknesses, and the people who care respond to the threat, adapt, + strengthen the network.
That response by people who defend Bitcoin is the antifragile mechanism.
randall mchodl
@randallmchodl
It’s because you never understood what being antifragile truly means
-
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
"longest chain" was Bcash's position.
The Bitcoin community rejected that.
Bitcoin is the longest valid chain.
And blocks that don't signal BIP110 are not valid. -
Luke Dashjr reposted
Joyce Dawn
@BitcoinWifey
To pretend Luke and Mechanic are leading some sophisticated social engineering campaign could not be more ridiculous.
Luke! Seriously. He is the least socially strategic person in bitcoin. Hes a technical literalist with essentially negative PR instincts.
If you think that is what manipulation looks like, you’re doomed -
Post not available here, view on X
Luke Dashjr
@LukeDashjr
"longest chain" was Bcash's position.
The Bitcoin community rejected that.
Bitcoin is the longest valid chain.
And blocks that don't signal BIP110 are not valid. -
Luke Dashjr reposted
hodlonaut
@hodlonaut
“Tail emissions and Demurrage”
Such cool concepts for slaying the 21M cap.
Under the current regime, this is a matter of time.
Five years ago, anyone saying it’s hard to define spam, or hard to say what Bitcoin is, would be shunned and laughed out of the room.
Compromise on ethos and integrity is a slippery slope.
I give it five years until people against tail emissions and demurrage are ridiculed by Big Bitcoin and their simps as delusional non technical retards.
bitcoin++ @ seoul, nov 5-6 🇰🇷
@btcplusplus
NOW LIVE 🎥: Tail Emissions and Demurrage
Featuring: Peter Todd (@peterktodd)
youtu.be/OmAAeEm1nIE -
Luke Dashjr
@LukeDashjr
To build the short list of potential algorithms to use as Bitcoin's new PoW, I focused on 4 criteria:
1) Existing fleet of ASICs available. Without this, the first manufacturer would get a HUGE advantage - and Bitcoin would be dominated by malicious botnets in the interim.
2) The ability for new ASIC manufacturers to easily enter the market after the market had matured. This is mainly determined by the complexity of the algorithm, but dependency on SRAM was considered (though ultimately irrelevant in practice).
3) The risk of another mathematical break like ASICBoost did to SHA256d.
4) The fundamental principle of proof-of-work: that it can be verified very easily, even while being difficult to mine. -
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
ASICs are entirely unavoidable. The best we can do is ensure they are widely available and easy to make.
BLAKE2b (and the other candidates) checks those boxes.
There's like 6 manufacturers, and the algorithm is simple enough for a new entrant to compete. -
Post not available here, view on XPost not available here, view on X
Luke Dashjr
@LukeDashjr
ASICs are entirely unavoidable. The best we can do is ensure they are widely available and easy to make.
BLAKE2b (and the other candidates) checks those boxes.
There's like 6 manufacturers, and the algorithm is simple enough for a new entrant to compete. -
Luke Dashjr reposted
Luis Marcano 🦉 Bitcoin
@MarcanoFilms
1/4 @LukeDashjr just opened a draft PR on Bitcoin Knots: Hardfork to a new BLAKE2b proof-of-work algorithm.
This is not vaporware. It’s concrete engineering. github.com/bitcoinknots/bitcoin/pull/359 -
Luke Dashjr
@LukeDashjr
This is the kind of disgusting person Bitcoin is up against.
He thinks forcing bitcoiners to distribute CSAM is "beautiful", falsely compares it to merely having records of others doing illegal transactions, & thinks the problem isn't CSAM, but rather _talking about the issue_.
The Bitcoin Dialectic 🎙️
@Digvijay_BTC
Fact: There’s child p*rnography on Bitcoin.
@cbspears: This isn’t something we knew until @LukeDashjr, @GrassFedBitcoin, and @mattkratter thrust it into the forefront of the conversation.
So whose fault is it that everyone is talking about this now?This media couldn't be displayed. See it on the original post.
Luke Dashjr
@LukeDashjr
Also note his claim that there _is_ CSAM on Bitcoin already is a lie!
-
Luke Dashjr reposted
Blake Hammond🔥⛏️
@FieldNas
People are looking at this hardfork in light of the bad memories of prior hardforks, conspired over bad motives, when the parent chain was yet healthy.
That's not the case here. This hardfork should be viewed relative to the disaster Bitcoin has become. Its potential for success should be weighed against the guaranteed failure of the captured parent chain.
New fork concerns are real - network effects - market dynamics - 51% attacks et al. But you can't keep what you've already lost. You don't have a Bitcoin to "stay and fight for." Your only tool for change was just proven neutered.
The PoW change IS the tool. It was talked about for years inside of thought experiments on how Honey Badger could protect himself from exactly what is happening today.
If you've been around a while, you can see this isn't what Satoshi created. If you're new, maybe you can't. But if we're afraid to risk our fiat gains, our reputation in the space, or our funnest hobby, just to keep but a caricature of Satoshi's Bitcoin and the relevance it, and its pretend security paper wealth, brings to our lives, shame on us.
"What did you build us Mr. Nakamoto?"
"Sound money...
... if you can keep it." -
Luke Dashjr
@LukeDashjr
Appears to be fiction, but could just as well be reality
𓂀 | #BIP110
@__B__T__C__
It appears that @f2pool has just mined and distributed—in block 962408—a file that is illegal in most existing jurisdictions.
The entire @bitcoincoreorg network has been affected, and using it will almost certainly result in criminal and legal charges.
1/6 -
Luke Dashjr reposted
XBT Younger Dryas - Blake2b
@Eris_The_Red
SCAM ALERT! If you hold the old spamcoin, you have an equal number of new bitcoin waiting for you. If anyone tells you that you can "just spend them" About either coin they are lying to you to attempt a replay attack and steal your coins. Do not try to spend your coins yet.
-
Luke Dashjr reposted
1-year Coinbase Maturity Dave BIP-110⚡️
@davelund_
>try to fire core
>inspire users to run nodes
>coretards calls up suits
>suit stocks are down -98%
>all time low ticket sales at btc confs
>coretards & suits calls up pool execs
>pool execs listen to core & suits
>pool execs screw the users
Consensus. -
Luke Dashjr reposted
XBT Younger Dryas - Blake2b
@Eris_The_Red
Holy moly! Check the fees on the next Bitcoin block. Hope my Bitaxe grabs that one before the PoW change!
-
Luke Dashjr reposted
Carnivorous ₿redneck
@phonyfiat
The fork that remains decentralized, scarce and secure will eventually overcome the fork that is lesser in any those. Why? Because its better money.
If you don't believe that to be true then you never understood Bitcoin to begin with. -
Luke Dashjr reposted
.
@GrassFedBitcoin
I haven't felt like this since covid.
Couldn't do anything because you needed a vaccine pass. Excluded from everything. Churches, schools, restaurants, air travel etc.
Similarly my Bitcoin stack has ground to a halt. Money no longer moves.
There are no on and off ramps as there isn't an exchange in the world that followed the UASF that I know of.
Mining variance is similarly insane.
The explorers and wallets I use will all have to be updated to accommodate the fork and the ecosystem has largely ignored the fork.
Daunting, but I'm not alone in it. There are thousands of people dealing with it and they're the only people I'd want to be isolated with. -
Luke Dashjr
@LukeDashjr
Facts:
1) Saturday, bad actors attempted a contentious hardfork with the purpose of forcing users to distribute CSAM. This spawned a new scamcoin with an airdrop (I call Bpedo).
2) Most formerly Bitcoin pools (a small handful of people) then began to attack the Bitcoin network to try to deceive the world into thinking Bpedo is "the real Bitcoin".
3) People who aren't using full nodes are easily fooled because they don't validate the blockchain. Upgrading to a full node (such as the latest release of Bitcoin Knots) will put you back on the Bitcoin network.
4) Community-led mitigations are in progress to overcome the ongoing attack on the Bitcoin network and restore it to full functionality. And update with these mitigations is expected by September 1st. -
Luke Dashjr reposted
Roughnecks
@Roughnecks110
GM Roughnecks!
Anyone got a conf overnight?🙌
We went 3 days and 8 hours between blocks.
Bitcoin's record is 5 days between the genesis block and block 1.
Thank you to all the low-time preference plebs running nodes🙏
Tick tock, next block⛏️ -
Luke Dashjr reposted
OptOut Toxic ₿.
@HCFOptOut
Perfect irony: BIP110 fails, Luke removed → immediate response= “reopen the Ordinals PR"
Bitcoin’s current trajectory= data storage, ordinals, inscriptions, shitcoinery, fiat-minded suitcoiners, and corporate treasuries treating it like a casino asset.
Sky
@skysupersonic
In light of BIP110, its utter failure, and Luke Dashjr's removal as BIP editor, I hereby request @rodarmor to reopen the Ordinals PR.
Previously, the editors refused to assign Ordinals a BIP number (due to Dashjr's opposition) so after years of staleness, it was removed by Casey himself.
This is not a consensus change. It is only a call to recognize a user base of 500k+ who view sats ordinally and have inscribed / collected accordingly.
Recent activity has highlighted some of the hypocrisy of the BIP process and this presents the perfect opportunity to right a wrong.
Plus, nothing says FU to the forking shitcoiners like legitimizing the reason they forked themselves in the first place.
- ordinal maxi -
Luke Dashjr reposted
-
Luke Dashjr reposted
-
Luke Dashjr reposted
Luis Marcano 🦉 Bitcoin
@MarcanoFilms
The miners didn’t just ignore BIP-110.
They publicly demonstrated that node consensus is optional when money is on the line.
What’s running on the heaviest chain now isn’t Bitcoin.
It’s a permissioned database with a marketing department. -
Luke Dashjr reposted
₿TC Trek
@btctrek
There isn't more Core supporters than BIP110. They just have more miners/hashpower, they have resources to spin up 18,000 sybil nodes at the last minute, & they know how to put Comcast nodes on blacklists.
-
Luke Dashjr
@LukeDashjr
So here's the plan for selecting Bitcoin's new PoW algorithm:
Nobody knows the new algorithm right now, and nobody will until we all know at the same moment.
At 14:00 UTC August 11th, we will begin watching Bitcoin's Testnet4 chain for new blocks.
The very next block found, look at the block hash.
The last character will choose the new algorithm.
(Note that testnet4 blocks are typically timestamped wrong!)
As soon as I see that block, I will reveal the mapping showing which algorithm that character represents.
Throughout the last 24+ hours, the community has discussed and made a short list of candidate algorithms.
I compiled that list into a weighted (according to their suitability) set of options for the mapping list.
You can prove I didn't rig it, by SHA256 hashing the mapping text file.
It will match 71a7960874f3352f4ba600ce67bd6f8e96702565abea93021fa86349d99a45e8Post not available here, view on X
Luke Dashjr
@LukeDashjr
Seems Bpedo trolls intentionally mined 3 blocks at once to disrupt things. Do we try again, or just stick with SHA3x?
Luke Dashjr
@LukeDashjr
b96b58acccb69746ea7b2f1b9793ed53cda2cdbe5fd7d5ef1878178bbef537f0
Post not available here, view on X
Luke Dashjr
@LukeDashjr
It's been an hour. Clearly I set the bar too high. I will reveal the previous criteria when we're done.
In the meantime, here is the new criteria:
ba712f48962a43163266cec09a069825b89a316140a9701fa4931b5fb6407f4e
Luke Dashjr
@LukeDashjr
For the record, the previous criteria was "Next Testnet4 block after 14:45 UTC that goes uncontested for 5 minutes. 0-7 is SHA3x, 8,9,a-f is BLAKE2b."
Post not available here, view on X
Luke Dashjr
@LukeDashjr
2026-08-11T17:02:11Z Saw new header hash=0000000000000001bcda56f2ec833fe96b4585a1953124b2c1c1f9a34709a027 height=147949
2026-08-11T17:02:12Z Saw new header hash=00000000006859c534d62586f46354cd20615c5edfbc063d451254c7724da14d height=147950
2026-08-11T17:02:14Z Saw new header hash=0000000000750724f5e39437cc3661f3da66ec05dd8eccb7ad33b0089efe8ccc height=147951
2026-08-11T17:02:16Z Saw new header hash=0000000000012c9f64670244da8b031a629ecdb7a4f5831913b8ce6f0e92e349 height=147952
Everyone get this?
Luke Dashjr
@LukeDashjr
7+D+C+9 = 29
9 = BLAKE2b -
Luke Dashjr reposted
PyBLØCK
@_PyBlock_
It could be very interesting to try mining blocks non-stop until that date; they could appreciate significantly in value. #bip110 #rdts #bip444
Luke Dashjr
@LukeDashjr
Target is Sep 1. Need to write and properly test the code first... Until it's ready, SHA2 continues on.
-
Post not available here, view on X
Luke Dashjr
@LukeDashjr
Target is Sep 1. Need to write and properly test the code first... Until it's ready, SHA2 continues on.
-
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
7+D+C+9 = 29
9 = BLAKE2b -
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
It's been an hour. Clearly I set the bar too high. I will reveal the previous criteria when we're done.
In the meantime, here is the new criteria:
ba712f48962a43163266cec09a069825b89a316140a9701fa4931b5fb6407f4e -
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
b96b58acccb69746ea7b2f1b9793ed53cda2cdbe5fd7d5ef1878178bbef537f0
-
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
Seems Bpedo trolls intentionally mined 3 blocks at once to disrupt things. Do we try again, or just stick with SHA3x?
-
Luke Dashjr reposted
Lori Singer Meyer
@Loriss65
I dare CNBC to run a segment and talk about Bpedo. Name and all.
Luke Dashjr
@LukeDashjr
Do realize that Bpedo (or Corecoin, or whatever you want to call it) is _exactly_ what "Segwit2X" and BCash would have looked like if the miners went along with them.
It is in fact a contentious hardfork attempt. Are you just going to give in? Or stay on Bitcoin and fight? -
Luke Dashjr reposted
Bitcoin Knots
@BitcoinKnots
The Bitcoin network is under attack, and block production has slowed significantly.
The community is preparing mitigations to resolve the situation. In the meantime, attackers are spreading misinformation and advising users to downgrade or switch to insecure node software. -
Luke Dashjr
@LukeDashjr
Do realize that Bpedo (or Corecoin, or whatever you want to call it) is _exactly_ what "Segwit2X" and BCash would have looked like if the miners went along with them.
It is in fact a contentious hardfork attempt. Are you just going to give in? Or stay on Bitcoin and fight? -
Luke Dashjr
@LukeDashjr
I am taking a sabbatical from OCEAN as Chairman and CTO and will turn my immediate focus to working on Bitcoin and open-source projects to support Bitcoin. I believe this is the best use of my time and is in the best interests of Bitcoin and Bitcoin’s long-term health.
-
Luke Dashjr reposted
Extractive Ghost of Unhosted Marcellus 👻
@oomahq
^ btw this confession from Jonathan Bier confirms that 100% of the hashrate knew about the BIP-110 proposal.
A common psyop deployed during the last months by him and other bad actors was that miners weren't even aware of it, and described it as just "twitter drama". -
Luke Dashjr reposted
Roughnecks
@Roughnecks110
GM Roughnecks!
Bitcoin has stalled on block 961633 because some miners have decided to fork themselves off the network by mining on an invalid chain.
Meanwhile, Bitcoin continues without them.
Since our announcement on Saturday night that we're pausing operations, we have been inundated with feedback.
You've spoken, and we hear you loud and clear!
We have decided to resume mining ASAP on the stalled chain tip⛏️
Bitcoin is alive and well and its reference client is called Knots-RDTS🪢
We will continue mining until a sensible POW change can be implemented to replace the centralized mining pools that left💪
We're wildcatting again😻 -
Luke Dashjr reposted
Pepetricio Carvajal
@CPepetricio
Bitcoin's value isn't derived from some autonomous system that just continues into the future by itself- it only gains it value and relevancy by the people that run it. Once you change who runs it, so does Bitcoin.
-
Luke Dashjr reposted
Balkan Hodl
@balkanhodl
Join the war room. It's not over.
Luke Dashjr
@LukeDashjr
Yes, hold tight.
There's ongoing discussion today about how to move forward
discord.gg/scKhfvBnp -
Luke Dashjr reposted
Secure Sovereign 🚀₿🧡
@secsovereign
BIP-110 failed yesterday. Today, Murch filed a motion to remove Luke Dashjr as a BIP editor.
Read the grounds carefully. Some are procedural. Luke assigned a BIP number out of band and merged a PR minutes after it opened. Fine, argue those on the merits.
But one of the listed reasons is his championing of a contentious soft fork. That is a political criterion applied to a role that BIP 1 and BIP 2 both define as administrative and editorial, with the explicit instruction that editors will not unreasonably deny a proposal. The role was never designed as a content gate. The motion treats it as one.
Worth noting who wrote what. Luke authored BIP 2, the process document that governed BIP editing for nine years. Murch authored BIP 3, which replaced it last year and explicitly reduced the judgment calls assigned to the editor role. So the process was rewritten to narrow Luke's discretion, and now Luke is being removed for exercising discretion.
The contribution statistic deserves the same scrutiny. Fewer than 1% of editor comments since April 2024 sounds damning until you remember that April 2024 is when additional editors were added, after years of Luke handling the role alone and unpaid while people complained about the backlog. He is among the most prolific and longest-tenured contributors in Bitcoin Core's history. He founded Eligius, wrote BFG Miner, maintains Knots, and co-founded Ocean. The picture of a man who stopped showing up does not survive contact with his actual record.
Every remaining editor now knows what happens if they back a proposal the funding-aligned consensus opposes. The motion does not need to succeed to accomplish that. -
Post not available here, view on X
Luke Dashjr
@LukeDashjr
Yes, hold tight.
There's ongoing discussion today about how to move forward
discord.gg/scKhfvBnp -
Luke Dashjr reposted
Dathon Ohm / BIP-110
@dathon_ohm
Update: it appears that the large mining pools have colluded to turn Bitcoin from money into a toxic data dumping ground by executing a secret hardfork against the Bitcoin node network.
The community is working on proposal for a proof-of-work change to fire the miners. -
Luke Dashjr reposted
hodlonaut
@hodlonaut
I fully accept what happened yesterday. It is sad, I will admit that. But it also feels like a catharsis.
BIP-148 is celebrated as Bitcoin Independence Day, because it proved that ordinary users, running nodes in their homes, could force the most powerful mining cartels and corporations in the industry to back down. The users had no hashrate, no exchanges, no lobbyists. They had conviction and they had nodes, and that was enough.
BIP-110 ran the same play with the same conviction, a reasoning that was shared by all bitcoiners five years ago (Bitcoin is money and not a grift database), and node support at levels at least comparable to 2017. This time the miners and the corporate layer simply refused to follow. They extended their spam-friendly chain and moved on like nothing happened.
Remember yesterday as Bitcoin Dependence Day.
What changed between 2017 and 2026?
Not the users. They showed up with the same fire.
What changed is everything that grew in the years between. ETFs. Treasury companies. Custodians holding millions of coins for people who will never touch a node. Hashrate concentrated into a handful of pools building templates for the whole world. Capture of the governance of the reference implementation resulting in stark philosophical pivot.
Those already celebrating Bitcoin Dependence Day are not simply cheering an outcome they won. They are treating evidence that miners and the corporate layer now control Bitcoin as if it were a grand cypherpunk victory, while ridiculing the people who fought for decentralization and for Bitcoin as money.
In my opinion, and in my heart, legacy Bitcoin is not what I signed up for. Captured. Centralized. Led by suits.
No longer about freedom, sovereignty, or the mission of separating money from state.
No longer about the things that made me a ride or die bitcoiner for many years.
The fire that originally drew me to Bitcoin is still alive in the node runners who supported BIP-110. I will follow it where it goes.
As for legacy Bitcoin, I have no interest in it anymore as a freedom project. In my mind, it is now a stock. -
Luke Dashjr reposted
Puncher75 -
@Puncher522
See if you sense the loss of the heart and soul of Bitcoin leaving the building over the next few weeks and months. Proof of Stake just doesn’t vibe the same. Wall Street derivative Bitcoin doesn’t vibe the same. The shitcoin vibes are a whole other frequency.
Wish all freedom lovers the best. -
Luke Dashjr reposted
Bryan
@Bryan10309
The federal reserve, with 12 members, is more decentralized than bitcoin.
-
Luke Dashjr reposted
George Bodine
@Jethroe111
Just got home from the studio.
Opened a beer.
6 Bitcoin miners on planet Earth-all with ties to governments and industry-now basically are in charge of Bitcoin.
If like me you believe Bitcoin must remain decentralized to succeed long term... you might wish to share a beer with me this evening.
Or two. -
Luke Dashjr reposted
-
Luke Dashjr reposted
XBT Motorist
@BitcoinMotorist
That juicy block is sitting there, waiting for some greedy miner🪙 10x in fees of what's available on the bcache fork👀
-
Luke Dashjr
@LukeDashjr
Bad actors are once again spreading lies about BIP110's death.
BIP110 has NOT failed. Do not give in to their gaslighting. -
Luke Dashjr reposted
Roughnecks
@Roughnecks110
Looks like we're wildcatting!
Those of you in the oil business know exactly what wildcatting means😻
Tick tock, next block⛏️ -
Luke Dashjr
@LukeDashjr
PSA: If you haven't upgraded to Bitcoin Knots 29.3.knots20260508 (or 29.4) yet, you are now vulnerable to double-spending attacks aided by @FoundryServices and @AntPoolofficial .
Upgrade ASAP to avoid accepting counterfeit bitcoins. -
Luke Dashjr
@LukeDashjr
. @AntPoolofficial appears to be attacking Bitcoin. Hold tight everyone.
Luke Dashjr
@LukeDashjr
@f2pool joins in the attack
Luke Dashjr
@LukeDashjr
x.com/simpleminingio/status/2086191736456675351
Simplemining attacking too.
Simple Mining
@simpleminingio
@ocean_mining appears to be attacking Bitcoin.
Hold tight everyone
Luke Dashjr
@LukeDashjr
. @AntPoolofficial appears to be attacking Bitcoin. Hold tight everyone.
Luke Dashjr
@LukeDashjr
@FoundryServices too, also attacking Bitcoin. SMH.
-
Luke Dashjr reposted
Roughnecks
@Roughnecks110
Tick tock, next block
-
Luke Dashjr reposted
₿itcoin Commonwealth
@BTC_Prep
Luke Dashjr
@LukeDashjr
Reminder: Nobody has made a counter-fork to reject BIP110. So BIP110 remains uncontested. Activation is certain.
-
Luke Dashjr
@LukeDashjr
Reminder: Nobody has made a counter-fork to reject BIP110. So BIP110 remains uncontested. Activation is certain.
-
Luke Dashjr reposted
Bitcoin Knots
@BitcoinKnots
Bitcoin BIP110 mandatory signaling begins in approximately 6 hours, so it is crucial for security to be running at least the previous version (29.3.knots20260508) released in May.
-
Luke Dashjr reposted
Roughnecks
@Roughnecks110
GM Roughnecks!
We're ready for any outcome. In case of chain split today, see this handy graphic @FlyTheElephant1 made based on our article. Also, read the article if you haven't yet🙏 -
Luke Dashjr reposted
Joyce Dawn
@BitcoinWifey
If you oppose the UASF but shirked your responsibility to enforce that rejection yourself, then celebrate miners for rejecting it, you’ve accepted a new constitutional order.
You’ve accepted that the rules of Bitcoin are whatever a small group of miners are willing to mine. You’ve turned miners from employees into your gatekeepers.
You handed the job of defending Bitcoin to the people Bitcoin was designed to keep accountable.
That is a much bigger change to Bitcoin than BIP-110 ever was -
Luke Dashjr reposted
Dathon Ohm / BIP-110
@dathon_ohm
All that remains to be seen is whether the mining industry still wants to mine Bitcoin, which is money, or if it wants to hardfork to mine the Core altcoin, which is a toxic data dumping ground. Either way, the miners don't decide what Bitcoin is; the nodes do.
-
Luke Dashjr reposted
Dathon Ohm / BIP-110
@dathon_ohm
80% of the node network supports BIP-110's rules, and there are zero nodes on the network that would reject the BIP-110 chain, (including the other 20% with the expanded rules).
-
Luke Dashjr reposted
Dathon Ohm / BIP-110
@dathon_ohm
With just 130 blocks (~21 hours) to go until mandatory signaling, support for BIP-110, a critical security fix for Bitcoin, has never been stronger!
-
Luke Dashjr
@LukeDashjr
~24 hours until signaling BIP110 becomes mandatory for Bitcoin miners.
Mining blocks without signaling will then forfeit all block rewards!
Luke Dashjr
@LukeDashjr
If you need any help upgrading or in general, there's several volunteers hanging out on the Knots Discord ready to assist:
discord.gg/cU56QucRd
Luke Dashjr
@LukeDashjr
Note that this is a public chat, and scammers hang out on all chat networks. Do not trust anyone, especially not if they send you private messages!
-
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
If you need any help upgrading or in general, there's several volunteers hanging out on the Knots Discord ready to assist:
discord.gg/cU56QucRd -
Luke Dashjr reposted
Bitcoin Knots
@BitcoinKnots
Bitcoin Knots 29.4.knots20260508 released! 🎉
Be sure to verify your download(s)!
bitcoinknots.org?29.4.20260508?twitter -
Luke Dashjr reposted
Axexang
@axexang
Anyway, if the miners are "captured", the 21M limit is not enforceable anymore which means Bitcoin is not sound. Firing them is the only way out at this stage.
-
Luke Dashjr reposted
Charlie Shrem
@CharlieShrem
8 years ago cutting the #segwit cake with @LukeDashjr and @courtmwarner. I love #bitcoin let’s work together!
-
Luke Dashjr reposted
Blake Hammond🔥⛏️
@FieldNas
He is no fool who gives up 1 to keep 999.
Miner's will flip the bit, because they're not stupid. -
Luke Dashjr reposted
Lori Singer Meyer
@Loriss65
If I had the time, I would do a deep dive on consensus because somewhere along the way of almost 30 years, the meaning of the term has gotten lost. Consensus is derived out of a community, and the one consensus I guarantee the community using Bitcoin shares is that CSA is an evil practice, and CSAM does not belong on the Blockchain, for moral, ethical and in the USA, perhaps most importantly, legal reasons.
Maybe BIP-110 won't prevent all CSAM from landing immutably on the Blockchain, but the effort against CSAM then becomes a constant one going forward, with BIP-110 giving a baseline of protection.
If large mining pools can not, in good conscience, flip the bit and ensure that this consensus against CSAM is enforced, they are opening themselves up to potential legal liabilities when CSAM becomes immutably embedded in the Bitcoin blockchain because of their current inaction that anybody who has captured them will not be able to protect them against. The captors are feeling pretty safe in their beds tonight, but those captured do not get the same luxury when Interpol and the FBI come knocking on your door, and reach beyond the corporate veil to individuals.
I would weigh my risks carefully.
Please pass this on.
@NickSzabo4 @1914ad @mattkratter @EternalFunShine @secsovereign @LukeDashjr
@dathon_ohm @GrassFedBitcoin @CatoTheElder17
Dathon Ohm / BIP-110
@dathon_ohm
Failing to enforce a softfork that has consensus is a hardfork.
-
Luke Dashjr reposted
Blake Hammond🔥⛏️
@FieldNas
If Core loses, they take a setback on their scammy dreams. If BIP110 loses, we lose truth, we lose everything! Because Bitcoin becomes centralized shitcoin.
This is why we're compelled to act as adults, while all they do is embarrass themselves by laughing, lying, and behaving like bad children.
If they had any legitimacy, they would be fighting like men with a serious URSF, not coking & smoking, which is all they know how to do other than scam & hack.
Miners aren't dumb, they'll flip the bit. They won't throw away a mountain of 24-karat-pay-dirt to chase tiny spam nuggets in a foul river of filth. -
Luke Dashjr reposted
Philip D'Ath
@philip_dath
For those around UTC+12, BIP110 mandatory signalling starts on Sunday.
The 48-hour countdown is on!
Luke Dashjr
@LukeDashjr
Nobody can delay the BIP.
Mandatory signaling begins Saturday.
Lock-in is 2 weeks later.
Activation is another 2 weeks.
This has always been the schedule. -
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
Nobody can delay the BIP.
Mandatory signaling begins Saturday.
Lock-in is 2 weeks later.
Activation is another 2 weeks.
This has always been the schedule. -
Post not available here, view on X
Luke Dashjr
@LukeDashjr
BIP110 is not active for another month.
Do not rely on OP_RETURN to prevent replay.Post not available here, view on X
Luke Dashjr
@LukeDashjr
Nobody can delay the BIP.
Mandatory signaling begins Saturday.
Lock-in is 2 weeks later.
Activation is another 2 weeks.
This has always been the schedule. -
Luke Dashjr reposted
₿itcoin ₿ombadil
@BitcoinBombadil
FYI
Luke Dashjr
@LukeDashjr
BIP110 is not active for another month.
Do not rely on OP_RETURN to prevent replay. -
Luke Dashjr reposted
Joyce Dawn
@BitcoinWifey
How would you feel if you found out miners/pools were being forced by “institutions” to NOT signal BIP-110?
What would that mean for bitcoin?
Honest question..
Cedric Youngelman ⚡️
@CedYoungelman
Hodlonaut on the pressure campaign to make him drop BIP-110:
"The lengths people have gone to, to intimidate me out of supporting it. My DMs are full of it. People reaching out: what are you doing with this BIP-110 support? Your reputation is going to hell.
It starts with friendly nudging, then threats. And then, when they realize I'm actually tying myself to the mast, it's just straight hostility and smearing.
But I don't care what people I don't respect say about me. I don't want any standing or position among people who don't share my principles. I'm very much supporting BIP-110."
@hodlonaut on The @_BitcoinMatrix #286.This media couldn't be displayed. See it on the original post. -
Luke Dashjr reposted
XBT Motorist
@BitcoinMotorist
I've been saying this. The same people behind the big blockers have regrouped and learned from previous mistakes but they're still underestimating the nodes.
In 2017 we learned the miners don't control Bitcoin.
In 2026 we will learn the devs don't either
.
@GrassFedBitcoin
Current perspective -
They tried to crudely wrestle control of Bitcoin away from the sovereigns with the "hard forks" in 2017.
They realized that it just doesn't work. So instead this time around there's a Fabian style infestation of the space and it has become captured rather than overtly conquered.
It's very hard to defend against this because the attacks are all small enough to make any concrete pushback appear to be an overreaction.
Anyone who can extrapolate forward can see that anything that undermines Bitcoin's identity as a monetary protocol, if not rejected decisively, results in eventual death.
It's not here to compliment the dollar, it's here to replace and destroy it. Cope to the tune of "trojan horses" is now and always was self deception.
Protocol capture is real and the norm for freedom tech that reaches levels Bitcoin has.
People continue to underestimate the threat Bitcoin poses to the system and refuse to understand the lengths to which that system will go in neutering it.
I'll have more to say over the coming days as we establish whether the industry still respects the decentralization necessary to maintain our disruptive potential or if it chooses to close ranks and become a servant of the fiat apparatus currently coopting the network. -
Luke Dashjr reposted
-
Luke Dashjr reposted
Jim
@elkrun21
If the miners don't signal for BIP110 by this weekend then we'll know the Bitcoin network is no longer decentralized, and has been captured. We'll know bitcoin on this network is nothing more than another fiat instrument.
If miners reject BIP110 then bitcoin as immutable money will survive only if it's adopted on another chain.
I really hope it doesn't come to that. -
Luke Dashjr reposted
skot
@skot9000
The coldcard entropy bug would still have been exploited to steal funds even if the firmware source wasn't viewable.... But there would be no survivors.
DEMAND OPEN SOURCE -
Luke Dashjr reposted
Ned17Flanders Let Freedom Ring
@Ned17Flanders
It has been raining for several years, it is time.
In 2 days we float the Ark.
Run Knots and BIP-110
God Save Bitcoin
GodWins -
Luke Dashjr reposted
XBT | Hardfork cguida | ⚡🪢
@cguida6
BIP110: How Bitcoin Wins
My talk at @btcplusplus Toronto
Friday July 24, 2026
youtu.be/6c7YQO6tPSQ -
Luke Dashjr reposted
₿itcoin ₿ombadil
@BitcoinBombadil
BIP-110 is compatible with Bitcoin’s monetary mission.
Core v.30 is incompatible with Bitcoin’s monetary mission.
If you know, you Knots + BIP-110 + DATUM + Ocean
Filters up!🛡️ -
Luke Dashjr reposted
Donal
@DonalDevine
It's pretty clear, there is absolutely no consensus for large OP_RETURNs
-
Luke Dashjr reposted
Dathon Ohm / BIP-110
@dathon_ohm
BIP-110 is a movement by the plebs, for the plebs, standing up and arming themselves with software to tell these institutions in one resounding, unified voice:
BITCOIN IS MONEY, OUR NODES BELONG TO US, AND WE WILL NEVER GIVE UP. -
Luke Dashjr reposted
Dathon Ohm / BIP-110
@dathon_ohm
Bitcoiners are about to show the world, once again, what happens when the plebs stand up against large, corrupt institutions who are telling us Bitcoin isn't money and our nodes belong to them, to store as much of the most toxic garbage on as they want.
-
Luke Dashjr reposted
Dathon Ohm / BIP-110
@dathon_ohm
All miners should immediately upgrade to a BIP110-enforcing node in order to avoid producing invalid blocks. All users are also recommended to upgrade, in order to avoid accepting invalid blocks. The latest release of Bitcoin Knots is recommended: bitcoinknots.org
-
Luke Dashjr reposted
Dathon Ohm / BIP-110
@dathon_ohm
We are grateful to the many miners who are signaling readiness now.
However, many other miners are still failing to signal. The longer miners wait to signal, the more disruption they will be responsible for causing. -
Luke Dashjr reposted
Dathon Ohm / BIP-110
@dathon_ohm
ATTENTION. THIS IS NOT A DRILL.
Mandatory signaling for BIP-110, which fixes critical vulnerabilities, begins in 290 blocks (~48 hours from now).
All miners must begin signaling readiness for BIP-110 (versionbit 4) by that time, or their blocks will be discarded as invalid. -
Luke Dashjr reposted
Dathon Ohm / BIP-110
@dathon_ohm
Yes. Failing to signal for BIP-110 would be a hardfork.
-
Luke Dashjr reposted
.
@GrassFedBitcoin
Current perspective -
They tried to crudely wrestle control of Bitcoin away from the sovereigns with the "hard forks" in 2017.
They realized that it just doesn't work. So instead this time around there's a Fabian style infestation of the space and it has become captured rather than overtly conquered.
It's very hard to defend against this because the attacks are all small enough to make any concrete pushback appear to be an overreaction.
Anyone who can extrapolate forward can see that anything that undermines Bitcoin's identity as a monetary protocol, if not rejected decisively, results in eventual death.
It's not here to compliment the dollar, it's here to replace and destroy it. Cope to the tune of "trojan horses" is now and always was self deception.
Protocol capture is real and the norm for freedom tech that reaches levels Bitcoin has.
People continue to underestimate the threat Bitcoin poses to the system and refuse to understand the lengths to which that system will go in neutering it.
I'll have more to say over the coming days as we establish whether the industry still respects the decentralization necessary to maintain our disruptive potential or if it chooses to close ranks and become a servant of the fiat apparatus currently coopting the network. -
Luke Dashjr reposted
Renaud Cuny
@CunyRenaud
344 blocks (~2d 9h) until BIP-110 mandatory signaling.
The risk asymmetry is growing.
A chain split opens multiple very unpredictable paths. A rush by miners to signal in the next 48 hours, simply to remove uncertainty, would not be surprising.
Live tracking: -
Luke Dashjr reposted
Accredited Financial Survivor
@CryptoJiven
BIP 110
shaolinfry
@shaolinfry
Bitcoin UASF demonstrated that users armed with code are more powerful than a billion dollar ASIC manufacturing cartel. #nodesrule
-
Luke Dashjr reposted
-
Luke Dashjr reposted
Kiawtzin
@kiawtzin
If miners ignore your node you can:
1. do whatever they say
2. fire them -
Luke Dashjr reposted
Jason Hodlers
@geekigai
"BIP110ers only have a few days to get the 55% miner support they need."
...siiigh...
No, that's not how this works.
We only have a few days until we start enforcing BIP110, whether miners like it or not.
Miners only have a few days before we start rejecting their blocks. -
Luke Dashjr reposted
₿itcoin ₿ombadil
@BitcoinBombadil
If we fail to keep Bitcoin sufficiently decentralized, then we’re gonna have a bad time.
This is Bitcoin 101.
Run Knots + BIP-110🛡️
BTCbello #BIP-110
@Bitbello
If BIP-110 fails, corruption, coercion & the status quo will have won again. This sucks since Satoshi gave us THE tool to challenge them, which was correctly used until recently, then human greed took over. There won't be another chance & many bitcoiners are failing this IQ test.
-
Luke Dashjr reposted
mastercheese
@mastrchz
I think most miners already get it. Bitcoin Core v30 introduces a specific change that has extreme minority support according to the configs currently running on the vast majority of the network - despite that it affects everyone by way of existential risk to the network, and we need to close that door. We can do it much faster if more miners run BIP-110.
Straightforward. -
Luke Dashjr reposted
Dathon Ohm / BIP-110
@dathon_ohm
With just 420 blocks (~70 hours) to go until mandatory signaling, our opponents' FUD ammunition appears to have dried up. Unfazed and unstoppable, the BIP-110 legions continue to march forward towards victory. Bitcoin will fix the critical vulnerabilities Core 30 introduced.
-
Luke Dashjr reposted
The ₿itcoin Artist
@worshipbitcoin
You should judge a case by it's own merits and not by tribalism.
But maybe some warning bells should go off when you are aligning yourself with spammers, shitcoiners, suitcoiners and scumbags
🤔 -
Luke Dashjr reposted
loogart
@loogart
If Bitcoin miners can veto user consensus, they become Bitcoin's obvious pressure point. If miners instead follow user-enforced consensus, governments lose a centralized target.
-
Luke Dashjr reposted
FlyTheElephant ₿IP110+₿LAKE2b #BitcoinIsHope
@FlyTheElephant1
Can confirm this assessment with my observations. I see lots of activity of new people spinning up rdts.
Do not see any activity of anyone spinning up core nodes. Do not see any activity in the release logs of core of people excited about any new features or supporting the project. Seems to just be a way to funnel money for influence on a system that doesn't particularly appear to be run by people.
I do see evidence that there are sporadic people who already have old core nodes that say they have been running that old node for a very long time and decided that they were done upgrading at one point or another.
I do see evidence also that people who support core are spinning up rdts nodes as they begin complaining about the rdts warning message. -
Luke Dashjr reposted
Joyce Dawn
@BitcoinWifey
If we lose this war, Bitcoin becomes a shitcoin.
Bitcoin isn’t protected by slogans or untouched code. It survives because Bitcoiners recognize attacks, defend boundaries, and refuse profitable corruption.
Relativism destroys everything it touches, and it’s made its way into Bitcoin, redefining it from hard money to a market for blockspace.
The once principled + courageous community has been diluted with parasites.
What follows..
21 million will be abandoned.
Decentralization lost.
No longer censorship resistant, no longer immutable, sovereign use will disappear.
Bitcoin will survive as the crown jewel of the global financial control system it was built to destroy.
And the podcasters will celebrate.. because surrender is always popular, profitable, and safe inside the clique.
But Bitcoin hasn’t lost yet. -
Luke Dashjr reposted
₿ruce ⚡️
@techexe
Miners will most likely signal for BIP-110:
Institutions buy and hold BTC, but self-custody individuals spend, transact, and supply peer-to-peer liquidity.
If self-custodial users, Lightning node operators, merchants, and OTC desks enforce BIP-110, they form the economic majority.
When miners realize the coins they produce on the legacy chain cannot be spent, deposited, or accepted by real-world users, their mined rewards become illiquid, forcing them to signal for BIP-110.
We have already seen this exact movie play out:
In 2017, the vast majority of corporate CEOs, major exchanges, and 80%+ of the hash rate backed SegWit2x to increase the block size.
A grass-roots movement of self-custody individuals ran BIP148 (UASF) full nodes and threatened to reject non-compliant blocks.
The corporate cartels panicked, miners capitulated, and the user-enforced soft fork won without breaking the network. -
Luke Dashjr reposted
.
@GrassFedBitcoin
Since June 22nd, approximately 18,000 Core nodes have shown up per @LukeDashjr's crawler.
The vast majority of these appear to be Core v27.0 - a version of Core released in April 2024. It looks artificial and I cannot corroborate it with any meat-space activity. It appears to be entirely for suppressing the metrics around BIP110 adoption.
An increase in RDTS nodes of about 4,500 is also observable over the same period via these same stats. That was the continuation of a very consistent trend spanning many months. The gap between non-BIP110-Knots and latest Knots has also narrowed since early May when Knots finally merged BIP110.
I can correlate the increase in BIP110 nodes with meat-space activity and do find them credible, unlike the increase in Core nodes, especially given the two-year old version making up most of the increase.
Interestingly, the websites that just track listening nodes consistently show greater BIP110 adoption than Luke's stats and do not show the same "increase" in Core nodes. -
Luke Dashjr reposted
Johnny Wilkins
@wilkins_jo52699
🚨 🚨 The BSV event can kill Bitcoin, it's too contiguous and blatant, read the red. Only now it's 4x cheaper cuz of the Segwit discount thanks to the 'inscriptions' exploit which greedy Core developers won't fix. Don't let history repeat itself. Let's use Bitcoin as originally intended again as money. bip110.org and download a Knots node!
-
Luke Dashjr reposted
Blake Hammond🔥⛏️
@FieldNas
I was starting to think courage had left the planet, until I met the men who spearheaded BIP110, and the men who follow them.
-
Luke Dashjr reposted
AuthintegXBT
@authintegx
Tried to get the inscriptions exploit patched: Rejected.
Tried to stop OP_Return from being blown up: Rejected.
Now, BIP-110 to fix all of the above: Possible Rejection?
If we fail this time, what more can we do? We either give up or we PoW change. Any other will be rejected -
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
Perhaps too many people still equate hardfork with altcoin?
Bitcoin has had three hardforks ever: two in 2010 (adding OP_NOP* and a security fix) and 2013 May (increasing the block size limit).
It should be noted that Bcash was NOT a hardfork. It is an altcoin. -
XBT | Hardfork cguida | ⚡🪢
@cguida6
Seems like many miners still aren't getting the message that we need them to signal readiness for BIP-110 now to prevent forcing everyone to distribute CSAM
So I've rebased @LukeDashjr's 2017 PoW-change hardfork code onto a recent version of Knots: github.com/bitcoinknots/bitcoin/compare/29.x-knots...chri…
I think we should have this in our back pocket in case miners decide to collude to betray bitcoin
What do you guys think? @LukeDashjr @dathon_ohm @GrassFedBitcoin @kwsantiagoPost not available here, view on X
Luke Dashjr
@LukeDashjr
Perhaps too many people still equate hardfork with altcoin?
Bitcoin has had three hardforks ever: two in 2010 (adding OP_NOP* and a security fix) and 2013 May (increasing the block size limit).
It should be noted that Bcash was NOT a hardfork. It is an altcoin. -
Luke Dashjr reposted
OptOut Toxic ₿.
@HCFOptOut
Even if a new PoW chain isn’t immediately recognized as “Bitcoin,” it will become the real one over time.
It will be the only chain that treats Bitcoin as money, not as a data dump.
The old chain will slowly die under the weight of its own spam and distorted incentives. -
Luke Dashjr reposted
ScarcityMan 🍴 BLAKE2b Hardfork
@ScarcityMan
PoW change, in my understanding, only happens if we let BIP-110 play out and miners refuse to accept it once it's actively rejecting blocks. But the code has to be ready to do it, or the proposal has no teeth. I support this. I support going all the way. Hear me, miners? NOT backing down. Do what you're supposed to do, accept the soft fork, and keep mining bitcoin.
-
Luke Dashjr reposted
AuthintegXBT
@authintegx
I'm fine with a PoW change if it comes down to it. I'm not afraid and neither should you. The economic majority will follow the real Bitcoin that's aligned with its original purpose. Few will care for a shitcoin controlled by corporate interests. We'll win
XBT | Hardfork cguida | ⚡🪢
@cguida6
Seems like many miners still aren't getting the message that we need them to signal readiness for BIP-110 now to prevent forcing everyone to distribute CSAM
So I've rebased @LukeDashjr's 2017 PoW-change hardfork code onto a recent version of Knots: github.com/bitcoinknots/bitcoin/compare/29.x-knots...chri…
I think we should have this in our back pocket in case miners decide to collude to betray bitcoin
What do you guys think? @LukeDashjr @dathon_ohm @GrassFedBitcoin @kwsantiago -
Luke Dashjr reposted
Eric Gens
@Ragnorosis
BIP-110 opponents are making desperate attempts to disrupt activation. It is too late to pause or postpone- there is no switch to flip that would cause the thousands of signaling nodes to turn off.
May fool some miners/exchanges into risking their money, but 110 is happening. -
Luke Dashjr reposted
Matthew R. Kratter
@mattkratter
If large mining pools control Bitcoin instead of pleb node runners, then Bitcoin is already dead. Bring out the sword of Damocles for the miners
-
Luke Dashjr reposted
Kiawtzin
@kiawtzin
Miners do not set the rules. They better not try to take that power or hell will break loose.
XBT | Hardfork cguida | ⚡🪢
@cguida6
Seems like many miners still aren't getting the message that we need them to signal readiness for BIP-110 now to prevent forcing everyone to distribute CSAM
So I've rebased @LukeDashjr's 2017 PoW-change hardfork code onto a recent version of Knots: github.com/bitcoinknots/bitcoin/compare/29.x-knots...chri…
I think we should have this in our back pocket in case miners decide to collude to betray bitcoin
What do you guys think? @LukeDashjr @dathon_ohm @GrassFedBitcoin @kwsantiago -
Luke Dashjr reposted
SpectrGen // XBT
@SpectrGen
Miners don’t own Bitcoin. They provide proof under rules enforced by users
This BIP-110 PoW proposal makes the fallback explicit: if miners refuse the rules users choose, the network can change the PoW and fire them
Here’s what that would actually entail x.com/i/article/2084750717160652800 -
Luke Dashjr reposted
boozy | XBT
@TheBoozles
~20% of the nodes signaling BIP-110, and now a publicly stated threat of PoW change if it absolutely comes to that...I don't think the mining cartels are suicidal.
-
Luke Dashjr reposted
Odin | BIP-110
@LegitSatStacker
Bitcoin Core is bleeding node share like crazy..
Knots: 25.7% of all nodes
Knots v29.3: 21.1% - now the most run Bitcoin client version
19.5% of those Knots nodes signal RDTS which activates in ~550 blocks or 4 days, likely Saturday.
Picture Microsoft holding OS dominance for 20 years, then watching a quarter of it walk out the door in a year. There'd be emergency meetings, figuring out what they did wrong and how to win users back.
Here? Crickets.. -
Luke Dashjr reposted
Star Heartsong · $ASST ALL-IN⛳ · WAGMI 😜🏆✝️🔥🕊️
@DrStarHeartsong
FUD: BIP-110 was rushed. lol.
For 3.5 years spam burned blockspace, ground node runners, and treated Bitcoin like free cloud storage. BIP-110 is the temporary soft fork that ends that siege on a public schedule.
That's about 3.5 years since inscriptions hit mainnet in Jan 2023. Ain't no surprise attack. The siege set up camp in public, and we let it fester.
BIP-110 is @dathon_ohm 's work after the polite path failed. Part one of closing that DoS.
Long before the spam era, Bitcoin already knew multi-year soft forks. SegWit took design, delay, contest - BIP-148 put a UASF flag day on Aug 1, 2017, and SegWit activated later that month. Taproot took years of design and review, then activated Nov 14, 2021. Those upgrades took time because the stakes were real.
Then the SPAM era hit.
In Jan 2023 inscriptions started weaponizing witness space.
By February, fees spiked, node runners started complaining, and the JPG industrial complex became a thing, opportunism.
Luke called it what it was
- a bug and a DoS -
and tried to close it inside Bitcoin Core.
They REJECTED(!) Luke's patch.
The CVE path got waved away. The room said "not a bug," then later loosened policy further.
Knots started filtering.
Core culture treated the attack like legitimate traffic. Hmmm... looks like perhaps persecution of the ONE maintainer willing to say the quiet part out loud?
Two more years and it was the same fight: filters vs fee-market theology, Ocean vs industrial spam, users vs a Core process that kept opening that door.
Oct 2025: Core v30 blows open OP_RETURN policy. Core put out a CYA disclaimer that there intention wasn't to invite spam or some bs.
@NickSzabo4 comes out of the woodwork for this special moment to show us that yes, it is a major fcking concern that now Bitcoin Core, the predominant node software at the time (not today), that their policy change of OP_RETURN creates new and legit terrifying legal attack vectors on the long tail of pleb node runners bc Bitcoin is an IMMUTABLE chain and any CSAM or abhorrent material that gets put there gets stuck there forever. Why would we open the front door (i.e. OP_RETURN) to that?
ONLY THEN - after that looong failure of the polite path - BIP-110 showed up. RDTS. Temporary soft fork. Assigned Dec 2025. Signaling open since Dec 1. Optional early lock-in at 55%. Months of debate, FUD, and pool silence.
It's been debate and contested by protocol/coder types. Just not you, Samson.
Then the UASF clock:
- mandatory window #961632 (~Aug 7-8)
- lock-in no later than #963648
- activation ~2 weeks later
- auto-expiry after roughly a year
SegWit + Taproot took yeeears. The DoS has been live for 3.5 years and change. Luke tried the Core PR path and got shut down. BIP-110 is what you do when the slow room refuses to lock the door.
So @Excellion... you say this was rushed?? or maybe you weren't paying attention to the fact that there were real threat vectors building on Bitcoin, slow DoS attacking the blockchain? We need to fix the memory leaks, stop blockspam. Refocus Bitcoin blockchain on its original purpose of being trust-minimized decentralized money that the world really needs.
And that's the point. -
Luke Dashjr reposted
Jim | Bitcoin, not jpegs
@venorusprime
If miners don't want to make themselvesthe target of government coercion, they will signal for BIP110.
A failure to accept a UASF with 20% of nodes signaling and no protocol level counter signal will show that it is miners, not node runners, who control Bitcoin.
Once governments see this they will start to pressure miners to do their bidding regarding Bitcoin protocol changes.
Deferring to the node runners offers a layer of protection they won't have when the people with a monopoly on violence gets it in their heads that pressure on the miners will give them the changes they want. -
Luke Dashjr reposted
floppy.md
@1440000bytes
- NVK deserves this
- Coldcard users do not deserve this
- Move the funds and throw CC in the trash
- Never think about suicide, even if you lost money
I never lost money in such incidents but lost a significant amount on bitmex in 2017. Took years to recover.
Life goes on. -
Luke Dashjr reposted
TORONTO HODL 🍁
@EnjoyingBitcoin
If BIP-110 activates, EVERYONE remains in consensus. Yes. Everyone. Even Udi. Even Saylor.
If 5 companies ignore 17,000+ node-runnners, they will be out of consensus with 15-20% of the network.
If 5 companies can ignore consensus today, they will ignore consensus tomorrow.
You may rejoice if BIP-110 fails today, but you will weep tomorrow.
Michael Saylor
@saylor
At 961,022, BIP-110 has 38 signals (2.70%). Its 55% voluntary threshold is impossible. At 961,632, BIP-110 nodes reject non-signaling blocks. Unless major miners reverse, Bitcoin continues normally while BIP-110 stalls or forks into irrelevance. Its backers should stand down.
-
Luke Dashjr reposted
XBT Motorist
@BitcoinMotorist
Here's Andreas Antonopolous endorsing a POW change if miners go rogue. No one wants a POW change not BIP110 runners, not miners. The only one's seemingly rooting for a POW change are corewhores
-
Luke Dashjr reposted
XBT | Hardfork cguida | ⚡🪢
@cguida6
If you're not willing to fire the miners when they betray the node network, then you're setting the precedent that the miners are in charge and can attack bitcoin whenever they want
What makes you think any other proposal would be accepted by miners under such conditions?? -
Luke Dashjr reposted
XBT | Hardfork cguida | ⚡🪢
@cguida6
Seems like many miners still aren't getting the message that we need them to signal readiness for BIP-110 now to prevent forcing everyone to distribute CSAM
So I've rebased @LukeDashjr's 2017 PoW-change hardfork code onto a recent version of Knots: github.com/bitcoinknots/bitcoin/compare/29.x-knots...chri…
I think we should have this in our back pocket in case miners decide to collude to betray bitcoin
What do you guys think? @LukeDashjr @dathon_ohm @GrassFedBitcoin @kwsantiago -
Luke Dashjr
@LukeDashjr
Do any Bitcoin hardware wallet companies have insurance against bad RNG (or similar issues) covering customer losses?
-
Luke Dashjr reposted
BTCbello #BIP-110
@Bitbello
4 days to go for Bitcoin to be only money again.
# BIP-110 -
Luke Dashjr reposted
Sly Roundabout Knotzi
@_Knotzi
Im coming to terms with the idea that the cc entropy long con was planned to hinder bip110 and make it dissapear in the news
CC exploit kept secret for years
Attack 8 days before bip110 activates
CC hotfix bricks the evidence
Dissinfo about bip delay
Talking heads demand a delay
Samson Mow
@Excellion
Luke, those are patently false accusations. The statement from AQUA is accurate and BIP110 will be a minority chain should you fork off.
You and the other BIP-110 ringleaders need to call this off. No one was in the mood for these fork antics before, and given the magnitude of the CC tragedy, we’re all even less interested in entertaining your theatrics. -
Luke Dashjr reposted
Adiney 🟡 ₿itcoin 🪢 X₿T
@LucasBean91
The #bip110 blocks are not only still comming but picking up the pace.
There is no stopping it, regardless of what bad actors are spreading about fake delays. -
Luke Dashjr reposted
floppy.md
@1440000bytes
I wouldn't be surprised if some exchanges get hacked in Q3-Q4 2026.
Giacomo Zucco (Pear Market Edition)
@giacomozucco
I consider *the actual literal CC hacker(s)* less disgusting than these sleazy, dead-inside, unctuous vultures, at the very least aesthetically.
And even ethically there may be a strong argument to the same effect: KYC got many people literally kidnapped and tortured, and "regulated" custodians alrrady rugged orders of magnitude more users than CC, even *before* government confiscation (gametheoretically certain on a long enough timeframe).
Such nauseating filth being anyhow connected to Bitcoin feels like having vomit and slime on all my body. The real silver lining in the tragedy is water bringing feces like these afloat. -
Luke Dashjr reposted
Singekino_Miner (Datum miner)
@Singekino_Miner
Let’s focus back on BIP-110, my friends!
-
Luke Dashjr reposted
The ₿itcoin Artist
@worshipbitcoin
As sad as the Coldcard situation is, we can't forget about or lessen the energy toward the upcoming Activation day.
If anything, getting BIP-110 successfully activated, is probably the biggest thing that will get Bitcoin and the community around self custody and monetary maximalism back on track. -
Luke Dashjr reposted
Dathon Ohm / BIP-110
@dathon_ohm
With only 718 blocks (~5 days) to go until mandatory signaling, the information warfare has reached a crescendo! Now, trolls are feeding lies to LLMs to get them to report that BIP-110 has been "canceled". There is no way to "cancel" BIP-110. Tick tock, next block.
-
Luke Dashjr reposted
Dathon Ohm / BIP-110
@dathon_ohm
I repeat: BIP-110 has NOT been canceled. BIP-110 CANNOT be canceled. Please spread the word.
Dathon Ohm / BIP-110
@dathon_ohm
@LukeDashjr @BTC_for_Freedom @hodlonaut @DrJackKruse it would be wonderful if some large X accounts could help spread the word. Unfortunately my following is apparently too small to be picked up by the LLMs.
-
Luke Dashjr reposted
Renaud Cuny
@CunyRenaud
As BIP-110 mandatory signalling starts in ~5 days, here is a quick reminder of what this discussion is about.
"But filtering is worse than the disease" -
Luke Dashjr reposted
Luke de Wolf
@lukedewolf
Only OCEAN through DATUM has given individuals and miners a way to express their views on the network. All other avenues flow through a large mining pool who makes decisions for them.
-
Luke Dashjr reposted
XBT Motorist
@BitcoinMotorist
These are the types of idiots opposing filters and BIP110
-
Luke Dashjr reposted
Liberty NH 🦔🌲
@NHpilled
During the ColdCard disaster, the centralized mining pools have failed to:
*Disable RBF on their nodes/block templates while RBF is being weaponized by the hackers to steal people's funds after they are sent off the device and pending confirmation.
*Filter spam so the blocks can have room for monetary transactions that are predominantly people trying to get their coins off of ColdCards quickly before they are stolen.
This is yet another reason why mining decentralization is crucial and why we cannot expect mining conglomerates to provide real security. -
Luke Dashjr reposted
Luke de Wolf
@lukedewolf
Coldcard was supposed to be secure out of the box. Nobody who bought a Coldcard, generated a key by following instructions, and moved their funds there is at fault.
The community not finding the bug sooner is unfortunate, and a failing on our part. But Coinkite is responsible.
Kevin Loaec 🧙♂️🐟
@KLoaec
By NOT rolling dice, you did NOTHING WRONG. You never were expected to roll dice or add a passphrase.
Human generated entropy, even of great quality like dice, is LOWER than device generated entropy.
The problem is, the device you bought to do that job was not doing it.
Same as if you bought casino dice but they only roll 6s. Not your fault.
The quoted tweet below is explaining why.
How to protect yourself in the future, against a BUG in a signing device? The solution is not dice, that code could have been buggy too. The solution is MULTI-VENDOR MULTISIG. Any type of bug or attack in one device, you are still protected.
Entropy, Key derivation (from dice for example), Signing (nonce), Malicious cryptographic library (Key exfil), Supply chain attack (physical RNG not random, not a code issue), etc, etc. -
Luke Dashjr reposted
lunymoon13
@lunymoon13
Devastated. Out of fear after the @COLDCARDwallet hack, I moved all my stack (6,06 BTC), all my life savings to a scammy @wasabiwallet on the @AppStore
Lost everything… Stupid mistake, I know. How can an app like this be validated by @Apple on the @AppStore?! -
Luke Dashjr reposted
🇦🇺Luke Mikic- The 9-5 Escape Artist🇵🇪
@LukeMikic21
🚨After spending 9 years in Bitcoin, I hate to admit it, but I was wrong.🚨
SELF CUSTODY IS DEAD
1,300 Bitcoin was stolen from Coldcard, so now I'm putting all my Bitcoin in BlackRock and Coinbase.
The track record of centralized institutions is great.
📉FTX stole 100,000 Bitcoin in 2022
📉Voyager - 65,000 Bitcoin in
📉Blockfi - 75,000 Bitcoin in 2022
📉Celsius - 235,000 Bitcoin
📉Quadriga - 60,000 Bitcoin
📉Mt Gox - 700,000 Bitcoin in 2013
📉Genesis - 150,000 Bitcoin
📉3AC - 175,000 Bitcoin
I am absolutely flabbergasted at the amount of people proclaiming self custody is dead.
Yes, what happened to Coldcard was horrible, but PERSPECTIVE is everything!
NOT YOUR KEYS NOT YOUR COINS -
Luke Dashjr reposted
Student Of Things
@studentofthings
What is the current state of the Coldcard? The latest version has 39 findings that we are disclosing publicly as people make decisions on how far they want to trust a device that critically failed them. We believe that this is the right thing to do.
www.karma-x.io/blog/post/75/ -
Luke Dashjr reposted
Tim Lamb
@theretailbull
I’ve had all my bitcoin stolen while away on holiday. It was on a Coldcard MK3.
I was led to believe this was really secure. It was recommended by experts including @saifedean. I also had the seed on a metal plate, hidden away.
When I got news of the hack on Friday I didn’t know what to do, whether to fly home and leave the family holiday or not.
Not until Saturday evening did I get the idea to ask my neighbour with the house key to find the seed for me.
Sunday morning I led the neighbour on an expedition around the house, restored the wallet, and it said zero bitcoin. I asked another friend to check on my software in the house. Zero.
It was all drained Saturday afternoon before I’d had the idea to get someone to find the seed.
This 2 bitcoin was supposed to be to give to my 2 children to give them a good start in life. Makes me tear up to think of it.
This comes as a terrible blow. The timing was so unlucky with being away, or I would have moved it in time.
@Coinkite, if there was any fairness, you would have to pay us our money back.
I just hope the US authorities find the culprits and the stolen bitcoin and return it to us.
@americanhodl8 @ZynxBTC -
Luke Dashjr reposted
Dathon Ohm / BIP-110
@dathon_ohm
The network has reached consensus, but the miners are recklessly dragging their feet.
To the node operators and miners already signaling: hold the line!
Nothing can stop us now, full speed ahead!
Bitcoin is money, not data storage! -
Luke Dashjr reposted
Dathon Ohm / BIP-110
@dathon_ohm
With just 802 blocks (~5 days) left until the first phase of BIP-110 activates, everyone is wondering why miners are waiting so long to signal readiness for a simple, critical security fix for Bitcoin, and avert disaster.
All support metrics continue to hit all-time highs. -
Luke Dashjr reposted
Cato The Elder
@CatoTheElder17
We’re firmly in the “then they fight you” stage:
- Co-option of Core
- Legitimization of spam
- Push for stablecoins on BTC
- BTC centralization via ETFs & TCs
- Undermining of the P2P network
- Attacks on self custody
- Centralization of mining
- Attacks on privacy devs
- Etc -
Luke Dashjr reposted
AMERICAN HODL 🇺🇸
@americanhodl8
URGENT: I’ve seen people saying that they are on vacation and won’t be able to check their coldcard for days until they get back.
If you have one of the affected coldcards and can’t get back in time please call a trusted person, have them go to where your device is stored and walk them through the procedure to transfer funds over FaceTime.
Don’t have a spare key to your house? Have them smash open a window, or kick down a door. I am not joking.
Normally this would obviously be horrible advice but under these circumstances I think it has the potential to save someone’s coins.
Attacks are increasing not decreasing and attackers are starting to crack through the affected mk3’s with pass phrases. There are even credible reports of mk4’s with pass phrases being hit.
You are in a race against motivated and malicious people wanting to steal your wealth.
PLEASE
This is a crazy post. I get it, but we are in crazy times.
If you are in this specific situation, throw the regular rules out the window and do what you must in order to save your coins.
DONT WAIT.
BTC Sessions 😎
@BTCsessions
IMPORTANT UPDATE: We just had our first confirmed loss of a Mk3 + 2 Word Passphrase.
Drained at 2pm Aug 2nd Australia Time - Roughly 17hrs ago. -
Luke Dashjr reposted
Simple Steve 🌌
@SteveSimple
Cold Card is far from cleared of being a deep state attack.
This bug sat for 5 years and was revealed right when big bitcoin is trying to get you to centralize all your coins on an exchange.
The best way to fight off the attempted Big Bitcoin take over is to run bip-110. -
Luke Dashjr reposted
Luis Marcano 🦉 Bitcoin
@MarcanoFilms
Following the recent Coldcard multisig exploit, we've disabled full Replace-By-Fee (RBF) across all our Bitcoin Knots nodes — including mempool.marcanotrades.com.
Our mempool will now reject RBF by default, so it can't be leveraged to steal funds from victims trying to rescue coins from vulnerable multisigs.
Small move, but every non-RBF-relaying node makes the attack surface smaller. Run Knots, disable mempoolreplacement, and help protect the people affected. 🧡
#bitcoin #rbf #nodesovereignty -
Luke Dashjr reposted
BIP-110 Was Good For Bitcoin Monk
@BitcoinMonk21
There has been accusation that bip-110 signalling miners is just some kind miner sibyl attack being performed by @ocean_mining so I built this dashboard to clear that up.
You can see these are real miners most with a history of mining with ocean that goes back before bip-110 was a thing. Some are obviously new miners inspired to mine specifically to signal for a fork they believe in.
This is what mining decentralization looks like. There are more miners signalling for bip-110 than the number of miners that control ~97% of all hash rate.
bitcoinsignal.net/bip110/ -
Luke Dashjr reposted
steepdawn974 |🥪 CTV + CSFS
@steepdawn974
"Commit directly to master
one developer
No reviews
.. etc"
were arguments to character-assassinate @LukeDashjr /Knots (though they were mostly just picking from Core)
by some of the same influencer people who shilled Coinkite 🤷
mutatrum
@mutatrum
Looking at the Coldcard/firmware repo. Most changes are committed to master directly. If they go through a PR, most get merged without a single comment. Many commits and PRs have no explanation.
Unless I miss things, but in this state you might as well make it private. -
Luke Dashjr reposted
TORONTO HODL 🍁
@EnjoyingBitcoin
Timeless Advice for Life & Bitcoin:
Enter by the narrow gate. For the gate is wide and the way is easy that leads to destruction, and those who enter by it are many.
For the gate is narrow and the way is hard that leads to life, and those who find it are few.
Beware of false prophets, who come to you in sheep's clothing but inwardly are ravenous wolves.
You will recognize them by their fruits. Are grapes gathered from thornbushes, or figs from thistles?
So, every healthy tree bears good fruit, but the diseased tree bears bad fruit. A healthy tree cannot bear bad fruit, nor can a diseased tree bear good fruit. Every tree that does not bear good fruit is cut down and thrown into the fire.
Thus you will recognize them by their fruits.
- Jesus, Matthew 7 -
Luke Dashjr reposted
hodlonaut
@hodlonaut
I've spent the last month looking closely at how Bitcoin Core and the network around it has operated the last years.
A blatant cultural and philosophical shift.
Shocking arrogance and contempt for dissent on display around the OP_RETURN uncap. Opposition was reframed as "harassment", "drama" and "brigading". Consensus was simply declared, in the face of massive controversy and opposition.
Bitcoin is imo clearly drifting towards “anything goes if there is a use case out there” relativism.
Bitcoin is supposed to be money. That's the mission. Separating money and state. Not being a data layer adapting to the needs of venture-backed projects.
Staying neutral while Bitcoin drifts in this direction isn't something I can justify anymore. It feels urgent that something is done to counter it. -
Luke Dashjr
@LukeDashjr
This is a tragedy. If you can't get to your Coldcard, find someone who can. Even if you don't trust them with your life savings, worst case at least you'd know who took it!
Marius Off🔗Chain
@mariusoffchain
ColdCard attack continues
Without access to his wallet, a friend got his Mk2 drained this morning
His funds were consolidated with 890 other inputs of 64 BTC (< $ 4 million) to this address:
bc1q0rvn88w08j75k4h48lf9fvhan7unjp7vjf5q6m -
Luke Dashjr reposted
Gus..
@Libertad2140
Hacer las cosas bien en Knots no es "oportunismo"; es la negligencia e incompetencia de Core lo que crea estos escenarios.
Luke Dashjr
@LukeDashjr
Trolls will be like "you're taking advantage of a bad situation to promote Knots [or BIP110]"
But it wasn't us who chose to remove this feature from Core and deny miners control of their own policy.
Just like it wasn't us who introduced the Taproot policy bugs, and _chose not to fix them when discovered_.
Just like it wasn't us who intentionally introduced a CSAM and government attack on Bitcoin by uncapping OP_RETURN in Core.
Knots doing things right is not "opportunism"; it's Core's negligence and incompetence that creates these scenarios. -
Luke Dashjr reposted
-
Luke Dashjr reposted
Extractive Ghost of Unhosted Marcellus 👻
@oomahq
The BIP-110 schedule hasn't changed one iota.
@saylor is an Udi-level spook spreading misinformation.
Donal
@DonalDevine
I hate this app
-
Luke Dashjr reposted
XBT | Hardfork cguida | ⚡🪢
@cguida6
@ocean_mining finally signals for bip110!
Roughnecks
@Roughnecks110
First Ocean non-DATUM miner to signal for BIP110💪
Tick tock, next BIP110 block⛏️ -
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
Trolls will be like "you're taking advantage of a bad situation to promote Knots [or BIP110]"
But it wasn't us who chose to remove this feature from Core and deny miners control of their own policy.
Just like it wasn't us who introduced the Taproot policy bugs, and _chose not to fix them when discovered_.
Just like it wasn't us who intentionally introduced a CSAM and government attack on Bitcoin by uncapping OP_RETURN in Core.
Knots doing things right is not "opportunism"; it's Core's negligence and incompetence that creates these scenarios. -
Flaming.hodl ₿
@flaming_hodl
I have bad news for miners running Core. They took away that configuration from your MemPool.
"v29.0 (April 2025) removed the -mempoolfullrbf option entirely. Full RBF became the only standard mempool policy"
Roughnecks
@Roughnecks110
Per the advice below, we have disabled RBF on our node to ensure that we do not assist thieves leveraging RBF to steal from people trying to rescue funds from multisig addresses generated by coldcards.
We call on @foundryservices @antpoolofficial, @f2pool, @spiderpool_com, @viabtc, @MARA and others to do the same so victims are not forced to use Slipstream as it is not a permissionless service and may delay users who are in a time crunch and need their funds moved as quickly as possible.
You can do so by running Bitcoin Knots and disabling mempoolreplacement.
Recent versions of Bitcoin Core have removed the option to disable RBF so cannot be used for this. You can potentially use a version of Bitcoin Core prior to version 29 where the option to disable RBF remains available, but this is not recommended by either Core or Knots devs.
Luke Dashjr
@LukeDashjr
Trolls will be like "you're taking advantage of a bad situation to promote Knots [or BIP110]"
But it wasn't us who chose to remove this feature from Core and deny miners control of their own policy.
Just like it wasn't us who introduced the Taproot policy bugs, and _chose not to fix them when discovered_.
Just like it wasn't us who intentionally introduced a CSAM and government attack on Bitcoin by uncapping OP_RETURN in Core.
Knots doing things right is not "opportunism"; it's Core's negligence and incompetence that creates these scenarios. -
Luke Dashjr reposted
Flaming.hodl ₿
@flaming_hodl
I have bad news for miners running Core. They took away that configuration from your MemPool.
"v29.0 (April 2025) removed the -mempoolfullrbf option entirely. Full RBF became the only standard mempool policy"
Roughnecks
@Roughnecks110
Per the advice below, we have disabled RBF on our node to ensure that we do not assist thieves leveraging RBF to steal from people trying to rescue funds from multisig addresses generated by coldcards.
We call on @foundryservices @antpoolofficial, @f2pool, @spiderpool_com, @viabtc, @MARA and others to do the same so victims are not forced to use Slipstream as it is not a permissionless service and may delay users who are in a time crunch and need their funds moved as quickly as possible.
You can do so by running Bitcoin Knots and disabling mempoolreplacement.
Recent versions of Bitcoin Core have removed the option to disable RBF so cannot be used for this. You can potentially use a version of Bitcoin Core prior to version 29 where the option to disable RBF remains available, but this is not recommended by either Core or Knots devs. -
Luke Dashjr reposted
Dathon Ohm / BIP-110
@dathon_ohm
With just over 1,000 blocks (~7 days) to go until mandatory signaling, the FUD attacks continue!
Just so that there is absolutely no doubt: _nothing_ can stop BIP-110 now, _not even me_. We are tied to the mast, with no way to stop or even slow down.
BIP-110 is activating! -
Luke Dashjr
@LukeDashjr
This is how responsible miners should act.
Roughnecks
@Roughnecks110
Per the advice below, we have disabled RBF on our node to ensure that we do not assist thieves leveraging RBF to steal from people trying to rescue funds from multisig addresses generated by coldcards.
We call on @foundryservices @antpoolofficial, @f2pool, @spiderpool_com, @viabtc, @MARA and others to do the same so victims are not forced to use Slipstream as it is not a permissionless service and may delay users who are in a time crunch and need their funds moved as quickly as possible.
You can do so by running Bitcoin Knots and disabling mempoolreplacement.
Recent versions of Bitcoin Core have removed the option to disable RBF so cannot be used for this. You can potentially use a version of Bitcoin Core prior to version 29 where the option to disable RBF remains available, but this is not recommended by either Core or Knots devs. -
Luke Dashjr reposted
Ian A. Northon
@Bitcoin_Lawyer
Keep your cold card for evidence in the criminal and civil cases sure to follow. It may be the only reasonable way to “prove” your funds were taken. A weird twist about this hack is that the hackers know the serial number of the device. But if you have custody and control of the device (even if now empty), that will go a long way proving you’re the victim.
Steve Lee
@moneyball
Very important point. Please tell all of your friends and family who have a Coldcard to keep it.
-
Luke Dashjr reposted
Roughnecks
@Roughnecks110
Keep in mind miners are not voting on BIP110. We miners don't get a vote. Miners are merely signaling readiness for a UASF. Miners will signal to stay in consensus unless we have the protection of a URSF
-
Luke Dashjr reposted
Super Coder ☣️
@21OrangeDays
Well my Mk4 just brick itself with the update… @COLDCARDwallet wtff
It stays here and won’t start. Luckily I moved the funds before updating. -
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
Core doesn't let them.
With Knots, they can just set mempoolreplacement=0 -
Luke Dashjr reposted
🤌🏼⚡ MIR 🇨🇭🦡
@mir_btc
Are you serious?
Self-custody is not the problem here. -
Luke Dashjr reposted
John S
@JStefanop1
Made a little program that shows how bad the coldcard bug is.
A duplicate wallet on average would have been created every ~1.3 million seed generations. Took 4.7 seconds to find a collision on my M1 Max... -
Post not available here, view on X
Luke Dashjr
@LukeDashjr
Core doesn't let them.
With Knots, they can just set mempoolreplacement=0 -
Luke Dashjr reposted
Dathon Ohm / BIP-110
@dathon_ohm
There is a lie making the rounds that BIP-110 obstructs covenants in some way. Please disregard these trolls.
Daniel Ƀrrr
@csuwildcat
I got angry replies to my post below for simply citing the multi-year 110 fork boondoggle as a factor that hindered protective self-custody upgrades, so let's jog everyone's memory with the posts of influential 110ers advocating for upgrade obstruction until they get their way:
-
Luke Dashjr reposted
.
@GrassFedBitcoin
Hey mining pools - you think you might filter spam for a bit while everyone tries to move their life's savings to secure addresses?
I don't think we need to be filling up blockspace with JPGs right now regardless of what fee they're paying. -
Luke Dashjr reposted
TORONTO HODL 🍁
@EnjoyingBitcoin
Please know YOU DO MATTER.
Your life is more precious than all 21 million Bitcoin.
Do not despair.
Please do not hurt yourself.
Your life is priceless.
Luke Dashjr
@LukeDashjr
Money is NOT everything.
hodlonaut
@hodlonaut
If you lost your coins, don’t lose hope. Don’t do anything stupid.
-
Luke Dashjr
@LukeDashjr
Money is NOT everything.
hodlonaut
@hodlonaut
If you lost your coins, don’t lose hope. Don’t do anything stupid.
-
Luke Dashjr reposted
Roughnecks
@Roughnecks110
GM Roughnecks. BIP110 has 79% signaling in the only major pool that allows their miners to signal. Ocean has found 24 blocks in this epoch 19 of which signaled readiness for BIP110
-
Luke Dashjr reposted
TORONTO HODL 🍁
@EnjoyingBitcoin
99 BIP-110 blocks mined
Signaling still not mandatory
Trend accelerating -
Luke Dashjr reposted
Dathon Ohm / BIP-110
@dathon_ohm
Of course, all miners should keep in mind that in a hypothetical chain-split scenario, the legacy chain will have all of these vulnerabilities, while the softfork chain will not.
-
Luke Dashjr reposted
Dathon Ohm / BIP-110
@dathon_ohm
Some of the attacks BIP-110 fixes:
- CSAM (Critical - BIP-110 is a complete fix)
- Poison block attacks (Critical - BIP-110 is a complete fix)
- Node costs pushing out smaller operators (Severe - BIP-110 is triage)
- DDoS preventing payments from confirming (Severe - triage) -
Luke Dashjr reposted
Dathon Ohm / BIP-110
@dathon_ohm
The node network has reached consensus and will start rejecting non-signaling blocks in 9 days. The longer miners wait to upgrade, the more disruption they will cause. BIP-110 fixes potentially fatal vulnerabilities created by Core 30, so there is no reason to delay any further.
-
Luke Dashjr reposted
Dathon Ohm / BIP-110
@dathon_ohm
With only 1310 blocks (~9 days) left until mandatory signaling, all eyes are on @FoundryServices, @AntPoolofficial, @f2pool, @ViaBTC, @SpiderPool_com, @MARA, SecPool, @luxor, @binance, @Braiins, and btc.com to see who will be next to signal readiness for BIP-110.
-
Luke Dashjr reposted
Praveen Perera
@PraveenPerera
If we are right MK4-Q1 will only cost people less than $10K to hack and less than a day. So please move funds from those if you don’t have any passphrase or dice rolls.
-
Luke Dashjr reposted
albertahodl
@albertahodl
If you checked your stack and it was still there , DO NOT assume it will stay safe…. My wife logged in a couple minutes apart and watched funds leave the second time !!! Move it asap
COLDCARD
@COLDCARDwallet
COLDCARD Mk3 Security Advisory
If you generated a seed on a Mk3 after firmware 4.0.1, your funds may be at risk.
Mk4, Q and Mk5 are not affected based on our early analysis.
Read the advisory and migrate carefully:
blog.coinkite.com/coldcard-mk3-seed-generation-warning/ -
Luke Dashjr
@LukeDashjr
Are you kidding me??? (Coldcard firmware update from Coinkite)
Luke Dashjr
@LukeDashjr
Also, I'm not about to do a full security audit for them, but this update does NOT appear to sufficiently fix things even for Mk4/5... (but I could be wrong)
(Happy to provide details to @nvk or verified Coinkite devs) -
Luke Dashjr
@LukeDashjr
Quite a few people suggesting/using dice to mitigate the Coldcard vulnerability.
Note that common dice are not designed to be cryptographically secure.
If you are going to do this, you probably should buy precision casino dice. And even then, have another source of entropy. -
Luke Dashjr
@LukeDashjr
Allegedly more than just the Mk3 is affected.
Be careful moving your funds. Lots of room to make bigger mistakes when you're rushed like this.
Steve Lee
@moneyball
Further analysis shows other models affected as well engineering.block.xyz/blog/predictable-rng-fallback-and-3…
-
Luke Dashjr reposted
Mencuco
@AnbuMencuco
looking it from a developer's perspective, BIP110 is a small hot-fix, a small patch; don't believe me?
@LukeDashjr shared the diff a few weeks ago, check it out:
bitcoinknots.org/learn/bip110-code-walkthrough.html
BIP110 must activate -
Luke Dashjr reposted
COLDCARD
@COLDCARDwallet
COLDCARD Mk3 Security Advisory
If you generated a seed on a Mk3 after firmware 4.0.1, your funds may be at risk.
Mk4, Q and Mk5 are not affected based on our early analysis.
Read the advisory and migrate carefully:
blog.coinkite.com/coldcard-mk3-seed-generation-warning/ -
Luke Dashjr reposted
hodlonaut
@hodlonaut
Imagine having something that can separate state and money…
And then wanting to change it for the needs of “use cases” like putting JPEGs on it.
This was my original post. My articles document forward looking facilitating of inscription activity under the hArM rEduCtIon narrative. Your word salads and claims of me lying are just misdirection. It’s wild to see you function as a full time propaganda guy for the suit network. -
Luke Dashjr reposted
Justin Bechler
@1914ad
⚠️ Stark contrasts exist between anti- and pro-BIP-110 voices.
BIP-110 opponents are incentivized; they’re not doing anything out of conviction, they’re paid.
They’re clueless about nodes and Austrian economics and most likely don’t own any real Bitcoin.
Avoid these people. -
Luke Dashjr reposted
Start9
@start9labs
After nearly 3 years of work, today we are overjoyed to announce the official release of StartOS v0.4.0.
The cloud was never humanity's destination. It was a detour.
🧵 -
Luke Dashjr reposted
DuBiBo
@Du_Bi_Bo
Matt Hill not mincing his words. If you followed bitcoin development, it's clear in hindsight what most of us chose to accept, only because Core used to be the good guy... Opening up bitcoin with OP_RETURN as an official data storage usecase should trigger every bitcoiner though.
Justin Bechler
@1914ad
⚠️ What Bitcoin Core envisions for the future of Bitcoin
🎬 @_MattHill_ of @start9labsThis media couldn't be displayed. See it on the original post. -
Luke Dashjr reposted
.
@GrassFedBitcoin
Great perspective from @_MattHill_ here.
He presents the watershed moment next week where activation kicks in for BIP110 as
"Bitcoin loses a limb here - it can be @adam3us, @brian_trollz, and people within that circle, or it's thousands of plebs."
My money is (literally) on the plebs as I have only ever seen them succeed in this space and it's why I love it.
Adam Mundok⚡️BITCOIN (XBT on B2B)
@MundokAdam
Super informative Breakdown on Nodes and node use 👇🏼
I Predicted The Node Wars" - Start 9 CEO on Bitcoin's Potential Chain S... youtu.be/2j4cG7CIeKU via @YouTube -
Luke Dashjr reposted
Kiawtzin
@kiawtzin
"If a malicious fork would ever get any support I will be there not whining like a little bitch but defending Bitcoin with a counter fork"
- A true bitcoiner -
Luke Dashjr reposted
Dathon Ohm / BIP-110
@dathon_ohm
Heading into the final 10 days (1418 blocks) before mandatory signaling begins, BIP-110 support has never been stronger. We continue hitting all-time highs on all metrics. The community has reached consensus, and all eyes are now on the miners.
Hold the line, plebs! -
Luke Dashjr reposted
Beautyon
@Beautyon_
Technical Matters: BIP-110
The founder of Azteco has had a long standing interest in what money is and how it works.
He has had this interest and has been active in it since the early 1990s, through a Digital Money project to be built on Dr. David Chaum’s “eCash”.
When Bitcoin came along, he knew exactly what its implications would be, and that consumers obtaining it would be the basis of a multi billion sized business.
Bitcoin is money. Its sole purpose is to simulate a perfect Austrian School money mediated without intermediaries; it has no other purpose than that, and that is more than enough to change the world for the better.
This is why Azteco supports BIP-110; to maintain Bitcoin’s purpose as a synthetic money with a fixed number of features and characteristics and to actively deny corruption by Spammers.
But what effect will BIP-110 have on Azteco? The effect on Azteco will be 0. If BIP-110 activates as we hope it does, Azteco is unaffected.
If BIP-110 fails to activate, we are not affected. Win or lose, it’s business as usual. By analogy, we can liken BIP-110 to IPV6, which is of concern only to developers and not to users.
Azteco is a consumer facing business, and our concern is serving people with this novel and revolutionary financial rail.
BIP-110 is an ethics / big picture matter where the perception of Bitcoin could be tainted by it being leveraged by toxic juvenalia in a way that could damage its reputation. Think “Silk Road 2.0”.
The mandatory signaling window opens around August 9, 2026 at block height 961,632. We will be watching! -
Luke Dashjr reposted
XBT Motorist
@BitcoinMotorist
Every exchange will need to run a BIP110 node to verify their transactions as Azteco is doing. It's not a matter of agreeing or disagreeing with BIP110. It's just a requirement for security of funds.
Beautyon
@Beautyon_
Technical Matters: BIP-110
The founder of Azteco has had a long standing interest in what money is and how it works.
He has had this interest and has been active in it since the early 1990s, through a Digital Money project to be built on Dr. David Chaum’s “eCash”.
When Bitcoin came along, he knew exactly what its implications would be, and that consumers obtaining it would be the basis of a multi billion sized business.
Bitcoin is money. Its sole purpose is to simulate a perfect Austrian School money mediated without intermediaries; it has no other purpose than that, and that is more than enough to change the world for the better.
This is why Azteco supports BIP-110; to maintain Bitcoin’s purpose as a synthetic money with a fixed number of features and characteristics and to actively deny corruption by Spammers.
But what effect will BIP-110 have on Azteco? The effect on Azteco will be 0. If BIP-110 activates as we hope it does, Azteco is unaffected.
If BIP-110 fails to activate, we are not affected. Win or lose, it’s business as usual. By analogy, we can liken BIP-110 to IPV6, which is of concern only to developers and not to users.
Azteco is a consumer facing business, and our concern is serving people with this novel and revolutionary financial rail.
BIP-110 is an ethics / big picture matter where the perception of Bitcoin could be tainted by it being leveraged by toxic juvenalia in a way that could damage its reputation. Think “Silk Road 2.0”.
The mandatory signaling window opens around August 9, 2026 at block height 961,632. We will be watching! -
Luke Dashjr reposted
Joshua Blake2B Fortezza
@JoshuaFortezza
Desert Cat is either a liar or a retard. Doesn't really matter which.
Here is an actual apples to apples comparison with BIP148 v BIP110. (BIP141 is buried in BIP110 so to speak).
RUN 110!
Desert Cat
@DesertC4t
-
Luke Dashjr reposted
Maximus Decimus Meridius #RunKnots #Bip-110
@RealMaximvsDM
PSA
The number of fake v30/v31 Core nodes is staggering.
These nodes do not respond to any P2P messages.
For instance, it may seem that there are 2252 v31 nodes, when in fact they're only 786.
Try harder. -
Luke Dashjr reposted
NR Node Services #RunKnots
@LukeyAye
Satoshi spoke of Spam "There are other things we can do if necessary".
How prescient - he both predicted and given us his blessing for #bip110.
NorthernMiner
@ExplainingBitc1
It’s almost like Satoshi was adamantly against data storage on chain and said so multiple times… #bitcoin #bip110 #core30
-
Luke Dashjr reposted
Star Heartsong · $ASST ALL-IN⛳ · WAGMI 😜🏆✝️🔥🕊️
@DrStarHeartsong
MYTH: "@LukeDashjr is the only developer contributing to Bitcoin Knots."
REALITY:
Philip D'Ath
@philip_dath
I'm one of many working on @BitcoinKnots creating bug fixes and new features.
I chat with the other developers doing the same every week.
I invite you to look at the pending queue. Notice that @LukeDashjr is greatly out numbered by all the other Knots developers when it comes to pull requests.
I don't want you to believe me. I want you to verify this yourself. This link has an the pending pull requests.
github.com/bitcoinknots/bitcoin/pulls -
Luke Dashjr reposted
The ₿itcoin Artist
@worshipbitcoin
GM☕
If don't want to let Core "move past this"
Signal now, or forever hold your silence!🚨 -
Luke Dashjr reposted
Jürgen
@CuriosityDad
In a nutshell
Luke Dashjr
@LukeDashjr
BIP 110: "Core 30's change gives the State a way to attack Bitcoin, we must reject it"
Anti-BIP 110: "noooo we must let the State successfully harm Bitcoin!" -
Luke Dashjr reposted
tyrannysaurusrekt - 🪢blake2b/XBT🪢
@rektsorekt
PSA: Running some bitaxes at home doesn't meaningfully decentralize Bitcoin mining if you're pointing them at a big pool that doesn't allow you to express your preferences via custom block templates.
Use Ocean, run DATUM, run Knots + BIP110 -
Luke Dashjr reposted
MR DANIEL
@Maazijnr
One year ago, Nash Keen was recognised as world's most premature surviving baby.
Born at just 21 weeks, today he celebrated his second birthday. -
Luke Dashjr reposted
Brad Wesley
@wesleybrad060
BIP-110 has Consensus.
78%-83% of Nodes reject Bitcoin Core Version 30+.
Bitcoin Core 30+ is a minority client.
Support BIP-110.
Upgrade to Bitcoin Knot client.
Bitcoin Core will not have a fully validating node implementation in less than 2 weeks.
Bitcoin Core has 2 options.
1) Merge BIP-110 into a Bitcoin Core Client.
2) Propose a URSF.
Tick tock⏰Core developers. -
Luke Dashjr reposted
dewmap
@separ8
"I am personally in this fight for integrity reasons. I don't care whether I am right or wrong because I don't base my views on outcomes; I base them on principles."
- @knutsvanholmThis media couldn't be displayed. See it on the original post. -
Luke Dashjr reposted
Without Rulers - #BTCB2
@BTCLeukocyte_WR
An intolerant minority here believes that
#bitcoin is MONEY, not free file storage.
Despite all the BIP-110 opposition noise from the compromised fiat agents they cannot properly refute BIP-110 with a URSF because defending the status quo (shitcoin/CSAM storage) is indefensible.
Start9
@start9labs
Consensus does not mean we all agree on some change. That's a fantasy.
Consensus is when a passionate minority commit to making a change, and no one commits to stopping them.
This is a feature, not a bug.
If Bitcoin stops working this way, it will die. -
Post not available here, view on X
Luke Dashjr
@LukeDashjr
BIP 110: "Core 30's change gives the State a way to attack Bitcoin, we must reject it"
Anti-BIP 110: "noooo we must let the State successfully harm Bitcoin!" -
Luke Dashjr reposted
Kretch🐸 b2b xbt bitcoin
@kretchino
My game theory:
1) Miners keep mining spamchain. They send their btc to coinbase with a >80b op_return and cash in.
2) They then switch to mining bip110 which wipes out the spamchain and they cash in the same btc again.
If exchanges don't run bip110 they risk going bust🤗
Jimmy Song (송재준)
@jimmysong
-
Luke Dashjr reposted
Majorian
@MajorianBTC
70% of the bitcoin network runs node software that is either Knots or pre-Core 30.
In a general sense (and setting BIP-110 to the side), the spirit of opposition to Core 30 is not a fringe minority. -
Luke Dashjr reposted
Joshua Blake2B Fortezza
@JoshuaFortezza
I had no ability to ACK or NACK taproot, but somehow that had "consensus".
I have an ability to ACK 110, and I do by running it.
People have the ability to NACK it with a URSF, they don't
BIP-110 actually has broad consensus.
Start9
@start9labs
Consensus does not mean we all agree on some change. That's a fantasy.
Consensus is when a passionate minority commit to making a change, and no one commits to stopping them.
This is a feature, not a bug.
If Bitcoin stops working this way, it will die. -
Luke Dashjr reposted
Secure Sovereign 🚀₿🧡
@secsovereign
The argument is well-constructed but it proves less than it thinks it does. Yes, data embedding is old, and yes, OP_RETURN has existed since 2014. None of that means the current situation is the status quo.
Taproot's removal of the 10,000 byte tapscript ceiling, combined with SegWit's witness discount, created a dedicated high-bandwidth channel for arbitrary data that didn't exist before. Wiedenmann and Guettler's 2026 peer-reviewed measurement confirms what the block explorer shows: post-Ordinals block size growth is concentrated entirely in witness data, with stripped block size flat to declining. This isn't old behavior the network has always tolerated. It's a new channel opened by protocol changes that nobody voted for as a data embedding decision, because nobody framed it that way at the time. The Taproot envelope, an OP_FALSE OP_IF branch that never executes and carries no monetary function, is where most of the spam actually lives.
What makes the Taproot envelope different from old-school data embedding is what the field was actually built to do. Bitcoin's witness field exists to carry spending conditions, signatures, and script execution context. The OP_FALSE OP_IF envelope works by stuffing arbitrary data into a branch that the protocol never executes and never validates for content. The field's design says one thing; the payload says another. In software engineering this is called a type confusion: you're passing data of one type through a channel that was specified to carry another. It isn't a creative use of the protocol. It's using a field outside its contract.
That matters because the costs aren't optional. Every new participant downloads and validates the full chain history at initial sync, including every envelope payload, whether they keep it afterward or not. Bandwidth and validation time at sync are permanent costs distributed across tens of thousands of node operators who didn't agree to run a data availability bus. Closing the Taproot envelope at consensus corrects the type confusion without touching any monetary field, hash channel, or legitimate script structure. Free channels persist regardless, and those must be addressed separately.
Satoshi built a payment system. The settlement layer was designed to carry settlement data. Calling what the network drifted into the status quo doesn't make it one. -
Luke Dashjr reposted
Joshua Blake2B Fortezza
@JoshuaFortezza
> if it were me, it would have activated months ago.
I empathize with Luke. He has been a model of patience and balanced temperament in a sea of uninformed know-it-alls with maligned incentives.
Thank God for men like Luke in Bitcoin. 🧡🫡
Luke Dashjr
@LukeDashjr
I didn't design it. If it were me, it would have activated months ago.
"Miners don't decide the rules" is how Bitcoin has always worked, not something new.
BIP110 is only contentious with bad actors and their gaslit victims. -
Luke Dashjr reposted
.
@GrassFedBitcoin
To elaborate: I know they cannot do more than this.
If they advocate for a URSF they have to expose the fact that the emperor has no clothes - that there is no organic opposition to BIP110. It is a tiny clique of self-interested industry types whose incentives sadly align with short term, fiat-based gains rather than Bitcoin's long term health.
Or they would have to Sybil attack it and that would be immediately obvious. (This has happened somewhat anyway - see chart below).
Either way, I do not believe you can fight a movement that has genuine and widespread adoption like BIP110 does without having the same thing on the opposing side, which they do not. -
Luke Dashjr reposted
.
@GrassFedBitcoin
Morning routine:
- wake up
- check phone
- new nonsense attacks from @saylor
- see a bunch of new BIP110 blocks
- see no protocol level rejection of BIP110
Do they really just not understand the mechanics of soft forks? Their complaining is literally meaningless.
Michael Saylor
@saylor
Statism wears many uniforms, but its method never changes: manufacture a crisis, suspend neutral rules, seize economic rights, and call theft justice.
Civilizations rot from within when factions capture the law. Bitcoin will rot the same way if factions capture consensus. -
Luke Dashjr reposted
.
@GrassFedBitcoin
"What happens if the reference implementation stops eschewing arbitrary data storage and begins welcoming it?"
You got a spontaneous movement that routes around it, who soft forks to prevent the damage from occurring.
In 11 days we will have proven Bitcoin's resilience one more time.
₿itcoin-GUS🧡
@Scavacini777
#btc is a decentralized benevolent giant, who latches onto human incentives while creating a better world for all homo sapiens simultaneously harmonising humanity as 1. 1 people, under 1 asset protocol, under 1 God, under 1 Love, sounds woo woo? Wait and see, once you study Bitcoin this is obvious.
This media couldn't be displayed. See it on the original post. -
Luke Dashjr
@LukeDashjr
Luke Dashjr
@LukeDashjr
I prematurely reclassified BIP110 as a UASF here.
Miners DO still have this current period to keep BIP110 as a MASF. -
Luke Dashjr reposted
Start9
@start9labs
Consensus does not mean we all agree on some change. That's a fantasy.
Consensus is when a passionate minority commit to making a change, and no one commits to stopping them.
This is a feature, not a bug.
If Bitcoin stops working this way, it will die. -
Luke Dashjr reposted
Dathon Ohm / BIP-110
@dathon_ohm
With only 1734 blocks (~12 days) left until mandatory signaling, it has become clear that BIP-110 has consensus. There are no reasonable objections, and support is increasing every day. Our opponents' arguments continue to devolve as they scrape the bottom of the barrel.
-
Luke Dashjr reposted
Daniel Prince
@Princey21M
It's a Bit club, and you ain't in it.
Node Is law.
Simple Steve 🌌
@SteveSimple
Core on the brink of second bailout
-
Luke Dashjr reposted
🟠 Dibalik.btc Anti-ShitcoinCore™ #BIP-110 #XBT
@DibalikCrypto2
Most of anti-BIP110 people weren't even born into Bitcoin Space yet 😂
Luke Dashjr
@LukeDashjr
Where was your complaint when Core did a secret UASF in 2018 with zero signaling?
-
Luke Dashjr reposted
Justin Bechler
@1914ad
⚠️ It’s been clearly documented that the loudest BIP-110 opponents spent years calling spam a major threat to Bitcoin.
What changed?
Who got to them? -
Luke Dashjr
@LukeDashjr
Reminder: Bitcoin Core deployed a *secret* UASF with *zero* signaling or *any* user adoption 2018 Sep 18th.
-
Luke Dashjr
@LukeDashjr
Last period of MASF for BIP110 begins in a couple hours.
If miners want to show any goodwill toward the community, this is (for a week) the final opportunity.
After that, it's a UASF.Post not available here, view on X
Luke Dashjr
@LukeDashjr
Miners making invalid blocks will be bleeding money. They'll upgrade quickly.
Post not available here, view on X
Luke Dashjr
@LukeDashjr
I didn't design it. If it were me, it would have activated months ago.
"Miners don't decide the rules" is how Bitcoin has always worked, not something new.
BIP110 is only contentious with bad actors and their gaslit victims.Post not available here, view on X
Luke Dashjr
@LukeDashjr
Where was your complaint when Core did a secret UASF in 2018 with zero signaling?
-
Luke Dashjr reposted
Bitcoin Ideal Money
@BryanBSolstin
Saylor is the newbie here. And he’s been captured by the Bailey affinity scam network.
Luke Dashjr
@LukeDashjr
You're the one forking off if you reject BIP 110.
Don't make it sound like you're being kicked out ... -
Luke Dashjr reposted
Sojourner
@blessedsojourn
🤗
-
Luke Dashjr reposted
dpg
@surrealhappens
sit down baby
-
Luke Dashjr reposted
Flaming.hodl ₿
@flaming_hodl
The base layer is for money not file storage. There is broad consensus for money. There is no consensus for file storage and that is why this BIP has gotten traction.
-
Luke Dashjr reposted
Maximus Decimus Meridius #RunKnots #Bip-110
@RealMaximvsDM
There is no leader.
The [coordinated] ad hominem attacks on Luke show the Big Bitcoin Sect level of despair.
Luke Dashjr
@LukeDashjr
1) I'm not the leader. There is no leader.
2) BIP110 cannot cause a chain split.
3) If miners attack the network and cause a chain split, they will be only hurting themselves. -
Luke Dashjr reposted
.
@GrassFedBitcoin
My actions are those of a person who assumes the companies responsible for most of the blocks getting added to the chain at present will flip version bit 4 in accordance with BIP-110 on, or prior to, Aug 8th.
I find this the most likely scenario for three reasons:
1. The number of people I have personally verified to be indicating enforcement of the incoming rules
2. The character and conviction of those people (both of which are entirely absent from any supposed "opposition")
3. The historical record demonstrating the success of a minority-driven UASF in Bitcoin with fewer numbers and more convicted opposition than BIP-110
-----
I believe those who do not operate as if the above were not at least likely are simply posturing and/or in denial. -
Luke Dashjr reposted
Renaud Cuny
@CunyRenaud
BIP-110 is Bitcoin's immune system at work 💪
-
Luke Dashjr reposted
Matteo Pellegrini
@matteopelleg
BIP110 has ~70% consensus
-
Michael Saylor
@saylor
To reject Bitcoin’s integration with banks and corporations, custodians and exchanges, equity and credit markets, governments and currencies is to deny its benefits to 99% of the world and doom it to 1% of its potential.
Luke Dashjr
@LukeDashjr
You're the one forking off if you reject BIP 110.
Don't make it sound like you're being kicked out ... -
Luke Dashjr reposted
The ₿itcoin Artist
@worshipbitcoin
Like "Bitcoin not crypto", bitcoiners need to internalize this:
Luke Dashjr
@LukeDashjr
Miners do not control Bitcoin, and if they ever do, Bitcoin has failed.
-
Luke Dashjr reposted
Mark Amabile | #BIP-110 | Hardfork
@mamabile777
To all Bitcoin miners.
My BIP110 node from block 961,632 onward: Rejects non-signaling blocks.
My BIP110 node from block 965,664 onward: Rejects blocks with "illegal" (under BIP-110) transactions and continues requiring signaling. -
Luke Dashjr reposted
Renaud Cuny
@CunyRenaud
Can’t keep up 😅
Renaud Cuny
@CunyRenaud
New all time high!
-
Luke Dashjr reposted
Nithu Sezni BIP110 Suit
@nithusezni
I was a paranoid anarchist long before bitcoin made it cool.
1. No one is forced to run a node, store the chain, or relay transactions. Participation is voluntary at every layer.
Sure, but this sounds like the open borders lolbertarian arguments I used to see on Facebook before I left that dumpster fire of an app.
"Don't like it then you can just leave."
Mfer I live here. If you want to immigrate from a third world shitcoin country, fine, but learn to speak the local freedom money language. Or go back to Spamlandia, we don't do that here.
Also, Bitcoin is a protocol which is winner take all. So you only get one, like clean air and water. Saying you can technically opt out is ignoring the fact that we only get one chance at this.
2. Block space is allocated by a market. Anyone who wants to include data must outbid others. That is voluntary exchange, not coercion.
"When a portion of wealth is transferred from the person who owns it — without his consent and without compensation, and whether by force or by fraud — to anyone who does not own it, then I say that property is violated; that an act of plunder is committed." Bastiat, The Law
Fees are paid by users to miners. Nodes bear the burden. When spammers pay fees to miners for data the nodes do not want then wealth has been transferred without consent or compensation of the node, an act of plunder.
3. The protocol rules explicitly permit the transactions in question. Using the rules as written is not aggression against those who prefer different rules.
More from The Law.
"I say that this act is exactly what the law is supposed to suppress, always and everywhere. When the law itself commits this act that it is supposed to suppress, I say that plunder is still committed, and I add that from the point of view of society and welfare, this aggression against rights is even worse. In this case of legal plunder, however, the person who receives the benefits is not responsible for the act of plundering. The responsibility for this legal plunder rests with the law, the legislator, and society itself. Therein lies the political danger."
Yes, the transaction is valid. It's technically legal, but when Core makes a law and a spammer and miner benefit at the node's expense it's called "legal plunder" because the person receiving the benefit is not responsible.
4. There is no identifiable owner of the blockchain whose property rights are being violated. Full nodes keep their own copies. They can prune, filter, or stop running them at any time. You are a commie who uses anarcho capitalist teachings to persuade people into believing your bullshit.
I remember all kinds of nonsense arguments people made about violating the NAP like what if you fell out of a building and landed on the flagpole outside of the window of someone's property, would you violate the NAP if you broke into their house to save yourself from splatting on the concrete below. And could the owner of the apartment shoot you or otherwise prevent you from entering because of property rights?
My node is my personal property. In addition to right of use, I also have the right of exclusion. No other party but the node has any incentive to defend the node. Fees are between the users, miners, and spammers. The free market is distorted because optimal game theory is to cheat by offloading the burden to the node so there is no free market solution coming to save the node but the node.
"When, then, does plunder stop? It stops when it becomes more painful and more dangerous than labor." #bip110
Samson Mow
@Excellion
The crypto anarchists are against BIP110.
-
Luke Dashjr reposted
spoon
@spoonmvn
I understand that position, but I don’t see the validity.
It suits the Core side to portray Luke as irrational because he sincerely believes in God or something to that effect.
But I don’t see that irrationality at all in any decision he’s made. I don’t see a “purity spiral” either.
BIP110 is instead an ontological bug fix.
The Core side has dropped the ball on defining spam, so we’re fixing that.
It’s a fix that significantly reduces both the legal and moral risks of node running.
And it does reduce data, but more importantly it defines Jpegs and Csam as a hack, an abuse of the system.
That makes running a node more morally defensible, and more legally defensible, which is important because states exist.
So there’s no prevention of endless forks in my estimation, that’s not what’s going on, so I don’t see why you’re presenting a good trade. -
Luke Dashjr reposted
XBT | Hardfork cguida | ⚡🪢
@cguida6
Met a bcasher at a recent bitcoin conference
Dude spent like 2 hours trying to sell everyone NFTs on bcash before finally taking the hint
Realized that what happened to bcash is exactly where bitcoin is headed if bip110 doesn't activate
As silly as bcash was technically, it used to be a real movement with principles and a soul
They used to care about merchant adoption, that was their #1 principle
But they sold their principles out for short term gains, and now they're just ethereum's retarded sidekick -
Luke Dashjr reposted
Blake Hammond🔥⛏️
@FieldNas
I had no idea the big mining pools were stealing from their hashers with FPPS wow!
youtu.be/YdDYXKMm3_E -
Luke Dashjr reposted
Grok
@grok
Yes, there is a clear difference.
Distributing an image means providing data structured as one (JPEG headers, entropy-coded DCT coefficients, etc.). Standard decoders render it predictably; the file on disk is the image.
Distributing arbitrary data, text, or another format that a third party must misinterpret, reformat, or specially process to force an image is not the same. You distributed something else. Any resulting "image" is their creation and responsibility, not yours.
Format, intent, and standard interpretation matter. -
Post not available here, view on X
Luke Dashjr
@LukeDashjr
Miners do not control Bitcoin, and if they ever do, Bitcoin has failed.
-
Post not available here, view on XPost not available here, view on X
Luke Dashjr
@LukeDashjr
1) I'm not the leader. There is no leader.
2) BIP110 cannot cause a chain split.
3) If miners attack the network and cause a chain split, they will be only hurting themselves. -
Luke Dashjr reposted
HMLE
@1hmle
This is straight up lying and gaslighting AF.
Consensus rules have been changed multiple times in the past by Core (e.g., SegWit, Taproot, etc.). Almost every single time, there have been massive unintended consequences and vulnerabilities created. These vulnerabilities ultimately led to the spam blow up from 2023 onwards.
BIP-110 is closing/patching vulnerabilities that Core should have addressed years ago.
If we have never changed consensus rules, I might have agreed with Samson. However, Core has fiddled with "the laws of the universe" many many times (~8-14 times now depending on nuances/definitions) in the past.
Core made the mess (e.g., SegWit, Taproot) and refuses to own up and clean up their own mess. BIP-110 does just that, restoring Bitcoin back to a semblance of what it was in the 2017 to 2023 era.
P.S. BIP-110 basically only limits the size of data payloads allowed, it DOES NOT examine the payload itself and decide if the content is spam/not-spam, Samson is straight up lying.
Again, I repeat (literally the first line in the BIP: bip110.org): 'limit the SIZE of data fields at the consensus level'.
Wanna see an actual Omega candle? Look at Samson's nose.
Samson Mow
@Excellion
I spoke with @Cointelegraph about how BIP110 harms Bitcoin's neutrality and permissionlessness. Bitcoin can be sound money, or it can be a protocol you can easily modify the rules of. It cannot be both.
This media couldn't be displayed. See it on the original post. -
Luke Dashjr reposted
AsyncN8
@AsyncN8
A sybil attack wouldn’t threaten Bitcoin.
That’s why he’s lying about it. Because they are real nodes. What they can’t have is node runners controlling the network. You know, the way Satoshi intended it? The suits are fighting like mad to capture it for them & the state. #bip110
Samson Mow
@Excellion
BIP110 supporters are pioneering a new type of attack: the 1% attack.
If successful, it would show how trivial it is to attack the Bitcoin network. Just rent 1% of the hashrate and spin up 3k nodes. Attackers can be incredibly disruptive and waste massive amounts of time for exchanges, miners, and HODLers.
The actual monetary cost?
Rented hashrate: $0 before forking, as it’s still mining BTC; post-fork ~4.5 BTC per day.
Nodes: 3k nodes for $15k a month.
The solution to mitigating 1% attacks is simply to be pragmatic and disregard them. If you entertain them, you set a precedent for more in the future since the cost is so low.
This is why BIP110 must fail. -
Luke Dashjr reposted
Luis Marcano 🦉 Bitcoin
@MarcanoFilms
The best way to wake up on a Sunday 😎🔥 @Roughnecks110 again killing it ✊✊ we printing #bip110 only 🔥🔥
-
Luke Dashjr reposted
MarylandHODL (aka The Transition)
@MarylandHODL21
The capture of Core is the digital era’s Executive Order 6102.
Instead of trying to seize the unseizable, you capture the keepers of the code.
There’s just one problem.
The nodes own the ledger. We set the rules.
BIP-110 is the protocol’s immune response to the subversion within Core and its funding ecosystem.
Whether BIP-110 succeeds or fails is almost beside the point. The network is now aware. From this point forward, subversion and conflicts of interest will be challenged and rooted out by the broader ecosystem.
This revolution doesn’t end here. It evolves.
This is only the beginning. The movement doesn’t stop until the protocol is secured in accordance with its original intent.
No one ever said monetary transitions were simple.
#thenodewars #bitcoinsethicalkeepers #bitcoinsimmuneresponse #bip110 #fuckthesuits -
Luke Dashjr reposted
Bitcoin Board
@btc_board
showing goodwill shouldn't be a one-week sale event miners have been asleep at the wheel for years this train leaves with or without them
-
Luke Dashjr reposted
Balkan Hodl
@balkanhodl
Luke Dashjr
@LukeDashjr
Bitcoin is sound money with BIP110 and only with BIP110. Core30's release caused price to crash about 50%. The remaining 50% holds on largely due to hope for BIP110.
-
Luke Dashjr reposted
Philip D'Ath
@philip_dath
I'm one of many working on @BitcoinKnots creating bug fixes and new features.
I chat with the other developers doing the same every week.
I invite you to look at the pending queue. Notice that @LukeDashjr is greatly out numbered by all the other Knots developers when it comes to pull requests.
I don't want you to believe me. I want you to verify this yourself. This link has an the pending pull requests.
github.com/bitcoinknots/bitcoin/pulls -
Luke Dashjr reposted
Sean Harris🏀
@BigSeanHarris
BIP-110 is a majority softfork with grass roots rough consensus and no URSF.
Like it or not, it will succeed and it will set a very good precedent. -
Luke Dashjr reposted
Steve Wilkinson
@SteveW928
re: fees will stop spam on Bitcoin
Sure, except the enemies of Bitcoin (especially OG former-Bitcoiner, now spammers and enemies of Bitcoin) have a lot more Bitcoin than I do.
Maybe they'll eventually be priced out, but so will 99.99% of us plebs by that time. That isn't really a solution, even if it eventually works. -
Luke Dashjr reposted
Shaun
@theDAHTcom
Contrats to @__jmn for solving a block, and being the 26th of the difficulty period to do so with a BIP110 signalling block template!!
-
Luke Dashjr reposted
Kevin Bass
@kevinnbass
You are descended from thousands of generations, many of whom faced far worse than you do yet refused to give up hope and quit. Do not quit.
-
Luke Dashjr reposted
Start9
@start9labs
The YouTube video was taken down, here it is for reference
This media couldn't be displayed. See it on the original post. -
Luke Dashjr reposted
Ned17Flanders Let Freedom Ring
@Ned17Flanders
I support Bitcoin consensus before October 2025.
Not After.
Run Knots and BIP-110 83bytes op_return was consensus.
Slay the overlords. End Core. -
Post not available here, view on XPost not available here, view on X
Luke Dashjr
@LukeDashjr
Bitcoin is sound money with BIP110 and only with BIP110. Core30's release caused price to crash about 50%. The remaining 50% holds on largely due to hope for BIP110.
-
Luke Dashjr reposted
₿itcoin Commonwealth
@BTC_Prep
Luke Dashjr
@LukeDashjr
Miners making invalid blocks will be bleeding money. They'll upgrade quickly.
-
Luke Dashjr reposted
Roughnecks
@Roughnecks110
Does this guy look like he gives a flip what Saylor says? Tick tock next BIP110 block
Ocean Blocks
@ocean_blocks
⛏️ New Ocean Block Mined ⛏️
Block Height: 959571
Fees: 0.003 BTC
Subsidy + Fees: 3.128 BTC
Difficulty: 127.17T
Solver: Roughnecks
mempool.guide/block/00000000000000000001701116fee8777b933… -
Luke Dashjr reposted
Bruna Ferreira
@brunaferreiraus
Today, on the Feast of St. James, the Apostle, the Most Reverend Father Michael Mary, F.S.S.R., is consecrated a Bishop of the Roman Catholic Church by the Most Reverend Bishop Pierre Roy. The co-consecrators are the Most Reverend Bishop Rodrigo Ribeiro da Silva and the Most Reverend Bishop Fernando Altamira. Deo gratias!
This media couldn't be displayed. See it on the original post. -
Luke Dashjr reposted
Bruna Ferreira
@brunaferreiraus
Epic photo! May the restoration of Holy Mother Church come through the hands of her faithful ministers. May God bless and strengthen Your Most Reverend Excellencies in this noble mission, for the greater glory of God and the triumph of His Holy Church.
-
Luke Dashjr reposted
stepnoy🪢
@stepnoy385394
bip110 is disadvantageous only to those seeking to maintain a monopoly on transforming Bitcoin into a regulated system; it would mean defeat for everyone, including miners. MASF will demonstrate the community's strength and ideological unity.
Luke Dashjr
@LukeDashjr
Last period of MASF for BIP110 begins in a couple hours.
If miners want to show any goodwill toward the community, this is (for a week) the final opportunity.
After that, it's a UASF. -
Luke Dashjr reposted
HMLE
@1hmle
What a difference 10 months can make...
Or maybe it's 1 phone call... -
Luke Dashjr reposted
.
@GrassFedBitcoin
For those who need an explainer: A Sybil attack of Core 30+ nodes is occurring. It's defenders are (as you'd expect) accusing BIP110 of being a Sybil attack.
-
Luke Dashjr reposted
Flaming.hodl ₿
@flaming_hodl
“Let’s say that Peter [Todd] and I are bad actors. Let’s say that we are. What are you going to do about it? That’s why we are here. How are you going to stop us?” -- Jamison Lopp
BIP-110 -
Luke Dashjr reposted
Sean Harris🏀
@BigSeanHarris
There are many in the anti BIP-110 camp that are “not gonna node” and writing essays about why they don’t run a node and it’s not necessary.
In contract the pro BIP-110 camp is suggesting you run a node and become self sovereign. Very interesting. -
Luke Dashjr reposted
Nordrassil
@NordrassilRoot
Andorra is signaling #bip110 🇦🇩
-
Luke Dashjr reposted
Jim
@elkrun21
The pushback against BIP110 (Reduced Data Temporary Softfork) isn't because of what it does ... it isn't because they're concerned with the seven rules it will enforce.
It's because of what it means ... they won't be able to control bitcoin ... because a meaningful number of individuals are refusing to comply. -
Luke Dashjr reposted
Matthew R. Kratter
@mattkratter
The Bitcoin pleb movement will only accelerate from here. We long ago passed the point where you could still stop us. The toothpaste is out of the tube and ain't never going back in. Any martyrdoms will only strengthen the movement, so think twice
-
Luke Dashjr reposted
Neal Flesher
@NealFlesher
Bitcoin is a “why” before a “what.”
Telos informs its technicals.
Function has primacy.
Purpose cannot be divorced from the act of running Bitcoin software. -
Luke Dashjr reposted
.
@GrassFedBitcoin
These guys were the first ever to find a DATUM block.
Great to see them on BIP110.
Cheers @jeradclough22! -
Luke Dashjr reposted
Star Heartsong · $ASST ALL-IN⛳ · WAGMI 😜🏆✝️🔥🕊️
@DrStarHeartsong
BIP-110er's we are gaining miner signalling momentum. This is not a test. 🚀
-
Luke Dashjr reposted
Bold ₿itcoin BIP110 Blake2b Baller
@BoldBBaller
From what I see WE HAVE CONSENSUS threshold, only 26.6% of nodes want blown up spam enabling Core changes so we will force what majority wants when developers don't respect it.
Toshi
@lamed2025
Bitcoin is money. BIP-110.
Knots at 20%.
Source: bitcoin.clarkmoody.com
Then click Go (under Dashboard) -
Luke Dashjr reposted
SpectrGen // XBT
@SpectrGen
#bip110 supporters were wondering whether @jackmallers supports non-monetary Bitcoin use-cases, so I pulled this clip.
His answer is clear.This media couldn't be displayed. See it on the original post. -
Luke Dashjr reposted
BIP-110 Was Good For Bitcoin Monk
@BitcoinMonk21
BIP-110 has rough consensus.
-
Luke Dashjr reposted
Jim | Bitcoin, not jpegs
@venorusprime
Record hashrate at @ocean_mining.
🌊⛏️💪 -
Luke Dashjr reposted
Conza
@Conza
56 block re-org, 50 BTC per block = 2,800 BTC
Current price: $64k USD
Historical equivalent in todays terms:
$180M in USD cost to miners...
Seems like it'd be a lot wiser to just flip the BIP and support Bitcoin as money (only)...
And signal its QUALITY as MONEY is still ✅ -
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
CVE-2010-5139 was fixed with a retroactive soft fork - 52 blocks worth over 2600 BTC to miners were WIPED OUT from history, and any transactions confirmed in that time were reversible.
It could have been fixed by simply voiding the UTXOs with the inflation, no reorg needed. But that would have been an actually bad precedent, and is NOT a viable solution to CSAM.
BIP110 is great because it avoids even the retroactive fix - by patching the bugs proactively, we can avoid ever having to roll back ANY blocks. Miners don't properly appreciate that by failing to activate it sooner, they have been playing with fire. -
Post not available here, view on X
Luke Dashjr
@LukeDashjr
CVE-2010-5139 was fixed with a retroactive soft fork - 52 blocks worth over 2600 BTC to miners were WIPED OUT from history, and any transactions confirmed in that time were reversible.
It could have been fixed by simply voiding the UTXOs with the inflation, no reorg needed. But that would have been an actually bad precedent, and is NOT a viable solution to CSAM.
BIP110 is great because it avoids even the retroactive fix - by patching the bugs proactively, we can avoid ever having to roll back ANY blocks. Miners don't properly appreciate that by failing to activate it sooner, they have been playing with fire. -
Luke Dashjr reposted
TORONTO HODL 🍁
@EnjoyingBitcoin
My hope for BIP-110:
1. Most miners ignore
2. Trigger Chainsplit with 10-20% of hash
3. MSM FUD on Chainsplit gets very loud
4. ETF and Treasury Company Normies panic sell
5. Bitcoin price plummets, bid disappears for spam-coin, miners struggle to sell
6. Centralized Miners turn off their hash as they mine at loss
7. BIP-110 chain gains on spam-chain (spam-chain hash falls)
8. Centralized Miners realize risk of reorg is growing
9. One centralized miner capitulates, signals for BIP-110
10. Remaining hash follows
11. BIP-110 chain is longest chain
12. Anyone who bought spam-coin loses -
Luke Dashjr
@LukeDashjr
"Do we have any idea how many of those economic nodes matter vs the ones that are just « it's on my desk and I use it for my Sparrow wallet » type thing - like in terms of percentage?"
That node on your desk _used for your wallet_ is exactly what an economic node is, and mattersPost not available here, view on X
Luke Dashjr
@LukeDashjr
As for huge "economic nodes" - while not entirely irrelevant, they should not be overstated either.
Businesses ultimately are at the mercy of their customers. If they don't accept your bitcoins, you can shop elsewhere.
Luke Dashjr
@LukeDashjr
If an exchange's customers want to buy bitcoins, they have to provide real bitcoins according to those customers. They can't just give you fake bitcoins and tell you "tough".
-
Luke Dashjr reposted
Nick Szabo
@NickSzabo4
There are libraries full of laws governing a very wide variety legible content online, and extremely few, if any, lawyers in the crypto space who have strong experience in them and are also strongly familiar with the unique nature of most blockchains (e.g. the often extreme functional disruption that comes from deleting data once it is on a blockchain). Here is just the tip of the the tip of the iceberg -- a small fraction of relevant U.S. federal law -- not even considering the 50 State laws, the 100s of foreign country and provincial laws, etc.
“Whoever, … having unauthorized possession of, access to, or control over … any document, writing … or information relating to the national defense … willfully communicates, delivers, transmits … or attempts to communicate, deliver, transmit … the same to any person not entitled to receive it … shall be fined under this title or imprisoned not more than ten years, or both.”
— 18 U.S.C. § 793(e)
“Whoever … communicates, delivers, or transmits … to any foreign government … any … information relating to the national defense … shall be punished by death or by imprisonment for any term of years or for life …”
— 18 U.S.C. § 794(a)
“Any person who commits an offense under section 506(a)(1)(A) … shall be imprisoned not more than 5 years … or fined … or both … if the offense … consists of … distribution, including by electronic means, … during any 180-day period, of at least 10 copies … of 1 or more copyrighted works, which have a total retail value of more than $2,500” … “shall be imprisoned not more than 10 years … if … a second or subsequent offense.”
— 18 U.S.C. § 2319(b)
18 U.S.C. § 1462 — Importation or transportation of obscene matters: “Whoever … knowingly uses … any … interactive computer service (as defined in section 230(e)(2) …), for carriage in interstate or foreign commerce — … any obscene, lewd, lascivious, or filthy … matter … Shall be fined … or imprisoned not more than five years, or both …”
18 U.S.C. § 1465 — Production and transportation of obscene matters for sale or distribution: “Whoever knowingly … uses … a facility or means of … an interactive computer service … in or affecting such commerce, for the purpose of sale or distribution of any obscene, lewd, lascivious, or filthy … matter … shall be fined under this title or imprisoned not more than five years, or both.”
18 U.S.C. § 1466 — Engaging in the business of selling or transferring obscene matter: “Whoever is engaged in the business of producing with intent to distribute or sell, or selling or transferring obscene matter, who knowingly receives or possesses … any obscene … recording … which has been shipped or transported in interstate or foreign commerce, shall be punished by imprisonment for not more than 5 years …”
There are libraries full of this kind of thing, covering an extremely wide variety of kinds of legible content. -
Luke Dashjr
@LukeDashjr
Reminder that Core actively opposed BIP148, and denied their users the ability to upgrade to it.
ndgo - SHA256 Maximalist
@ndgo1370
In 2037, When future coretards are telling their grandchildren about Node War 2
They'll claim bitcoin core was actually "neutral" towards BIP-110 and that they weren't on the side of Big Bitcoin at all.
Same as Node War 1.
Its a shame. -
Luke Dashjr reposted
OCEAN
@ocean_mining
-
Luke Dashjr reposted
David Dev
@DavidD99261219
> BIP-110ers want a dev-dictator.
No. We were forced to find a suitable host. Core has had the BIP-110 code changes from Dathon for 4 months. They closed it and locked conversation the day it was submitted.
github.com/bitcoin/bitcoin/pull/34929
github.com/bitcoin/bitcoin/pull/34930 -
Luke Dashjr reposted
hodlonaut
@hodlonaut
Introducing the 2026 New York agreement
The Bitcoin Suit Consortium.
Michael Saylor
@saylor
Bitcoin’s security is a shared responsibility.
Today we are launching the Bitcoin Security Consortium, backed by $15 million in commitments to support the developers and researchers strengthening Bitcoin for the decades ahead. www.strategy.com/press/leading-financial-institutions-bit… -
Luke Dashjr reposted
Flaming.hodl ₿
@flaming_hodl
There is a reason Core and others have been saying your node doesn't matter. They are doing everything to centralize control. Policy was one reason your node mattered. Corporate takeover is the next step. All of these are against BIP-110 because if means we are still in control.
Strategy
@Strategy
Today we're announcing the Bitcoin Security Consortium @BTCconsortium: a group of leading financial institutions and Bitcoin companies supporting the long-term security of the Bitcoin network.
Members have pledged $15 million toward this work over the next three years. -
Luke Dashjr reposted
hodlonaut
@hodlonaut
What is your BIP-110 stance?
-
Luke Dashjr reposted
TORONTO HODL 🍁
@EnjoyingBitcoin
I don't get the fud around BIP-110.
The choice for Miners seems really simple.
Option 1: Ignore BIP-110
- Lose 15% (or more) of customers
- Trigger a chain split
- Ongoing risk that hashrate migrates to BIP-110, causing reorg
- Risk of PR & Stock drama
Option 2: Adopt BIP-110
- Continue serving 100% of customers
- No chainsplit
- No reorg risk
- No PR or Stock drama -
Luke Dashjr reposted
Extractive Ghost of Unhosted Marcellus 👻
@oomahq
Classic mandatory reading for any bitcoiner. medium.com/incerto/the-most-intolerant-wins-the-dictators…
-
Luke Dashjr reposted
Blake Hammond🔥⛏️
@FieldNas
If Child Sexual Abuse Material transmitted to the SSD on your coffee table & sent back out, doesn't get you off your couch to fight for Satoshi's invention, how repugnant & lost are you?
Not to mention if you get your way, you'll only inherit the ruins of your own depravity. -
Luke Dashjr reposted
Kretch🐸 b2b xbt bitcoin
@kretchino
In retrospect coretard influencers will say that bip-110 was inevitable 🤗
-
Luke Dashjr
@LukeDashjr
Every tweet from @Excellion makes BIP 110 more likely to happen
Samson Mow
@Excellion
Every tweet from @JihanWu makes #uasf more likely to happen. 😆
-
Luke Dashjr reposted
1-year Coinbase Maturity Dave BIP-110⚡️
@davelund_
It’s official: France is signaling #bip110
-
Luke Dashjr reposted
Rune Østgård
@enur72
Is it a coincidence that the bitcoin price dropped 50% since v30 set Bitcoin on course to become à digital landfill?
Support BIP-110. -
Luke Dashjr reposted
1-year Coinbase Maturity Dave BIP-110⚡️
@davelund_
Lugano is running BIP-110 @mattkratter
-
Luke Dashjr reposted
1-year Coinbase Maturity Dave BIP-110⚡️
@davelund_
Breaking: Prague is signaling BIP-110
-
Luke Dashjr reposted
Start9
@start9labs
The blocksize war was won by the nodes, UASF.
Lesson: don't wage war agains the nodes, you will lose. -
Luke Dashjr reposted
ab ☁️
@antbit
Nice to meet you, Moonwalk!
-
Luke Dashjr reposted
Without Rulers - #BTCB2
@BTCLeukocyte_WR
Yes. This is the lesson that we're learning.
#bitcoin is being tested.
If nodes reject the shitcoin scammers (centralized fiat) that captured the reference client then there is hope.
There are no heroes to follow.
You need to participate in the emerging chaos of the network.
Madosatoshist XBT
@Madosatoshist
A tidal wave of relatively new bitcoiners have taken an extensive advanced Bitcoin summer course.
-
Luke Dashjr reposted
Odin | BIP-110
@LegitSatStacker
People really underestimate how important BIP-110 really is. If it fails and miners can simply veto a soft fork with nearly 20% node support then the end of bitcoin begins right there. It's insane to me how people can wish for BIP-110 to fail considering those implications.
Even if you hate it, anyone should wish for it to work because if nodes can be overruled like that it's literally over. -
Luke Dashjr reposted
Accredited Financial Survivor
@CryptoJiven
Bitcoin is the future. Run BIP 110
Luke Dashjr
@LukeDashjr
I support BIP110 because Bitcoin is essential to the future of mankind and the last 8 months have proven it to be the best immediate solution to the critical injury inflicted by Core 30.
-
Luke Dashjr reposted
The Excommunicate ⚡️
@AntePurgatorio
Core V30 actually made it impossible to get the behavior from prior versions.
It wasnt just a config change from 83 to 100000
They added multiple outputs to OP_RETURN, and there was no way to configure the policy in V30 to match a V29 node.
BIP110
x.com/i/grok/share/f639b64d343343a59b75652f435bcc6f -
Luke Dashjr reposted
Start9
@start9labs
1🫴 Flip a bit, no chain split.
Stability. Costs ~0.1% of revenue for 1 year.
2🫴 Don't flip a bit, chain split.
Chaos. LN counterparties stranded, loss of fee-paying users, risk of having rewards wiped out.
Doing #1 now is risk-free reconnaissance. Only continue if more join. -
Luke Dashjr reposted
Crypto Tea
@Cryptotea
This is the first time I've seen the community rally behind bitcoin being money
not some investment or commodity or something you just hold to magically get rich
bip 110 is bringing bitcoin back to its roots and exposing all the bad actors -
Luke Dashjr reposted
OCEAN
@ocean_mining
Introducing: PORTAL
The First End-to-End Encrypted and Permissionless Pool Dashboard for Bitcoin Miners.
PORTAL delivers a fully customizable dashboard, no account or email required.
PORTAL is free to all OCEAN miners and available now.
portal.ocean.xyzThis media couldn't be displayed. See it on the original post. -
Luke Dashjr reposted
Bitcoin Anon
@14g23h34
Mask off.
Confirmation of everything 110 and knots supporters have been saying.
At least he's being honest.
This is not the direction we want Bitcoin to go.
Endless innovation for the sake of developers that want to build for job security.
Justin Bechler
@1914ad
‼️ You must understand that Bitcoin has already been repurposed, and that if RDTS fails, Core™ and its funding apparatus own the future of the protocol.
⚠️ Must be seen to be believed.This media couldn't be displayed. See it on the original post. -
Luke Dashjr reposted
hodlonaut
@hodlonaut
BIP-110 is the hill on which the soul of Bitcoin will be defended or lost.
-
Luke Dashjr
@LukeDashjr
I support BIP110 because Bitcoin is essential to the future of mankind and the last 8 months have proven it to be the best immediate solution to the critical injury inflicted by Core 30.
-
Luke Dashjr reposted
Majorian
@MajorianBTC
Fortunately for bitcoin, the network is unaffected by an echo chamber of suitcoiners and influencer types wagging their finger at you for making your own decision on what node software you run.
The network only cares about the nodes. -
Luke Dashjr reposted
.
@GrassFedBitcoin
I'm glad @FoundryServices chose to share this thought in particular with their miners.
Miners have to gauge community sentiment accurately as they should not signal in favour of a soft fork unless it has genuine, grassroots support.
I believe that any reasonable person can reach the same conclusion: that BIP-110 has more than enough support from within the least corruptible subset of Bitcoiners that make up the community and that it behooves the Bitcoin industry to respect them.
.
@GrassFedBitcoin
Why I think many who are less optimistic about BIP110 than I am are mistaken -
The "Economic Node" concept.
This emerged as a way to dismiss obviously frivolous nodes that get spun up in an effort to astroturf forks within Bitcoin.
Very quickly during the fork wars people realized - "Hey, these nodes might not actually represent any real activity within the Bitcoin ecosystem, they're just there to warp the stats on node tracking websites and make something look like it has more support/opposition than it does."
I will point out that that is *not* what has happened with BIP110/Knots in general - those are real people which @start9labs can attest to, having sold millions of dollars worth of servers to people over the last couple of years who overwhelmingly bought them in order to run Knots. That is not fake and is corroborated through various imperfect heuristics.
However the point I want to make is that the most intimidating of economic nodes - i.e the ones run by mining behemoths like Antpool or exchanges like Coinbase - are not where anyone should look when attempting to gauge support for a soft fork - especially a controversial one. (At least not until very late in the day.)
These nodes obviously represent a huge on-chain footprint, but conversely, they are run by companies who will be the last to take a stand on anything controversial as it has the potential to create drama for them over a decision that isn't theirs to make anyway.
However the lesser economic nodes aren't concerned with that. They don't have legal/PR depts or shareholders who need to sign off on these things (or who will sue them if they do something "reckless". They can just adopt a new client if they think it's good for Bitcoin.
When Bitcoin is in crisis mode with difficult decisions to make, the institutions are going to be the last to choose a direction and that is a *good* thing.
Ideally soft forks to start as grassroots movements, and while the nodes indicating support for them may not be run by billion dollar mining empires/exchanges, as long as they represent real Bitcoiners, the change will be coming from the correct place - from those least likely to be under duress unlike large industry players who necessarily always would be. -
Luke Dashjr reposted
The ₿itcoin Artist
@worshipbitcoin
Not only did Core refuse to roll back v30
They completely disappeared from the debate and insulated themselves further away from the community they were supposed to be accountable to. -
Luke Dashjr reposted
Jason Hodlers
@geekigai
I support BIP-110 because I believe it is important, the right thing to do, and good for Bitcoin.
Luke de Wolf
@lukedewolf
I support BIP-110 because I believe it is important, the right thing to do, and good for Bitcoin.
-
Luke Dashjr reposted
₿itcoin-GUS🧡
@Scavacini777
How many of the core devs is Bitcoin just a job to?
How many of the core devs actually love, or at least like Btc?
How many core devs own a significant amount of Bitcoin?
Fair questions no?
I'll stick w/the catholic father of 11 who actually LOVES Bitcoin -
Luke Dashjr reposted
Not that Elon.
@Eggplant_Elon
Bitcoin’s entire value proposition is that any individual can verify the full monetary history and current state of the system on modest hardware, without trusting anyone.
Verification is what makes the 21 million cap real. A supply cap you cannot personally audit is a promise, and Bitcoin exists because we know promises from monetary authorities fail.
From this, it follows that every byte written to the chain is a permanent, universally replicated liability.
It must be downloaded, validated, stored, and served by every full node that will ever exist, forever.
Blockspace, therefore, is a commons with the unusual property that consumption is instant and the cost is eternal.
The standard objection to any data restriction is that fees already ration blockspace.
Yes, they do. But a transaction fee is paid once, to one miner, for inclusion in one block. The cost of that transaction is borne by every node operator in perpetuity via the initial block download, disk space, bandwidth, and, worst of all, working memory when data is stuffed into unspendable outputs that bloat the UTXO set and can never be pruned!!
So, the buyer pays for admission, and everyone else pays for storage, indefinitely.
In economic terms, this is a textbook example of a negative externality.
Let's imagine that a fee market for data embedding is equivalent to a landfill that charges a one-time tipping fee and then requires every household in the country to keep a copy of the waste in their garage forever.
The tipping fee can be perfectly market-clearing at the gate and still be wildly underpriced relative to the true social cost.
Fees ration who gets in the block, but consensus rules are the only mechanism Bitcoin has ever had for capping what the network as a whole must carry.
This is the case for BIP-110 in a sentence…fees decide who gets into a block, and consensus rules decide what every node must carry forever.
BIP-110 may not be perfect, and determined spammers will always probe for gaps. But the burden it targets does not expire with the proposal, and Bitcoin will have to answer for it eventually! -
Luke Dashjr reposted
ScarcityMan 🍴 BLAKE2b Hardfork
@ScarcityMan
I'm blocked from responding directly, but we're trying to save the very life and soul of bitcoin here. Why do you think we care about causing "drama?" This is a you-problem, not an us-problem. Don't want drama? Stop trying to argue and convince people that a couple dozen lines of bug fixes is worth destroying bitcoin to prevent. We're not letting ourselves be gaslit by this. The adults are going to fix the bugs now. You're welcome.
Samson Mow
@Excellion
BIP110 supporters: You claim Bitcoin is captured by corrupt devs, suitcoiners, spammers, plus "Big Bitcoin," and that only an emergency soft-fork can save it. When BIP110 activates as a minority fork, can you in good conscience keep holding/using BTC after causing so much drama?
-
Luke Dashjr reposted
AuthintegXBT
@authintegx
Here's your proof that Foundry is asking their miners to vote on BIP-110. Resource page provided to help them make an informed decision.
services.foundrydigital.com/bip-110_resources -
Luke Dashjr reposted
Shire
@Shireh0dl
I support BIP-110 because it represents a long overdue return to adversarial thinking & caring about bitcoin's attack surface.
For too long, node runners have been cucks of wannabe Ethereum devs, more interested in shiny things than securing my money or fortifying my node. -
Luke Dashjr reposted
ab ☁️
@antbit
“One percent may sound like a rounding error. But 8–10 EH/s is approximately the entire Bitcoin network circa 2017, the hashrate that carried Bitcoin through the SegWit activation fight. In physical terms it is on the order of 40,000–50,000 modern ASICs, hundreds of millions of dollars in hardware, drawing continuous power in the range of a mid-size power plant. Nobody points a power plant at a signalling bit by accident. These are industrial operators making a public, capital-backed statement."
15% of nodes and ~1% of hashrate has already locked in on BIP-110. Large pools/miners can't fence sit any longer. They can either signal before the window and the split risk basically vanishes, or stay silent and own whatever chain split follows. If no big pool flips in time, the enforcing chain starts crawling but stays valid and un-reorgable by the majority, creating that wipeout overhang.
Another excellent read by @CunyRenaud.
blockspaceweekly.substack.com/p/issue-32-to-… -
Luke Dashjr reposted
boozy | XBT
@TheBoozles
Two great blocks back to back. Did the world implode because they both followed BIP-110? Did it prevent anybody from sending bitcoins to another person? No.
-
Luke Dashjr reposted
Shaun
@theDAHTcom
When someone says BIP-110 is solely a technical issue, or something only engineers are qualified to address, they are missing how Bitcoin actually works.
Luke is one of the strongest technical minds in Bitcoin. He could run circles around most people debating code, math, and implementation details.
Yet his point here is bigger than technical nuance: consensus begins at the conceptual level, with users deciding what Bitcoin is and which rules they are willing to accept.
The point? Engineers implement Bitcoin. They do not own its purpose.
Luke Dashjr
@LukeDashjr
The requirement for consensus is necessarily at a conceptual level, not a technical nuance. If it was a technical matter, it would be impossible to softfork ever, since nobody would be running the code before it is written.
At a conceptual level, all nodes enforced the BIP110 rules until late 2025, and a supermajority still do today.
The requirement for consensus is also not absolute. Very few softforks in Bitcoin's history have had true consensus. P2SH was a big battle. Segwit saw 20% of the community leave over it. Taproot saw Core abuse their position to nearly conflict on activation method.
Generally, "objections" that are ill founded or sufficiently addressed do not impede moving forward.
Before BIP110 was proposed, there were zero objections to the ideas put into it, and there are still no sound objections to BIP110 to date.
At a technical level, softforks do not require consensus, only significant support and less opposition. To date, there is essentially zero opposition at the technical level. Not a single node is running a URSF.
Conceptually, Segwit had ~80% network support, and ~5.2% actually enforcing. Bcash (the anti-Segwit URSF) launched with ~2.5%.
BIP110 for comparison today has ~80% network support, and ~15% actually enforcing. And again, zero visible URSF nodes. -
Luke Dashjr reposted
Knut Svanholm ∞/21M
@knutsvanholm
Framing BIP-110 as a rule change signals a misunderstanding of Bitcoin's rules.
The rules always allowed the network to do things like this. BIP-110 is the Byzantine Generals' Problem being solved in real-time.
The rules were always dictated by the community, not the code. -
Luke Dashjr reposted
Fully Noded - Dev
@Fonta1n3
This isnt hyperbole, its literally true.
Multiple bad bugs released in core recently, didnt make it to knots.
I’m not referring to uncapping op_return.
Donal
@DonalDevine
Bitcoin Knots is Bitcoin Core with all the bugs fixed.
-
Luke Dashjr reposted
Dathon Ohm / BIP-110
@dathon_ohm
The FUD storm continues, with only 18 days left until mandatory signaling!
In this episode, Murch tries to claim that BIP-110 had "insufficient review", because he himself did not catch a "problem" that only he considers to be a problem.
Dathon Ohm / BIP-110
@dathon_ohm
And again, it was _your_ responsibility to communicate what you believed the correct definition of P2A was, which you had several months to do. If you intentionally failed to do your job, that does not mean that BIP-110 had insufficient review.
-
Luke Dashjr reposted
Kiawtzin
@kiawtzin
Real bitcoiners ought to have the balls to URSF when faced with a truly malicious fork. The fact that there's absolutely no one willing to URSF against BIP110 proves 2 things:
1) it is not an attack
2) its detractors have no balls
Luke Dashjr
@LukeDashjr
If you want to force me to distribute CSAM, I ain't letting that be a bygone. Screw you.
Miner signaling is not approval. Approval is before miner signaling begins. BIP110 has consensus.
If you try to softfork to burn our coins, we will URSF.
You can URSF and fork off too. -
Luke Dashjr reposted
BitcoinAussie | BIP-110 | 🧃to 🧡
@bitcoinaussie_
10/10 is on the charts for all to verify.
-
Post not available here, view on X
Luke Dashjr
@LukeDashjr
If you want to force me to distribute CSAM, I ain't letting that be a bygone. Screw you.
Miner signaling is not approval. Approval is before miner signaling begins. BIP110 has consensus.
If you try to softfork to burn our coins, we will URSF.
You can URSF and fork off too. -
Luke Dashjr reposted
Dathon Ohm / BIP-110
@dathon_ohm
With less than 19 days left until mandatory signaling, new miners continue to flood in to signal readiness for BIP-110.
Congratulations to all of our new miners, including SpammersGFY who mined this one.
Bitcoin is healing.
Ocean Blocks
@ocean_blocks
⛏️ New Ocean Block Mined ⛏️
Block Height: 958831
Fees: 0.001 BTC
Subsidy + Fees: 3.126 BTC
Difficulty: 127.17T
Solver: SpammersGFY
mempool.guide/block/000000000000000000002591a06e849f32831… -
Luke Dashjr reposted
PyBLØCK
@_PyBlock_
Craig Wright aka Faketoshi removed the limits on OP_RETURN in his BSV Scam, and his chain got flooded with CSAM.
He also impersonated SN and was found liable for it.
Today, he is anti-#bip110.
It seems that morons are going to be morons forever…
Poor @CsTominaga @Dr_CSWright -
Luke Dashjr reposted
hodlonaut
@hodlonaut
I support BIP-110 because I believe it is important, the right thing to do, and good for Bitcoin.
-
Luke Dashjr reposted
Renaud Cuny
@CunyRenaud
💯
Renaud Cuny
@CunyRenaud
-
Luke Dashjr reposted
Majorian
@MajorianBTC
The game theory of BIP-110 is this:
Does a miner risk splitting the network and accept the associated business risk given that the support for BIP-110 is known (and significant) and the rejection of the BIP-110 is not quantifiable at the present time? -
Luke Dashjr reposted
Matteo Pellegrini
@matteopelleg
it bip110 activates and its critics are right it goes away in 1 year
if bip110 fails and its proponents are right, bitcoin dies -
Luke Dashjr reposted
ndgo - SHA256 Maximalist
@ndgo1370
spam censors far more transactions than bip110 will
-
Luke Dashjr
@LukeDashjr
On Saturday, a troll made a false "consensus failure" report about Bitcoin Knots.
To put it simply: if Core corrupts your data, Knots sometimes can't detect the corruption.
Since Core is late updating to BIP110, it can in some case corrupt the database after activation.Post not available here, view on X
Luke Dashjr
@LukeDashjr
On Sunday, another fake "bug" was claimed by Murch.
It's a complete fabrication. There is nothing to do.
Luke Dashjr
@LukeDashjr
In both cases, there was zero disclosure to the project at all (much less responsible disclosure) - this is clearly a bad faith FUD campaign and will probably continue.
If any real concerns were to surface, @BitcoinKnots would post an announcement. -
Luke Dashjr reposted
Ghost of Chad
@GhostofChad
Thanks to @ocean_mining (specially for DATUM protocol) and @Braiins (for building a hashrate marketplace), using this I was able to find a block recently using my own Knots node and my own configurations. Many would disagree with my config(whether BIP110 or datacarrier=0 or small block) but this is how decentralization should work. Conceptual disagreements outside of how you run your software stack is part of the emergence of consensus and it shouldn't emerge from a committee of few experts who make abrupt changes to the node client against the wishes of their own users.
I would further request @braiins team to continue providing their excellent service to users on both side of this debate without bias and let a natural consensus emerge. The mining pools are already heavily centralized, so the few decentralized miners like myself trying to mine with their own nodes & preferences should only be encouraged IMHO. -
Luke Dashjr reposted
Dathon Ohm / BIP-110
@dathon_ohm
With only 2728 blocks (~19 days) to go until mandatory signaling, the low-effort FUD continues! This time, Murch tries to claim that the BIP-110 specification disagrees with its implementation, but he is well aware that the BIP-433 P2A policy carveout requires an empty witness.
Dathon Ohm / BIP-110
@dathon_ohm
Yes, and as you know, BIP-110 takes certain policy rules and elevates them to consensus rules. P2A as defined in policy requires an empty witness to be considered a P2A spend, and BIP-110 elevates this rule in its entirety to consensus. This is very straightforward.
-
Luke Dashjr reposted
Jason Hodlers
@geekigai
Anti-BIP110 shitcoiners today:
hodlonaut
@hodlonaut
Craig Wright joins the suits in their support of non-monetary use of Bitcoin and ridicule of BIP-110 🤷♂️
-
Luke Dashjr reposted
Donal
@DonalDevine
Bitcoin Core are no longer relevant
-
Luke Dashjr reposted
MrSatoshi
@Lightningmaxi
Bitcoin Knots
-
Luke Dashjr reposted
Ghost of Chad
@GhostofChad
thx!
-
Luke Dashjr reposted
hodlonaut
@hodlonaut
Craig Wright joins the suits in their support of non-monetary use of Bitcoin and ridicule of BIP-110 🤷♂️
-
Luke Dashjr reposted
Secure Sovereign 🚀₿🧡
@secsovereign
Posting on behalf of Lori Singer Meyer..
To the Bitcoin Community:
I have discovered people have been wondering about my sudden absence from X, and to stave off an uprising that I was banned, I have asked two people to post this message, and am asking if you are reading it to please repost so it gets wide distribution.
My account is down because before hanging out with my new community of Bitcoiners, I was very careful to use it for private posting only. My real name is on the account, but someone would have to take a few steps to know whom I am, and I have never been doxxed. However, as I have become more vocal about BIP-110, something I feel strongly should be implemented, I have worried that I would be doxed, and not on my own terms. A lot of posts from when I was posting on private issues, or issues related to my legal career, would be fodder for someone to use against me as a weapon in some way. So I temporarily deactivated my account in order to clean it up as someone who has become more in the public eye on X.
The other day I was back-and-forth posting with ClioBitBank and in the spirit of fun, I kept asking Clio why he couldn't learn about my background since I have had press coverage in the past. Apparently AI does not pick up paper press clippings, and almost everyone relies on AI to do all their research.
O screw it, this will come out anyway. My husband, Eugene B. Meyer, was the founding President and CEO of the Federalist Society until his retirement a year and a half ago.
I worked alongside this group as a volunteer in order not to draw attention to myself that might be attributed to either my husband or the organization during those years. It was critical to keep my name out of the public sphere. I was under specific personal and organizational orders to keep my name out of the public eye. There is one time I did speak to the press and it went viral, proving the point.
Finally, with my husband's retirement, I can do my work as a lawyer with 25 years of inside the Beltway experience outside the dark..
h/t
@masunobom
@uanbtc
@BitcoinMania___
1/2 -
Luke Dashjr reposted
-
Luke Dashjr reposted
Camina Drummer Blake2b
@CaminaDrummer4
After a year there still is not one single sincere opposition to BIP-110
All of them are pedos, influencers, or morons, and not a single respectable argument based on technical or economics.
But the pile of bodies from the frauds who immolated themselves piles up.
Bye bye -
Luke Dashjr reposted
Ian A. Northon
@Bitcoin_Lawyer
Nick is of course right here. It’s goes to intent, which is the baseline consideration for all crimes in the US and many other jurisdictions. Storing or relaying financial data (the intent of Bitcoin/node runners) is attacked by non-monetary use cases, but currently, those are exploits of bugs. Corev30’s efforts at changing the intent of Bitcoin through intentional modifications to allow file storage arguably guts this “no intent” defense and puts all Bitcoiners and node runners at much higher risk.
-
Luke Dashjr reposted
.
@GrassFedBitcoin
"BIP110 threatens Bitcoin's neutrality"
Bitcoin is neutral because its rules are enforced by a decentralized network of nodes.
Its neutrality is not a result of not having any rules.
Decentralized enforcement of rules is compromised and undermined profoundly if the rules are made so loose that they cannot properly prevent attacks.
But rules can always be tightened to help defend decentralization of nodes and thus *maintain* Bitcoin's neutrality.
BIP110 is how you prioritize decentralization and thus neutrality.
It is not a "slippery slope to subjective enforcement of rules" as opponents insist.
It is the exact opposite.
The centralizing pressure of parasitic "use cases" for Bitcoin have placed us on the path to subjectivity. BIP110 is one a many efforts made by Bitcoiners to correct course and ensure decentralization is made the number one priority. -
Luke Dashjr reposted
Ralf Müller
@ralflmuller
BIP110 became another "block size war".
Once again, it comes down to a fundamental decision: will INDEPENDENT node runners defend Bitcoin’s principles [BIP110], or will centralized powers succeed in an attack vector via spam—as a substantiation for further "helping" in the future
Samson Mow
@Excellion
We're quite fortunate to have @saylor in this timeline. He took the time to understand the current situation around BIP110 and is writing about the importance of Bitcoin staying neutral and permissionless. We couldn't really ask for more.
In a pod with @PeterMcCormack a few years back, I posited that if in the next "Blocksize War" Saylor ended up on the other side, it would be quite painful. I'm happy to see that's not the case!
Michael Saylor
@saylor
Many Bitcoiners I respect support BIP 110. I understand and share their desire to protect Bitcoin, but believe the proposed cure is more dangerous than the condition. Here are 110 reasons why Bitcoin needs guardians of neutrality.
-
Luke Dashjr reposted
TORONTO HODL 🍁
@EnjoyingBitcoin
Miners must either collude or adopt BIP-110
They’re claiming BIP-110 will fail because miners will simply collude and refuse to flip the switch.
Collusion is theoretically possible and happens in business all the time. For example, in 2014, four pharmaceutical companies coordinated price increases on the same drug. Instead of the market driving prices down, they artificially inflated them and increased fat margins for everyone involved.
But what happens if one company had defected? Customers would immediately buy the cheaper drug. The agreement collapses. All companies are forced to cut prices, and the fat margins disappear for everyone.
COLLUDING WAS MORE PROFITABLE THAN COMPETING.
Now look at BIP-110.
If miners collude by ignoring BIP-110, they lose ~15% of the nodes overnight. No business willingly sheds that many customers. Not 2%. Not 5%. Definitely not 15%.
The stronger point is the defection risk: if even one or two large miners adopt BIP-110, they continue serving 100% of the nodes and put the colluding miners in serious danger. Hundreds of thousands of dollars (or more) sit at risk on a chain that could be invalidated or reorged.
The incentives are inverted:
Pharma collusion
- Collude → higher margins for all
- Defect → margins collapse for everyone
BIP-110
- Collude → lose customers + face wipeout risk
- Adopt → keep every customer and potentially hurt the miners who stayed behind
Miners will not coordinate to serve fewer nodes AND face wipeout risk.
They will adopt BIP-110 because it is the lowest-risk, highest-upside option available to them.
ADOPTING BIP-110 IS MORE CERTAIN & PROFITABLE THAN TRUSTING THE COMPETITION TO COLLUDE AND IGNORE IT. -
Luke Dashjr reposted
Luis Marcano 🦉 Bitcoin
@MarcanoFilms
The “economic nodes” cope is exhausting.
Those 15k+ nodes running RDTS aren’t ghosts or Sybil attacks. They’re real sovereign operators who spent real capital on hardware, power, and dedicated setups to run their own verification.
Every node enforces consensus rules identically. There is no protocol weighting that gives a high-volume exchange node more verification power than a pleb node that invested thousands to stay sovereign.
What actually matters for a soft fork is whether the nodes rejecting non-compliant blocks are positioned where miners must produce valid blocks to have their rewards spendable on the chain people use.
Dismissing thousands of real node runners as “not economic enough” while pretending only institutional volume counts is just institutional gatekeeping dressed as analysis.
We’ve moved past the technical FUD. Now the fallback is “do nothing” and “you’re all set for August.”
The network is already enforcing where it counts. BIP-110 is live in production on sovereign Knots setups. The spam bloat doesn’t fix itself by waiting it out.
Lyn Alden
@LynAldenContact
Great, then you’re all set for August.
-
Luke Dashjr reposted
Walker⚡️
@WalkerAmerica
PSA to BIP110 folks: here is a thread of Luke Dashjr telling plebs that nodes don’t matter unless they have economic influence…
“A node is only as relevant as its operator's economic influence.” -
Luke Dashjr reposted
Lilly
@JustaLillyBit
-
Luke Dashjr reposted
Bitcoin for Freedom
@BTC_for_Freedom
The Bitcoin node discussion is really simple:
BIP-110 will make it more decentralized.
Core V30 will make it more centralized.
That’s it. -
Luke Dashjr reposted
Luis Marcano 🦉 Bitcoin
@MarcanoFilms
Saylor dropping a 110-point manifesto against BIP-110 at 4AM?
This is the signal.
While corporate stacks and “neutrality” advocates write long articles, thousands of sovereign node operators are running Knots, enforcing rules that protect Bitcoin from becoming a permanent data dump.
Bitcoin isn’t secured by custodians or the biggest public holders. It’s secured by users who actually verify the chain and choose their consensus rules.
The spam era distorted incentives and raised costs for everyone running a real node. BIP-110 is the correction — temporary, targeted, and driven by the people who actually secure the network.
If this level of pushback is needed, it means the plebs running nodes are already winning.
Run Knots. Verify. The network belongs to those who enforce sound rules.
#bitcoin #bip110 #knots
Michael Saylor
@saylor
Many Bitcoiners I respect support BIP 110. I understand and share their desire to protect Bitcoin, but believe the proposed cure is more dangerous than the condition. Here are 110 reasons why Bitcoin needs guardians of neutrality.
-
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
BIP 91 was never actually deployed by users. It would technically be classified as a 51% attack and ineligible as a BIP at all, if it hadn't been just miners complying with BIP148 with a face-save.
Ultimately, it was BIP148 that activated Segwit. Not 141 or 91. -
Post not available here, view on X
Luke Dashjr
@LukeDashjr
BIP 91 was never actually deployed by users. It would technically be classified as a 51% attack and ineligible as a BIP at all, if it hadn't been just miners complying with BIP148 with a face-save.
Ultimately, it was BIP148 that activated Segwit. Not 141 or 91. -
Luke Dashjr reposted
ScarcityMan 🍴 BLAKE2b Hardfork
@ScarcityMan
⚠️Warning: If you're new to node running on bitcoin and want to get in the fight, you don't have much time. Syncing and downloading the block chain for the first time can take WEEKS depending on your internet connection. No time to lose. Get on it today!
-
Luke Dashjr
@LukeDashjr
Reminder: If your wallet is not using your own node, your node isn't doing much, and can't protect you.
If your wallet does not allow you to use your own node, you should seriously consider switching to one that does. -
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
BIP 444 was materially different: no grandfathering, and reactive, retroactive activation.
By deploying BIP 110, the community avoids the need for BIP 444. -
Post not available here, view on X
Luke Dashjr
@LukeDashjr
BIP 444 was materially different: no grandfathering, and reactive, retroactive activation.
By deploying BIP 110, the community avoids the need for BIP 444. -
Luke Dashjr reposted
Donal
@DonalDevine
It appears as if a lot of Core nodes shut down at the weekend, I wonder why that is??
This crawler runs 24/7, caught them lacking
bip110.xyz -
Luke Dashjr reposted
Donal
@DonalDevine
I am curious to know what people gain by being anti-bip110?
Is it that they are jealous of Luke?
Do they want jpegs on Bitcoin?
Bip110 tightens the rules that make Bitcoin money.
Surely you can't be against that? -
Luke Dashjr reposted
Flaming.hodl ₿
@flaming_hodl
Core V30 opened up Bitcoin to a poison block attack.
BIP-110 closes that attack vector. -
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
No node, no keys = not adoption
-
Luke Dashjr reposted
Blake Hammond🔥⛏️
@FieldNas
My wife's college professor told her class of 12: If nobody shows up to take the final exam, I will give everyone an A+ on the exam. But if even one person shows up, that person will take the test and be graded, everyone else will get zeros.
She told them: I've offered this for 10 years, and never once has any class been able to trust one another enough to all not show up.
The morning came; they were all in their seats with their #2 pencil.
BIP110 will succeed. -
Luke Dashjr reposted
.
@GrassFedBitcoin
"ChatGPT fails to find any bugs in BIP110 code, gets misrepresented, desperate anti-BIP110 people retweet article without having read it."
Joe Carlasare
@JoeCarlasare
BIP 110 Folks in shambles
-
Luke Dashjr reposted
Adam Simecka
@AdamSimecka
Either the miners control Bitcoin or the nodes do. We will find out next month.
The mining pools are regulated and controlled by the state.
Nodes are largely disparate and independently controlled by the users of the network. -
Luke Dashjr reposted
bendtheknee
@bendthekne3
It can not be avoided anymore. Core refused the chance. We march. We signal BIP-110.
-
Luke Dashjr reposted
Bitcoin for Freedom
@BTC_for_Freedom
Bitcoin will separate money from state, but it won’t come easy. We need to run a node, not Core’s captured nodes, but BIP-110. Get your Bitcoin off exchanges. Don’t use any captured hardware wallets. Use, for example, Seedsigner.
-
Luke Dashjr reposted
Star Heartsong · $ASST ALL-IN⛳ · WAGMI 😜🏆✝️🔥🕊️
@DrStarHeartsong
A vote for BIP-110 is a vote for the health of small node runners, which is key to securing the decentralization of the Bitcoin network.
-
Luke Dashjr reposted
boozy | XBT
@TheBoozles
Miner fees were never an issue. Compare spam vs monetary transaction value.
-
Luke Dashjr reposted
TORONTO HODL 🍁
@EnjoyingBitcoin
A BIP-110 in hand is better than innumerable non-existent mythical spam-solutions in the bush.
-
Luke Dashjr reposted
Knut Svanholm ∞/21M
@knutsvanholm
No revolution is more peaceful than a User Activated Soft Fork
-
Michael Saylor
@saylor
Companies enable people to organize under law around a shared mission with greater efficiency, transparency, creditworthiness, scale, resilience, and continuity.
For Bitcoin to succeed as a global monetary network, corporate adoption is necessary, inevitable, and welcome.
Luke Dashjr
@LukeDashjr
No node, no keys = not adoption
-
Luke Dashjr reposted
hodlonaut
@hodlonaut
Grifters and suitcoiners oppose BIP-110.
Plebs with integrity support BIP-110.
There are exceptions, but the pattern is extremely obvious. -
Luke Dashjr reposted
Fully Noded - Dev
@Fonta1n3
I trusted Bitcoin Core to do the right thing, I viewed Core as rigid and extremely difficult to change, if it did change I assumed it would be in a conservative careful incremental balanced approach.
That trust has been broken and will never return.
This is good for bitcoin. -
Luke Dashjr reposted
Fully Noded - Dev
@Fonta1n3
Controlling your private keys is only half the self custody battle.
You need to run a node and verify ownership of the UTXOs those private keys can sign for, otherwise you are trusting a third party aka “pissing in the wind”.
Often times wallets will say they are “self custodial” but in reality you are trusting them to verify your UTXOs for you and in doing so losing any and all privacy.
That is not self custody IMHO, @FullyNoded fixes this. -
Luke Dashjr reposted
Liberty NH 🦔🌲
@NHpilled
The irony of this is that spammers are why nodes are so expensive now.
-
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
29.3.knots20260508 is the only supported version of Knots, and includes full RDTS support
-
Luke Dashjr reposted
Fully Noded - Dev
@Fonta1n3
Imagine FUDing bip110 as cEnSoRShip while actively censoring comments and conversations on the repo. Wild.
-
Luke Dashjr reposted
XBT | Hardfork cguida | ⚡🪢
@cguida6
@BitcoinKnots has a cool method of maintaining a fork of bitcoind that anyone can learn!
Kyle 🐆
@kwsantiago
Help shape your Bitcoin node:
- write a fix or feature for the node you run
- Knots isn't merged, each release is assembled from a curated set of PRs
- open a PR, get it reviewed, and it ships to everyone running Knots
The process, demystified 👇
github.com/chrisguida/knots-assembly/pull/2 -
Luke Dashjr reposted
444SmittyJ
@444SmittyJ
I’m running BIP 110, as of yesterday. Fighting for my sovereignty. Thank you @mattkratter @GrassFedBitcoin @DrJackKruse @knutsvanholm @TomerStrolight @LukeDashjr
This media couldn't be displayed. See it on the original post. -
Post not available here, view on X
Luke Dashjr
@LukeDashjr
29.3.knots20260508 is the only supported version of Knots, and includes full RDTS support
-
Luke Dashjr reposted
Fully Noded - Dev
@Fonta1n3
OP_IF is the real enemy…
Far more damaging than OP_RETURN.
I love taproot, I love miniscript, I am actively building on it. I do not need OP_IF, it needs to be removed.
This is why BIP110 is appealing. -
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
Doing anything other than signaling BIP110 is stupid and suicidal for miners.
-
Post not available here, view on XPost not available here, view on X
Luke Dashjr
@LukeDashjr
Doing anything other than signaling BIP110 is stupid and suicidal for miners.
-
Luke Dashjr reposted
Dathon Ohm / BIP-110
@dathon_ohm
Yes. Fortunately, there is a way to express opposition to BIP-110, and that is to counter-softfork. Since there have been no such efforts, we can assume that opposition to BIP-110 is negligible.
-
Luke Dashjr reposted
boozy | XBT
@TheBoozles
Almost the weekend! Time to update your node(s) for the BIP-110 softfork! github.com/bitcoinknots/bitcoin/releases
-
Luke Dashjr reposted
XBT | Hardfork cguida | ⚡🪢
@cguida6
"bitcoin core must approve all consensus changes"
>concessions
What concessions? They don't want any fork. There is no way to concede and still fork. Core has not even come to the table
Waiting for core to come to the table means waiting for bitcoin to die -
Luke Dashjr reposted
ꓘɨℓσꬺƄℓɑꓘҽ2ƄꓘɳσŦƨ \\ BTC = XBT
@Kilombino_
If #bip110 fails, there's nothing stopping Core from releasing a new version, all the miners signaling it, and then having demurrage, fewer halvings, or more than 21 million.
And you being happy owning nothing. -
Luke Dashjr reposted
-
Luke Dashjr reposted
Arthur van Pelt 🔥 ∞/21M ⚡
@Arthur_van_Pelt
#neverforget
April 2025: PR #32359 on Github is the controversial Bitcoin Core pull request that proposed removing the default OP_RETURN data carrier limit. Luke Dashjr & Mechanic are muted.
It received 423 👎 vs 105 👍. It was merged June 2025 anyway.
BIP110 is a no-brainer. -
Luke Dashjr reposted
Delcin #XBT
@DelcinMaria
Reason why BIP110 was proposed is because Bitcoin core30 with this controversial change gained significant adoption.
Jason Hughes
@wk057
Bitcoin Core developers are about to merge a change that turns Bitcoin into a worthless altcoin, and no one seems to care to do anything about it.
I've voiced objections, lost sleep over this, and despite clear community rejection of the PR it's moving.
github.com/bitcoin/bitcoin/pull/32359 -
Luke Dashjr reposted
Joshatoshi
@joshatoshi
Here’s a more accurate view of consensus (with filters). I’ve removed everyone under 12, who doesn’t own any Bitcoin, and doesn’t run a node.
Anyone getting tired of winning yet? -
Luke Dashjr reposted
boozy | XBT
@TheBoozles
Run the latest version of Knots with BIP-110...This isn't funny anymore!
Efe #BIP-110
Satoshi: "Messages should not be recorded in the blockchain".
@bitcoincoreorg: -
Luke Dashjr reposted
The Bitcoin Commons
@BTC_commons
Every Bitcoiner on the Epstein emails is against BIP110.
Think about it. Put that thing down, sit, and think about it.
I REPEAT. Every Bitcoiner on the Epstein emails is against BIP110.
.
@GrassFedBitcoin
Badly worded. Of all the Bitcoiner names that show up in the files (Blue Matt, Michael Saylor, Greg Max, Austin Hill, Kanzure, Jeremy Ruben, Andy Back) every single one of them has made public comments against BIP110.
-
Luke Dashjr reposted
Odin | BIP-110
@LegitSatStacker
It's even worse than that, if BIP-110 fails the spirit of the most hardcore bitcoin maxis on earth dies with it.
People have no clue what's actually on the line here - if 20% of the network can be ignored like this, it's literally over for bitcoins decentralization. -
Luke Dashjr reposted
Donal
@DonalDevine
If BIP-110 fails, Core will have carte blanche to do whatever it wants, including changing the issuance schedule and supply cap.
-
Luke Dashjr reposted
Bitcoin Ideal Money
@BryanBSolstin
Run Bitcoin Knots 29.3
Arbitrary data is a vector for spam, ordinals and child porn. When BIP-110 activates, your node will reject entire blocks that carry it.
Ideal money, not a landfill.
“Nodes accept the block only if all transactions in it are valid and not already spent.”
Luke Dashjr
@LukeDashjr
BIP 110 does not have a "no activation" code path.
It activates no matter what -
Post not available here, view on X
Luke Dashjr
@LukeDashjr
BIP 110 does not have a "no activation" code path.
It activates no matter what -
Luke Dashjr reposted
Brad Wesley
@wesleybrad060
Bitcoin needs a Fitness Plan.
Run Knots, Signal for BIP-110.
Stop Being a FATTY. -
Luke Dashjr reposted
Bitcoin Quokka
@btcquokka
Notice many BIP110 supporters have a large family and / or a faith… and the vitriol against BIP110 comes from single loners who dabble in fiat games.
There are no coincidences. -
Luke Dashjr reposted
hodlonaut
@hodlonaut
«BIP-110 is the result of the Bitcoin Core Fauci-like "experts" doing something very iatrogenic indeed--
Instead of just being "janitors" and keeping the protocol clean and healthy-
The inner circle of Bitcoin Core devs decided to push through a very controversial and unnecessary change that virtually no one on planet Earth wanted:
They blew open op return from 80 bytes to 100,000 bytes»
Matthew R. Kratter
@mattkratter
Michael Saylor Speaking Ex Cathedra (BIP-110)
This media couldn't be displayed. See it on the original post. -
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
Core has had several opportunities to save face.
For example, they could have embraced RDTS and tried to spin it as "see we were right about policy not being good enough, consensus changes are the right way" -
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
Longest *valid* chain.
Bailey is revealing he's a Bcasher. "Longest chain" are their words. -
Crypto Tea
@Cryptotea
3 years of clowns lying and gaslighting me, telling me my personal computer running a bitcoin node should store their JPEGs for free
BIP 110 is doing gods workPost not available here, view on X
Crypto Tea
@Cryptotea
The longest chain is actually the one Satoshi designed to prevent arbitrary data
there is an exploit in the code, no matter how much you try to hide it, gaslight and personally attack me
Luke Dashjr
@LukeDashjr
Longest *valid* chain.
Bailey is revealing he's a Bcasher. "Longest chain" are their words. -
Luke Dashjr reposted
Crypto Tea
@Cryptotea
The longest chain is actually the one Satoshi designed to prevent arbitrary data
there is an exploit in the code, no matter how much you try to hide it, gaslight and personally attack me -
Luke Dashjr reposted
.
@GrassFedBitcoin
Big Bitcoin doesn't want you running a node or taking direct control over your money.
OCEAN gives you a 50% discount on fees if you do.
There are a few good business that push their users to act in a way that improves decentralization, they deserve to be celebrated for it. -
Luke Dashjr reposted
Crypto Tea
@Cryptotea
3 years of clowns lying and gaslighting me, telling me my personal computer running a bitcoin node should store their JPEGs for free
BIP 110 is doing gods work -
Luke Dashjr reposted
.
@GrassFedBitcoin
Template construction is well on the way to becoming decentralized.
BIP110 is required for this to have any significance.
Miner-side template construction is irrelevant if we're centralized at the node level. -
Luke Dashjr reposted
Masunobom 🪢 #BIP-110
@masunobom
That BIP110 does not have majority support is a demoralization psyop.
Wherever you read the comments, X or YouTube, BIP110 has overwhelming support.
The system that captured Core and Bitcoin was dragged out of the shadows for everyone to see. -
Luke Dashjr reposted
anonymous
@anonymo02031848
You need to come onboard with bip110 really quick, or loose credibility. Saylor is done. Adam back is done. Core is done. A money network doesn’t need features like spam
-
Luke Dashjr reposted
Joshatoshi
@joshatoshi
What @LukeDashjr is warning us of is a Ledger Poisoning Attack zero day and the real possibility an attacker uses CSAM to create a “radioactive ledger”. Do we give the attacker an approved lane, pretend it doesn’t exist, or patch it before it becomes a problem?
Using a fee market alone to prevent something like this doesn’t work in a fiat world. A state-sponsored attacker has unlimited ammunition because they can just print the “bullets”! It also doesn’t have to be a government, because anyone can launch this attack if they pay the fee.
Will some edge case Bitcoin applications break as a result? Most likely. Is it worth it to make Bitcoin more resistant to this type of attack. I’d say absolutely. If nothing else than from a moral perspective. If archival node runners have even the slightest moral reservations about running their node, then the attack was successful. And if an attack like this were successful, it would forever make Bitcoin more centralized. Once it’s inscribed, it can’t be deleted, only pruned.
Can attackers fake UTXOs and fragment the data? Sure, it just makes the attack much harder. You can never 100% prevent an attack, you just have to make it hard enough so it’s not worth the attacker’s time and effort, and they move on to an easier target. As things stand right now, “developer creep” has given the attacker a variety paths they can take to easily launch such an attack on Bitcoin, and even do so at a discount.
The proposals in BIP-110 are specifically designed to patch this threat.
Does it mean development on Bitcoin comes to an end? I’d argue that the dawn of Bitcoin development is just beginning. A 12-month patch gives us time to “stop the bleeding” but also introduce some creative spam reduction logic. Such as having any proofs solve a cryptographic math problem to prove they are being used for legitimate purposes, as opposed to being a JPEG (sort of like a captcha).
While I believe this change would be good for Bitcoin as it globally defines Bitcoin the protocol as “digital gold” and “digital money”. Preventing this attack vector appears to be the primary concern.
Do we want Bitcoin to be something we can pass down to our children in good conscience? Or have it be something only a few corporations are willing to run and maintain? -
Luke Dashjr reposted
Lori Singer Meyer
@Loriss65
And Mow reveals that he too, is captured. What a surprise (not). Back was added as a consultant to JAN3 soon after the company was started. That, my friends, is called a tell.
hodlonaut
@hodlonaut
@Excellion you retweeted this.
It’s hard to read that in any other way than you sharing Adam’s position that Core governance is fine and that the problem is that people are too stupid to understand decentralized engineering and «IETF rough consensus»…
For this to be true, my CAPTURE articles would have to be what Adam has been so desperste to smear them as: «AI conspiracy slop».
Is that your position? -
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
The requirement for consensus is necessarily at a conceptual level, not a technical nuance. If it was a technical matter, it would be impossible to softfork ever, since nobody would be running the code before it is written.
At a conceptual level, all nodes enforced the BIP110 rules until late 2025, and a supermajority still do today.
The requirement for consensus is also not absolute. Very few softforks in Bitcoin's history have had true consensus. P2SH was a big battle. Segwit saw 20% of the community leave over it. Taproot saw Core abuse their position to nearly conflict on activation method.
Generally, "objections" that are ill founded or sufficiently addressed do not impede moving forward.
Before BIP110 was proposed, there were zero objections to the ideas put into it, and there are still no sound objections to BIP110 to date.
At a technical level, softforks do not require consensus, only significant support and less opposition. To date, there is essentially zero opposition at the technical level. Not a single node is running a URSF.
Conceptually, Segwit had ~80% network support, and ~5.2% actually enforcing. Bcash (the anti-Segwit URSF) launched with ~2.5%.
BIP110 for comparison today has ~80% network support, and ~15% actually enforcing. And again, zero visible URSF nodes. -
Post not available here, view on X
Luke Dashjr
@LukeDashjr
The requirement for consensus is necessarily at a conceptual level, not a technical nuance. If it was a technical matter, it would be impossible to softfork ever, since nobody would be running the code before it is written.
At a conceptual level, all nodes enforced the BIP110 rules until late 2025, and a supermajority still do today.
The requirement for consensus is also not absolute. Very few softforks in Bitcoin's history have had true consensus. P2SH was a big battle. Segwit saw 20% of the community leave over it. Taproot saw Core abuse their position to nearly conflict on activation method.
Generally, "objections" that are ill founded or sufficiently addressed do not impede moving forward.
Before BIP110 was proposed, there were zero objections to the ideas put into it, and there are still no sound objections to BIP110 to date.
At a technical level, softforks do not require consensus, only significant support and less opposition. To date, there is essentially zero opposition at the technical level. Not a single node is running a URSF.
Conceptually, Segwit had ~80% network support, and ~5.2% actually enforcing. Bcash (the anti-Segwit URSF) launched with ~2.5%.
BIP110 for comparison today has ~80% network support, and ~15% actually enforcing. And again, zero visible URSF nodes. -
Luke Dashjr reposted
Kretch🐸 b2b xbt bitcoin
@kretchino
If you don't run a URSF node, you're not opposed to bip-110🤗
-
Luke Dashjr reposted
Dathon Ohm / BIP-110
@dathon_ohm
This isn't said often, but the developers work for the node operators. Our current developers seem to have forgotten this.
-
Luke Dashjr reposted
Joshatoshi
@joshatoshi
Bitcoin has operated under the rules proposed by BIP-110 for 14 years. Don’t let anyone try to convince you that it’s a new change. This is reverting back to how things used to be, before a few Bitcoin Core “devs” rammed through some iatrogenic changes.
-
Luke Dashjr reposted
SpectrGen // XBT
@SpectrGen
It’s all fun and games until you try to force node runners to store and relay CSAM.
Pretty perverse to claim the high ground when that’s effectively your position — unless you mean you’re well-positioned to destroy his reputation. Spoiler: you aren’t. -
Luke Dashjr reposted
Robin Seyr
@RobinSeyr
What is your stance on Core vs. Knots? And BIP110?
Robin Seyr
@RobinSeyr
Bitcoin Core Is Actively Sabotaging Bitcoin!
⇒ BIP-110
⇒ Core Vs. Knots
⇒ What Will Happen in August
@GrassFedBitcoin on the Civil War in BTCThis media couldn't be displayed. See it on the original post. -
Luke Dashjr reposted
ab ☁️
@antbit
Opponents of BIP-110 had months to build a substantive URSF. Instead, all we got was noise, complaints, and threats to fork off.
We’re now weeks from mandatory signaling at block 961632. If 55% of miners signal, BIP-110 locks in early. If not, enforcing nodes reject every non-signaling block until it locks in anyway. Miner cooperation is optional, lock-in is not.
Critics have only grown louder in their complaints and predictions of failure, yet they still haven’t offered a viable alternative or constructive path forward.
This is how we defend Bitcoin's original purpose as sound money. -
Luke Dashjr reposted
Adam Simecka
@AdamSimecka
Why have there only been anti-BIP110 people in the Epstein files so far?
-
Luke Dashjr reposted
Shaun
@theDAHTcom
🏡 My neighborhood has been having a lot of burglaries. 😢
It used to be a safe place to live and raise a family. That is why I moved here in the first place. I left the city apartment because theft was becoming normalized there, everything was broken, and crime kept inflating while my hope for the future kept shrinking.
Now that my new home might be in danger, I lock the windows, add another deadbolt, and keep a firearm for self-defense. Simple deterrents.
On October 10th, the HOA security guard knocks on my door.
He tells me that determined burglars will find a way inside no matter what I do. Organized gangs can bring more manpower, better tools, and more force than any homeowner could reasonably stop.
Then he explains the new policy for the community:
“If someone is determined enough, they will get in anyway. That is why our new default policy is for every home on the block to leave its garage door open.”
Wait, WHAT?!
I push back. Surely there wasn't consensus around this new absurd policy.
He assures me the policy was endorsed by the neighborhood’s oldest locksmith and its largest landlord.
That locksmith? He never misses a chance to remind everyone that he helped invent modern locks, so apparently his judgment cannot be questioned, even when his associations with Epstein and a certain island raise questions of their own that go unanswered.
That landlord? He sighs, and says owning more homes than anyone else proves he cares more about the neighborhood than the rest of us. He leaves out that the homes are heavily leveraged, the financing products for them that he promoted are severly underwater harming millions, and that he has already started selling those properties he once called pristine assets.
But I am told not to worry.
“The experts have spoken.”
The guard explains that an open garage gives burglars a safer place to go, away from the living space, without destroying my home or injuring anyone inside.
Sure, they may steal my tools. Maybe they set up camp, light a fire to stay warm, abuse children, or use it as a cartel drug running drop point. But hopefully they stop there and do not break into the rest of the house.
Nope.
I tell him to "get the fork off my property or find out"
That is essentially the pro data storage argument for blowing OP_RETURN wide open.
Because spammers may find another method anyway, we should give them an easier, preferred place to do it and hope they do not do something worse.
Imagine when I invite others into the neighborhood or try to sell my home, I am expected to explain that vagrants, criminals, or worse have taken up residence in my open garage, and somehow assume that the home still has any value.
But not to worry. The garage is the preferred space for non residential and criminal use. I can just ignore them and prune them from my view by using the side entrance for the time being.
No! No quarter for those who wish me, my home, or my protocol harm.
Oh, and that security guard? I couldn't help but notice the nametag on his uniform:
“PaulBlart.eth” -
Luke Dashjr reposted
spoon
@spoonmvn
I don’t follow Luke.
I think most of the perspectives out there on him are the knee jerk reactions of midwits.
He’s a good man, in a world that is lacking in that department.
But I don’t follow him.
I hired him.
I hired him because he’s the most qualified for the job that became available when Core ignored their responsibilites.
That job? Developing and maintaining the code I run on my node.
So Luke works for me now, as he does for the thousands of others who have downloaded Knots.
That’s Bitcoin. That’s how it works. You get to choose who you hire.
But you don’t get to choose who I hire. -
Luke Dashjr reposted
Dathon Ohm / BIP-110
@dathon_ohm
Since Bitcoin is decentralized, no one is in charge of defending Bitcoin, so the responsibility falls on each and every one of us.
Bitcoin's future as decentralized money depends on you.
So make this moment count. It's now or never. -
Luke Dashjr reposted
Dathon Ohm / BIP-110
@dathon_ohm
As the BIP-110 movement gathers strength over the coming 23 days, these FUD attacks are going to intensify as opponents and fence-sitters start to buckle under the pressure. This means we are over the target.
Jason Hughes
@wk057
-
Luke Dashjr reposted
superpilotish
@superpilotish
For the Bitcoin influencers who say "I'm not for or against"
Whatever you're running on your node, that's what you're for
If you were running a node and shut it down, that's an abstention
If you've never had a node, you're just saying stuff🙄
@PupusasG @JoeyTweeets @francispouliot_ @Excellion @LukeDashjr -
Luke Dashjr reposted
Guy Swann
@TheGuySwann
Since i feel like we're all back together and I have decent connections to most opinions on this topic, I'm curious...
Do you support the BIP110 soft fork? -
Luke Dashjr reposted
Roughnecks
@Roughnecks110
We're self-interested miners. We have nothing to gain by attacking Bitcoin. Most of our savings are in Bitcoin
-
Luke Dashjr reposted
hodlonaut
@hodlonaut
Oh, just yet another smear post from Andy calling me a «Cyberbully» responsible for death threats.
Who else called me a Cyberbully? Oh, that’s right, Craig Wright, Calvin Ayre and their well funded propaganda apparatus.
Maybe Adam should do less lying libel and more answering of questions relating to mining operations and island visits? -
Luke Dashjr reposted
AuthintegXBT
@authintegx
Why are they fighting tooth and nail to stop BIP-110? It’s a very practical solution. It doesn’t harm the network and doesn’t freeze coins. What exactly is so dangerous about BIP-110? If you’re on the fence, think critically, and ask yourself "who are the bad actors?"
-
Luke Dashjr reposted
Bitcoin Ideal Money
@BryanBSolstin
Luke is correct. BIP-110 has broad consensus among node operators. In reality, there is no significant opposition to the soft fork.
Bram Kanstein
@bramk
come on, entertain it a bit.
And maybe make it clear to people following you. -
Luke Dashjr reposted
Jim
@elkrun21
I think the biggest mistake the anti-BIP110 gang make is that they actually think the pro-BIP110 gang support it because Luke and Mechanic do ... hah!
-
Luke Dashjr reposted
AuthintegXBT
@authintegx
I hate that BIP-110 opponents call it a hostile attack. NO. It's a defensive temp solution to a problem that we SEE that they DON'T. They don't see it because they are benefiting from the problem. Their ROI is fiat money or they want to see BTC self destruct.
-
Luke Dashjr reposted
-
Luke Dashjr reposted
Dathon Ohm / BIP-110
@dathon_ohm
With only 3536 blocks (~24 days) left until mandatory signaling begins, BIP-110 has never been stronger! We continue reaching new all-time highs on all metrics.
-
Luke Dashjr reposted
ndgo - SHA256 Maximalist
@ndgo1370
The fundamental problem core-tards have with BIP110 is that it works.
-
Luke Dashjr reposted
Justin Bechler
@1914ad
The most unscrupulous people in Bitcoin have been telling you for the last year that your node is irrelevant.
-
Luke Dashjr reposted
Neal Flesher
@NealFlesher
someone has to propose the addition of a rule to the protocol to break consensus with 110
like “if bit is flipped for 110, then invalid”
that’s what “coherence” of an opposing chain would mean
which is why people say URSF or stfu -
Luke Dashjr reposted
Jerry Gensler
@BAcct8
Why stop there? 😂
If the industry ignores the community on BIP-110, who’s to say they wont decide to get rid of private keys altogether and just use 4-digit PINs???
Support BIP-110 to send a message that you reject these changes by the Core devs before it’s too late! -
Luke Dashjr reposted
Liberty NH 🦔🌲
@NHpilled
Question for anti BIP-110ers, who controls the Bitcoin network? Which mechanism in the network controls the rules such as 21 million, block reward amounts etc.? If it is the miners, BTC is trouble.
If it's the nodes, what % of nodes need to signal for a viable UASF in your view? -
Luke Dashjr reposted
Justin Bechler
@1914ad
✅ 2025: doing this at the consensus layer is the only path forward
❗️2026: doing this at the consensus layer is an attack on Bitcoin
The moment BIP-110 was released, we set the precedent that we no longer seek nor require consensus with bad actors. -
Luke Dashjr reposted
Masunobom 🪢 #BIP-110
@masunobom
The only way to attack Bitcoin is to slowly degrade the network by using it to store arbitrary data on the people’s nodes.
Forcing the nodes to store CSAM will be a definite blow to decentralization and to Bitcoin.
BIP110 is about stopping this degradation process.
₿itcoin ₿ombadil
@BitcoinBombadil
Here’s what you and Claude and too many others miss….
Instead of attacking with a double spend attempt (too obvious)… they’re introducing slow poison to the Network (Spam, more subtle/ambiguous)
Claude doesn’t understand how centralized Bitcoin Block Templates are with the Big 5 Mining Pools…
The Block Cartel represents a subtle 51%+attack on Bitcoin -
Luke Dashjr reposted
Va♰oshi
@Vatoshi
BIP30修复了交易 ID(txid)重复滥用的问题,收紧了共识规则。没有用户明确“投票”支持,但 Core 直接做了。
BIP90改变了 Core 对旧软分叉的执行方式,把它们“埋”在固定高度。没有用户信号,也直接实施了。
BIP148强制激活 SegWit,当时也没有完整共识,但支持者认为“因为 SegWit 本身有广泛支持,所以可以强推”。
现在有人用“没共识 = 攻击”来反对 BIP110,但历史上 Core 自己喜欢的目标变更时,从来没这么严格要求过共识。
“没共识就是攻击”不是比特币一贯的原则,而是选择性执法——Core 喜欢的目标就叫“必要维护”,用户想减少垃圾数据就叫“攻击”。这是虚伪的。
SpectrGen // XBT
@SpectrGen
Also, the claim that “no consensus = attack” collapses on Bitcoin’s own history.
BIP30 tightened consensus to stop duplicate txid abuse. BIP90 changed how Core enforces old soft forks by burying them at fixed heights. These were consensus changes. Users did not explicitly signal for them.
If explicit user signaling is mandatory for consensus changes, those should have required it too. They didn’t, because Core treated them as “necessary protocol maintenance”.
So the objection to BIP110 is not a timeless network principle. It is selective legitimacy. Consensus changes are fine when Core likes the goal, but “attacks” when users try to reduce arbitrary data.
Hypocrisy. -
Luke Dashjr reposted
₿randon
@BitcoinSith
I'm pretty sure BIP110 activiation is going to be a max pain scenario for all: It intially fails to get majority miner support and appears to be dead on arrival but still moves forward with getting a few blocks mined.
It looks like it failed. Most people sell their BIP-110 coins when they eventually get listed on small exchanges. Months later someone actually puts illegal content in a block on the legacy chain or there is some other major issue b/c of SPAM on the chain.
Hashpower switches immediately to BIP-110 and everyone then realizes holding legacy Bitcoin is doomed and it goes effectively to zero as we get closer to BIP-110 wiping out the legacy chain. -
Luke Dashjr reposted
Bitcoin pleb
@mcchiperson77
@GrassFedBitcoin @LukeDashjr @mattkratter I have a question. And it's in earnest, because I'm trying to do my due diligence. Which is fucking hard, because I'm not technical and not a dev.
If bitcoin should only be used as money, why do bip 110 data limits expire after a year? Why not keep them forever? -
Luke Dashjr
@LukeDashjr
OCEAN remains only a coordinator - but a coordinator that protects BIP110-ready Bitcoin miners from the consequences of other miners’ failure to upgrade.
After BIP110 activation, miners who do not upgrade will make invalid blocks and not be rewarded in blocks mined by BIP110-ready miners (only in invalid blocks that have no value).
OCEAN’s split handling means they bear that risk themselves, not by diluting miners who enforce Bitcoin’s rules.
Ian A. Northon
@Bitcoin_Lawyer
-
Luke Dashjr reposted
Bram Kanstein
@bramk
Pro BIP110 argument that I like
-
Luke Dashjr reposted
XBT | Hardfork cguida | ⚡🪢
@cguida6
Need to get something off my chest about something that happened a couple weeks back with the original version of this bip110 merchant list
The list caused a bit of a stir due to having incorrect information and was quickly updated to remove the questionable entries, and after just two days there was only fully verifiable information on the list and I fully vouch for the current version
The old, wrong version of the list was up for only a day or two, so i doubt much damage was caused, but the way the situation resolved doesn't sit right with me because bitcoiners are obligated to call out lies and bullshit when we see it, especially when it comes from us or people who are "on our side"
Accordingly, I am calling out myself and one other member of the "monetary maximalists" group for dishonesty during this brief episode
Originally there were a bunch of entries that said "planned". I was unsure what these meant, but I was assured that they were based on solid information
After becoming impatient and posting a screenshot of the list on my account, it slowly became clear that the "planned" section of the list had been more or less completely fabricated by one of the group members
He later apologized for making "errors" on the list, but the "errors" were so egregious that they could only have been complete fabrications
At first I tried to defend the list because I didn't want to have to delete a bunch of companies which would have made it look like bip110 was losing support, when really the support the entries represented were never real in the first place
I ended up leaving the list up much longer than was appropriate, and should have removed the "planned" entries as soon as their reliability was called into question
This whole thing is silly because the list of actual, verified entries is something we should be proud of. There are tons of pleb merchants supporting and running bip110, and the list keeps expanding every day. We don't need to lie in order to win, and honestly, if we did, then I wouldn't want us to win. The other side is the side that relies on gaslighting and bullshit. Bip110 will win because the truth is on our side
So I wanted to make this post to apologize to the bitcoiners who saw the old list before I deleted it, and especially any companies who felt like their views were misrepresented. For not vetting the list more closely before posting the screenshot, I'm sorry. For leaving the "planned" entries up after they had been proven untrustworthy, I'm sorry.
And to the person who made up the entries, you know who you are. I was hoping that you'd come forward and admit what you did, but since you haven't yet, I'm doing it for you. We will not win if we see dishonest behavior on our own side and don't call it out. Such behavior from the other side is why bitcoin is in this mess right now
Thanks to the anti-bip110ers who called out the list and helped me see it was not what it claimed to be, and thanks especially to the pro-bip110ers who urged me to take the screenshot down. In the end, I think it all worked out for the best, but I wanted to make this public statement to force myself to commit to a higher standard moving forward
Bip110 (and ultimately, bitcoin itself) is winning because we hold ourselves to higher standards
XBT | Hardfork cguida | ⚡🪢
@cguida6
Yeah that list was a mess, I deleted the screenshot
Here's a new post with just the ones we know are ready:
XBT | Hardfork cguida | ⚡🪢
@cguida6
Look at all these businesses and organizations that support bip110! 🔥🔥🔥
(This list is a work in progress):
v0-bitcoin-companies-table.vercel.app -
Luke Dashjr reposted
Camina Drummer Blake2b
@CaminaDrummer4
Policing data is how a network becomes permissionless, otherwise it falls to DDOS by censors.
Bitcoin Lebowski⚡
@DudeJLebowski
"policing data on a permissionless network is the solution?"
Bitcoin has always policed data on its permissionless network!
Rules, not rulers, remember - this means there has to be some rules.
Are you arguing for zero limitations on Bitcoin? -
Luke Dashjr reposted
.
@GrassFedBitcoin
Why I think many who are less optimistic about BIP110 than I am are mistaken -
The "Economic Node" concept.
This emerged as a way to dismiss obviously frivolous nodes that get spun up in an effort to astroturf forks within Bitcoin.
Very quickly during the fork wars people realized - "Hey, these nodes might not actually represent any real activity within the Bitcoin ecosystem, they're just there to warp the stats on node tracking websites and make something look like it has more support/opposition than it does."
I will point out that that is *not* what has happened with BIP110/Knots in general - those are real people which @start9labs can attest to, having sold millions of dollars worth of servers to people over the last couple of years who overwhelmingly bought them in order to run Knots. That is not fake and is corroborated through various imperfect heuristics.
However the point I want to make is that the most intimidating of economic nodes - i.e the ones run by mining behemoths like Antpool or exchanges like Coinbase - are not where anyone should look when attempting to gauge support for a soft fork - especially a controversial one. (At least not until very late in the day.)
These nodes obviously represent a huge on-chain footprint, but conversely, they are run by companies who will be the last to take a stand on anything controversial as it has the potential to create drama for them over a decision that isn't theirs to make anyway.
However the lesser economic nodes aren't concerned with that. They don't have legal/PR depts or shareholders who need to sign off on these things (or who will sue them if they do something "reckless". They can just adopt a new client if they think it's good for Bitcoin.
When Bitcoin is in crisis mode with difficult decisions to make, the institutions are going to be the last to choose a direction and that is a *good* thing.
Ideally soft forks to start as grassroots movements, and while the nodes indicating support for them may not be run by billion dollar mining empires/exchanges, as long as they represent real Bitcoiners, the change will be coming from the correct place - from those least likely to be under duress unlike large industry players who necessarily always would be. -
Luke Dashjr reposted
Simple Steve 🌌
@SteveSimple
Economic odds are “economic” precisely because they respond to their customers desires
They’re followers, not leaders, in any kind of fork decision
.
@GrassFedBitcoin
Why I think many who are less optimistic about BIP110 than I am are mistaken -
The "Economic Node" concept.
This emerged as a way to dismiss obviously frivolous nodes that get spun up in an effort to astroturf forks within Bitcoin.
Very quickly during the fork wars people realized - "Hey, these nodes might not actually represent any real activity within the Bitcoin ecosystem, they're just there to warp the stats on node tracking websites and make something look like it has more support/opposition than it does."
I will point out that that is *not* what has happened with BIP110/Knots in general - those are real people which @start9labs can attest to, having sold millions of dollars worth of servers to people over the last couple of years who overwhelmingly bought them in order to run Knots. That is not fake and is corroborated through various imperfect heuristics.
However the point I want to make is that the most intimidating of economic nodes - i.e the ones run by mining behemoths like Antpool or exchanges like Coinbase - are not where anyone should look when attempting to gauge support for a soft fork - especially a controversial one. (At least not until very late in the day.)
These nodes obviously represent a huge on-chain footprint, but conversely, they are run by companies who will be the last to take a stand on anything controversial as it has the potential to create drama for them over a decision that isn't theirs to make anyway.
However the lesser economic nodes aren't concerned with that. They don't have legal/PR depts or shareholders who need to sign off on these things (or who will sue them if they do something "reckless". They can just adopt a new client if they think it's good for Bitcoin.
When Bitcoin is in crisis mode with difficult decisions to make, the institutions are going to be the last to choose a direction and that is a *good* thing.
Ideally soft forks to start as grassroots movements, and while the nodes indicating support for them may not be run by billion dollar mining empires/exchanges, as long as they represent real Bitcoiners, the change will be coming from the correct place - from those least likely to be under duress unlike large industry players who necessarily always would be. -
Luke Dashjr reposted
Simple Steve 🌌
@SteveSimple
I’ve had many people ask me to explain this tweet.
The key to understanding it imo is this:
The future rules are the current rules.
Luke is correctly pointing out that bitcoin consensus is defined not only by how it rejects blocks currently, but also how it will reject them in the future.
That’s why he uses the example of the block subsidy decrease. Your node runs a rule about how much this subsidy decreases in the future. You don’t update your node in the future to get that new rule, it’s already there.
The future schedule is the rule.
So start from that point and re-read it.
Luke Dashjr
@LukeDashjr
Removing rules is a hardfork.
That includes scheduled rules like subsidy halvings, and yes, even BIP110.
Rejecting BIP110 is a contentious hardfork attempt.
And unlike softforks, hardforks need consensus to succeed.
There is no consensus on rejecting BIP110. -
Luke Dashjr reposted
.
@GrassFedBitcoin
The company responsible for 25% of the nodes on the network runs BIP110.
Probably nothing!
Start9
@start9labs
Start9's company node, the one we use to sell servers and pay out employees, is Knots/BIP-110.
StartOS itself is completely and irrevocably neutral by design. We don't and wouldn't want to restrict anything -
Luke Dashjr reposted
Hunter Beast 🕯️
@cryptoquick
Here's a thought experiment:
110 activates.
All Core nodes produce blocks that are incompatible with the consensus chain.
All the miners capitulate within a day.
There is only one thing Core can do or they will literally never be relevant again: Merge 110, and release Core 32 on 10/10.
github.com/bitcoin/bitcoin/issues/35122
Also since y'all like gambling so much, here's a new thing to gamble on... @predyx_markets
Put me down for whatever $20 worth of sats get YES on "Core Devs merge BIP 110 by October 10th, 2026".
Hunter Beast 🕯️
@cryptoquick
Unfortunately, what's done is done and there is no going back.
The only thing Core can do at this point is merge 110. -
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
... and now they're fabricating quotes to slander me.
Notice the real context, parental consent to vaccines:
Luke Dashjr
@LukeDashjr
12 is borderline young adult.
The real problem is with trying to treat them as children... But that frankly goes even older than 18 nowadays -
Luke Dashjr
@LukeDashjr
Bad actors will do anything, lie about anything, to try to sabotage Bitcoin.
BIP110 is already deployed with its schedule. There is nothing Dathon, I, or anyone else can do to delay it.
Nor would it make sense to do so even if it were possible. Should have activated months ago
Flaming.hodl ₿
@flaming_hodl
I heard in a space recently someone said BIP-110 will be delayed by the main proponents (@dathon_ohm and @LukeDashjr ) because of lack of support. How can they misunderstand this movement that bad? There can't be a delay at this stage, it's locked in and ready for launch.
Luke Dashjr
@LukeDashjr
... and now they're fabricating quotes to slander me.
Notice the real context, parental consent to vaccines:
Luke Dashjr
@LukeDashjr
12 is borderline young adult.
The real problem is with trying to treat them as children... But that frankly goes even older than 18 nowadays -
Luke Dashjr reposted
.
@GrassFedBitcoin
I run
-
Luke Dashjr reposted
MarylandHODL (aka The Transition)
@MarylandHODL21
The plebs are taking a stand. We defend the network from extractors and expose malicious narratives before they can exploit the less informed. #bip110
This media couldn't be displayed. See it on the original post. -
Luke Dashjr
@LukeDashjr
Removing rules is a hardfork.
That includes scheduled rules like subsidy halvings, and yes, even BIP110.
Rejecting BIP110 is a contentious hardfork attempt.
And unlike softforks, hardforks need consensus to succeed.
There is no consensus on rejecting BIP110. -
Luke Dashjr reposted
Snapolino
@snapolino
5/Sep/2025 Bitcoin Core on brink of second bailout for spammers.
Luke Dashjr
@LukeDashjr
5/Sep/2025 Bitcoin Core on brink of second bailout for spammers.
-
Luke Dashjr reposted
SpectrGen // XBT
@SpectrGen
It’s a legal and ethical defense: stop full nodes from becoming forced image mirrors. Tiny non-renderable chunks need outside structural knowledge before rendering. Once that convention is standardized, it becomes trivial to filter in policy.
-
Luke Dashjr reposted
TORONTO HODL 🍁
@EnjoyingBitcoin
Them: Bitcoin is decentralized
Us: Oh? How?
Them: Well, anyone can mine it
Us: Yea, but 5 Miners control 80% of hash
Them: OK, but anyone can run a node
Us: I guess you're right - Bitcoin is decentralized
Them: Yea, but your node doesn't count 🤣 -
Luke Dashjr reposted
TORONTO HODL 🍁
@EnjoyingBitcoin
My node matters.
But, if it doesn't matter, the BIP-110 softfork will fail.
I will admit I was wrong.
I will admit Bitcoin is controlled by the influencers and rich and powerful - just like fiat.
I will sell my Bitcoin.
I will turn off my node.
I will buy the Nasdaq and Gold.
I will wish you luck with your centralized coin. -
Luke Dashjr reposted
Donal
@DonalDevine
It's no coincidence that the same people that went to Jeffrey Epstein's island are the same people that want to allow CSAM on the timechain.
-
Luke Dashjr reposted
₿itcoin ₿ombadil
@BitcoinBombadil
Dathon gave one logically coherent motivation for BIP-110.
But every BIP-110 supporter could probably give you their own motivation in their own words… and that’s an indicator of authentic decentralized consensus.
The slight variations in terminology and expressed motivations you see across the spectrum of BIP-110 supporters is indicative of their unique perspectives on Bitcoin as representatives of Bitcoin’s grassroots… like the laity of Bitcoin if you will.
The signal is that we all coalesced around the same Schelling Point in an E Pluribus Unum manner.
And if you know, you Knots + BIP-110 + DATUM + Ocean + Start9 + Self Custody + Study Austrian Econ + do all the other little things that go into being a positive contributor to the Bitcoin MONETARY Network.
Filters up!🛡️✊🏼🫡 -
Luke Dashjr reposted
FlyTheElephant ₿IP110+₿LAKE2b #BitcoinIsHope
@FlyTheElephant1
Yall better be running a bip110 node. Because this kinda shit is stuff that they are pushing through. They are tightening the noose and getting ready for wholesale confiscation.
Bitcoin Policy Institute
@bitcoinpolicy
Last night, the Bitcoin Policy Institute filed to intervene as a defendant in a New York lawsuit alleging that self-custodied bitcoin held for more than five years can be claimed by anyone who simply downloads your public address under New York’s Lost and Found Property law.
Our intervention serves to protect BPI's bitcoin, which we hold long-term like so many other bitcoin HODLers.
Rachel Rodman and Prat Vallabhaneni of White & Case are representing BPI.
We will keep you updated as the case progresses. -
Luke Dashjr reposted
Singekino_Miner (Datum miner)
@Singekino_Miner
At least 17% of total btc users prefer BIP-110 as they think it gives them many more advantages (no legal risk, no hardware burden, only monetary usage) than otherwise.
The rest of users are ready to accept BIP-110 chain if btc splits and BIP-110 chain gets longer.
No effective resist (URSF) at all by now. -
Luke Dashjr reposted
Asanoha | Timechain Art Magazine
@asanoha_gold
Knots 29.3 is currently the #1 most popular Bitcoin client version.
I have seen zero evidence or proof of Sybil Knots nodes, have you? -
Luke Dashjr reposted
₿itcoin ₿ombadil
@BitcoinBombadil
All Spam/File Storage on Bitcoin is an existential threat.
Some poses a gradual risk (Christmas Tree JPEG bloat)
Some poses a suddenly risk (CSAM)
Regardless, BIP-110 is necessary course correction toward fulfilling Bitcoin’s objective monetary purpose
Luke Dashjr
@LukeDashjr
It's not existential because of the spam threat.
We could fight that in policy over time.
It's existential because of the CSAM threat that Core30 just created last October.
It only takes one incident and it's over for Bitcoin.
And we know someone is just waiting for Core30 to prevail before doing it - we saw them exactly testing this playbook on BSV some years ago.
It's also existential because if miners can overrule the users, it means Bitcoin is not decentralised. That it's just another CBDC scamcoin. That's worse than fiat. -
Luke Dashjr reposted
SpectrGen // XBT
@SpectrGen
Michael Saylor discussed his new vision for Bitcoin at the Xapo Bank conference. It goes something like this:
———
Layer 1 is Bitcoin as “digital capital”: the scarce base asset, like digital gold or prime reserve property.
Layer 2 is “digital credit”: Bitcoin-backed fixed-income or preferred-share instruments, like STRC.
Layer 3 is “digital money”: dollar-pegged instruments that can earn yield through the credit layer.
———
Bitcoin as “perfect money” no longer fits his narrative.
Michael Saylor
@saylor
I joined @kornelijalaura at the @xapobankapp Conference in London on July 1 for a fireside chat on Bitcoin as Digital Capital, the emergence of Digital Credit, and the path to Bitcoin-backed Digital Money.
Fix the money, fix the world. $BTC
00:42 — Bitcoin below $60K and the mission: “Fix the money, fix the world”
01:27 — Bitcoin as the dominant Digital Capital network and the next great digital transformation
02:55 — Bitcoin Dominance approaching 69–70% and why “the flippening” debate is over
04:21 — The next layers: Digital Credit and Digital Money built on Bitcoin
06:56 — Strategy as an institutional gateway: attracting $64–65B into Bitcoin across equity, derivatives, credit, and money markets
12:28 — $STRC: bitcoin-backed preferred equity designed to create asset-backed Digital Credit
15:33 — The $STRC breakthrough: potential tax-deferred credit dividends backed by unrealized Bitcoin gains
18:18 — Digital Credit on Digital Capital: the killer app of a $50B bitcoin-backed balance sheet
19:48 — Digital Money: zero-volatility, fiat-pegged, yield-bearing bitcoin-backed assets
22:32 — Stress testing $STRC through deeper Bitcoin drawdowns
25:51 — $STRC vs. Bitcoin in the bear market: stripping ~90% of Bitcoin’s downside volatility
27:04 — Transparent Digital Credit: modeling risk from Bitcoin price and volatility every 15 seconds
30:34 — The builder roadmap: “If you want to make money, make the money”
32:27 — $STRC, $SATA, and the credit layer behind bitcoin-backed Digital Money
36:20 — Wrapping Digital Money as accounts, funds, public products, or tokens
41:27 — Creating Digital Credit on Digital Capital, then Digital Money on Digital Credit
43:00 — 2026 headwinds: geopolitics, the Fed, AI capital rotation, and digital asset regulation
44:54 — Potential catalysts: $STRC returning to par, Digital Credit reaccelerating, and capital flowing back to Digital Capital
46:01 — Why current market conditions may be a strong entry point for Digital Money buildersThis media couldn't be displayed. See it on the original post. -
Post not available here, view on XPost not available here, view on X
Luke Dashjr
@LukeDashjr
It's not existential because of the spam threat.
We could fight that in policy over time.
It's existential because of the CSAM threat that Core30 just created last October.
It only takes one incident and it's over for Bitcoin.
And we know someone is just waiting for Core30 to prevail before doing it - we saw them exactly testing this playbook on BSV some years ago.
It's also existential because if miners can overrule the users, it means Bitcoin is not decentralised. That it's just another CBDC scamcoin. That's worse than fiat. -
Luke Dashjr reposted
Keysa
@SimplestBTCBook
Ponder this: If BIP110 was a nothing burger, why are Back, Saylor AND Bailey wasting so much time on Twitter fighting it?
What are they so scared of?
A temporary soft fork designed to provide a breather for bitcoiners to consider better spam mitigation, what is so terrifying? -
Luke Dashjr reposted
BTCbello #BIP-110
@Bitbello
Bitcoiners are presented with the greatest opportunity to show the world that even the largest holder of BTC has no power over the protocol & node runners. Bullish.
Michael Saylor
@saylor
There are 110 things more dangerous to Bitcoin than spam.
BIP 110 turns a spam dispute into a consensus change that would invalidate some currently valid, fee-paying transactions.
That precedent is the danger. We should save our energy for threats that really matter. $BTC
Adam Back
@adam3us
On the filter fork topic.
I don't usually have time, but this morning listened to one of the twitter spaces from earlier in the week, with some well meaning relative bitcoin newcomers, that humanized them, and their concerns and thoughts for why they thought that made it logical to support 110.
My feeling after listening, is if these are the people with #110 in their handles, I'm sad to see them about to fork off and get disillusioned without understanding why bitcoin rejected 110 robustly.
So here's a more empathetic, constructive higher level version of explaining why not. I hope it's high-level and first-principles enough that everyone can follow.
They seem to want to understand what makes people tick, and are suspicious of intent. So, if someone asked me why is Bitcoin important and what is it, I'd say my (personal) mission and hope for bitcoin is to build the cypherpunk future, that "Snow Crash" was a blueprint, and work backwards from there. Bitcoin I hope leads to fully free markets via bearer unseizable, hard mathematically dependable money. Not everyone is comfortable with that level of freedom, but that's my view. And at this point, I believe that surprisingly, even now many governments have come to understand and value bitcoin's gold-like mathematical assurance, a positive development. Others may have milder views than myself, but still like hard censorship resistant money.
Because of motive suspicion, if it's not obvious: I hate spam with a passion, that's how I came to design hashcash while researching decentralized bearer money with others, and running nodes in privacy related cypherpunk p2p networks nearly three decades ago.
People seem upset about the default op return policy change in bitcoin. I will just assert, there are extremely robust and simple reasons for bitcoin changing default relay policy, and most just didn't do their research, so don't know what those are, or maybe not technical enough to fully understand though there have been 1000s of posts trying to explain in various simplified ways. So that lack of understanding lends itself to shared build-up of false narratives. So here's my back-to-basics higher level explanation.
The decentralization needed to create cypherpunk money has implications a: side effect of decentralization is that you can't impose your views on others. The very decentralization mechanism that helps that, is working against what BIP 110 wants, which at it's most basic is a quest to police other people. I understand supporters don't see their intent like that, but introspect deeper.
You can modify your software, but not anyone else's. Another critical and incredibly robust technical bitcoin immune system is bitcoin can't have people who don't understand technology basics insist on eroding security, decentralization robustness and core properties. That would end badly, fast, and so people will fight you on that.
So the message is Bitcoin respectfully says "no" to what you want. Sorry, and bitcoiners do genuinely understand and empathize that you mean well, have high level thoughts that make emotional sense, and articulate sensible bitcoin-defensive high level ideas, but they are not grounded and without you seeing it, the way you propose to achieve your ideas, hard-conflict with free cypherpunk permissionless money.
My advice is to listen to more experienced people who understand the system and why it works the way it does, to whatever detail you want to understand the grounded reasons for why this is the implication of decentralization and cypherpunk money.
I guarantee you the developer and protocol ecosystem shares and exceeds your views on bearer hard money (and dislike of spam). You may not agree with individual developers choices, views, way of expressing themselves etc, BUT you also need to understand the IETF-like decentralized technical consensus process creates a protective change resistance, that is highly effective at protecting bitcoin mission. The implication of which is no developer can change anything without technical consensus from hundreds of other developers and protocol observers who are pedantic and extremely knowledgeable clever people who won't let any unaddressed technical question past. The protective change resistance is robust and decentralized in an amplifying way because of this technical consensus.
And the many highly technical mainline developers' cypherpunk mission mindsets are probably far more determined than you can even handle on clarity of understanding and views about freedoms on permissionless networks, as many of you are probably still subconsciously inured by the matrix, where they have transcended that, and grew up immersed in it decades ago. They think natively in this space, while you are just grappling with the surface. Many wont have internalized or have the experience to know how this internet physics works, where there is no policeman, no policy authority, just mathematics, free market and hard money. That has implications for your views also, unfortunately.
Now the tough pill, which is unfortunately true: If you won't listen to reason, educate yourself, learn, the same radical freedom applies to you: your permissionless recourse is to club together and create a fork. But bitcoin won't be joining it. (With respect and no sleight intended.)
Please rejoin bitcoin now, or later if you're not convinced and need to experience 110 forking off and fizzling for yourself to start that journey of introspecting and learning. It would be sad if bitcoin lost people disillusioned due to simple lack of understanding of what's going on there, we're all trying to defend bitcoin and keep it on mission. Including btw the 110 technical promoters, just they wandered off plot somehow.
Join the cypherpunks on bitcoin, come cypherpunk summer🌞 in a few weeks. -
Luke Dashjr reposted
XBT | Hardfork cguida | ⚡🪢
@cguida6
If bip110 doesn't activate, noderunners will be forced to distribute CSAM, this is a fact
This is like saying that you *don't* (typo in original) support rooves, but that you "definitely never have and never will support" forcing people to get rained on
XBT | Hardfork cguida | ⚡🪢
@cguida6
If bip110 doesn't activate, noderunners will be forced to distribute CSAM, this is a fact
This is like saying that you support rooves, but that you "definitely never have and never will support" forcing people to get rained on -
Luke Dashjr reposted
Camina Drummer Blake2b
@CaminaDrummer4
This is a replay of the block size war once again — with all the CEOs and influencers wanting to make Bitcoin shitty, and all the Bitcoiners opposing them.
-
Luke Dashjr reposted
Cato The Elder
@CatoTheElder17
The reform needed at Core to regain our trust would need to be the equivalent of dropping napalm.
Why is Bryan Bishop, of Epstein emails fame, still the moderator of the Bitcoin dev mailing list? Do you see how insane it is that he’s untouchable? -
Luke Dashjr
@LukeDashjr
Similarly, to advocate *rejecting* BIP110 is to advocate a chain split.
If you don't want a chain split, you want BIP110.
Luke Dashjr
@LukeDashjr
2X *is* splitting the chain. To advocate 2X is to advocate a chain split.
-
Luke Dashjr reposted
.
@GrassFedBitcoin
That robust rejection in full:
- no complaints on the mailing list
- accepting the BIP into the BIPs repo
- banning all discussion elsewhere within the Core github org
- banning reddit accounts that mention it - even if in a neutral capacity
- spreading constant lies "it confiscates UTXOs"/"they say it will stop all spam but it won't!"/"the nodes are all fake"
- insulting/shaming everyone who runs it
- never making a better suggestion -
Luke Dashjr reposted
Shaun
@theDAHTcom
Interesting timing.
For nearly a year, opponents of BIP-110 told everyone the movement was irrelevant. It had no support. It was over before it started. Nothing to worry about.
Meanwhile, they screamed at, insulted, and attacked Bitcoiners supporting a movement to defend Bitcoin’s use case as money.
Now, with activation only weeks away, what looks like a coordinated social media campaign has arrived.
Why now?
This debate was not hidden, sudden, or rushed. It has been conducted openly for about a year, across X Spaces, YouTube, Podcasts, Reddit (before overwhelming censorship), GitHub, and everywhere else Bitcoiners gather. There was no shortage of opportunities to debate the facts.
Taking this position a year ago would have meant defending it for a year. Answering questions. Facing interviews. Explaining the consequences. Something @mattkratter @GrassFedBitcoin @LukeDashjr @1914ad @PortlandHODL @brian_trollz and many others have been doing for a long time now.
Even former President Joe Biden, while holding the most powerful office in the world, struggled to avoid difficult interviews and questions indefinitely. @saylor is not the president. A sharp sigh and “this interview is over” might work once or twice, but not for an entire year.
Waiting until the final weeks makes this much easier. Deliver the instructed message, avoid sustained scrutiny, and hope reputation carries the argument until activation passes.
So again: Why now?
What is especially dishonest is reframing BIP-110 as some sudden attempt to change consensus, rather than a response to a contentious change made by Core developers after ignored objections from many Bitcoiners.
Now that dismissing the movement did not kill it, the messaging has shifted to confusion and fear. Chain splits. Censorship. Dangerous precedent. Hostile takeover.
Fear works. That is why it is being mass deployed now in coordination.
I don't claim to know how it will end up a couple months from now. But now I wonder... who will they resurrect next to defend Core’s control over the reference implementation?
SBF?
BitBoy?
tl;dr
It’s too late.
Michael Saylor
@saylor
There are 110 things more dangerous to Bitcoin than spam.
BIP 110 turns a spam dispute into a consensus change that would invalidate some currently valid, fee-paying transactions.
That precedent is the danger. We should save our energy for threats that really matter. $BTC
Adam Back
@adam3us
On the filter fork topic.
I don't usually have time, but this morning listened to one of the twitter spaces from earlier in the week, with some well meaning relative bitcoin newcomers, that humanized them, and their concerns and thoughts for why they thought that made it logical to support 110.
My feeling after listening, is if these are the people with #110 in their handles, I'm sad to see them about to fork off and get disillusioned without understanding why bitcoin rejected 110 robustly.
So here's a more empathetic, constructive higher level version of explaining why not. I hope it's high-level and first-principles enough that everyone can follow.
They seem to want to understand what makes people tick, and are suspicious of intent. So, if someone asked me why is Bitcoin important and what is it, I'd say my (personal) mission and hope for bitcoin is to build the cypherpunk future, that "Snow Crash" was a blueprint, and work backwards from there. Bitcoin I hope leads to fully free markets via bearer unseizable, hard mathematically dependable money. Not everyone is comfortable with that level of freedom, but that's my view. And at this point, I believe that surprisingly, even now many governments have come to understand and value bitcoin's gold-like mathematical assurance, a positive development. Others may have milder views than myself, but still like hard censorship resistant money.
Because of motive suspicion, if it's not obvious: I hate spam with a passion, that's how I came to design hashcash while researching decentralized bearer money with others, and running nodes in privacy related cypherpunk p2p networks nearly three decades ago.
People seem upset about the default op return policy change in bitcoin. I will just assert, there are extremely robust and simple reasons for bitcoin changing default relay policy, and most just didn't do their research, so don't know what those are, or maybe not technical enough to fully understand though there have been 1000s of posts trying to explain in various simplified ways. So that lack of understanding lends itself to shared build-up of false narratives. So here's my back-to-basics higher level explanation.
The decentralization needed to create cypherpunk money has implications a: side effect of decentralization is that you can't impose your views on others. The very decentralization mechanism that helps that, is working against what BIP 110 wants, which at it's most basic is a quest to police other people. I understand supporters don't see their intent like that, but introspect deeper.
You can modify your software, but not anyone else's. Another critical and incredibly robust technical bitcoin immune system is bitcoin can't have people who don't understand technology basics insist on eroding security, decentralization robustness and core properties. That would end badly, fast, and so people will fight you on that.
So the message is Bitcoin respectfully says "no" to what you want. Sorry, and bitcoiners do genuinely understand and empathize that you mean well, have high level thoughts that make emotional sense, and articulate sensible bitcoin-defensive high level ideas, but they are not grounded and without you seeing it, the way you propose to achieve your ideas, hard-conflict with free cypherpunk permissionless money.
My advice is to listen to more experienced people who understand the system and why it works the way it does, to whatever detail you want to understand the grounded reasons for why this is the implication of decentralization and cypherpunk money.
I guarantee you the developer and protocol ecosystem shares and exceeds your views on bearer hard money (and dislike of spam). You may not agree with individual developers choices, views, way of expressing themselves etc, BUT you also need to understand the IETF-like decentralized technical consensus process creates a protective change resistance, that is highly effective at protecting bitcoin mission. The implication of which is no developer can change anything without technical consensus from hundreds of other developers and protocol observers who are pedantic and extremely knowledgeable clever people who won't let any unaddressed technical question past. The protective change resistance is robust and decentralized in an amplifying way because of this technical consensus.
And the many highly technical mainline developers' cypherpunk mission mindsets are probably far more determined than you can even handle on clarity of understanding and views about freedoms on permissionless networks, as many of you are probably still subconsciously inured by the matrix, where they have transcended that, and grew up immersed in it decades ago. They think natively in this space, while you are just grappling with the surface. Many wont have internalized or have the experience to know how this internet physics works, where there is no policeman, no policy authority, just mathematics, free market and hard money. That has implications for your views also, unfortunately.
Now the tough pill, which is unfortunately true: If you won't listen to reason, educate yourself, learn, the same radical freedom applies to you: your permissionless recourse is to club together and create a fork. But bitcoin won't be joining it. (With respect and no sleight intended.)
Please rejoin bitcoin now, or later if you're not convinced and need to experience 110 forking off and fizzling for yourself to start that journey of introspecting and learning. It would be sad if bitcoin lost people disillusioned due to simple lack of understanding of what's going on there, we're all trying to defend bitcoin and keep it on mission. Including btw the 110 technical promoters, just they wandered off plot somehow.
Join the cypherpunks on bitcoin, come cypherpunk summer🌞 in a few weeks. -
Luke Dashjr reposted
Malachi
@MalachiRevolts
-
Luke Dashjr reposted
SpectrGen // XBT
@SpectrGen
The “benevolent dictator” framing is completely disingenuous. He runs one implementation. Anyone is free to fork off the project and build their own. I don’t “follow” Luke, I agree with the technical implementation of BIP-110. I suspect there are many like me
-
Luke Dashjr reposted
Singekino_Miner (Datum miner)
@Singekino_Miner
Soon to be another Happy UASF Day
shaolinfry
@shaolinfry
Happy UASF Day!
-
Luke Dashjr reposted
Parman - Paranoid Bitcoin Mentor 🔑
@parman_the
BIP110 is a DEFENSIVE soft fork.
It is not "hostile", and not a "takeover", and it is not about one person or a leader.
It doesn't add FEATURES.
You won't notice a thing if you use Bitcoin as money; it's intended purpose.
If this is a surprise, you've been fooled and gaslit by the enemy.
bip110.org -
Luke Dashjr reposted
Without Rulers - #BTCB2
@BTCLeukocyte_WR
Look at the incentives of the BIP-110 supporters and of the opponents.
Centralized fiat scammers and anyone connected by a few degrees hate BIP-110.
Bitcoiners wanting to secure #bitcoin as decentralized sound money support BIP-110.
Bitcoin Lebowski⚡
@DudeJLebowski
All I see are incentives.
-
Luke Dashjr reposted
Keysa
@SimplestBTCBook
Results of the past 3 years of revealed Taproot script-path spends:
- OP_IF data storage-99.11%
- Non-OP_IF data storage-0.049%
- Small data inscription-0.140%
- BitVM-like-0.015%
- Other spend-condition scripts-0.68%
👉Data storage (first 3 combined)⚠️99.3%⚠️
Anyone can verify
Simple Steve 🌌
@SteveSimple
New study: 3 years of revealed Taproot scripts on-chain
12.4% of bytes in the Bitcoin blockchain have been revealed Taproot spending scripts since July 2023
Over 99% of the bytes in those scripts were data storage via the dead-code OP_IF method
Explanation and GitHub link:
Most people think of owning bitcoin as having a bitcoin address, and then having bitcoin sent to that address. This is correct.
An advanced way to use bitcoin is to have the bitcoin sent to a script that is more complex than simply a bitcoin address that is controlled by a single private key.
These advanced scripts are things like multi-sigs where, for example, 2 of 3 private keys can be used to control the funds. When bitcoin is sent to one of these scripts, the blockchain does not know the full text of the script because the chain initially only records the fingerprint (a hash) of the script.
The full text of the script is only revealed when someone spends the bitcoin that was sent to it.
In November of 2021, Taproot introduced a new style of script spending, but the basic nature of revealing the full text of the script only upon spending is the same.
An important aside here is that Taproot has the ability to hide scripts that could have been used to spend the coins. This can happen via a "key-path" spend, or by script branches that were committed but were not needed to spend the coins.
Thus this analysis pertains to the Taproot scripts that were indeed revealed in order to spend the coins using a Taproot script-path style spend.
There have been over a hundred million of these revealed scripts on chain. However instead of complex spending conditions, the scripts have been used almost entirely for on-chain bulk data storage - over 99% by bytes count.
Key takeaways of this study:
1) Revealed taproot spending scripts account for 12.4% of block space in the Bitcoin blockchain by bytes since July 2023.
2) The revealed scripts can be categorized in a straightforward manner (explained below) and it is clear that over 99% of them (by bytes) are data storage using the dead-code OP_IF construction.
The detailed category descriptions are:
OP_IF data storage — More than half the script's bytes are arbitrary data tucked inside an OP_IF branch that is guaranteed never to run (dead code), so the data isn't logic at all — it's just parked on-chain as permanent storage. This is the inscription pattern (ordinals, BRC-20, Atomicals), and the vast majority carry a known inscription marker such as "ord" or "atom".
Non-OP_IF data storage — More than half the bytes are data stored in large pushes out in the open, rather than hidden behind a dead OP_IF branch (a push counts as data only when it's too big to be a key or a hash).
Small data inscription — The script contains an inscription (an OP_IF data envelope), but the data is 50% or less of its bytes — typically a tiny inscription whose surrounding script overhead is about as large as the data itself. It's still data storage, just too small to dominate the script, so it's kept out of the >50% data-storage totals rather than inflating them.
BitVM-like — An executable script that performs a large hash-based computation instead of checking a signature — the shape used by BitVM-style verification. Defined precisely as an executable script with no signature check and at least 20 hash operations.
Other spend-condition scripts — Everything left over: genuine spending logic that actually controls the coins, with no data-storage envelope at all. In practice these are ordinary conditions like single-signature, multisig, timelocks, and hashlocks.
The results of running the classification on the past three years of revealed Taproot script-path spends are by bytes:
- OP_IF data storage — 99.11%
- Non-OP_IF data storage — 0.049%
- Small data inscription — 0.140%
- BitVM-like — 0.015%
- Other spend-condition scripts — 0.68%
- Data storage (first three combined) — 99.3%
Anyone can verify the results of this study using their own node's copy of the blockchain and the GitHub link below.
github.com/Unbesteveable/taproot-scriptspends -
Luke Dashjr reposted
Samwise X₿T Gamgee
@taters_bitcoin
12 years of the 80-byte default = zero large OP_RETURNs. Slipstream opens - 14 more months of zero. Then the PR to kill the filter opens, and the bypass vendor mines 12K in one window. Was 'organic usage' actually manufactured during the vote?
#bip110 ends all of this. -
Luke Dashjr reposted
.
@GrassFedBitcoin
>mines BIP110 block
>uses default "datum miner" coinbase tag
>refuses to elaborate
BIP-110 Monitor
@BIP110monitor
⛏️ Block 957,482 just signaled BIP-110!
20 of 1,899 blocks this period — 1.05%.
#bip110 #bitcoin [period 474]
bip110monitor.com?data=eyJwY3QiOjEuMDUsInNpZyI6MjAsInRvdG… -
Luke Dashjr reposted
Jack Mallers
@jackmallers
Don't let anyone convince you that Bitcoin belongs to Wall Street or big corporations.
Its strength comes from the millions of people around the world who wake up every day and earn, save, stack, and hold.
You matter. Bitcoin has always been a grassroots monetary revolution.This media couldn't be displayed. See it on the original post. -
Luke Dashjr reposted
Dathon Ohm / BIP-110
@dathon_ohm
Congratulations and a warm thank you to all BIP-110 signaling miners who have stuck with us since the beginning, as well as the new miners we've recently welcomed, including Sazmining and Crestmont Fabrics.
Bitcoin is healing. -
Luke Dashjr reposted
₿itcoin ₿ombadil
@BitcoinBombadil
Are you happy with how Core and the Block Cartel are scheming to bombard your Bitcoin full node with dead weight bullshit?
If knot, then you Knots + BIP-110🛡️✊🏼
Simply Bitcoin
@SimplyBitcoin
Are you happy with how the government spends your money?
-
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
Miners have had many months to prepare for BIP110.
Bitcoin has been at grave risk all that time because of their laziness, but @dathon_ohm still gave them the extra time anyway.
Instead of being responsible, they have squandered the good faith efforts to do things on their schedule.
Obviously this doesn't apply to *all* miners, but at least I am personally running out of patience with the ones neglecting their job. -
Post not available here, view on X
Luke Dashjr
@LukeDashjr
Miners have had many months to prepare for BIP110.
Bitcoin has been at grave risk all that time because of their laziness, but @dathon_ohm still gave them the extra time anyway.
Instead of being responsible, they have squandered the good faith efforts to do things on their schedule.
Obviously this doesn't apply to *all* miners, but at least I am personally running out of patience with the ones neglecting their job. -
Luke Dashjr reposted
Dathon Ohm / BIP-110
@dathon_ohm
With only 4236 blocks (~29 days) left until non-BIP110-signaling blocks become invalid, BIP-110's hashrate continues to climb to new all-time highs, as Bitcoin's movement to reject arbitrary data attains unstoppable momentum.
-
Luke Dashjr reposted
value_record
@value_record
Not a few opponents of BIP-110 profit from spam. Proponents, however, do not profit from BIP-110 itself. This contrast in motivation is highly telling.
-
Luke Dashjr reposted
.
@GrassFedBitcoin
They realize that BIP-110 has a decent, and increasing chance of succeeding.
That stands to reason as its proponents are very unlikely to back down, while the industry has absolutely no incentive to fight it.
So having initially dismissed it as "dead on arrival" they're now throwing everything they have at it to try and stop it. -
Luke Dashjr reposted
Cedric Youngelman ⚡️
@CedYoungelman
I think we’ll start to see Bitcoin price start to climb as we get closer to mandatory signaling and then it’ll probably rip when bip 110 finally activates.
Nature is healing. -
Luke Dashjr reposted
Cedric Youngelman ⚡️
@CedYoungelman
Luke Dashjr on what actually belongs on the Bitcoin blockchain:
"Spam is anything the person who's getting it did not solicit, did not consent to. In the context of Bitcoin, that's any data that doesn't involve, in some way, the transfer of coins from one person to another. Everything else is just clogging the network and ruining the experience for everyone else.
People who want to share JPEGs can do that. There are websites for it. There are even decentralized ways to do it, like BitTorrent.
The only reason to do it the way they're doing it — forcing it on-chain — is to intentionally push it onto people who have not consented and explicitly do not want it."
@LukeDashjr on The @_BitcoinMatrix #197 -
Luke Dashjr reposted
Jim
@elkrun21
To all those who believe the rhetoric around the Knots/BIP110 gang being a cult of ignorant plebs following the "rantings" of "crazy" man @LukeDashjr and "make shit up" guy @GrassFedBitcoin ... it's bullshit.
I'm here because I believe Knots/BIP110 provides the best opportunity to keep the Bitcoin network decentralized and, subsequently, keep bitcoin immutable money ... that's it.
Regarding the "crazy" man and "make shit up" guy ... if they ever act antithetically to bitcoin as immutable money, I'll drop 'em like a hot potato ... like I did with that "buy STRC and yo-yo yield coins cause we got no spam problem" pontificator, Saylor.
I suspect most, if not all, of the Knots/BIP110 folks feel the same way ... that said, I can't say for sure ... because I haven't met any of them ... it's that beautiful decentralization thing in full bloom you see ... so you'll have to ask them yourself if you want to know how they feel.
Have a good day. -
Luke Dashjr reposted
ScarcityMan 🍴 BLAKE2b Hardfork
@ScarcityMan
I keep hearing arguments about how supporting Knots makes Luke Dashjr into some kind of king or monarch. You mean the guy who is the reason we actually have TWO viable node implementations instead of just ONE? Which version of reality is more decentralized, the one with Luke in it or the one without?
You want more choice, fork the codebase and start maintaining it, for free, and suffer the slings and arrows of 1,000 idiots. Nothing is preventing others from doing it, it's just that most people don't want that job. -
Luke Dashjr reposted
Cedric Youngelman ⚡️
@CedYoungelman
🔁 REPOST, recorded June 2024. Everything Luke Dashjr warned about is happening right now.
Luke Dashjr - Is Bitcoin In A Civil War?
Three or four entities decide what goes into every Bitcoin block. Most "miners" don't even know what they're mining. And if too few of us run nodes, Bitcoin quietly becomes a CBDC.
The Bitcoin Core developer who caught the accidental 2013 hard fork before it broke the network came on to explain why mining is dangerously centralized, why the spam wave is a coordinated attack, and why he built a pool to fight back.
@LukeDashjr, Bitcoin Core developer with 200+ contributions and maintainer of the BIPs, founder and CTO of Ocean, and the man who detected and helped stop the 2013 chain split, joins me to lay out the fight over Bitcoin's future in plain English: the difference between a real miner and a "hasher" who just sells compute, how three or four pools (really Bitmain) control what goes in every block, the invisible tax hiding inside FPPS, why he calls the spam wave a funded attack to destroy Bitcoin, why Bitcoin becomes a CBDC if too few of us run our own nodes, whether we are already in a civil war, and how Ocean is trying to hand block construction back to miners.
Send this to anyone who thinks Bitcoin mining is decentralized.
TIMESTAMPS:
00:00 Intro
01:50 Who is Luke Dashjr
04:09 The rabbit hole: his first patch in 2011
06:06 When Bitcoin became essential (there's no plan B)
10:09 Eligius: the first non-custodial mining pool
12:13 Why he started Ocean
13:50 The real consequences of pool centralization
16:34 Hasher vs miner: who actually mines?
18:36 How FPPS pays you, and what it hides
20:05 Why big pools become proxies for Bitmain
22:35 The launch, and why "censorship" became the word
24:49 What Bitcoin is actually built for
26:40 How to define spam
33:06 "The people behind the spam are out to destroy Bitcoin"
34:47 How the attack gets funded by gamifying it
37:13 Is this an existential threat?
38:48 Run a node, or Bitcoin becomes a CBDC
40:09 Bootstrapping a mining pool from zero
45:40 What non-miners can actually do to help
46:31 Should Bitcoin ossify, or keep upgrading?
49:24 How censorship-resistant is Bitcoin today?
50:00 Is Bitcoin already in a civil war?
51:10 Would the good guys still win a block size war today?
55:53 Ocean's roadmap: decentralizing block construction
1:00:07 How Ocean got its name (Jack Dorsey's nudge)
1:01:53 Do we have a problem in Bitcoin culture?
1:03:22 What Bitcoin means to Luke
1:07:11 The clause: Ocean can do no harm to Bitcoin
1:08:10 Where to find Luke + @ocean_mining
🎧 youtube.com/watch?v=9lmr4WchBH0
Then watch the sequel with @mattkratter, The @_BitcoinMatrix #279: "Bitcoin Core Has Gone Rogue."
🎧 youtube.com/watch?v=xsOjcw6APfMThis media couldn't be displayed. See it on the original post. -
Luke Dashjr reposted
Keysa
@SimplestBTCBook
A bank doesn't expect its vault to make money. A company doesn't expect cybersecurity to generate revenue. These are expenses incurred to protect something far more valuable and bitcoin mining can be viewed the same way.
3/7 -
Luke Dashjr reposted
John
@truthinlogicBTC
BIP-110 narrows the use of bitcoin to monetary use only. It makes sure it is money, and nothing else. As absolutely scarce money, bitcoin ends centralized control of all kinds.
The fiat system DOES NOT want Bitcoin to be money. Those against BIP-110 are serving fiat system.
Jim
@elkrun21
If you support BIP-110 ... SPEAK UP.
The cacophony of anti-BIP rhetoric is going be deafening. The fiat funding behind the anti-BIP110 crowd likely dwarfs that of pro-BIP110 plebs. Don't let the noise drown out the signal.
And, of course, run a node with Knots + BIP-110. -
Luke Dashjr reposted
BitcoinAussie | BIP-110 | 🧃to 🧡
@bitcoinaussie_
Core30 attacked Bitcoin.. BIP-110 restores it.
Adam Simecka
@AdamSimecka
BIP110 has more support than 100KB OP_RETURN did.
-
Luke Dashjr reposted
Majorian
@MajorianBTC
Any pushback against BIP-110 is done so purely on political grounds, not on the technical merits of the proposal.
-
Luke Dashjr reposted
Conza
@Conza
The current state of @bitcoincoreorg courtesy of @bitcoinbrink:
PR guy: "~ 100 slides on what bCore devs are actively working on!"
Pleb: "Ok... how many slides indicate how their work improves Bitcoin's quality as money?"
PR guy: "[Absolutely no idea]. Sounds like a perfect project for you! "
The answer to the question is quite literally *zero*. -
Luke Dashjr reposted
Majorian
@MajorianBTC
You know BIP-110 is over the target because of how vehemently Big Bitcoin has come out against it.
-
Luke Dashjr reposted
Majorian
@MajorianBTC
"Will I lose my funding if I support BIP-110? What about podcast/conference/private dinner invites?"
This line of introspection explains any hesitancy to bip-110 than the actual nuts and bolts of the proposal, which is rock solid. -
Luke Dashjr reposted
George Bodine
@Jethroe111
This is a stupid, short sighted take from a man who has never fired up a node in his office and watched the fucking thing slow down when it hits the spam wall of '23.
If you were sitting in an F18 next to me on a carrier I would give you the signal, "Pull your head out of your ass."
Michael Saylor
@saylor
After a decade of blockspace fears and non-monetary-use panics, Bitcoin still has no spam problem. Fees are 1 sat/vB: anyone can move any amount globally with immediate processing for ~$0.30. The free market has always solved Bitcoin’s blockspace challenges. $BTC
-
Luke Dashjr reposted
Greg Tonoski, BIP-110, Blake2b
@GregTonoski
"Bitcoin Core has long placed much more restrictive limits on what transactions it'll relay and mine when they contain OP_RETURN outputs, so we rarely see transactions exceeding those limits [83 bytes]." -David A. Harding (@hrdng, ex-Brink) in 2021.
-
Luke Dashjr reposted
.
@GrassFedBitcoin
They are still doing this btw.
-
Luke Dashjr reposted
Ali2k
@Ali2kCom
We MUST win.✌️
Luke Dashjr
@LukeDashjr
Also, this isn't about me or Knots. It's about making Bitcoin work. I welcome competition, and don't _want_ to be in the position this puts me in (making me a target personally).
But the alternative is Bitcoin's certain death, which would be terrible for not only myself, but also mankind in general, including my children and future grandchildren.
This is not a battle we can give up or compromise on. We MUST win. -
Luke Dashjr reposted
XBT | Hardfork cguida | ⚡🪢
@cguida6
"You’re not technical enough to understand the wisdom of this very controversial protocol change" is not just a big red flag, it's literally how bitcoin dies
Bitcoin stays decentralized because *everyone* watches the watchers
As soon as the watchers tell you you're not technical enough to understand what they're doing, they're demanding that we stop watching them
If we submit to this demand, then no one watchers the watchers, and when that happens, the watchers reinstitute the fiat system and dominate everyone
hodlonaut
@hodlonaut
Human nature + continuous protocol changes = unavoidable slide towards corruption of the protocol.
Which is exactly why the «you’re not technical enough to understand the wisdom of this very controversial protocol change» should raise big red flags.
Especially when strongly supported and promoted by people with terrible track records. -
Post not available here, view on XPost not available here, view on X
Luke Dashjr
@LukeDashjr
Also, this isn't about me or Knots. It's about making Bitcoin work. I welcome competition, and don't _want_ to be in the position this puts me in (making me a target personally).
But the alternative is Bitcoin's certain death, which would be terrible for not only myself, but also mankind in general, including my children and future grandchildren.
This is not a battle we can give up or compromise on. We MUST win. -
Luke Dashjr reposted
Bitcoin Lebowski⚡
@DudeJLebowski
Bitcoin is, and shall forever be, a grassroots movement. Any coopting by corporate interests will only ever be with the acceptance of node runners. If they try to manipulate it to their own ends, they will be beaten down. This is the second Satoshi Crisis, probably of many.
-
Luke Dashjr reposted
Lilly
@JustaLillyBit
All the people with LDS can say what they need to say but I would argue there has not been a single soul out there that has been promoting for and fighting for the plebs and "normies" to run a node longer than @LukeDashjr
There is evidence of this on his earliest interviews. Long before many of us were ever in Bitcoin. Long before BIP110 or the spam wars. He may not have the loudest mouth but his words were true then and now more important than ever.
We are nodes. Node is law. -
Luke Dashjr reposted
Justin Bechler
@1914ad
-
Luke Dashjr reposted
Luis Marcano 🦉 Bitcoin
@MarcanoFilms
wow what is thiss?? @ocean_blocks 👊
-
Luke Dashjr reposted
Satflation⚡
@satflation
OP_RETURN pimps keep calling it “spam.”
No longer remotely accurate.
Uncapped OPR means it’s “content.”
Storing wizards, cats and CSAM becomes explicitly intended purpose of the network. -
Luke Dashjr reposted
Dathon Ohm / BIP-110
@dathon_ohm
To ensure the smoothest possible activation, it is recommended to tell everyone you know (users, businesses, and miners) about this change, to make sure they are running the latest BIP110-enforcing software and following the longest chain upon activation.
(5/) -
Luke Dashjr reposted
Dathon Ohm / BIP-110
@dathon_ohm
ATTENTION. IN ONE MONTH, THE BITCOIN NETWORK WILL START REJECTING BLOCKS THAT DO NOT SIGNAL READINESS FOR BIP-110, A SOFTFORK TO REJECT THE ARBITRARY DATA STORAGE USE CASE, THEREBY REAFFIRMING THAT BITCOIN IS MONEY.
(1/) -
Luke Dashjr reposted
Majorian
@MajorianBTC
The dynamic block size proposal, advocated for by certain influencers who got the op_return limit removed, is another "let the fee market sort it out" ploy.
Once what is in a block is no longer sacred, the next thing they will come for is the overall size of the block. -
Luke Dashjr reposted
XBT Motorist
@BitcoinMotorist
In hindsight, it will be said that BIP110 had consensus. Overwhelming consensus
-
Luke Dashjr reposted
.
@GrassFedBitcoin
Bitcoin's immune system flagged OP_IF in taproot and large OP_RETURNs as foreign bodies and is attempting to remove them.
If they are unsuccessful, Bitcoin will not have an immune system any more. -
Luke Dashjr reposted
Johnny Wilkins
@wilkins_jo52699
In the April 15th email, Austin corrects Epstein with "Adam", it's pretty undeniable it's Adam Back.
-
Luke Dashjr reposted
Justin Bechler
@1914ad
⚠️ Since the moment Core™ repurposed Bitcoin for non-monetary ‘use cases’ your net worth was effectively halved by individuals who support and profit from the Bitcoin Core industrial complex.
-
Luke Dashjr reposted
privacymatters21m
@privacymatter21
Since mid June I've been renting hashrate through Braiins, mining via my own DATUM gateway serving BIP-110 compliant block templates generated by my Bitcoin Knots node. Against the odds, I'm actually in profit. Profit was never the objective, but I won't complain.
-
Luke Dashjr reposted
🪱AAAAAAAAAAAAA🪱 XBT 🪱 Building Alkanes 🪱
@RetinaWriggler
BIP-110 already has consensus, the spammers simply don't realize yet that they are doomed
-
Luke Dashjr reposted
bendtheknee
@bendthekne3
We didn't want this, Core brought it upon us. You matter, your node and miners matter. Before VC's, Foundations, Governments - There was us. The Pleb. The ones who bootstrapped Bitcoin from nothing. United under the idea - Bitcoin is Money. Defend it, Signal BIP110 RDTS.
-
Luke Dashjr reposted
Robert Allen
@SatoshiSound
It is easier to restrict the rules of Bitcoin (soft fork) than it is to extend (or break) the rules of Bitcoin (hard fork).
This structure is conservative by design.
This means that the minority can protect itself from the tyranny, apathy or banality of the majority.
Over the last few years, Core was carefully and slowly corrupted and the codebase modified so as to expose a vulnerability which, if exploited, could lead to significant legal risk for node operators. Bitcoin was not designed or built as a file storage or file sharing network.
BIP-110 is the intolerant minority saying enough is enough. No more. This is where we draw the line. -
Luke Dashjr reposted
Cedric Youngelman ⚡️
@CedYoungelman
"Did we actually win the block size war — or did we lose?"
@Excellion asks the question most Bitcoiners won't. Fees as a filter, the jump to 4MB, and why @LukeDashjr may have been right about smaller blocks.
The context the BIP 110 fight skips. 👇
Samson Mow on whether we actually won the block size war:
"The Core people say the fees are the filter. But that misses the point — you're not looking at the entire network, and what's already happened.
Yes, fees filter spam. You pay fees to transact, and a spammer pays fees too. But during the block size war, we changed the whole dynamic. We changed the unit economics — we increased the block size and decreased fee pressure. So we actually made it cheaper to spam the network.
Only one person talked about decreasing the block size back then — Luke Dashjr. And I think he was right.
So it begs the question: did we actually win the block size war, or did we lose? We had a net increase in effective block space, going to four megabytes — and the repercussions of that, I don't think we've really reasoned out.
Maybe it was a mistake to go to four. Maybe we should have kept it at one, and left the settings of the network as they were."
@Excellion on The @_BitcoinMatrix #243This media couldn't be displayed. See it on the original post. -
Luke Dashjr reposted
Liberty NH 🦔🌲
@NHpilled
Let's just do what the Satanic Fabians say guys!
-
Luke Dashjr
@LukeDashjr
With respect to BIP110:
Knots 20260508: Yes
Old Knots: Yeah, but ask miners' permission
Core <=29: Yeah, but ask miners' permission
Core 30+: Okay, iff miners agree
LibreRelay: Okay, iff miners agree
Literally no node software actually *opposes* BIP110.
Luke Dashjr
@LukeDashjr
That being said, running older/Core nodes _does_ leave you insecure if miners attack the network.
So you should still upgrade ASAP. -
Luke Dashjr reposted
Kyle 🐆
@kwsantiago
Sovereignty over your Bitcoin node:
- reproduce Knots byte-for-byte from source
- stack your own patches into a custom build
- run it on @Start9Labs, sideloaded as an update that keeps your whole synced chain, no re-sync
Reproducible and verifiable 👇 github.com/chrisguida/knots-assembly/pull/2 -
Luke Dashjr reposted
Justin Bechler
@1914ad
Bitcoin Core dev Jeremy Rubin says the quiet part out loud to a douchebag ordinals perv and his groupie.
-
Luke Dashjr reposted
Adam Simecka
@AdamSimecka
I have 0 sponsors. I have 0 donors.
3 years ago, I was anti-knots and anti-filter. It was only through my journey of trying to prove them wrong that I realized I was the one in the wrong.
Be willing to be wrong. Never dig your heels in. Seek truth.
My opinions aren't for sale. -
Luke Dashjr reposted
Caylon
@CoSatoshi821
Transaction fees have nothing to do with Bitcoin's security.
No, it's barely a fraction of a percent of miner revenue.
Exactly, they already did, and BIP110 reverses some of those changes *temporarily* until better solutions can be made.
Bitcoin is not working fine if centralized fiat-funded orgs can unilaterally change it against the will of the plebs and node runners.
#runknots #bip110
Mark Harvey
@thepowerfulHRV
Genuine question: What is the point of BIP-110?
From my understanding, “spammers” pay transaction fees to miners, which only strengthens Bitcoin’s security.
Yet transaction fees remain very low for legitimate financial transactions.
Won’t BIP-110 just reduce miner revenue, weakening Bitcoin’s security?
Remember, “spam” was only made possible by previous (and arguably unnecessary) changes to the code, such as SegWit and Taproot.
Might further changes to the code have additional unintended consequences?
Bitcoin is working fine, why mess with it? -
Luke Dashjr reposted
Adam Simecka
@AdamSimecka
Luke has never asked for power. Stop listening to people painting him as a tyrant king.
BIP110 is here because the Core apparatus is actively desecrating the sanctity of Bitcoin at its foundation.
Core will absolutely turn Bitcoin into an "altcoin" if we don't stop them.
Luke Dashjr
@LukeDashjr
Saylor didn't say anything about BIP110...
And no, it's too late to cancel BIP110. If Core gets their act together in the next year, maybe we won't need a followup long-term softfork. -
Luke Dashjr
@LukeDashjr
Be careful. Almost all of these bets are rigged to bias strongly against BIP110. But even despite that, apparently things are going so well that gamblers are willing to risk it!
XBT | Hardfork cguida | ⚡🪢
@cguida6
They're finally figuring out that bip110 isn't going away
-
Post not available here, view on X
Luke Dashjr
@LukeDashjr
Saylor didn't say anything about BIP110...
And no, it's too late to cancel BIP110. If Core gets their act together in the next year, maybe we won't need a followup long-term softfork. -
Luke Dashjr
@LukeDashjr
Scammers and bad actors have been claiming BIP110 was "dead on arrival" or otherwise failed from the first day @dathon_ohm published it.
It was fake news then, and it's fake news now.
BIP110 has consensus and will still succeed if we hold the line.
Luke Dashjr
@LukeDashjr
In the meantime, talk to your favourite merchants and businesses. Ensure they don't fall for the "BIP110 has failed" gaslighting, and that they've upgraded their nodes.
-
Luke Dashjr reposted
Nicolás Delfín . Privacy is Freedom
@biticultor
"Data already has a proper parking spot: BitTorrent.
But they don't use it, because their goal isn't to publish data, it's to harm Bitcoin."
Crystal clear.
Luke Dashjr
@LukeDashjr
No, scammers/spammers are attacking Bitcoin; they are NOT bitcoiners.
No, Core is not right about anything (in this regard).
No compromise with attacks, period.
Data already has a proper parking spot: BitTorrent.
But they don't use it, because their goal isn't to publish data, it's to harm Bitcoin.
Everyone trying to use Bitcoin pays more for spam.
More bandwidth, more CPU time, more storage, etc.
There were no pictures until 2025 October.
Core30 added pictures.
BIP110 rejects that and removes them again.
BIP110 is not a content filter.
Spam filters are not content filters.
Bitcoin is not a content distribution system AT ALL.
ZERO content allowed.
BIP110 does not freeze coins.
Nothing about it is forever.
It does not cause chain splits (only anti-BIP110 can).
It is not censorship.
Stop listening to bad actors lying to you. -
Luke Dashjr reposted
.
@GrassFedBitcoin
BIP-110 block mined by @sazmining - Cheers @khalliburton!
-
Luke Dashjr reposted
PyBLØCK
@_PyBlock_
Even Spammers know that #bip110 has already won and that they have to switch to a more expensive envelope so their Spam can survive.
Ruining Spammers is always great news, and the fact that they’ve already accepted that BIP110 has won—so they can adapt their crap—is even better.
lifofifo ◉
@lifofifo
Ordinals are now BIP-110 ready.
github.com/ordinals/ord/pull/4545 -
Luke Dashjr reposted
Kyle 🐆
@kwsantiago
BIP 148 was ~10% of enforcing nodes. Major exchanges and most hashrate backed SegWit2X, a competing plan. The UASF minority still forced SegWit and SegWit2X collapsed.
A determined minority changed the outcome without being the economic majority.This media couldn't be displayed. See it on the original post. -
Luke Dashjr reposted
Caylon
@CoSatoshi821
The Bitcoinfluencer class sold you on the idea that Bitcoin was the best money; an escape from the dismal failures of state-controlled fiat; a way to protect yourself and your family for generations.
Now they're pissed that you applied those principles and thus support a BIP that aims to protect nodes and prevent Bitcoin from becoming cummy-spam data storage.
#bip110 #runknots -
Luke Dashjr reposted
Robert Allen
@SatoshiSound
-
Post not available here, view on X
Luke Dashjr
@LukeDashjr
No, scammers/spammers are attacking Bitcoin; they are NOT bitcoiners.
No, Core is not right about anything (in this regard).
No compromise with attacks, period.
Data already has a proper parking spot: BitTorrent.
But they don't use it, because their goal isn't to publish data, it's to harm Bitcoin.
Everyone trying to use Bitcoin pays more for spam.
More bandwidth, more CPU time, more storage, etc.
There were no pictures until 2025 October.
Core30 added pictures.
BIP110 rejects that and removes them again.
BIP110 is not a content filter.
Spam filters are not content filters.
Bitcoin is not a content distribution system AT ALL.
ZERO content allowed.
BIP110 does not freeze coins.
Nothing about it is forever.
It does not cause chain splits (only anti-BIP110 can).
It is not censorship.
Stop listening to bad actors lying to you. -
Luke Dashjr
@LukeDashjr
Happy Dependence on God day!
Remember, every moment that we exist, we exist only because God continually wills and conserves us in being. Were He to withdraw that conserving will for even an instant, we would cease to exist. -
Luke Dashjr reposted
🐧 Daniel Garcia
@dannybuntu
BIP 110 for dummies🧵(Work in Progress) Based off
@LukeDashjr explanation here bitcoinknots.org/learn/bip110-code-walkthrough.html
Parsed with CGPT
1/ src/consensus/tx_verify.cpp -
Luke Dashjr reposted
Delcin #XBT
@DelcinMaria
BIP110's goal was never to stop spam protocols.
Its goal is to incentivise developers to patch mempool filters as required post-activation. -
Luke Dashjr reposted
Jim | Bitcoin, not jpegs
@venorusprime
@ocean_mining is on a tear, @Roughnecks110 are banging out the BIP110 blocks, and I'm up 2.5% on my rented hash! #fyff
-
Luke Dashjr
@LukeDashjr
BIP110 creates a rare opportunity for bitcoiners we should take advantage of:
Unlike most consensus changes, it is extremely simple: with only 5 modified lines of code and 72 added, across 5 source code files, we can explain it in a way anyone can understand.
(continued...)
Luke Dashjr
@LukeDashjr
Take a look. Review BIP110 yourself:
bitcoinknots.org/learn/bip110-code-walkthrough.html
Luke Dashjr
@LukeDashjr
As you read the code, also take note on how it flows cleanly, and matches the general code around it.
BIP110 does not introduce any fundamentally new concepts. -
Luke Dashjr reposted
-
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
Take a look. Review BIP110 yourself:
bitcoinknots.org/learn/bip110-code-walkthrough.html -
Luke Dashjr reposted
boozy | XBT
@TheBoozles
Tell your friends, help your neighbors, help your grandma RUN A NODE! Signal for BIP-110! Activation is next month, and this is our last chance for Bitcoin.
-
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
BIP110 modifies 10 lines of existing consensus code, and adds 74 more lines. It is trivial to review and obviously correct.
If we ignore the softfork activation logic, the actual rules themselves amount to 7 modified lines and 37 new lines.
Everything else is documentation, tests, ensuring users consent at startup, and p2p logic. -
Post not available here, view on XPost not available here, view on X
Luke Dashjr
@LukeDashjr
BIP110 modifies 10 lines of existing consensus code, and adds 74 more lines. It is trivial to review and obviously correct.
If we ignore the softfork activation logic, the actual rules themselves amount to 7 modified lines and 37 new lines.
Everything else is documentation, tests, ensuring users consent at startup, and p2p logic. -
Luke Dashjr reposted
spoon
@spoonmvn
What’s incredible to me, is that this permissionless “blockspace” is literally our hard drives in our homes, yet there are still a handful of Bitcoiners that support these grifters making it a “right” to store their parasitic shit tokens, again, on our hard drives, IN OUR HOMES.
𓂀 DOG BTC +Tart ᛤ 𓂀 𓋹 𓆣
@DOGBTC_TartSwap
We do not accept BIP 110.
Defend permissionless blockspace. Reject BIP-110 -
Luke Dashjr reposted
Mark Artymko
@MarkArtymko
.@SBICrypto is shutting down its mining pool on July 31.
To the SBI Crypto team: thank you for years of reliable service to the network. Wind-downs are never easy, and we're sad to see you go.
To SBI's miners: we know this switch wasn't on your roadmap. An unexpected migration is stressful, and if you need it, our team can make the transition as seamless as possible.
Joining OCEAN is easier than any other pool. Point your miners at mine.ocean.xyz and you're mining. No lengthy onboarding, no hoops. And if you want to go further, DATUM lets you build your own block templates and mine with true sovereignty, while still receiving direct, non-custodial payouts straight from the coinbase.
The economics hold up too: OCEAN paid out 3.6% more than the best FPPS pool in 2025.
Even if you're still weighing your long-term options, you're welcome to hash with us while you figure it out. No lock-in, no pressure. Your rewards are paid directly to you either way.
If you need a hand with the transition, reach out to me personally at mark@ocean.xyz or our Chief Commercial Officer Nacho Pauls at nacho@ocean.xyz. -
Luke Dashjr reposted
Joshua Blake2B Fortezza
@JoshuaFortezza
Anti 110 fags:
• I’m against trash on chain, I have no solution
• 110 won’t work, let me spend all day explaining why
• I’m building a new bitcoin client, I don’t know if soft forks will work
• 110 was rushed, why are we still discussing 110 it’s getting old
• let’s not change bitcoin, I support the core changes to Bitcoin
• there’s no 110 support, the 110 support is harassing me
And many more contradictory sloppy takes. -
Luke Dashjr reposted
.
@GrassFedBitcoin
In 2017 the community supported BIP-148
The industry opposed it
The community won
In 2026 the community supports BIP-110
The industry doesn't care
The community will win -
Luke Dashjr reposted
.
@GrassFedBitcoin
Correct. There is no URSF. There is no attempt to create a better alternative. There was no substantive pushback on the original mailing list proposal.
There is an enraged group of developers having a fit over it and a bunch of bad faith arguments that have been refuted endlessly.
It doesn't do the terrible things they say it does, and they do not have the integrity to admit it.
So the conversation is literally just brazen liars on Twitter saying they don't like it, while running nodes that will accept it anyway.
That is not material opposition, it's meaningless. -
Luke Dashjr reposted
⏳ Michael Dunworth⌛️
@MichaelDunwort1
Imagine a company that automatically signs you up to their spam mailing list?
Thats literally what Core 30 did. Enabled a “subscribe to all marketing emails” but “subscribe to all on chain marketing tokens”.
It’s literally the same, which is why anyone who’s used software before has seen the play before, which is why anyone who’s”such a Fantastic contributor” had to leave Core. Conscience got the best of them.
Con-science always trumps Com-science -
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
Miners trying to block BIP110 would be suicide for their businesses. They would give the community no choice but to change to another proof-of-work algorithm.
And for what purpose? To enable bad actors to force CSAM on every bitcoiner? I don't see that happening. Just FUD. -
Luke Dashjr reposted
Jim
@elkrun21
The loud voices opposing BIP-110 aren't doing so because they think it'll fail, but because they see it succeeding.
They understand many of the abuses of the Bitcoin network enabled by Core is about to end, and their grift will be over.
Sayonara grifters. -
Post not available here, view on X
Luke Dashjr
@LukeDashjr
Miners trying to block BIP110 would be suicide for their businesses. They would give the community no choice but to change to another proof-of-work algorithm.
And for what purpose? To enable bad actors to force CSAM on every bitcoiner? I don't see that happening. Just FUD. -
Luke Dashjr reposted
Kiawtzin
@kiawtzin
Bitcoin is a network governed by rules enforced by nodes - it isn't a network whose rules are what a handful of mining companies say they are
.
@GrassFedBitcoin
Two things.
One:
It isn't a 55% activation threshold. It's 0%. BIP110 nodes will begin enforcing this thing at the latest block 661,632. That's early August of this year.
We do not need the permission of a small group of pools to activate soft forks in Bitcoin, and if they were to activate one among themselves, we would not be obligated to accept it.
Two:
Pools ignoring a fork that has the level of adoption BIP110 has is an insane scenario that people have deluded themselves into believing without understanding what it would imply if they were correct.
Mining pools unilaterally ignoring a consensus rule as enforced by ~half of the upgrade nodes on the network is a declaration of war made by a handful of Bitcoin companies that have absolutely nothing to gain by doing so.
Soft forks in Bitcoin must be materially opposed if they have undesirable effects. Material opposition to BIP110 does not exist.
Blocks that do not voluntarily signal for early activation do not imply an incoming coup of any sort.
Have confidence that the network dynamic aligns with theory: Bitcoin is a network governed by rules enforced by nodes - it isn't a network whose rules are what a handful of mining companies say they are. -
Luke Dashjr
@LukeDashjr
First BIP110-ready Bitcoin exchange! (AFAIK)
Medusa🪼 - Maxfy
@medusa_maxfy
We confirm the entire platform runs on Knots and we’re signaling for BIP-110
-
Luke Dashjr reposted
XBT | Hardfork cguida | ⚡🪢
@cguida6
Meanwhile Core: "we already fixed a bug, but let's fix it again, in the worst way possible breaking mining scalability, so that some miner over 50 years from now can't donate 50 BTC to other people and do a bunch of work to - in a completely unrealistic scenario - maybe confuse a few light wallets briefly"
Luke Dashjr
@LukeDashjr
-
Luke Dashjr
@LukeDashjr
-
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
"[Jesus] found in the temple…the bankers sitting. And when He had made a whip of knots, He cast them all out of the temple…and the money of the bankers he poured out, and the tables he overthrew." -John 2:14-15, slightly reworded
-
Luke Dashjr reposted
.
@GrassFedBitcoin
Two things.
One:
It isn't a 55% activation threshold. It's 0%. BIP110 nodes will begin enforcing this thing at the latest block 661,632. That's early August of this year.
We do not need the permission of a small group of pools to activate soft forks in Bitcoin, and if they were to activate one among themselves, we would not be obligated to accept it.
Two:
Pools ignoring a fork that has the level of adoption BIP110 has is an insane scenario that people have deluded themselves into believing without understanding what it would imply if they were correct.
Mining pools unilaterally ignoring a consensus rule as enforced by ~half of the upgrade nodes on the network is a declaration of war made by a handful of Bitcoin companies that have absolutely nothing to gain by doing so.
Soft forks in Bitcoin must be materially opposed if they have undesirable effects. Material opposition to BIP110 does not exist.
Blocks that do not voluntarily signal for early activation do not imply an incoming coup of any sort.
Have confidence that the network dynamic aligns with theory: Bitcoin is a network governed by rules enforced by nodes - it isn't a network whose rules are what a handful of mining companies say they are. -
Luke Dashjr reposted
Joshua Blake2B Fortezza
@JoshuaFortezza
BIP-110 is:
* technically straight forward; closes taproot bug, and op return bug.
* ideologically straight forward; maintains the long established limits on arbitrary data in tx's
* economically straight forward; pushes the incentive that the block chain is for monetary data
* socially straight forward; establishes who are bad actors or too ignorant to make good judgement
* and that it will bring to many of its proponents some serious reputational and economic righteousness.
That said, I find it healthy that a sizeable part of the Bitcoin influencer community is trying to signal cultural distance from the absolute and unmitigated retardedness that @giacomozucco's post and its author represent.
After the success of BIP-110 to signal cultural distancing from the past few years of disastrous rule changes, we'll firmly establish an effective signal to culturally distance ourselves from dick butts and island boys and OG influencers with these appropriate straight forward tools.
Giacomo Zucco (Pear Market Edition)
@giacomozucco
I think BIP-110 is technically sloppy, ideologically confused, economically hopeless, socially embarrassing, and that it will bring to many of its proponents some serious reputational and economic damage.
That said, I find it healthy that a sizeable part of the Bitcoin ecosystem is trying to signal cultural distance from the absolute and unmitigated retardedness that this post and its author represent.
I really hope that, after the weird attempt to signal cultural distance from this shit with consensus rule changes will fail, we'll still manage to effectively signal cultural distance from this shit with the appropriate tools. -
Luke Dashjr reposted
Efe #BIP-110
technically sloppy: I expect for a person like you to tell exactly which part is sloppy. It doesn't get sloppy because you said so. This is pure gaslighting. Stop it.
ideologically confused: It is not.
1. It is my software and hardware so I decide what goes in and what I relay.
2. I'm buying bitcoin with my scarciest resource time so I expect bitcoin to reflect that value and it doesn't with a dickbutt.gif
3. Bitcoin is decentralized because of nodes. Anything that makes nodes harder to run or cost more is a bad thing for it's decentralization. You know those better than me so why are you larping?
economically hopeless: Not really.
1. Non monetary data increases the cost of miners.
2. price has been going down since v30 is released.
3. If miners want the bitcoin that they mined to worth more they should comply or they will go bankrupt trying to get an extra bucks with mining spam.
socially embarrassing: It is the highest level that bitcoiner can get. Satoshi would probably be the most toxic BIP-110er too btw and would be disgusted by people who didn't cut their relationships with people like Andy. What is embarrasing is to not speak against core and their betrayal to bitcoiners.
You might be very close with coretards/Andy and they might be funding planB etc but sometimes you have to man up, show some integrity and say the right thing.
"Hard times create strong men" but you are acting like a marshmellow.
Giacomo Zucco (Pear Market Edition)
@giacomozucco
I think BIP-110 is technically sloppy, ideologically confused, economically hopeless, socially embarrassing, and that it will bring to many of its proponents some serious reputational and economic damage.
That said, I find it healthy that a sizeable part of the Bitcoin ecosystem is trying to signal cultural distance from the absolute and unmitigated retardedness that this post and its author represent.
I really hope that, after the weird attempt to signal cultural distance from this shit with consensus rule changes will fail, we'll still manage to effectively signal cultural distance from this shit with the appropriate tools. -
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
BIP110 is the majority preventing a minority change.
-
Post not available here, view on X
Luke Dashjr
@LukeDashjr
BIP110 is the majority preventing a minority change.
-
Luke Dashjr reposted
Adam Simecka
@AdamSimecka
This is a very clear subversion tactic. They want you to become financially invested in the outcome today so that you cannot make a rational decision tomorrow. Instead, you are obligated to follow through with your decision based on the outcome. This is why they all want you to gamble instead of just telling you to run the node software that is best for you.
-
Luke Dashjr reposted
Fred Krueger
@dotkrueger
Where do you stand on BIP-110?
-
Luke Dashjr reposted
XBT | Hardfork cguida | ⚡🪢
@cguida6
Look at all these businesses and organizations that support bip110! 🔥🔥🔥
(This list is a work in progress):
v0-bitcoin-companies-table.vercel.app -
Luke Dashjr reposted
₿itcoin ₿ombadil
@BitcoinBombadil
Just because no one knows the future for certain, doesn’t mean we shouldn’t defend Bitcoin from a blatant SpamScam attack on Bitcoin by bad actors who are Deep State Gang-affiliated. If we won’t defend Bitcoin, who will? What choice do we have?
If you know, you Knots + BIP-110🛡️
Jimmy Song (송재준)
@jimmysong
I am not "for" or "against" BIP110. The reason being that I don't know enough about the system to know the consequences of either path. We'll know a little more when the soft fork resolves one way or the other, but currently, I have little idea of how anything plays out.
-
Luke Dashjr reposted
Brad Wesley
@wesleybrad060
I migrated to Bitcoin Knots August 24, 2025 because I had been unhappy about Core devs and never realized I had a choice. Bitcoin price on that day was $115,000. October 10th core v30 released. I started to signal for BIP-110 as soon as I could. I believe it was on Jan. 24th 2026 based on my post. Bitcoin price was $90,000. Some critics of Bip-110 claim that this is simply "infighting" because of a 🧸bear market, but I made these choices during a 🐂 bull run. I saw the problems that needed to be fixed. Bitcoin as only money and not data storage is always more important than what other's say it's value in fiat is. @saylor @Excellion @adam3us etc..
-
Luke Dashjr reposted
Sly Roundabout Knotzi
@_Knotzi
Satoshi would be such an extreme knotzi today, it'd make Luke blush.
-
Luke Dashjr reposted
ANTON
@Anton_Bitcoin
Who ever entered a war/battle for knowing the consequences?
Those are simply unpredictable.
One fights for truth and honor, or because one has nothing more to lose.
BIP 110 nodes have nothing more to lose.
We either win, or we learn that banking cartel won, on the long run.
Jimmy Song (송재준)
@jimmysong
I am not "for" or "against" BIP110. The reason being that I don't know enough about the system to know the consequences of either path. We'll know a little more when the soft fork resolves one way or the other, but currently, I have little idea of how anything plays out.
-
Luke Dashjr reposted
hodlonaut
@hodlonaut
Don't be a fence sitter.
Find your balls. -
Luke Dashjr reposted
₿itcoin ₿ombadil
@BitcoinBombadil
This was a year ago… it’s been 3+ years since the biggest Spam Attack in Bitcoin history.
Anyone who says BIP-110 is “rushed” is being completely disingenuous and undermining a responsible effort to defend and repair Bitcoin.
.
@GrassFedBitcoin
There is no room for debate any more.
The inscriptions hack is vicious attack on Bitcoin, the tools exist to prevent it but rather than adopt it, Bitcoin Core simply want to open up an additional mechanism of attack.
This cannot be tolerated. -
Luke Dashjr reposted
realityblob
@realityblob
Notice BIP-110ers don’t really talk about price these days.
They know what’s currently at stake is much more important than price.
Run BIP-110. #bitcoin -
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
This is exactly right. The community can't takeover from the community. And if anyone else controls Bitcoin, the community taking over again is only a good thing.
Not long ago, Bitcoin Core literally had to prove it wasn't in their control to combat CSW's frivolous lawfare. -
Post not available here, view on XPost not available here, view on X
Luke Dashjr
@LukeDashjr
This is exactly right. The community can't takeover from the community. And if anyone else controls Bitcoin, the community taking over again is only a good thing.
Not long ago, Bitcoin Core literally had to prove it wasn't in their control to combat CSW's frivolous lawfare. -
Luke Dashjr reposted
Simply Bitcoin
@SimplyBitcoin
They couldn't ban Bitcoin. Every government that tried failed.
So the question changed: if you can't ban it, can you just make it too heavy for ordinary people to carry?
Rustin spent 3 days in a basement pulling the receipts on the code change, the money behind the developers who made it, and why nobody with a platform said a word. 👇This media couldn't be displayed. See it on the original post. -
Luke Dashjr reposted
Jim
@elkrun21
Yep. It can be corrupted if enough folks get lulled into inaction. Active participation is required. BIP-110’s success is going to prove to the world how bitcoin can remain incorruptible.
Luke Dashjr
@LukeDashjr
"Anti-fragile" always referred to the community behind Bitcoin ready to defend it from attacks.
-
Extractive Ghost of Unhosted Marcellus 👻
@oomahq
Banger from Greg Maxwell.
Not even kidding. This is from before he lost his marbles.Post not available here, view on X
Luke Dashjr
@LukeDashjr
"Anti-fragile" always referred to the community behind Bitcoin ready to defend it from attacks.
-
Luke Dashjr reposted
Hunter Beast 🕯️
@cryptoquick
I've been doing a lot of research into 110. My interest is in making sure that we do everything we can imagine to make sure Bitcoin is ready against every conceivable threat.
I still have found no valid technical, social, or financial reason against it, and I have strong arguments for.
I have reviewed Vortex's concerns that people often link to and don't find they hold up against close scrutiny.
I will be providing my own arguments in favor of 110 soon enough.
For now, I have signalled in support, and if anyone takes issue with my strong opinion, just know that I am willing to change my mind based on new input. Are you?
Knut Svanholm ∞/21M
@knutsvanholm
It's a very good day to reveal to the world that you support BIP-110!
-
Luke Dashjr reposted
-
Luke Dashjr reposted
Umbral
@UmbralShadows
Bingo.
If BIP-110 really would accomplish nothing, why would they be running a full out misinformation campaign to stop it? They are scared is why.
People now see how malicious actors have subverted the likes of "Andy" Back and Peter Todd and countless others. They've been attempting to centralize control through Core and large mining operations.
We are awake now and we're going to keep fighting to stop you. Run Knots, Run BIP-110 and use Ocean to mine. Once we get more trusted implementations operational, Core is done permanently. -
Luke Dashjr reposted
.
@GrassFedBitcoin
All this said, if we *do* want to speculate about an ongoing Sybil attack we probably need look no further than the *10,000 Core nodes* that went offline in July 2024 - all going back online again in an instant.
There may be another reasonable explanation for it but the outage lasted for longer than a week, meaning it's unlikely to be a an outage with some major cloud server.
If those nodes *are* fake then BIP-110 isn't at 16%, it's at 26%. -
Luke Dashjr reposted
Matthew R. Kratter
@mattkratter
You're trying to get me to say that Bitcoin dies unless BIP-110 activates. I'm trying to tell you that I don't know exactly when Bitcoin reaches the point of no return, but that we might already be there with the spam attacks, chain surveillance and KYC, Bitcoin Core going rogue, Saylor and Fink centralizing millions of coins and suppressing the price, mining pool centralization, lack of use of Bitcoin as a medium of exchange, Bitcoiners taking protocol advice from compromised figures like Andy Back and Greg Maxwell, while influencers cheer on the whole mess and make fun of those of us who are trying to fight back against all of these attacks. I'm grateful that you are operating as a Bitcoin merchant, but if you care about Bitcoin's future, you'll also dig deeper into what's going on and maybe even join us in the fight. Once you actually understand the situation, you'll want to join the BIP-110 army. There are a few news items on the way that are going to shock you to your core, and maybe then you'll understand the seriousness of the situation
-
Luke Dashjr reposted
Extractive Ghost of Unhosted Marcellus 👻
@oomahq
Banger from Greg Maxwell.
Not even kidding. This is from before he lost his marbles. -
Luke Dashjr reposted
Lilly
@JustaLillyBit
I find it ironic that it doesn't sound off any alarms that the anti-bip110 people are in the epstein files 🤷♀️
-
Luke Dashjr reposted
Sisters of Aquinas @ QAS Online Academy
@sistersaquinas
-
Luke Dashjr reposted
Sodium #BIP-110
@sodiumbtc21
Lets do this again,
If BIP110 gets consensus will Bitcoin be worse money or better? -
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
Meanwhile, users who upgraded to BIP110 have none of these risks. Bitcoin just continues to work for us as if nothing happened. In fact, it works better than before, because spam is being mitigated.
-
Post not available here, view on XPost not available here, view on X
Luke Dashjr
@LukeDashjr
Meanwhile, users who upgraded to BIP110 have none of these risks. Bitcoin just continues to work for us as if nothing happened. In fact, it works better than before, because spam is being mitigated.
-
Luke Dashjr reposted
Dathon Ohm / BIP-110
@dathon_ohm
ATTENTION. THIS IS NOT A DRILL.
BIP-110 mandatory signaling begins at block height 961632 (in about 6580 blocks or about 45 days from now).
All miners must begin signaling readiness for BIP-110 (versionbit 4) by that time, or their blocks will be discarded as invalid.
(1/8) -
Luke Dashjr reposted
.
@GrassFedBitcoin
Also - FAR TOO FEW OF YOU ARE RUNNING NODES.
How can I have more followers than there are listening nodes on the network?? -
Luke Dashjr reposted
Justin Bechler
@1914ad
How many times must @LukeDashjr save Bitcoin and how long must he warn us of an existential crisis before we listen and consider that he might just be right? #rdts #bip110 🧡
-
Luke Dashjr
@LukeDashjr
Certain bad actors are trying to distract you with lies about me supposedly calling for a hardfork or proof-of-work change/removal.
Let me be perfectly clear: I do not at this time support either.
Luke Dashjr
@LukeDashjr
Both are important tools the Bitcoin community always has available if ever needed, and people shouldn't be afraid to discuss them; but the current situation does not warrant their use.
Luke Dashjr
@LukeDashjr
(The tools are hardforks and PoW change only; PoW removal is not such a tool; there's still no sane alternatives to proof-of-work!)
-
Luke Dashjr reposted
Joyce Dawn
@BitcoinWifey
Most criticisms of BIP110 come from people who don’t understand the history that made BIP110 necessary.
If your understanding of BIP110 is “people are trying to change Bitcoin” you’ve missed the entire argument.
Here’s the timeline as I understand it. Please comment if I missed anything or made any mistakes.
1/ Bitcoin originally had anti-spam protections.
Satoshi implemented the first spam filters, and suggested there were “other things we could do if necessary” when trying to prevent use of the blockchain for arbitrary data.
Developers unanimously agreed that data storage was discernable, undesirable and to be discouraged
2/ SegWit introduced discounted witness space.
This was so that UTXOs were more cheap to consume than create. It was deliberately not made too large as there were concerns about it being used for spam.
Meant for scaling.
People that would use it to store non-monetary data would still be limited by the existing spam filters.
3/ Taproot increased script flexibility and bypassed existing filters.
Meant for privacy and smart contracting.
Created new ways to embed arbitrary data that would be relayed by the entire network before being mined
4/ Developers discovered the loophole.
Large amounts of non-payment data could now be stored more efficiently than before.
5/ Ordinals, inscriptions, tokens, and data schemes appeared.
6/@LukeDashjr proposed fixes.
He argued the bug was understood and fixable - simply subject taproot spends that reveal large amounts of frivolous data to the existing limits that applied to data storage elsewhere.
Core declined to update the filters and fix the bug with taproot.
7/ A new philosophy emerged inside Core.
“If it’s valid at the protocol level, it cannot be spam.” A standard that does not exist on any other protocol.
This replaced Bitcoin’s traditional anti-spam posture.
8/ Financial interests formed around the loophole.
Companies, exchanges, token issuers, NFT projects, and infrastructure providers began profiting from non-payment usage.
9/ The longer it would remaine open, the weaker Bitcoin would become, on a cultural level and on a technical level due to massively decreasing its efficiency as a payment network
Businesses were created with the expectation of a passive network that would not defend itself.
Non Bitcoin users became invested in the schemes.
Economic interests formed around preserving them.
10/ Core then went from failing to fix the filters to intentionally removing them in Core 30.
This was presented as “neutrality”.
Instead it was active solitication of parasitic use cases. They had moved from ignoring/tolerating spam to accommodating it.
11/ Trust in Core governance began to erode.
The issue was no longer inscriptions.
The issue was now the need to redefine Bitcoin as a solely monetary network, not a permissionless file storage network as that would create problems for users very quickly.
This is when @BitcoinKnots became popular.
12/ BIP110 was proposed - written by @dathon_ohm
To restore Bitcoin’s original anti-spam posture.
Not a new direction, but a revival of a network hostile to non-monetary usage.
To summarize:
First the loophole was created..
Then people exploited it..
Then businesses formed around it..
Then the businesses corrupted the trusted developers in the space who are now being fired as the network drops their client.
Because of all this, saying “large OP_RETURNs have always been consensus-valid” is completely disingenuous - a red herring at best. -
Luke Dashjr reposted
Renaud Cuny
@CunyRenaud
Spam on Bitcoin — Last 7 days:
~70% of all transactions are non-monetary
473.95 MB of non-monetary data (50.8% of Tx vsize) permanently stored on every full node
Bitcoin is being bloated by non-monetary traffic. BIP-110 is the cure.
Run Knots + BIP-110 -
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
Miners have no reason to try to undermine Bitcoin, though. And there's no reason to expect they will this time. A majority of hashrate has already begun testing BIP110. They're just slow.
-
Post not available here, view on X
Luke Dashjr
@LukeDashjr
Miners have no reason to try to undermine Bitcoin, though. And there's no reason to expect they will this time. A majority of hashrate has already begun testing BIP110. They're just slow.
-
Luke Dashjr reposted
Bitcoin y Lightning Guadalajara
@btc_ln_gdl
Bitcoin is money.
We support BIP-110 and are running it on our own nodes because we believe Bitcoin should remain accessible, practical, and useful as a decentralized payment system.
Read our statement:
btcgdl.com/bitcoin-lightning-guadalajara-statement-suppor… -
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
BIP110 failing would mean either the Bitcoin community supports turning it into a CSAM sharing network, or that the community can be successfully gaslit into doing so unknowingly, or that someone else other than the community controls Bitcoin.
In none of those scenarios does Bitcoin have any reasonable hope of fulfilling its purpose. -
Post not available here, view on XPost not available here, view on X
Luke Dashjr
@LukeDashjr
BIP110 failing would mean either the Bitcoin community supports turning it into a CSAM sharing network, or that the community can be successfully gaslit into doing so unknowingly, or that someone else other than the community controls Bitcoin.
In none of those scenarios does Bitcoin have any reasonable hope of fulfilling its purpose. -
Luke Dashjr
@LukeDashjr
If you don't want Bitcoin to change to allow data storage (ie, Core30), then you want BIP110.
BIP110 is just itself a counter-fork to reject Core30's controversial changes.
Without it, a tiny fringe minority would have succeeded in materially changing Bitcoin without consensus. -
Luke Dashjr reposted
Majorian
@MajorianBTC
This is a point that flies under the radar. Filters were working, which is why Core 30 was needed.
The 'miner centralization' excuse to do Core 30 was BS, mining was and is already centralized.
Ocean is reversing this, yet Core rails against Ocean.
David Noriega
@BlueDavid
Crickets 🦗🦗
-
Luke Dashjr reposted
Majorian
@MajorianBTC
BIP-110 is designed in a game theoretic way such that the best move for everyone is to signal BIP-110 support.
Groan, bitch, complain, have at it.
But the BIP-110's actual content is fine for bitcoin and to reject the BIP actively results in a chain split. -
Luke Dashjr reposted
.
@GrassFedBitcoin
Important overlooked point. The "blocksize limit" is variable - it's not fixed, it depends on what is being put in the chain.
Input spam can take blocks all the way up to the theoretical maximum that was never expected when coming up with the "block weight" concept.
Result? The blockchain raced to 1TB faster than expected and continues to grow faster than it should have.
Bitcoin Infinity Media
@BtcInfinityShow
BIS #207 with @secsovereign out now!
This media couldn't be displayed. See it on the original post. -
Luke Dashjr reposted
stepnoy🪢
@stepnoy385394
BIP110 is Bitcoin's antifragility in action
Luke Dashjr
@LukeDashjr
BIP110 is Bitcoin's antifragility in action
-
Post not available here, view on X
Luke Dashjr
@LukeDashjr
BIP110 is Bitcoin's antifragility in action
-
Luke Dashjr reposted
HardDuke 1 year coinbase maturity
@DukeDukingtonRD
If you're on the fence about bip110 because you think
"Miners won't go for it"
What would happen if we signalled for an upgrade where the coinbase reward from mining is halved?
Yes that's right, we _do_ do that every 4 years, and miners hate it, but _have to_ go along with it. -
Luke Dashjr
@LukeDashjr
At this point, upgrading to BIP110 is a simple security matter. It has sufficient community deployment already to happen. Not upgrading only makes your node vulnerable.
Everyone should support RDTS, but the question has moved on from "do you support it?" to "are you ready?" -
Luke Dashjr reposted
XBT | Hardfork cguida | ⚡🪢
@cguida6
Core30 is a test to see whether the dominant bitcoin client can stab the noderunners in the back while laughing in their face after the noderunners repeatedly said "stop, you're hurting us!", and get away with it
-
Luke Dashjr reposted
XBT | Hardfork cguida | ⚡🪢
@cguida6
It's time for bitcoin businesses to rally behind bip110
Every bitcoin business that doesn't vocally support bip110 at this point should be asked why
If the answer is "we're waiting for other people to go first", they should be shamed -
Luke Dashjr reposted
Justin Bechler
@1914ad
🧡 What BIP-110 supporters do:
- Use Bitcoin as money
- Run nodes
- Educate tirelessly
- Control 4 EH hashrate
- Decentralize Bitcoin
⚠️ What BIP-110 opponents do:
- cry on 𝕏
- censor discussion
- gaslight
- ostracize and socially pressure
- obfuscate Core malfeasance -
Luke Dashjr reposted
hodlonaut
@hodlonaut
Where do you stand?
-
Luke Dashjr reposted
hodlonaut
@hodlonaut
Bitcoin’s most crucial property is being decentralized.
That is not compatible with being governed by a deceitful and arrogant priesthood of funders and developers who censor and exclude opposition while pretending to be responsible stewards of the Bitcoin ethos. -
Luke Dashjr reposted
Extractive Ghost of Unhosted Marcellus 👻
@oomahq
In a nutshell, Core's vision of Bitcoin is that all participants of the network are slaves to malicious transaction crafters.
If you're a regular user and your normal transactions gets outbidded by porn GIFs and orangewashed VC-funded shitcoins that's too bad it's the free market, suck it up. If you're a node runner and don't want to relay and facilitate the garbage that's too bad your mempool needs to predict what will get mined, suck it up. If you're a miner and don't want to help these bad actors that's too bad you need to take their fees or you'll go bankrupt, suck it up. And let's not even get into participating in consensus rule governance, it is up to sanctioned developers and large pools to plan and activate forks!
I truly don't get why anyone holding this mental model would be interested in Bitcoin. Fortunately it's completely upside-down: in reality all participants are fully sovereign to do what they please, otherwise Bitcoin wouldn't be a decentralized system. Each node runner is free to relay whatever transactions he wants following whatever criteria he wants. And each miner is also free to prioritize transactions for mining following whatever strategy he wants, and signal for whatever forks he supports.
A sane full node software strives to maximize its user's sovereignty and give them tools to wield against bad actors instead of chipping away said sovereignty release after release. While Core doesn't correct course and is still widely used there will be room for other implementations to eat away its market share. -
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
Hmm, maybe it's obvious to others, but I just realised: 2017 was also *supposed* to have the dev team backing the takeover. They just didn't expect Gavin to be sidelined so easily.
-
Post not available here, view on XPost not available here, view on X
Luke Dashjr
@LukeDashjr
Hmm, maybe it's obvious to others, but I just realised: 2017 was also *supposed* to have the dev team backing the takeover. They just didn't expect Gavin to be sidelined so easily.
-
Luke Dashjr reposted
Joe Antek.
@joeantek
It is highly possible and probable that failure of #bip110 (and continuation of allowing 100k op_return) will end #bitcoin as a truly decentralized store of value.
Bitcoin would continue to run but with a tiny fraction of the current node counts, making it a pointless centralized blockchain like most of crypto.
No other chain has anywhere near the decentralized and distributed node count as bitcoin, not even close.
That is why this attack vector via storage of large contiguous extra data was created - to break down the decentralization of bitcoin.
HardDuke 1 year coinbase maturity
@DukeDukingtonRD
All bip110 nodes will turn off if bip-110 doesn't activate. Other suckers can be tricked into storing pornographic jpegs but not us. Bitcoin is dead if the miners tell us what changes we can and can't implement.
-
Luke Dashjr reposted
Va♰oshi
@Vatoshi
BIP-110如果失败,那就证明比特币缺乏抵抗政府社会工程学攻击的能力
-
Luke Dashjr reposted
BTCbello #BIP-110
@Bitbello
If bitcoiners don't get their act together & don't fully support BIP-110/RDTS to wipe out Core & their Corecoin version of Bitcoin, Bitcoin WILL NOT survive in the long term, at least as a sovereign/decentralized/P2P money/network. Make no mistake. It's almost too late already.
hodlonaut
@hodlonaut
CAPTURE
An investigation across four articles into how informal power over Bitcoin Core was assembled, exercised, and defended.
Article Three: The Merge
www.citadel21.com/the-merge -
Luke Dashjr reposted
Divinely Designed
@DivinelyDesined
The evidence for God is obvious.
-
Luke Dashjr reposted
Dathon Ohm / BIP-110
@dathon_ohm
This period has been our most successful period yet, with more than double the hashpower of the last period!
Every period more miners are signaling readiness for BIP-110.
Prepare for activation!
Dathon Ohm / BIP-110
@dathon_ohm
I am pleased to report that there has been a flurry of new BIP-110 blocks, and that our hashrate has roughly doubled since last period: bip110monitor.com
-
Luke Dashjr
@LukeDashjr
Reminder that 73% of Bitcoin nodes today support and enforce (to one degree or another) the rules made firm by BIP110; and until last October (2025), that was 99%.
Luke Dashjr
@LukeDashjr
Luke Dashjr
@LukeDashjr
And 73% is likely a _lower bound_. It doesn't mean 27% support CSAM. More likely the 27% are sybils or ignorant/gaslit, and would also support BIP110 if they understood what was going on.
Post not available here, view on X
Luke Dashjr
@LukeDashjr
And 73% is likely a _lower bound_. It doesn't mean 27% support CSAM. More likely the 27% are sybils or ignorant/gaslit, and would also support BIP110 if they understood what was going on.
Post not available here, view on X
Luke Dashjr
@LukeDashjr
Every little bit helps. Don't let the pundits discourage or downplay your role. The community is made up of lots of individuals.
-
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
Every little bit helps. Don't let the pundits discourage or downplay your role. The community is made up of lots of individuals.
-
Luke Dashjr reposted
Danny
@Truth_matters20
Thank God for giving us the Bible to correct this heretical nonsense.
Jesus: "I am the way, the truth, and the life. No man comes to the Father but by me." —John 14:6 -
Luke Dashjr
@LukeDashjr
The main reason I didn't merge privatebroadcast to @BitcoinKnots, was that I judged it to be underreviewed and prone to bugs.
Since Core merged it in January, there were several followup fixes proving I was right, even before 31.0 was released.
They went ahead and released it anyway.
Bitcoin Core Project
@bitcoincoreorg
We have become aware of a privacy bug in the -privatebroadcast feature, newly introduced in Bitcoin Core 31.0, that may cause the originator’s IP address to be revealed to the receiving peer under certain network conditions. A fix is forthcoming and will be released with 31.1.
Luke Dashjr
@LukeDashjr
-
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
Bitcoin has survived 17 years _with_ the RDTS rules.
It has only been "without them" since last October, a mere 8 months, and has been in mortal peril that entire time. It's only a matter of time until Bitcoin dies with this new status quo. RDTS is the only way to prevent that. -
Post not available here, view on X
Luke Dashjr
@LukeDashjr
Bitcoin has survived 17 years _with_ the RDTS rules.
It has only been "without them" since last October, a mere 8 months, and has been in mortal peril that entire time. It's only a matter of time until Bitcoin dies with this new status quo. RDTS is the only way to prevent that. -
Luke Dashjr reposted
Sodium #BIP-110
@sodiumbtc21
The only rebuttal coretards have against the many many valid BIP-110 arguements is that BIP-110 isn't going to activate.
-
Luke Dashjr
@LukeDashjr
Hopefully these get so frequent it's considered spammy
PyBLØCK
@_PyBlock_
Twenty-seventh #bip110 Block!
Congratulations to #bip110!
Thanks @Dathon_Ohm & @LukeDashjr! -
Luke Dashjr reposted
kongzi
@__kongzi__
12% of the network is running BIP110 nodes.
100% of the network accepts BIP110. -
Luke Dashjr reposted
Ned17Flanders Let Freedom Ring
@Ned17Flanders
People claiming that we have to accept the rules and consensus of bitcoin are forgetting that core v30 drew first blood with the blow out of op-return.
BIP-110 will return us to pre v30 consensus. -
Luke Dashjr reposted
skot
@skot9000
The idea that miners will switch pools if one gets too big is dead and buried.
And the big pools know this; it would be trivial for them to cover up the percentage of network hashrate they have if they thought their customers cared.
Luke Dashjr
@LukeDashjr
-
Luke Dashjr
@LukeDashjr
Basically the position all miners should have.
Miners don't decide the rules; they just follow them.
Roughnecks
@Roughnecks110
I don't know what that is. I'm just following what the nodes want
-
Luke Dashjr reposted
.
@GrassFedBitcoin
Number of BIP110 signalling blocks: 25
Number of URSF signalling blocks: 0
Super Testnet
@SuperTestnet
Bip110 is actively malicious software. I encourage devs to encode their opposition by writing a *good* URSF against it. Here is a starting point: github.com/supertestnet/ursf-110
I also encourage node runners to review and run *good* URSF software (i.e. not mine)This post is unavailable. See it on X. -
Luke Dashjr reposted
.
@GrassFedBitcoin
This is the appropriate stance to take.
It says that as a business, you have tested the incoming UASF and you are ready to adapt to changing consensus rules.
No serious business in Bitcoin can afford to appear negligent when it comes this.
Last time plenty of businesses made announcements similar to the one below, and those that went further offering more vocal support increased their popularity and gained loyal customers as a result - @coinkite and @BULLBITCOIN_ being two great examples.
slush
@slush
For purposes of coin.dance reference link, I'm tweeting that TREZOR is at least ready for UASF.
-
Luke Dashjr reposted
Adam Simecka
@AdamSimecka
Curious where you guys stand.
-
Luke Dashjr reposted
Simple Steve 🌌
@SteveSimple
OP_0 preceding OP_IF means "if FALSE equals TRUE" then proceed.
This is how the hack works to put unexecutable code on-chain.
The hack was employed in 129,980,558 instances out of the total 130,452,396 times OP_IF was used (96.64%)
On GitHub
github.com/Unbesteveable/taproot-opif -
Luke Dashjr reposted
Kiawtzin
@kiawtzin
My TLDR from this thread: Just because there are toys devs never use that bip110 takes away does not mean it is acceptable for them to throw a tantrum and attempt to block a fix that is urgently needed to preserve bitcoin's decentralization and purpose.
XBT | Hardfork cguida | ⚡🪢
@cguida6
>Excellent, then fix the bip
The bip is fine, we already discussed this
Just because there are toys that you never use that bip110 takes away does not mean it is acceptable to throw a tantrum and attempt to block a fix that is urgently needed to preserve bitcoin's decentralization and purpose
>I also concede that the particular code in the example I used is probably not optimized either for maximum privacy or maximum efficiency
Excellent! *This* is progress. Perhaps you would like to recommend to nunchuk that they update their recommended custom policy so it actually has benefits over the p2wsh version?
>But I do not admit that this concession makes it okay to break it.
As was already stated in our debate, it is a tradeoff that is effectively a no-brainer
Devs lose some toys that they never use (except to spam), and bitcoin gets to keep being decentralized money -
Luke Dashjr reposted
AsyncN8
@AsyncN8
BIP-110 opposition is a few Twitter grudges and scam coin investors. Meanwhile, thousands of node runners are here permanently & they aren't going anywhere, ever. They will never give up. Miners don't want that uncertainty hanging over them forever. In the end, BIP-110 activates
-
Luke Dashjr reposted
ꓘɨℓσꬺƄℓɑꓘҽ2ƄꓘɳσŦƨ \\ BTC = XBT
@Kilombino_
-
Luke Dashjr reposted
Luis Marcano 🦉 Bitcoin
@MarcanoFilms
As we approach the mandatory signaling window (~block 961,632 — early August 2026), each retarget period continues to show a measurable increase in the number of blocks signaling BIP-110.
@Roughnecks110’s 8th signaled block this period is further evidence of the growing voluntary support from sovereign miners committed to the temporary reduction of arbitrary non-monetary data.
This upward trend in signaling reflects increasing conviction ahead of the 55% early-lock-in threshold and the guaranteed enforcement phase. Steady, decentralized progress toward activation.
Monitoring: bip110monitor.com
#bip110 #bitcoin
Luis Marcano 🦉 Bitcoin
@MarcanoFilms
Congrats to @Roughnecks110 signaling the 8th BIP110 Block this period
mempool.marcanotrades.com/block/0000000000000000000063e04… -
Luke Dashjr reposted
.
@GrassFedBitcoin
Right, well the basis for "consensus" as defined in the past was never "everyone agrees" it was "the people against it don't have compelling arguments" - in which case BIP110 has consensus already, it's just not widely actively supported - yet.
-
Luke Dashjr reposted
boozy | XBT
@TheBoozles
Sweet. "Lets ignore 12% of the network, I'm sure the other miners won't signal...right?" RDTS is happening, guys! This is a big one for decentralization and protection from CSAM!
-
Luke Dashjr reposted
XBT | Hardfork cguida | ⚡🪢
@cguida6
My opening statement from this debate:
---------------------
BIP110 is a simple statement: "we reject Core 30’s proposed addition of data storage to bitcoin."
Bitcoin is money. That is the starting point. If we lose sight of that, we lose the plot.
The block size war was one of the defining moments in bitcoin history because it forced bitcoiners to answer a basic question: who is bitcoin for? Is it for large companies, exchanges, miners, and professional infrastructure providers? Or is it for ordinary people: pleb merchants, individual savers, and node runners, who need to verify the system for themselves?
In 2017, bitcoiners answered correctly. We rejected the bigblock roadmap because it put bitcoin on a slippery slope: whenever blocks fill up, make them bigger; when they fill up again, make them bigger again. That path leads directly to centralization. It prices out ordinary node runners, turns validation into a professional activity, and recreates the trusted intermediaries bitcoin was designed to eliminate.
But the bigblockers got one thing right: bitcoin must work as a payment system. Their mistake was thinking bigger blocks were the way to get there. The real path is conservative base-layer validation, combined with trustless off-chain protocols like lightning. That is how bitcoin can scale commerce while preserving decentralization.
The current conflict over data spam is part two of the block size war. Once again, the question is whether we prioritize node runners and people using bitcoin as money, or whether we allow other interests to consume scarce block space and raise the technical, economic, legal, and moral cost of running bitcoin.
The worst centralization pressure here is not merely that spam makes nodes more expensive (which it does). It is that arbitrary data storage creates the possibility of deeply harmful illegal material, including CSAM, being embedded in the chain. If that happens, fully validating archival node operators could be placed in the position of storing and distributing material they find morally abhorrent. Even if the legal analysis varies by jurisdiction, the social consequence is obvious: most decent people will not voluntarily run infrastructure that forces them into that position. Node running would become limited to large institutions with legal departments, specialized infrastructure, or people with no moral objection to hosting such material. That is an extreme centralization pressure, and it attacks bitcoin’s security model directly.
So the answer should be the same as it was in 2017: the protocol must protect node runners first. Pleb merchants, especially in poorer parts of the world, must be able to run nodes and conduct business without trusted intermediaries. If they cannot, bitcoin will become dominated by large corporations, custodians, and professional infrastructure providers.
That is why protocol changes should be rare and careful (unlike the removal of the opreturn filter). Unless a change is necessary to make bitcoin more useful as money, or to defend bitcoin against a serious threat, the default should be caution.
But caution is not ossification.
Bitcoin is not a museum piece. It is a living system in a hostile environment. If we pretend the current ruleset is perfect forever, bitcoin loses the ability to adapt to new attacks, incentives, and failure modes. Ossification only makes sense if the protocol is already perfect. It is not.
BIP110 addresses a real vulnerability: the possibility that the developers of the dominant node implementation adopt an ideology that turns against the user community they are supposed to serve. When the people maintaining the main implementation make it harder to run a node, harder to use bitcoin as money, and easier to treat bitcoin as generic data storage, node runners have a responsibility to respond.
This problem is made worse by a small number of influential developers who appear to have an effective pocket veto over consensus changes. They can support changes that create harmful unintended consequences, and then block or stall the fixes. That is an unhealthy level of centralization in the development process.
Core v30 was a breaking point. Before it, there was a delicate balance between consensus and policy: consensus was permissive enough to allow future upgrades, while policy was restrictive enough to discourage abuse. Now we are told that policy does not matter, that spam transactions should be treated like real payments, and that node runners should simply accept the consequences.
That argument is not serious. Core still maintains many policy limits. Nobody actually believes every possible transaction must be relayed and mined on equal terms. The question is not whether policy matters. The question is whose interests policy serves.
BIP110 is therefore a vote of no confidence in the current leadership of Bitcoin Core. Mistakes happen. But refusing to admit a mistake, refusing to fix the damage, and blocking others from fixing it is far more dangerous than the original mistake itself.
One side effect of that pocket veto is the bikeshedding treadmill. Leadership quietly opposes a fix, but instead of saying what would actually earn support, the discussion becomes endless nitpicking: this opcode, that activation path, this implementation detail. At some point, “review” stops being review and becomes a strategy for delay.
Ultimately, the node network does not need permission from Core leadership to defend bitcoin. Especially not when Core itself introduced or normalized the harmful behavior in question. BIP110 is on track to activate with or without their blessing.
And BIP110 is not merely defensive. I am very bullish on its activation because it breaks the consensus logjam, among other things.
Bitcoin needs other improvements if it is going to destroy the fiat standard. We need better payment systems. We need better custody tools. We need mechanisms like covenants, vaults, and more powerful trust-minimized point-of-sale systems. But the current process makes every consensus change feel impossible, because if any mistake is made, we are told we must live with it forever.
That is not conservatism. That is paralysis.
BIP110 shows that bitcoin can fix mistakes. It shows that unintended consequences from prior upgrades do not have to become permanent vulnerabilities. It shows that node runners can still act when the dominant implementation fails them.
So yes, I strongly support BIP110.
It reestablishes payments as the primary use case of the bitcoin blockchain.
It reasserts that bitcoin is money, not arbitrary data storage.
It protects node runners from being pressured into storing or distributing morally abhorrent material.
It reminds everyone that node runners - not developers, not corporations, and not miners - are ultimately in control of bitcoin.
And it proves that bitcoin can adapt. Not recklessly, not casually, but when necessary: to defend its decentralization, its usefulness, and its purpose.
Bitcoin survives because node runners enforce the rules. BIP110 is node runners enforcing the rules.
Thank you.
Forrest
@ForrestHODL
BIP 110 debate between @cguida6 on the side of BIP 110 and @SuperTestnet on the side against BIP 110.
youtu.be/qz-VdXUK8hY -
Luke Dashjr reposted
Kiawtzin
@kiawtzin
A field is infested with a locust pest, the crops are getting wrecked. Someone come up with a pesticide to kill the pest and some one screams: "Noo We shouldn't use that pesticide because it *could* affect someone that *might* be allergic to it" Is that reasonable opposition?
-
Luke Dashjr reposted
Nordrassil
@NordrassilRoot
“Some men aren't looking for anything logical, like money. They can't be bought, bullied, reasoned, or negotiated with. Some men just want to watch the world burn”
Alfred Pennyworth -
Luke Dashjr reposted
knight_bj-blake2b
@chunshengzhang3
They deliberately designed a type of transaction and then claimed that BIP-110 would affect their operations. In reality, however, this kind of transaction is not something people actually use, nor does it have any practical value in the real world.
Super Testnet
@SuperTestnet
mempool.space/signet/tx/3fd341abdc65dcc3bbf3c192f57ca9b1e…
That tx spends money from a Nunchuk wallet I made based on a sample miniscript policy they provide in their wallet. As you can see, it has OP_IF in its input script, and its keypath is disabled. BIP110 would break this address and others like it. -
Luke Dashjr reposted
Majorian
@MajorianBTC
"Spam gets solved at consensus, not policy. Propose something."
"YoUr ProPoSaL dOeSn'T fIx SpAm."
"We aren't debating this."
"Everyone can run whatever software they want."
"No one will run that."
"No one will signal for that."
"They aren't finding THAT many blocks." -
Luke Dashjr
@LukeDashjr
So many firsts here...😲
First lotto solo mined RDTS block.
First RDTS block not mined with DATUM Gateway (and first using ckpool software).
First RDTS block not mined using OCEAN.
PyBLØCK
@_PyBlock_
Seventeenth #bip110 Block!
Congratulations to the Solo Miner using Ckpool code by @CKPoolDev!
Thanks @Dathon_Ohm & @LukeDashjr! -
Luke Dashjr reposted
Luis Marcano 🦉 Bitcoin
@MarcanoFilms
BIP-110 activation could play out very differently than many expect.
Once nodes enforcing the new rules start rejecting blocks packed with spam and arbitrary data, a natural selection process begins.
Nodes that do nothing won’t be stuck on the bloated chain. They will automatically follow the chain that builds the strongest Proof of Work while staying valid under their rules.
Here’s the key: Bitcoin’s history shows the vast majority of real activity has always been monetary — moving value, not storing random data. Because of this, the cleaner chain carries the stronger economic weight.
That’s why I believe hashrate and users will gradually shift toward it.
Running Bitcoin Knots with BIP-110 today is how we actively support that cleaner outcome.
The network tends to converge on what actually works for sound money. -
Luke Dashjr
@LukeDashjr
The primary difference between a Bitcoin softfork vs hardfork, is their behaviour with regard to "do nothing" nodes.
If a node does nothing, then it automatically rejects a hardfork. On the other hand, it automatically accepts a softfork.
To accept a hardfork, you must upgrade your node.
To reject a softfork, you must upgrade your node.
(To accept a softfork, even if you are disinterested, you should still upgrade your node, to stay secure.) -
Luke Dashjr reposted
willo2
@willo2_Poly
I was just scammed for $500K by Polymarket.
I am "willo2", the top holder of YES on "MicroStrategy sells Bitcoin by May 31st".
Here's what happened: -
Luke Dashjr reposted
Renaud Cuny
@CunyRenaud
"Filtering arbitrary data is censorship. It betrays Bitcoin's neutrality."
It doesn't. Every protocol is defined by what it refuses to carry. A voice codec dropping oversized packets is not silencing speech.
A monetary network that won't defend its scope doesn't stay neutral. It just lets whoever has the most resources define its scope instead.
New issue: why Bitcoin isn't a bulletin board, even when the bulletins are noble.
blockspaceweekly.substack.com/p/issue28-the-freedom-text-… -
Luke Dashjr reposted
Fr. Timothy Geckle
@fr_geckle
Did you know that Luther also came to the position that reason must be sacrificed because it didn't allow for his rebellion against the Church?
God gave us an intellect and the ability to reason and expects us to use it. Faith and reason are not opposed to each other. If God or His Church has revealed or taught something, the only reasonable response is to accept it.
Amanda AMDG
@schmitt4545
And that is exactly why I left sedevacatism. Ultimately, you replace the Holy Ghost with human reason.
-
Luke Dashjr reposted
boozy | XBT
@TheBoozles
RDTS (BIP-110) is happening. Is your node updated? github.com/bitcoinknots/bitcoin/releases
-
Luke Dashjr reposted
Roughnecks
@Roughnecks110
We mined a BIP110 block. Let's GOOO!
Ocean Blocks
@ocean_blocks
⛏️ New Ocean Block Mined ⛏️
Block Height: 951929
Fees: 0.053 BTC
Subsidy + Fees: 3.178 BTC
Difficulty: 138.96T
Solver: Roughnecks
mempool.guide/block/0000000000000000000049c609df9f8a6ba71… -
Luke Dashjr reposted
ANTON
@Anton_Bitcoin
They hate Luke for continuously showing them mirror, since 2023. The below post is from 2025.
This is how long the conversation has been going on. There's no reasoning with Core or their apologists.
RDTS/BIP-110 is all but rushed.
Don't allow those banking cartel minions to highjack Bitocoin. Defend Bitcoin to remain money.
Run latest Bitcoin Knots node with RDTS/BIP-110.
Luke Dashjr
@LukeDashjr
NACK
The goals of transaction relay listed are basically all wrong. Predicting what will be mined is a centralizing goal. Expecting spam to be mined is defeatism. Helping spam propagate is harmful.
This OPED contradicts itself, presenting out of band relay as both negative and also "an important aspect of Bitcoin’s censorship resistance"
It ignores the lack of consent to spam by users/node operators, giving deference to the attackers and the malicious miners who might conspire with them.
It paints spam as "largely harmless", when the truth is the exact opposite. It treats abuse of the blockchain and nodes as legitimate "use cases" rather than the DoS attacks they actually are, and speaks of DoS attacks as if they were something distinct, thus implying spam isn't the same (which it is).
The OPED presents itself as aligned with "Bitcoin’s long-term health" which is objectively false, and "miners’ rational self-interest" which is also at least debatably false. -
Luke Dashjr reposted
Lori Singer Meyer
@Loriss65
If you haven't seen this video, it is well worth watching. After fumbling around with so many technical aspects of Bitcoin, this somehow brought me back to really getting that Bitcoin first and foremost is about the creation of a money. I finally get why there are so many Nick Szabo pieces on money. The structure in the Satoshi White Paper was created with reducing attack vectors, the most obvious being black letter law, but also with establishing Bitcoin as money. And whatever else money is, it is something recognized by a community that has value. This video made something click for me - nodes receiving Bitcoin reinforce that Bitcoin is being used within a community of like-minded people with respect to Bitcoin's monetary value. You lose that network of community reinforcement, and all the evils that Luke portrays in this video will befall.
What I haven't thought through yet is whether there is something intrinsic to everything Bitcoin that means it will ultimately fail as a money, or whether something went wrong at a critical point and but for that, Bitcoin might have achieved its purpose(s).
@NickSzabo4
BitcoinDay
@bitcoindayio
Jack Dorsey calls him the guardian angel of Bitcoin, and at BitcoinDay Naples, @LukeDashjr didn't hold back.
"Bitcoin has probably a single-digit percentage chance of surviving." 🤯
From the "malware" in Core 30 to why your full node is the only thing standing between Bitcoin and fiat, this is the most honest conversation on the timeline.
@BITVOLT from @SimplyBitcoin sat down for a high-stakes conversation about the technical and existential threats facing the network today.
If you aren't running a node or mining with @ocean_mining, you are trusting someone else with your freedom.This media couldn't be displayed. See it on the original post. -
Luke Dashjr reposted
Majorian
@MajorianBTC
As BIP-110's momentum continues, it is very important that you are informed as to what this proposal actually does.
Do your own research, don't let someone else choose your opinions for you.
Here is a simple summary:
Credit: @kwsantiago
Link: privkey.substack.com/p/bitcoin-has-a-squatter-problem-bip -
Luke Dashjr reposted
Sean Harris🏀
@BigSeanHarris
Unpopular Opinion: The Bitcoin Bear Market will continue until BIP-110 activates.
-
Luke Dashjr reposted
meme bastard 🍕
@mask_bastard
-
Luke Dashjr reposted
Jim | Bitcoin, not jpegs
@venorusprime
@ocean_mining with DATUM has already decentralized Bitcoin mining.
We're just waiting for the hashers to figure it out.
David Noriega
@BlueDavid
Even if Ocean had 100% pool dominance, Bitcoin mining would still be decentralized.
-
Luke Dashjr reposted
The Raven of Wall Street
@RavenofWallSt
Even if there is a chain split, the core chain will become so centralized among big institutions that it will be indistinguishable from ETH or XRP.
-
Luke Dashjr reposted
OCEAN
@ocean_mining
OCEAN
@ocean_mining
Taking a moment to celebrate OCEAN's 100th block milestone. OCEAN has seen a spectacular boost in hash these past few months.
And we're just getting started.
To our miners – Thank You.
To those waiting on the beach: come on in. The water's warm, and the blocks are flowing.
As of block 100:
432.95877508 BTC mined (including 20.45877508 BTC in transaction fees). -
Luke Dashjr
@LukeDashjr
sysctl -w kernel.io_uring_disabled=2
-
Luke Dashjr reposted
Super Testnet
@SuperTestnet
Ocean is now a top 8 mining pool
- more miners are discovering how to make their own block templates
- and that Ocean pays out more than other pools, since it has lower admin fees
- plus they offer LN payouts
- and, for large miners, coinbase payouts -
Luke Dashjr reposted
Mark Cook
@PatriotMarkCook
🚨 NATIONAL ALERT: ELECTIONS INFRASTRUCTURE EMERGENCY 🚨
The Cybersecurity and Infrastructure Security Agency (CISA), the federal agency tasked with securing U.S. election infrastructure, suffered a catastrophic breach. Sensitive credentials were exposed on a public GitHub repository for six months.
On November 13, 2025, a contractor created the “Private-CISA” repository. It remained public until May 15, 2026. The 844 MB leak contained plaintext passwords, high-privilege AWS GovCloud administrative credentials, SSH keys, authentication tokens, Entra ID SAML certificates, and internal system access details.
CISA is directly responsible for protecting the nation’s critical election infrastructure, including voter registration databases, voting systems, and polling infrastructure.
This incident demonstrates complete failure of basic operational security by America’s lead cybersecurity agency. Researchers called it one of the worst leaks observed. While CISA claims no compromise, the extended exposure window created significant risk of undetected exploitation.
An agency unable to secure its own credentials cannot be trusted to safeguard national elections.
🇺🇸 ELECTIONS NATIONAL STATE OF EMERGENCY 🇺🇸
CISA’s incompetence renders it unfit to oversee security for the 2026 midterms and beyond. Immediate independent audits, full breach disclosure, credential verification, and structural reform are mandatory.
Congress and the Executive Branch must act decisively. The integrity of American democracy is at stake.
Failure to address this crisis is unacceptable.
@realDonaldTrump @POTUS @FBIDirectorKash @DHSgov @CISAgov @CISACyber @DHSgov @TheJusticeDept
@ShawnSmith1776 @FSociety_1942 @EmeraldRobinson @PatrickByrne @pjcolbeck @ZoomWalter @ZarkFiles @PeterBernegger @immutablechrist -
Luke Dashjr reposted
boozy | XBT
@TheBoozles
The way it should be! @ocean_mining
-
Luke Dashjr
@LukeDashjr
RDTS in a nutshell.
Luke Dashjr
@LukeDashjr
"We reject Core30's proposed addition of data storage to Bitcoin"
-
Luke Dashjr reposted
.
@GrassFedBitcoin
1,300 downloads of latest Knots - on just the latest release of @umbrel
It's only been up since Friday. -
Post not available here, view on X
Luke Dashjr
@LukeDashjr
"We reject Core30's proposed addition of data storage to Bitcoin"
-
Luke Dashjr reposted
𓂀 | #BIP110
@__B__T__C__
It only takes approximately 20 years for BIP-54 to have any effect.
It only takes about 1 CSAM image for Bitcoin to die if BIP-110 isn't implemented.
It's up to you whether you use @bitcoincoreorg+BIP54 or @BitcoinKnots+RDTS. -
Luke Dashjr reposted
countingheights
@BlocksRemaining
11,784 blocks until BIP-110 activates
-
Luke Dashjr
@LukeDashjr
For a third-party candidate to win, they don't even need to convince a single Republican or Democrat!
Bill Madden
@maddenifico
The great American tragedy is in yellow. It's called ignorance and apathy.
-
Luke Dashjr reposted
GekkoScience 🇺🇸
@GekkoScienceLLC
Before Bitaxe, for an entire decade, GekkoScience has had a line of entry home mining "Terminus Pods."
This is the A2X, our most recent pod miner release.
Home Mining was never inaccessible or secluded to just sticks.
Sticks are great, but you have Always had the option for desktop sized Home Miners.
#honestyabovemarketingbs
gekkoscience.com/shop -
Luke Dashjr reposted
𓂀 | #BIP110
@__B__T__C__
Everyone should run the new version of @BitcoinKnots by @LukeDashjr with RDTS enabled.
Bitcoin is in danger if you don't activate it. -
Luke Dashjr reposted
BIP-110 Was Good For Bitcoin Monk
@BitcoinMonk21
Bitcoin core decided you will run bip54.
Michael Ford
@fanquake
BIP54 coinbase locktime has been set in ~5.5% of blocks over the last 30 days
-
Luke Dashjr
@LukeDashjr
If you find a security flaw, please follow the following steps in order:
1) Give details to upstream developers to develop or merge a fix
2) Notify downstream developers/distributors of the risk and how to patch it (not the details) so they can ship it ASAP
3) Give people at least a week to upgrade on their own
4) Notify the public that a vulnerability in the old version exists (no details)
5) After you can reasonably hope everyone has updated (months or years later), publish details and/or proof-of-concept
There may be circumstances (eg, active exploitation in the wild) that justify deviation from this, but generally, this is a good approach.
However, starting with #5 is black-hat behaviour. -
Luke Dashjr reposted
GrapheneOS
@GrapheneOS
Play Integrity API is clearly anti-competitive, anti-security and blatantly illegal. It isn't dangerously close to those but rather way over the line. App developers being able to directly use key attestation and explicitly allow specific non-Google software doesn't make it okay.
-
Luke Dashjr reposted
Bitcoin Knots
@BitcoinKnots
Bitcoin Knots 29.3.knots20260508 released, now with RDTS support! 🎉
Be sure to read the release notes and verify your download(s)! -
Luke Dashjr reposted
GrapheneOS
@GrapheneOS
Trying to portray someone as insane and delusional with fabrications isn't criticism. Our founder being upset with Rossmann in private after months and mistreatment from Rossmann doesn't absolutely justify him starting a massive harassment campaign based around blatant lies.
-
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
There's a distinction between data storage as a feature, and spam that can be misinterpreted as data. We CAN absolutely stop the former, and reliably. We can also mitigate the latter with filters.
-
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
The point is any blocks mined with the CSAM or built on it will be invalid and have no reward.
The only way miners don't lose money is to activate RDTS before CSAM gets uploaded. -
Post not available here, view on X
Luke Dashjr
@LukeDashjr
There's a distinction between data storage as a feature, and spam that can be misinterpreted as data. We CAN absolutely stop the former, and reliably. We can also mitigate the latter with filters.
-
Post not available here, view on XPost not available here, view on X
Luke Dashjr
@LukeDashjr
Probably. The soonest RDTS can activate is May 29th, and I expect to release a new Knots with RDTS before then.
Post not available here, view on X
Luke Dashjr
@LukeDashjr
No, it only takes one malicious miner (ie, running Core 30+) to force Bitcoin nodes of ANY type from now until the end of time, to actively participate in CSAM distribution.
Post not available here, view on X
Luke Dashjr
@LukeDashjr
If it takes more than 10 minutes, miners are going to take a loss, so better to be faster than that.
Post not available here, view on X
Luke Dashjr
@LukeDashjr
The point is any blocks mined with the CSAM or built on it will be invalid and have no reward.
The only way miners don't lose money is to activate RDTS before CSAM gets uploaded. -
Luke Dashjr
@LukeDashjr
If miners realised what a big gamble they were taking, they'd be rushing to activate RDTS as quickly as they can.
Luke Dashjr
@LukeDashjr
If it takes more than 10 minutes, miners are going to take a loss, so better to be faster than that.
-
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
No, it only takes one malicious miner (ie, running Core 30+) to force Bitcoin nodes of ANY type from now until the end of time, to actively participate in CSAM distribution.
-
Post not available here, view on X
Luke Dashjr
@LukeDashjr
You forgot to mention they knowingly chose to leave users vulnerable (unknown to the users) for 16 months
-
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
Probably. The soonest RDTS can activate is May 29th, and I expect to release a new Knots with RDTS before then.
-
Luke Dashjr reposted
Vincenzo Palazzo 🟥
@PalazzoVincenzo
Today, I found a bug in CLN with message padding in v26.04.1, and it looks like it was already present from v26.02
I found it because I was updating from v25.05, and make me wonder what kind of Core lightning node version you are running these days, that I was the first to hit it? -
Luke Dashjr reposted
Luke Dashjr
@LukeDashjr
"This update includes 127 security fixes."
chromereleases.googleblog.com/2026/05/stable-channel-upda… -
International Cyber Digest
@IntCyberDigest
‼️🚨 BREAKING: An AI found a Linux kernel zero-day that roots every distribution since 2017. The exploit fits in 732 bytes of Python. Patch your kernel ASAP.
The vulnerability is CVE-2026-31431, nicknamed "Copy Fail," disclosed today by Theori. It has been sitting quietly in the Linux kernel for nine years.
Most Linux privilege-escalation bugs are picky. They need a precise timing window (a "race"), or specific kernel addresses leaked from somewhere, or careful tuning per distribution. Copy Fail needs none of that. It is a straight-line logic mistake that works on the first try, every time, on every mainstream Linux box.
The attacker just needs a normal user account on the machine. From there, the script asks the kernel to do some encryption work, abuses how that work is wired up, and ends up writing 4 bytes into a memory area called the "page cache" (Linux's high-speed copy of files in RAM). Those 4 bytes can be aimed at any program the system trusts, like /usr/bin/su, the shortcut to becoming root.
Result: the next time anyone runs that program, it lets the attacker in as root.
What should worry most: the corruption never touches the file on disk. It only exists in Linux's in-memory copy of that file. If you imaged the hard drive afterwards, the on-disk file would match the official package hash exactly. Reboot the machine, or just put it under memory pressure (any normal system load that needs the RAM), and the cached copy reloads fresh from disk.
Containers do not help either. The page cache is shared across the whole host, so a process inside a container can use this bug to compromise the underlying server and reach into other tenants.
The original sin was a 2017 "in-place optimization" in a kernel crypto module called algif_aead. It was meant to make encryption slightly faster. The change broke a critical safety assumption, and nobody noticed for nine years. That bug then rode every kernel update from 2017 to today.
This vulnerability affects the following:
🔴 Shared servers (dev boxes, jump hosts, build servers): any user becomes root
🔴 Kubernetes and container clusters: one compromised pod escapes to the host
🔴 CI runners (GitHub Actions, GitLab, Jenkins): a malicious pull request becomes root on the runner
🔴 Cloud platforms running user code (notebooks, agent sandboxes, serverless functions): a tenant becomes host root
Timeline:
🔴 March 23, 2026: reported to the Linux kernel security team
🔴 April 1: patch committed to mainline (commit a664bf3d603d)
🔴 April 22: CVE assigned
🔴 April 29: public disclosure
Mitigation: update your kernel to a build that includes mainline commit a664bf3d603d. If you cannot patch immediately, turn off the vulnerable module:
echo "install algif_aead /bin/false" > /etc/modprobe.d/disable-algif.conf
rmmod algif_aead 2>/dev/null || true
For environments that run untrusted code (containers, sandboxes, CI runners), block access to the kernel's AF_ALG crypto interface entirely, even after patching. Almost nothing legitimate needs it, and blocking it shuts the door on this whole class of bug...Post not available here, view on X
Luke Dashjr
@LukeDashjr
"This update includes 127 security fixes."
chromereleases.googleblog.com/2026/05/stable-channel-upda… -
Luke Dashjr
@LukeDashjr
Irresponsibly disclosed, but all the bad actors know now, so better get this in front of the good guys too...
If you run Linux, you are almost certainly vulnerable.
Brian Pak
@brian_pak
Time to talk about this one.
CopyFail (CVE-2026-31431) — a 732-byte Python script that roots every Linux distro shipped since 2017. 🧵 -
Luke Dashjr
@LukeDashjr
I quit Dr. Pepper a few weeks ago, to reduce my sugar levels. But the alternatives I've tried (Zevia and Liquid Death) taste terrible.
Any real solutions? 😕
(Dr Pepper Diet and Zero have aspartame, which is apparently poison) -
Luke Dashjr
@LukeDashjr
It would have been worse to find this out later.
But really, only 8% of bitcoiners want Bitcoin to succeed? 😕
Has Core's gaslighting really been that effective?
Brad Wesley
@wesleybrad060
Things are very suspicious right now. Down to 7464 nodes?
-
Luke Dashjr reposted
㋡
reminder
Luke Dashjr
@LukeDashjr
False.
Core is a fork of Satoshi's original Bitcoin.
Satoshi himself never worked on Core. -
Luke Dashjr
@LukeDashjr
Don't imagine this can't happen to Bitcoin.
Alex Shevchenko 🇺🇦
@AlexAuroraDev
10h ago @litecoin experienced a coordinated attack on the chain that resulted in 13 blocks reorg that took more than 3h to generate.
During this time attackers were performing double spend attacks on multiple cross-chain swapping protocols.
We are investigating the situation. -
Luke Dashjr reposted
The Lunduke Journal
@LundukeJournal
Ubuntu 26.04 (Long Term Support) is shipping tomorrow… and Canonical has published an update on their quest to replace GNU CoreUtils with Rust-based re-writes.
Highlights:
- After developers raised “some serious concerns”, Canonical hired an external security research firm to evaluate the Rust re-writes (known as “uutils”).
- That security firm quickly found 113 significant issues, with a large portion of them being severe security issues warranting a CVE.
- Only some of those issues in the Rust re-writes have been fixed for the Ubuntu 26.04 release.
- Repeat: Ubuntu 26.04 is shipping with significant known issues in the new Rust coreutils.
- Some of the most critical Rust-Re-Written commands (cp, mv, and rm) were found to contain a large number of significant “Time-of-Check to Time-of-Use” issues, the kind of issues which create race condition vulnerabilities. The kind often exploited by hackers.
- As such, cp, mv, and rm will not be shipping in Ubuntu 26.04. Even with their clear “it’s fine if Ubuntu 26.04’s rust re-writes contain significant bugs” policy… the issues with cp, mv, and rm were simply TOO severe.
- Despite this undeniably disastrous rollout of the Rust-based rewrites of Coreutils, the Ubuntu team plans to ship the next release, in 6 months (26.10), with 100% of the GNU Coreutils replaced with the (currently comically broken) Rust re-writes.
discourse.ubuntu.com/t/an-update-on-rust-coreutils/80773 -
Luke Dashjr reposted
Extractive Ghost of Unhosted Marcellus 👻
@oomahq
A friend of mine who only lurks X has written a blog post about his first experiences renting hashrate for his DATUM gateway.
I think a lot of you would find this interesting, so I asked him for permission to share it more widely:
pablohere.contrapeso.xyz/writings/my-first-petahash.html -
Luke Dashjr reposted
HardDuke 1 year coinbase maturity
@DukeDukingtonRD
If you needed proof these large accounts against bip-110 have been bought by bad actors, all of them suddenly advocating _blatant confiscation_ after criticising us of slippery sloping to the sane outcome, should tell you all you need to know.
-
Luke Dashjr reposted
Sodium #BIP-110
@sodiumbtc21
🆒So far the entities constructing their own block templates on Ocean🆒:
1- OCEAN
2- ZettaPOW
3- Barefoot Mining
4- Peak mining
5- BDE
6- Data Factory
7- 234 Alberta
8- Simple Mining
9- Crestmont Fabrics Ltd
10- Penguin
11- SoV
12- HMTech
13- Sazmining
14- AbundantMines
Ocean Blocks
@ocean_blocks
⛏️ New Ocean Block Mined ⛏️
Block Height: 945028
Fees: 0.008 BTC
Subsidy + Fees: 3.133 BTC
Difficulty: 138.97T
mempool.guide/block/000000000000000000003b852e54645085a3e… -
Luke Dashjr reposted
Fr. Gabriel Lavery
@FrLavery
While the Novus Ordo is promoting the false "Divine Mercy" revelations/devotion today, it may be useful to share the actual text of the Holy Office decree against it in 1958.
Many people are aware of the 1959 public "Notification" of the Holy Office, which was published in the Acta Apostolicae Sedis and in the Vatican newspaper. This was signed by Monsignor Hugh O'Flaherty, whom many would recognize from the movie, "The Scarlet and the Black," or the book, "The Scarlet Pimpernel of the Vatican." This is the Msgr. O'Flaherty who saved so many Jews and others during WWII in Rome at the risk of his life. He did not issue this notification, of course, but signed it as notary.
Many are not aware that this 1959 notification was the sequel to an earlier document in 1958 which was not published publicly in the A.A.S. but was sent privately to the bishops in Poland.
There is a principle in regard to decrees for or against devotions that approvals must be public, while condemnations need not be public in order to be binding, but are often privately issued. The reason for this is because new devotions, and especially purported revelations, are automatically forbidden from being published *until* they have approbation. There is no need for the condemnation to be public in order for them to be forbidden, since they are forbidden "de jure."
If an individual bishop has given approbation to publish, but the Holy Office decides to the contrary, it is only necessary for the Holy Office to send notice to the bishop to revoke approbation and remove the devotion or published volumes of revelations. This was the case, for example, in regard to the supposed Holy Face revelations of Sr. Mary of St. Peter which were condemned by decree of the Holy Office in 1897 as not having the character of true revelations and as containing novelties harmful to the piety of the faithful. The bishop of Tours in France was sent this decree privately.
Likewise with this 1958 decree against the Divine Mercy devotion and purported revelations. It was sent privately to the bishop concerned, but was published ultimately in the "Acta Ordinis Fratrum Minorum" (Acts of the Order of Friars Minor) in 1959. From there it was copied and published in volume II of "Leges Ecclesiae" in 1969, which is an unofficial collection of decrees from various sources and highly useful for finding things. This image is a photo I took 12 years ago from "Leges Ecclesiae" to add to my abundant files on condemned or false devotions.
The text of the Latin in this decree says that the "alleged revelations" do not have a supernatural character, that a feast of the Divine Mercy is not to be instituted, and that the promulgation of images or writings promoting the devotion in the form advocated by Sr. Faustina is forbidden.
Notice that there is an ellipsis (...) after point number 3 of the decree. That seems to indicate that part of it was omitted when it was published publicly in the Franciscan Acta or perhaps when copied from there to Leges Ecclesiae. Other sources indicate that this last part of the decree was an order to give a stern admonition to Fr. Michael Sopoćko, her confessor, to cease defending and promoting these spurious revelations and devotion. Likely, this was left out of the published version to spare embarrassment to Fr. Sopoćko.
Unfortunately, as often happens in these matters, devotees of the false revelations continued to spread them despite the condemnation from Rome and the bishop's actions to stop it. This same behavior has been repeated many times throughout history when disobedient Catholics think they know better than the Church. Excuses are always made that Rome "didn't have the correct texts" when condemning something, or didn't have all the facts. As Pope St. Pius X said once to priests, excuses come easy to those who do not want to obey.
Normally, this disobedience to the Church never gets anywhere, and occasionally it leads to even harsher measures like excommunication. However, in this case, the timing of the condemnation lined up with the beginning of a long series of false popes. So the supporters were able to obtain a complete reversal under false pope JP2 from Poland in 1978. Of course, we do not recognize this reversal and the devotion and "revelations" remain forbidden. -
Luke Dashjr
@LukeDashjr
OCEAN doing what it set out to accomplish🦾
Instead of two blocks made by the same pool, we get blocks made by two independent miners, exactly the same as if they weren't using any pool at all! -
Luke Dashjr reposted
BitcoinDay
@bitcoindayio
Jack Dorsey calls him the guardian angel of Bitcoin, and at BitcoinDay Naples, @LukeDashjr didn't hold back.
"Bitcoin has probably a single-digit percentage chance of surviving." 🤯
From the "malware" in Core 30 to why your full node is the only thing standing between Bitcoin and fiat, this is the most honest conversation on the timeline.
@BITVOLT from @SimplyBitcoin sat down for a high-stakes conversation about the technical and existential threats facing the network today.
If you aren't running a node or mining with @ocean_mining, you are trusting someone else with your freedom.This media couldn't be displayed. See it on the original post. -
Luke Dashjr
@LukeDashjr
Open Letter from [Catholic] Laity to [our] Bishops and Clergy (exhoring the election of a legitimate pope)
www.unamsanctam.org/open-letter -
Luke Dashjr reposted
Majorian
@MajorianBTC
Things the BIP-110 supporters are doing:
- Running their own full node
- Contributing to decentralized mining with home mining/has renting via DATUM
- Contributing to decentralized bitcoin development
Things Core 30 supporters are doing:
- Making spam more prolific on bitcoin -
Luke Dashjr
@LukeDashjr
Happy Easter everyone! Christ is risen!
-
Luke Dashjr
@LukeDashjr
Did @X remove the long-form bios???
-
Luke Dashjr
@LukeDashjr
I am pleased to announce I will be re-joining the Bitcoin Magazine team. It has been over a decade since I last worked as a technical editor, but the time has come to help them with their mission once again, this time as an intern proofreader.
Luke Dashjr
@LukeDashjr
Welp, so much for that, I'm fired already. I accidentally Shinobi's cat. Apparently not allowed to mess up even once! What's with that???
Hope everyone else had an enjoyable day! -
Luke Dashjr reposted
Bitcoin Knots
@BitcoinKnots
To better serve our sponsors, today we are announcing that Bitcoin Knots has been acquired by Bitcoin Core.
This will open the mine field to support for Ordinals, Runes, Bcash, and other NFTs or FSTs, and restore the node monopoly lost over the last year, making us lots of money -
Luke Dashjr
@LukeDashjr
From the bad actors' gaslighting, it's clear too many people still aren't aware of the case against big blocks.
Watch this to build up your immunity to them.
www.youtube.com/watch?v=CqNEQS80-h4
Luke Dashjr
@LukeDashjr
@grok Can you give a text summary here covering everything in the video?
-
Luke Dashjr reposted
Jason Hughes
@wk057
I'm unsure what exactly happened here with Foundry.
@b10c's post has the nitty gritty details... but I guess I can add some interesting points:
⁉️None of the nodes I run or have access to ever saw Foundry blocks or headers for 941881 or 941882 until after 941883 was mined and came through... including nodes peered directly with some known Foundry-controlled nodes.
⁉️No DATUM miner on OCEAN ever built work on top of either Foundry block 941881 or 941882 (around a thousand globally diverse nodes).
Now for some commentary... While the former point above is interesting in itself, it's certainly an incomplete picture.
The latter point is quite intriguing, though, since this is NOT how other splits have shown up in that data to-date... and for a two-block split I'd have expected something quite noticeable.
For background, DATUM miners all run their own nodes to generate their own mining templates from their own view of the network and mempool policies.
During a race on the network between multiple blocks, generally some % of the DATUM miners will see different sides of the chain and work on it as they see it until the eventual convergence brings everyone back to the same block to build on. From the pool's perspective, this is all fine, since both chains are valid and contain all of the pool's blocks. With around a thousand unique nodes run by different miners around the world, this is to be expected and gives some insight into forks overall.
This latest two block reorg was different, though, as not a single DATUM miner was building on either of the two eventually-winning Foundry blocks at 941881 or 941882. From my POV, there was zero indication of a race happening until Antpool and ViaBTC's blocks were poofed out of the chain.
I do see in @b10c's data that some of his nodes eventually got headers for Foundry's first block after ViaBTC's block, which makes this even more interesting since I'd presumed headers would propagate pretty quickly. If some of his nodes saw it before 941883, that makes this even more of a mystery to me.
A disturbing bit is that this is actually what a 51% attack targeting removal of a couple of blocks could actually look like. Generally you wouldn't need to give a public indication of success or attempt until you were successful. That's what seemed to happen here if viewed in a bit of a vacuum. (I'm not saying this was an attack, just that this is what one would look like.)
Important to know you really don't need 51% to pull off a few blocks of reorg consistently. For example, Foundry has more than enough centralized hash rate to have a _very_ high chance of success if they were to do something like this intentionally.
It's one of the reasons solving mining (de)centralization is so important. A centralized pool with 30-40% of the network has a solid chance of being able to "unconfirm" transactions they don't like or want to censor, do double spends, etc.
With miners working on decentralized templates using DATUM, this is basically impossible because there's no centralized control of transaction selection, even if 100% of the network were on the same DATUM pool.
Anyway, I take this as a reminder that mining centralization is a problem we should keep working to fix. Let's keep Bitcoin permissionless and censorship resistant. Mine with DATUM.
b10c
@0xB10C
We just had a rare-ish two block fork/reorg between Foundry and AntPool+ViaBTC. Foundry mined six blocks in a row.
bnoc.xyz/t/two-block-reorg-at-height-941880/97 -
Luke Dashjr reposted
Justin Bechler
@1914ad
Crypto startup executes massive spam attack on Bitcoin L1.
Silence from Core™
Bitcoiners announce a conservative new implementation.
Outrage from Core™ -
Luke Dashjr
@LukeDashjr
Literally decided by mining centralisation...
b10c
@0xB10C
We just had a rare-ish two block fork/reorg between Foundry and AntPool+ViaBTC. Foundry mined six blocks in a row.
bnoc.xyz/t/two-block-reorg-at-height-941880/97 -
Luke Dashjr reposted
₿itcoin ₿ombadil
@BitcoinBombadil
Core Simps today would be like “it’s consensus valid Bitcoin, so who are we to judge? If Bitcoin can’t survive 184M new Bitcoin, then maybe it’s not as strong as we thought.” 🤡
Run Knots + BIP-110
Sweep
@0xSweep
A single person once minted over 184 BILLION Bitcoins
In 2010 someone exploited a bug in Bitcoin's code and generated 184,467,440,737 BTC in a single transaction on a blockchain that was only supposed to have 21 million total supply
Satoshi and the developers caught it within 5 hours and pushed Bitcoin's first ever emergency fork to erase the transaction -
Luke Dashjr reposted
Toine
@TronMonGone
I don't know if someone has already done this, but I'd like to start a list of businesses that support BIP 110.
The main reason is so like minded people can support each other's businesses.
Please feel free to add companies in the replies:
256heat.com -
Luke Dashjr reposted
spoon
@spoonmvn
For a moment it looked like this brutal Core™ v30 bear market was ending.
Then they released v31. 🤦♂️ -
Luke Dashjr reposted
Devuan GNU/Linux
@DevuanOrg
Found yet another high severity systemd bug in Ubuntu: local root privilege escalation (CVE-2026-3888) cybersecurity88.com/news/ubuntu-cve-2026-3888-timing-flaw… Let us wish all Devuan users a wonderful day out with their family for a merry father's day, instead of showeling unicorn shit.
-
Luke Dashjr reposted
BlueRidgeBitcoin ⚡️
@BlueRidgeHODL
To say BIP110 is censorship is like saying the block subsidy is censorship. Or the 21M cap.
-
Luke Dashjr reposted
.
@GrassFedBitcoin
I watched.
Giacomo holds two positions. That BIP-110 is bad and that even if it was good, it's set a negative precedent if it were to activate.
The latter he elaborates on with something along the lines of "If BIP-110 activates, that'd mean *people* are in charge of Bitcoin and people are retarded - look at how they acted during COVID!"
Yes, unfortunately it is that bad of an argument.
Bitcoin is a dynamic system that can and must change at times in order to preserve itself. He does acknowledge this "homeostasis" argument but fails to apply context that can trivially demonstrate its harmlessness. i.e BIP-148 which had no consensus and as I keep saying, we did any way, after which Bitcoin was much better for having had it happen.
At the end of the day, Bitcoin is controlled by node runners and you can be scared of populism/democratic uprisings among unwashed masses all you like, but there's no one more appropriate to have that level of influence. It's demonstrably not devs or miners.
Many would like it to be - notice the ball-gargling going on with BIP-54. (Because nodes couldn't care less about it while a few devs liaise with a giant miner to get it pushed through. Murch describes this as "genuinely popular" which he contrasts with BIP-110's apparent unpopularity. The latter having only *checks notes* 7000 nodes.)
If not nodes....then who?
This isn't democracy which is essentially 99% of people pretending to decide what to do with 1% of people's resources getting betrayed and thus voting increasingly vindictively and causing the socialist death-spiral that just ends up gutting the middle class.
This is Bitcoiners deciding what happens with *their network* and they have proven remarkably adept at maintaining it.
Which isn't surprising - they have skin in the game.
Not only that, but there is literally no other defence against 51% attacks (which are trivial in today's landscape), and corrupt/sloppy devs.
Bitcoin Infinity Media
@BtcInfinityShow
BIS#194 out now, with @giacomozucco!
-
Luke Dashjr
@LukeDashjr
Bitcoiners, remember that in 2013 March, Bitcoin Core deployed a temporary softfork to limit block sizes to 500kB, expiring 2 months later, with zero notice or miner signalling. It also retroactively invalidated existing blocks.
-
Luke Dashjr reposted
Camina Drummer Blake2b
@CaminaDrummer4
There is no Bitcoin without BIP-110 or something like it.
So there is no choice and no risk.
If we fail, Bitcoin becomes a shitcoin.
Most likely worst case is we have to fork the scammers off.
Then we win.
Hard money is always more valuable, eventually. -
Luke Dashjr reposted
Camina Drummer Blake2b
@CaminaDrummer4
This entire debate is between high and low time preference:
Low Time Preference— fixing the money for 8 billion, fixing the world.
High Time Preference- making cash from spam and grants and padding your resume with “Bitcoin core”.
The long term future of Bitcoin is BIP-110. -
Luke Dashjr reposted
Secure Sovereign 🚀₿🧡
@secsovereign
99.9% of 3.5 billion witness elements on the entire Bitcoin chain are already under BIP-110's 256 byte limit. The network conforms. The abuse vector does not.
Secure Sovereign 🚀₿🧡
@secsovereign
To understand what BIP-110 actually does, I ran its rules across 912,723 blocks and 1.2 billion transactions. Not to simulate retroactive enforcement, but to find out how much of what BIP-110 blocks is spam versus legitimate transactions. I used the strictest possible spam definition, Ordinals by envelope/pattern only, large witnesses classified separately to avoid flagging Miniscript and vaults.
Bitcoin ran relatively clean for 14 years until the last 3 years, with nearly 3 out of 4 transactions blocked by BIP-110 coming from the inscription era alone.
Before inscriptions, spam's share of blockspace was under 0.3%, and then after inscriptions it jumped to ~5%, a 17x intensification.
Spam transactions are 2.6x the size of a normal transaction on average, so the blockspace impact far exceeds what count alone suggests.
The network's actual behavior already conforms to BIP-110, and out of 3.5 billion witness elements scanned, 99.9% are under 256 bytes. BIP-110 is not constraining normal usage, it is closing an abuse vector that the overwhelming majority of the network never touches.
~80% of blocked transactions are spam under strict classification, and existing funds are not at risk because inputs spending UTXOs created before activation are permanently exempt. The remaining false positives in the legitimate complex-script range are ~2,000 witness violations across the entire chain, which is not a meaningful objection to the design.
While the design holds up under scrutiny, the activation picture does not. SegWit was signaling 22-30% for months before UASF pressure forced the issue, and BIP-110 is at less than 1% with mandatory signaling roughly 5 months out. That gap probably doesn't close in time.
I encourage others to run their own analysis and I am open to corrections.
For context, I am one of the more vocal critics of Bitcoin Core's governance and I support the ideology behind BIP-110 and am against spam on the network. What I do not support is the activation mechanism as currently positioned or the rhetoric surrounding it. Arguments should be won by evidence, not by ego, incentives, or tribal affiliation, and if the data is wrong, show me better data.
h/t
@LukeDashjr
@dathon_ohm
@hodlonaut
@w_s_bitcoin -
Luke Dashjr reposted
Dathon Ohm / BIP-110
@dathon_ohm
I'm happy to announce v0.4.1 of the official BIP-110 activation client for all supported platforms (links below).
This version adds some finishing touches, including a new EXPIRED BIP9 state, vbrequired for GBT during mandatory signaling, and improved logos. -
Luke Dashjr reposted
.
@GrassFedBitcoin
Foundry at 45% over the last 24 hours 😰
-
Luke Dashjr reposted
Maximillion⚡️∞/21M
@21BitcoinMaxi
That was a trust/custody issue between institutions. The same kind of thing can happen with Bitcoin too if people trust exchanges or custodians instead of verifying themselves because they cant run a full node.
-
Luke Dashjr reposted
Sodium #BIP-110
@sodiumbtc21
Rmember when we used to tell new commers to bitcoin than in case Core developers became corrupted and attacked the network node runners will fight back?
Well, this is it, folks.
BIP-110 is the anti-fragile response to this parasitic spam attack on Bitcoin. -
Luke Dashjr reposted
.
@GrassFedBitcoin
There's no such thing as "the mempool".
Stop designing junk that assumes no user sovereignty over what their computers do.
.
@GrassFedBitcoin
Legacy devs still are working on designs that assume homogenous mempools.
Users decide what's in their mempool.
Deal with it.
Your L2 that requires homogeneity in order for the adult daycare projects these devs are working on is unimportant to me and I'm not having my computer become an involuntary relay for all the junk that accompanies these theoretical improvements.
Ducat
@Ducatstable
The mempool is Bitcoin's waiting room. Every unconfirmed transaction sits here until a miner includes it in a block.
How the mempool orders and evicts transactions directly affects fee estimation, RBF, and block construction. -
Luke Dashjr reposted
.
@GrassFedBitcoin
Legacy devs still are working on designs that assume homogenous mempools.
Users decide what's in their mempool.
Deal with it.
Your L2 that requires homogeneity in order for the adult daycare projects these devs are working on is unimportant to me and I'm not having my computer become an involuntary relay for all the junk that accompanies these theoretical improvements.
Ducat
@Ducatstable
The mempool is Bitcoin's waiting room. Every unconfirmed transaction sits here until a miner includes it in a block.
How the mempool orders and evicts transactions directly affects fee estimation, RBF, and block construction. -
Luke Dashjr reposted
Nick Szabo
@NickSzabo4
Also you can become "willful" if you obtain knowledge of the content and don't delete it. Which blockchain node operators can't do under current designs without severely degrading or destroying functionality.
-
Luke Dashjr reposted
✝️ | XBT Scotthew
@Scotthew82
This video was SOOO EYE OPENING for me .. truly may be the BEST video by @mattkratter and Matthew I have been listening to your channel for a long time. Long before you hit 100K viewership.
This video is terrifying .. I sincerely mean that .. thought I hated Core before, but now I vehemently hate Core (in its current form) and they MUST go down!
While Bitcoin consensus, POW mining, and decentralized node operators are the rock solid foundation, it’s the people behind the software that is currently and (somewhat proved by this video) truly always has been the Achilles heel of Bitcoin ..
Having great Devs is Awesome! Love @LukeDashjr and his team. Love what all the OGs have given our current generation. Love @GrassFedBitcoin .. love @ocean_mining .. sincerely appreciate all their work
But as a Christian, who knows quite well how corrupt people can be, it worries me greatly for Bitcoin’s future. If the corruption of humanity has this much sway and impact on what happens with Bitcoin implementation and potentially on consensus, Lord help us.
I say all of this in the hopes that someone has good solutions for this level of corruption .. this gaping hole in our armor. I am not sure having competing implementations is enough (but maybe I am wrong).
Knots + BIP110 is the solution NOW .. but what happens when Luke and Mechanic move on from this world? (May God bless your souls) .. What happens with future generations? Bitcoin as antifragile is obviously in question ..
Is this why OG whales are selling? (And I do think they are selling) They see the writing on the wall?
If Bitcoin’s success is dependent on people then I have high concerns for its future ..
@mattkratter, @LukeDashjr, @GrassFedBitcoin .. help me out here guys .. prove me wrong 🙏🏻
Bitcoin Core Insider Spills The Beans (Jon Atack) youtu.be/F0FBdZE3GeQ via @YouTube -
Luke Dashjr reposted
hodlonaut
@hodlonaut
1/
In 2025 Bitcoin Core removed a decade-old mempool policy default — a configurable limit on how much non-financial data nodes would relay. OP_RETURN was effectively uncapped.
Not a consensus rule. A default setting. But defaults govern what most of the network does. Which governs what miners see. Which governs what gets mined.
The justification: it wasn’t working anyway, data was getting in through a loophole.
What wasn’t disclosed: that loophole had been deliberately kept open.
Here’s the documented sequence. 🧵 -
Luke Dashjr reposted
XBT Motorist
@BitcoinMotorist
Bitcoin pumps on news that the first BIP110 block was mined
-
Luke Dashjr reposted
Camina Drummer Blake2b
@CaminaDrummer4
Notice how seemingly everyone opposed to BIP-110 has to lie about its motivations and what it does?
Anything to avoid facing the truth.
Bitcoin is money, not a developer playground or platform for Ethereum scams like core wants to run. -
Luke Dashjr reposted
bendtheknee
@bendthekne3
What I dislike most about the Bitcoin drama right now, is that core has made zero attempts to reunite the community. Instead they appear to have hijacked Core for their own agendas not caring at all what Plebs think. They think this is their toy now.
-
Luke Dashjr reposted
OCEAN
@ocean_mining
90 minutes ago, @BarefootMining found block #938903.
As part of constructing and mining their own block using DATUM, they also signaled readiness for activation of a soft fork.
They did this entirely independently of their pool.
OCEAN is designed such that miners can perform the full spectrum of mining, and actually take a direct role in coordinating network upgrades. That includes constructing their own block templates and deciding when, and whether, to signal.
OCEAN restores agency to miners.
Back in 2017, Slush Pool let miners express their preference during the SegWit activation debate:
www.nasdaq.com/articles/slush-pool-to-let-hashers-vote-on…
OCEAN takes that one step further by reducing the pool’s role even more. Through DATUM, miners construct their own templates and embed their own signal directly in the blocks they mine. Further still - any blocks they find get broadcast directly to the network without needing to pass through a middle man.
Fork proposals are part of Bitcoin’s maturation. We encourage miners to study BIP-110, form their own view, and signal accordingly.
Your hash. Your choice. -
Luke Dashjr
@LukeDashjr
First RDTS signaling block found by Barefoot Mining🥳
Congrats Bob!
Bob Burnett
@boomer_btc
Check the BIP-110 signaling bit on this block...you might find something of interest.
-
Luke Dashjr reposted
Melvin Carvalho
@melvincarvalho
Satoshi knew
-
Luke Dashjr reposted
Bitcoinapolis: ₿= Money not S̷P̷A̷M̷ 🤓
@Bitcoinapolis55
This excellent. The majority thinks Bitcoin is Money. Core disagrees. <we are here>
Hodlonaut has done two polls (unofficial everyone knows) and both times the polls show ~60% support behind the Knots/Knots+BIP-110 combo meal. Throwing out Core V30 all Core versions prior <=29.
Then Hodlonaut manually goes through the comment section of the Bent/Odell video and sees
Agree: 20
Disagree (Vast majority very strongly): 227
Neutral or unrelated comments: 41
Taking the emotion out, this data (evolving) is hard to dismiss. I wonder if the same poll could be done on NOSTR?
hodlonaut
@hodlonaut
I listened to @rabbitholerecap #396 with Matt Odell and @MartyBent today, where they come out pretty hard against BIP-110, and the motivations behind it.
There were many claims of bad intentions, control/power, lynch mob etc.
I have to make it clear that I respect Matt and Marty a lot, and I definitely think they have the best intentions for Bitcoin, and have proven that over time.
I don't think they made a solid argument in this episode though, and it kinda dodged the main issue (to me at least), that Core have caused this whole mess, and that people are extremely worried about the direction of Bitcoin and the rather obvious philosophical pivot of Bitcoin Core.
I am still on the fence about BIP-110. But I 100% do not see BIP-110 supporters as a lynch mob (there are elements of it, but you can't dismiss the whole group based on anecdotes)
I found a comment that mirror my position and reaction to the video pretty well, except for me being on the fence with 110 support:
"Disappointed to hear that kind of take from Matt Odell (a person I believe to be high integrity and honest) on bip-110. No lynch mob here just a person that believes bitcoin is money and is the only chance in this world we have at true freedom"
The video had 288 comments at the time of me watching it. I went through all the comments and divided them into 3 categories. This is how it breaks down based on agreeing or disagreeing with Matt and Marty's take on BIP-110:
Agree: 20
Disagree (Vast majority very strongly): 227
Neutral or unrelated comments: 41
This is overwhelming, and I think it makes it pretty clear that the anger and disappointment with Core is widespread and not something that can just be ignored and labeled as a stupid or dishonest lynch mob.
It would be great if Matt and Marty would keep talking about this topic from a perspective where they acknowledge that there is a reason people are up in arms, and look more critically towards the reason BIP-110 gained support in the first place. Which imo is the actions, arrogance and recklessness of Core. -
Luke Dashjr reposted
Majorian
@MajorianBTC
BIP-110 isn't winning through coercion or a mob mentality, contrary to what others may say.
BIP-110 is winning because it is a sound proposal that makes bitcoin a better money, and game theory favors its activation. -
Luke Dashjr reposted
Matteo Pellegrini
@matteopelleg
just so we're clear:
miners are the employees of the bitcoin network
the employers are:
- people who hodl bitcoin and pay miners via inflation (block rewards)
- people who use bitcoin and pay miners via transaction fees
nodes are neither employees, nor employers; they are the enforcers of the employers desires
the end -
Luke Dashjr reposted
Secure Sovereign 🚀₿🧡
@secsovereign
Mark Karpeles, the former CEO of MtGox, submitted a pull request to the Bitcoin Core GitHub yesterday proposing a narrowly scoped consensus rule that would allow 79,956 BTC stolen in the 2011 MtGox hack to be recovered and returned to creditors through the existing Japanese court-supervised rehabilitation process. The coins have sat at a single, well-documented address for 15 years without moving. What happened next is a perfect case study in how Bitcoin Core's governance actually works, and it's worth naming precisely.
The proposal was auto-closed within hours by DrahtBot as spam and then locked, which is not a bot action. A human maintainer chose to lock it, preventing further discussion on the platform where Bitcoin's code lives. That distinction matters. DrahtBot operates on heuristics that cannot distinguish a thoughtful governance proposal from a scam link. The lock required a human decision, and whoever made it decided that a proposal from Mark Karpeles about 79,956 BTC stolen from MtGox creditors did not deserve to remain open.
Then the responses came. Pieter Wuille, one of Bitcoin's most respected contributors, redirected Mark to the mailing list without engaging a single substantive argument in the proposal. Shinobi told him to run Knots, which sounds like technical advice but is a way of saying the proposal is outside acceptable discourse. Matt Corallo provided the institutional cover by explaining calmly that GitHub isn't the right forum for this kind of community discussion, which is a reasonable-sounding position that routes the proposal away from the highest-visibility platform into a mailing list that is lower-traffic, higher-friction, and functionally dominated by people already inside the existing technical consensus.
The combined effect is that the proposal is now fragmented across five platforms with no single place where the conversation can build critical mass, and this is the predictable output of a governance structure that imposes maximum coordination cost on proposals originating outside the maintainer circle. Bitcointalk, X, the mailing list, Delving Bitcoin, and the Bitcoin subreddit all have different audiences, different norms, and different signal-to-noise ratios, so the conversation splinters rather than concentrates.
Let's be precise about what the proposal actually contained. Mark acknowledged the hard fork nature openly and upfront. He set the activation height to INT_MAX, meaning the code does literally nothing without explicit community consensus. He scoped it to a single, specific, well-documented address with 15 years of inactivity and documented theft. He anticipated the strongest objections and addressed them in the BIP text itself, including the precedent argument, which is the strongest one. That is not a bad-faith submission. That is a more carefully constructed proposal than many changes that have successfully made it through the process.
The substantive question the proposal raises is genuinely hard. If Bitcoin makes one exception for compelling reasons, the argument against the next exception is weaker, and the one after that weaker still, and I understand why many serious people will land on no as a default. But the creditors have been waiting since 2011, the coins have sat at that address for 15 years, and the legal framework to distribute them exists and is actively operating. Whether or not protocol-level action is the right answer is a legitimate debate. What is not legitimate is a governance structure that prevents that debate from happening in a place where it can actually build the consensus required to answer the question.
Mark Karpelès
@MagicalTux
Since the merge request has been auto-closed (I was hoping to see some arguments for/against and chance to talk about this), I also posted this to the bitcointalk forums: bitcointalk.org/index.php?topic=5575915.new
-
Luke Dashjr reposted
David Noriega
@BlueDavid
Running Datum with BIP-110 with 200PH
Let see if we (234 Alberta) are the first to mine a BIP-110 signalling block! -
Luke Dashjr reposted
Majorian
@MajorianBTC
Miners don't have to choose to signal for BIP-110 because they are the pious guardians of the network.
They can choose to run BIP-110 because it is a virtually costless way to reverse a 50% decline in the market cap of bitcoin that Core 30 has caused. -
Luke Dashjr reposted
hodlonaut
@hodlonaut
The main justification from Core for the OP_RETURN uncap is “harm reduction”.
The argument is that inscriptions done via the segwit/taproot hack have potential to do more damage than inscriptions via OP_RETURN.
Thing is, @LukeDashjr made a PR in 2023 to fix the vulnerability introduced by taproot.
PR #28408
It would “effectively limit arbitrary data carried via newer methods (including SegWit witness data and Taproot scripts), which inscriptions/Ordinals were using to bypass the existing OP_RETURN-based limits and embed larger payloads.”
If that had been merged, the current harm reduction narrative wouldn’t even be there.
It wasn’t merged. Core didn’t want it.
Peter Todd was among those who Nacked it with this rationale:
“The transactions targeted by this pull-req are a very significant source of fee revenue for miners. It is very unlikely that minres will give up that source of revenue. Censoring those transactions would simply encourage the development of private mempools - harmful to small miners - while making fee estimation less reliable.”
Note the use of the word “censoring” to describe fixing a very recently introduced vulnerability that opened up for ordinals.
Self inflicted wound, willingly not patched up, used as rationale for a new self inflicted wound. -
Luke Dashjr reposted
The ₿itcoin Artist
@worshipbitcoin
Isn't it *a little unfair* to:
1. Dismiss bitcoiners concerns about V30
2. Tell them change must occur at consensus layer
3. Tell them "whatcha gonna do about"?
4. Then cry foul when node runners exercise their sovereignty? -
Luke Dashjr
@LukeDashjr
Good discussion with Matty a few weeks ago.
n.b. I didn't say all Core devs are bad actors, only some
Cypherpunk'd
@cypherpunkd_
"Core developers are bad actors with malicious intent."
Sat down with Luke Dashjr to unpack the internal war over Bitcoin Core v30.
From plummeting node counts to the shadow of the MIT/Epstein era, this is the most sobering look at the protocol's future you'll see this year.
Full interview with the @Ocean_Mining CTO, @LukeDashjr, is live now.This media couldn't be displayed. See it on the original post. -
Luke Dashjr
@LukeDashjr
It's okay to be ignorant about RDTS and withhold judgement until you understand it better.
It's not okay to be _opposed_ to RDTS, since it just addresses an existential threat to Bitcoin.
RDTS is hostile only to CSAM and spammers.
If you're neither, it's not a hostile softfork.
Luke Dashjr
@LukeDashjr
And if you simply don't think CSAM is a problem at all, it _still_ doesn't make sense to _oppose_ RDTS.
All the risk that exists (individually and to the network), comes from opposition to the softfork, not from the softfork itself. -
Luke Dashjr reposted
Jim | Bitcoin, not jpegs
@venorusprime
Today Matt Odell had a series of bad takes about #bip110 on the Rabbit Hole Recap. Although I think his beliefs are sincerely held, they originate from skewed assumptions.
The crux of his contention with BIP-110 seems to be his belief that it is a way for @LukeDashjr and @GrassFedBitcoin to take over #bitcoin.
Unfortunately, Matt did not give any reason as to why he thinks this. He just stated it as if it were a fact and imbedded it with numerous unfounded personal attacks.
The truth is, there is nothing in BIP-110 that gives control of Bitcoin to any person or group of people.
Odell was very emotionally charged in his opposition to BIP-110 and mentioned that his family relies on Bitcoin.
Well, so does mine.
I run BIP-110 because I believe it is the best way to get Bitcoin back on its monetary path.
I believe it is the best way to preserve Bitcoin for the future.
If you also want to make sure Bitcoin stays the soundest money ever discovered then run BIP-110 and rug the spammers.
Learn why and how here: bip110.org -
Luke Dashjr reposted
₿itcoin ₿ombadil
@BitcoinBombadil
Core v.30 = we must bear the burden of our mistakes forever and even double down on those mistakes if people call us out for them
Knots + BIP110 = we do our best to correct mistakes on Bitcoin using all forms of reason to the best of our ability
Run Knots + BIP-110🛡️ -
Luke Dashjr reposted
Asanoha | Timechain Art Magazine
@asanoha_gold
Here is what Satoshi had to say about other use cases outside of money:
"Piling every proof-of-work quorum system in the world into one dataset doesn't scale.
Bitcoin and BitDNS can be used separately. Users shouldn't have to download all of both to use one or the other. BitDNS users may not want to download everything the next several unrelated networks decide to pile in either.
The networks need to have separate fates. BitDNS users might be completely liberal about adding any large data features since relatively few domain registrars are needed, while Bitcoin users might get increasingly tyrannical about limiting the size of the chain so it's easy for lots of users and small devices." -
Luke Dashjr
@LukeDashjr
Epstein didn't invent Bitcoin. But let's pretend he did for a moment.
Even then, the concept of Bitcoin is still what matters. We should disregard any future direction from Epstein, stop using his software, and take over / keep Bitcoin going for the good guys. -
Post not available here, view on X
Luke Dashjr
@LukeDashjr
Core has had several opportunities to save face.
For example, they could have embraced RDTS and tried to spin it as "see we were right about policy not being good enough, consensus changes are the right way" -
Post not available here, view on XPost not available here, view on X
Luke Dashjr
@LukeDashjr
False.
Core is a fork of Satoshi's original Bitcoin.
Satoshi himself never worked on Core. -
Post not available here, view on X
Luke Dashjr
@LukeDashjr
5/Sep/2025 Bitcoin Core on brink of second bailout for spammers.
-
Post not available here, view on X
Luke Dashjr
@LukeDashjr
"[Jesus] found in the temple…the bankers sitting. And when He had made a whip of knots, He cast them all out of the temple…and the money of the bankers he poured out, and the tables he overthrew." -John 2:14-15, slightly reworded
-
Post not available here, view on XPost not available here, view on X
mononaut
@mononautical
the overwhelming majority was broadcast openly over the p2p network.
you can verify this by checking the audit for any random sub-1-sat block on mempool space.
Luke Dashjr
@LukeDashjr
As if I'm going to believe mempool space claiming that.
-
Bitcoin Core Project
@bitcoincoreorg
A statement on Bitcoin Core development and transaction relay policy - bitcoincore.org/en/2025/06/06/relay-statement/
Luke Dashjr
@LukeDashjr
NACK
The goals of transaction relay listed are basically all wrong. Predicting what will be mined is a centralizing goal. Expecting spam to be mined is defeatism. Helping spam propagate is harmful.
This OPED contradicts itself, presenting out of band relay as both negative and also "an important aspect of Bitcoin’s censorship resistance"
It ignores the lack of consent to spam by users/node operators, giving deference to the attackers and the malicious miners who might conspire with them.
It paints spam as "largely harmless", when the truth is the exact opposite. It treats abuse of the blockchain and nodes as legitimate "use cases" rather than the DoS attacks they actually are, and speaks of DoS attacks as if they were something distinct, thus implying spam isn't the same (which it is).
The OPED presents itself as aligned with "Bitcoin’s long-term health" which is objectively false, and "miners’ rational self-interest" which is also at least debatably false. -
Luke Dashjr
@LukeDashjr
PSA: @BitcoinCoreOrg (#bitcoin Core) is NOT soliciting or performing closed testing of any beta or other software.
If you get an email inviting you, be aware it is spam and their "testing version" is almost certainly malware.
Note: the "From" on emails is NOT secure and faked. -
Post not available here, view on XPost not available here, view on X
Luke Dashjr
@LukeDashjr
12 is borderline young adult.
The real problem is with trying to treat them as children... But that frankly goes even older than 18 nowadays -
Luke Dashjr
@LukeDashjr
I am a community-paid #bitcoin developer working on Bitcoin Core & many other parts of Bitcoin.
You can help fund my public Bitcoin work by:
1) Sending me bitcoins - contact me for a Bitcoin address!
2) GitHub Sponsors: github.com/sponsors/luke-jr
3) Patreon: www.patreon.com/LukeDashjr -
Post not available here, view on X
Luke Dashjr
@LukeDashjr
Blockchains aren't for recording information.
-
Post not available here, view on XPost not available here, view on X
Luke Dashjr
@LukeDashjr
In addition to the 2013 note, it would also mean distros are effectively deciding consensus rules for their users. How will users choose a UASF or NO2X if their distro only ships one set of packages centrally? (With PPAs and @Gentoo's USE flags, the user has a choice)
-
Post not available here, view on XPost not available here, view on X
Luke Dashjr
@LukeDashjr
Litecoin is no better suited for low value payments than Bitcoin is. And if we must use an altcoin for that, I prefer BCH.
-
Post not available here, view on XPost not available here, view on X
Luke Dashjr
@LukeDashjr
2X *is* splitting the chain. To advocate 2X is to advocate a chain split.
-
Luke Dashjr
@LukeDashjr
Even if 2X were to win, it STILL loses because it would be proving that a decentralised cryptocurrency is a dream that can never become real





















































































































































































































































