Jesus, Family, Bitcoin, my economic node runs Knots /w BIP-110
Joined January 2021
- Tweets7.6K
- Following2.1K
- Followers2K
- Likes14.5K
We are born owning nothing.
We live struggling to own something.
Bitcoin made true ownership a possibility.
Turns out, 5 mining pools are the deciders of Bitcoin.
And then we die.
Turns out, all we have is Christ.
I hoped maybe we had Bitcoin too, but no.
Sell a kidney, get one Bitcoin
Sell a bitcoin, get two kidneys.
It's fiat-math, except instead of printing money, we're printing kidneys.
TORONTO HODL 🍁 retweeted
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 is irreplaceable.
Even if you disagree with 100% of everything he says, he knows Bitcoin better than you, and Bitcoin is better because of his knowledge, experience and unique perspective.
Banning @LukeDashjr is another own-goal.
Be still before the Lord
and wait patiently for him;
do not fret when people succeed in their ways,
when they carry out their wicked schemes.
- Psalm 37, verse 7
Fun activity: Read the whole psalm, but replace the "wicked" with "spammers". 🙂
Should be about 16 instances.
God bless.
biblegateway.com/passage/?se…
If Pierre is serious, and I can't tell, I would support this.
Are you serious @BitcoinPierre?
"...they had been counted worthy of suffering disgrace for the Name of Jesus." - Acts 5, Bible
I invest in alignment with my faith in Jesus.
This is why I supported BIP-110: It was good and aligned with the values of Christ.
We lost: that is sad, but many good people doing good things have lost in the course of history.
In the end, the arc of the moral universe is long, but it bends toward justice.
God bless y'all.
TORONTO HODL 🍁 retweeted
Reminder: Nobody has made a counter-fork to reject BIP110. So BIP110 remains uncontested. Activation is certain.
.@natbrunell asks @mattkratter a good question: People can already put spam on the Bitcoin blockchain. So why hasn’t anyone put something horrifically illicit on it yet?
I believe a large part of the answer is: Timing
The bigger and more important Bitcoin becomes, the more reason someone has to try to wreck it with the worst content - stored on pleb nodes. The more valuable it gets, the more damage a vicious attack can do.
It’s how someone might design a sex scandal to destroy a man: the attack only works at the right time.
- At age 20, he has almost nothing: no wife, no kids, no career, no money, no reputation. A scandal gains the attacker nothing.
- At age 35, he has more to lose: a wife, young kids, a job, a growing reputation. It still hurts, but he has time to recover.
- At age 50, he has the most to lose. He is at the peak of his power and influence. His wife has been faithful for decades and expected to enjoy their later years together in peace & joy. His older kids will be humiliated. His career is over and he has no time to start again. He has real money and a reputation he spent fifty years building. This is when the attack does the most damage.
Bitcoin is still young. It has potential, but it is not big or important enough yet for a major attack to be worth the cost.
So, the time to develop the discipline of fidelity is now.
I belong to my wife in marriage.
Bitcoin belongs to plebs as money.
To defile either is cause for much sorrow, in their own way.
The attacks are coming, in time.
BIP-110 says "no" to the future temptress, today.
And, if we do not say "no" to the destroyer today, we will be unable to say "no" to her tomorrow.
Interview: youtu.be/txT754BEpJA?t=2336
TORONTO HODL 🍁 retweeted
I know that not everyone will agree. But if/when BIP110 activates, I won't be gloating.
I'm not going to exile people for being wrong or disagreeing. I am not going to say "I told you so" or discredit them for buying into the biggest COVID-level manipulation campaign in Bitcoin of all time.
They will always have a place in Bitcoin because it is open to all. Node runners run the show, and there is nothing we can do about it besides run one ourselves.
Looking forward to this afternoon. See you guys on the other side.
Guys, Bitcoin is money. But you can't change Bitcoin - immutability comes first.*
- Love, Yan
*unless you're Core - then you can change Bitcoin by introducing bugs (and refusing to fix them) and changing policy. That's OK. I don't count that as change because I'm intellectually dishonest. But if *YOU* try and revert Bitcoin back to correct for these errors, you're a shitcoiner.
"Will keep the exact details private so that it can't be easily gamed in the future. It is impossible to find ALL duplicate nodes, however false positives are somewhat unlikely with my methodology."
AKA: "Trust me bro." - NVK
Since we're about 48 hrs away from the BIP-110 "mandatory" signaling height, I wanted to quickly share my private node crawler stats.
Over the past several weeks, I gave a program of mine more spending power than is probably reasonable. It spent a not insignificant amount of BTC deduplicating nodes. Enjoy.
Raw node counts (% of total)
🔵 Total: 131,762
⚫️ Bitcoin Core: 99,401 (75.4%)
⚫️ Bitcoin Knots: 30,755 (23.3%)
⚫️ Other: 1,606 (1.2%)
Raw BIP-110 signaling counts (% of total)
🔸 Bitcoin Core: 17 (0.01%)
🔸 Bitcoin Knots: 19,388 (14.7%)
🔸 Other: 0 (Unknown)
🔹 Total: 19,405 (14.7%)
Nodes found to be duplicates (% of version)
🔴 Bitcoin Core: 17,892 (17.8%)
🔴 Bitcoin Knots: 18,049 (58.7%)
🔴 Other: Unknown
🔴 Total duplicates: 35,941 (27.2% of total)
Deduplicated node counts (% of unique)
🟢 Bitcoin Core: 81,672 (85.1%)
🟢 Bitcoin Knots: 12,706 (9.6%)
🟢 Other: 1,606 (1.7%)
🟢 Total unique: 95,984 (72.8% of total)
Of the 19,388 Bitcoin Knots BIP-110 nodes discovered signaling for BIP-110, 71% of them were eliminated as duplicates, above average for the Knots nodes, leaving only 5,663 BIP-110 signaling nodes.
That puts non-duplicate BIP-110 signaling nodes at 5.9% of non-duplicate nodes.
My criteria for deduplication includes the basics (same IP) and some additional more advanced sleuthing of available data. Additionally, you may have already surmised from my intro that part of it also involves strategically sending real transactions.
Will keep the exact details private so that it can't be easily gamed in the future. It is impossible to find ALL duplicate nodes, however false positives are somewhat unlikely with my methodology. If my software has flagged a group of nodes as duplicate, there's an extremely high probability that its either the exact same node (with multiple IPs) or in the exact same location.
If a node wasn't able to be tested thoroughly enough to be confident for whatever reason, and isn't deemed duplicate by conventional means (same IP, for example) then it isn't considered a duplicate and gives it the benefit of the doubt.
If I get more time, I may start publishing some more detailed stats more regularly, since it seems my crawler successfully finds a large amount of nodes beyond those listed every public crawler. Unfortunately it's not cheap to handle the deduplication aspect, so will need to figure out how feasible that is to continue. It also involves operating from dozens of IPs to get connected to a supermajority of the network, which is pretty bandwidth intense.
Anyway, figured I'd share, since I don't think anyone is actually doing this at all at this level. There's a lot more to this, too. Some of it might scare privacy conscious people... so I'll probably keep my publicly shared info limited to node stats.
I feel like I'm getting a divorce, and I'm super excited. 😬
Never got a divorce before.
Is that the wrong metaphor?
Maybe it's like getting a tumor removed?
If it goes well, the spammers are removed, and we win.
If it goes badly, spammers kill Bitcoin, but suffering will be over?
I'm giddy.
BIP-110.