According to @ToneVays I am:
- suffering from "Megalomania" with a God Complex
- a useful idiot
- a "everything is a conspiracy" guy
- just there for the clicks and engagement
- working with the feds because confidential informants & undercover feds look exactly like him (Every Time)
Show more
"...the combativeness had a function. It made criticizing Coldcard expensive, and the clearest examples are the ones where the target was not a competitor but the machinery of verification itself.
In June 2023, WalletScrutiny, a project whose entire purpose is to check whether a wallet's public code actually matches the binary that ships, reported that it could not reproduce certain Coldcard builds.
Speaking about it a year and a half later, on Citadel Dispatch episode 8, NVK owned it without reservation: “it was 100% our fault”. And in the same breath, he characterized the people who had reported it: “it was like PR terrorism”.
Elsewhere he called the disclosing researchers “salty cunts” and explained his refusal to pay them a bounty with “I don't deal with terrorists”."
Show more
Really hard to believe there isn’t something to this.
Coldcard: “The bug lived in public for 5yrs, even third party researchers didn't find it.
We believe if took the lastest LLM models to find it.”
Public record: “The flaw was pointed at, in May of 2025, by a person, with no frontier model, who traced it to the library by name and was told the company would already know if something were wrong.
It was found again after disclosure by people pointing ordinary code-analysis tools at a public repository. What took five years was not the finding. It was the looking.”
Show more
“Gray was asking himself for permission, and granting it, in public, to establish that libngu had come to Coldcard as an outside contribution.”
A very comprehensive and thorough analysis/breakdown of the COLDCARD catastrophe. A MUST READ 👇
There's only one question left to answer from @Coinkite, and it's this:
Why wasn't the libNgU project hosted in the official GitHub organization side by side with the firmware repo, and why did @DocHex use an alt nym to develop it instead of his main account?
Mind you, given the available evidence it's impossible that @DocHex tricked everyone and managed to import this library into the firmware undetected.
The changelog for version v3.2.2 of the ColdCard's firmware includes a shout-out to @switck, and even the official @COLDCARDwallet account interacted with him on Twitter.
Combine this with the fact that @nvk always claims that the CC firmware is 100% developed in-house, he had to know @switck was @DocHex: he really wasn't lying when he was saying that.
PS Thank you @brashratel for bringing the changelog and this interaction to my attention.
Show more
@saylor Another day, another post about something that is irrelevant. Weird that…
@saylor Another day, another post about something that is irrelevant. Weird that…
Coldcard: “The bug lived in public for 5yrs, even third party researchers didn't find it.
We believe if took the lastest LLM models to find it.”
Public record: “The flaw was pointed at, in May of 2025, by a person, with no frontier model, who traced it to the library by name and was told the company would already know if something were wrong.
It was found again after disclosure by people pointing ordinary code-analysis tools at a public repository. What took five years was not the finding. It was the looking.”
Show more
This is the worst thing @nvk has done. He actually sent a cease and desist letter to an open source developer who made an open Blockclock competitor (btcclock) AND sent a trademark claim to GitHub who took down the repo.
NVK has harmed open source more than any other Bitcoiner.
Show more
For many years we theorized about a nation state attack. Now we will see if Bitcoiners and Bitcoin can truly withstand and survive it.
Whatever happens today with BIP110, even if there is a chainsplit, know this:
The fight is just getting started.
Show more
Quoting since I can't reply.
This is just straight weird.
Why is Samson glazing Adam like this in post after post right now?
The other day it was Adam's enormous humbleness.
"There are probably a dozen-plus research papers his name should be on too"....
No offense, but this reads like Craig and his wheelbarrow of degrees.
Show more
Just a few of the things @adam3us has contributed to Bitcoin. There are probably a dozen-plus research papers his name should be on too.
@ckpooldev The fact that you pretend strong signals of direction and philosophy aren't sent with mempool policy and dirty tactics ignoring 4:1 community opposition after a year of people trying to clarify it explains how we got here
Show more
@ckpooldev The fact that you pretend strong signals of direction and philosophy aren't sent with mempool policy and dirty tactics ignoring 4:1 community opposition after a year of people trying to clarify it explains how we got here
Show more
"The destruction of clear definitions, the elevation of confusion into sophistication, and the weaponization of tolerance to smuggle in an entirely different value system while pretending it is still the same Bitcoin."
Show more
> They didn't even start the real "then they fight us"
No.
The 'fight stage' been ongoing insidiously for years IMHO.
A new breed of Bitcoiners is emerging; one that sees the monetary purpose of the protocol as merely one use case among many they hope to build, and views Bitcoin's current scripting constraints as limitations standing in their way.
This same group strategically refuses to define spam.
Instead, they argue that Bitcoin is fundamentally nothing more than a 'thermodynamic something database', where all data is simply ones and zeros.
The "What even is spam?" from Core isn't just a rhetorical question.
It's laying the foundation for the next one:
"What is Bitcoin?"
The destruction of clear definitions, the elevation of confusion into sophistication, and the weaponization of tolerance to smuggle in an entirely different value system while pretending it is still the same Bitcoin.
"who is getting hurt: everyone. Humanity. I believe that. By increasing friction for monetary uses of Bitcoin and lowering the chance of ultimate success of the project."
~ @lukedewolf
Bitcoin being abused as a dumping ground for toxic waste by bad actors maliciously was the price we accepted for the separation of money and state.
Core expanding the attack surface and normalizing that abuse with sophistry is not.🤷♂️
Show more
🚨 A vulnerability affecting all BTCPay Server instances is being actively exploited.
Update immediately to v2.4.2 to mitigate.
We’ll publish a full post-mortem in the coming days. Alert anyone you know who runs BTCPay.
Retweet to amplify please
Show more
Inside the fight for the soul of Bitcoin, with @hodlonaut.
Is Bitcoin Core captured, and can BIP-110 stop it?
TIMESTAMPS:
0:00 A message on ColdCard
3:34 Meet the Space Cat, on a brutal day
6:15 The Capture series: becoming a citizen journalist
18:38 Why a node runner is the canary in the mine
25:51 The birth of Hodlonaut & the Lightning Torch
31:21 The Craig Wright letter, the bounty, the doxxing
38:54 What five years vs Craig Wright taught him
44:48 How Bitcoin Core's power was assembled
53:10 The armor: DEI and "extractive"
1:00:13 "Every line of code must serve monetary sovereignty"
1:04:43 Sponsors
1:13:30 BIP-110: judge the idea, not the messenger
1:21:53 We bypassed the human layer: fight for Bitcoin
1:24:24 The real fight is the ledger & the node-cost problem
1:28:50 Why he's all-in on BIP-110
1:36:10 The three buckets & why people won't engage
1:47:07 If BIP-110 fails
1:51:30 Ossification & the anti-spam team
2:01:46 Outro
Show more
I predict that the motives and dirty laundry of some of the most vocal anti-bip-110 voices will be exposed the next months.
This is not me saying everyone who is against BIP-110 are bad guys btw.
