TLDR: The sabotage of Core.

FreedomMoneyIsFuture

npub1wl6kysagynfz2ulmw4wa2trnc9ycd52upjv9zt297n0tpr5ls7dqk5caw8

hex

6914a4e9a60d5fa419f9ed7a211b71cc6f9826649bf35965431ab42d6084efae

nevent

nevent1qqsxj99yaxnq6hayr8u7673prdcucmucyejfhu6ev4p34dpdvzzwltsprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgs80atzgw5zf539w0ah2hw493euzjvx69wqexz394zlfh4s360c0xsuh6jx9

Kind-1 (TextNote)

2026-07-08T11:06:15Z

TLDR: The sabotage of Core. Core are compromised and corrupted. Core V30+ is a malware and an insider attack on Bitcoin.

By @hodlonaut

1/

In 2022, two developers put their name forward to become Bitcoin Core maintainers. Same project, same year, same process.

One was waved through in six days.

The other was worn down over five months and gave up.

The difference between them tells you how Core actually decides. A thread.

2/

July 2022. Gloria Zhao files the PR to add herself to Core's trusted keys. It draws substantive NACKs.

James O'Beirne, a co-founder of Bitcoin Optech, no outsider, lays out a specific worry: she'd be maintaining the same mempool area she was actively writing and proposing designs for. A built-in conflict.

3/

O'Beirne goes further.

He names a "virtuous circle of mutual ACKs" among a cohort of young maintainers tightly linked by funding and social ties, and asks for someone "more disjoint from the funding and social graph."

The concern is structural, not personal.

https://pbs.twimg.com/media/HLqMuiQWkAA10c0.png

4/

It doesn't matter. The reservations are noted, then set aside as raised in the wrong venue.

The PR is merged in six days.

The conflict O'Beirne flagged is never resolved, just routed past. Speed: one week.

5/

August 2022. Vasil Dimov proposes himself as P2P maintainer. Dimov built Core's privacy networking from the ground up, BIP155, Tor v3, I2P.

The lead maintainer agrees on sight: "you've been the most active in P2P development for quite a while." Broad support follows.

https://pbs.twimg.com/media/HLqOq7zXIAA6b-6.jpg

6/

Then fanquake files a scope objection, a list of 18 PRs Dimov supposedly wasn't involved in.

Dimov answers it with data and offers to narrow his scope to exactly what fanquake asked.

fanquake's response? Nothing. No ACK, no NACK, no acknowledgment of the change he himself demanded. Just silence.

https://pbs.twimg.com/media/HLqPHCBWgAASJGJ.png

7/

That silence is the weapon. Zhao, now a maintainer, says nothing for five months despite being asked by name, repeatedly.

The PR can't move without a maintainer signing off, and the maintainers won't speak.

Dimov, later: "The silence was deafening. To me that meant disapproval, for reasons that cannot be publicly stated." and "it was being sabotaged and something was happening behind the scenes."

https://pbs.twimg.com/media/HLqP7BiWYAAg78A.png

8/

Michael Folkson says out loud what the record shows:

"I remember the uproar when Luke didn't merge a PR adding a new BIP maintainer within a month of it being opened. He was hounded on IRC by certain individuals. Here it is fine to have a Bitcoin Core maintainer PR dangling for 5 months. Certain people should be ashamed of themselves."

https://pbs.twimg.com/media/HLqQuNpWAAAtxLu.png

9/

When contributors ask why it's stalled, the asking becomes the offense.

AJ Towns invokes the CIA's Simple Sabotage Field Manual, against the people requesting an answer, not the people withholding one.

Asked if he's calling Zhao and fanquake saboteurs, sipa replies: "wtf." The question hangs.

https://pbs.twimg.com/media/HLqSFRsXAAAEI3O.png https://pbs.twimg.com/media/HLqSha9XwAAi9mW.png

10/

The loop closes on itself. The maintainers won't explain their silence. When pressed, the explanation offered is that the people pressing are "aggressive."

The demand for accountability is named as the reason accountability can't be given.

You cannot break it from outside, because trying to is the cited proof you're the problem.

11/

January 2023, 148 days since Dimov's maintainer PR was opened.

Ava Chow flips to NACK, having "reached out to several contributors privately" to form it.

Zhao finally posts, framing a maintainer as someone who should override "any number of ACKs," and tells critics of Brink's influence to go found their own nonprofit.

Dimov closes his own PR: "Doing so feels like failing all the people who ACKed it, sorry."

https://pbs.twimg.com/media/HLqTS5BXsAAAX2i.png https://pbs.twimg.com/media/HLqTd3AWcAAHBA1.jpg

12/

Put the two side by side.

Gloria's PR: NACKed on conflict grounds, merged in 6 days.

Dimov's PR: broadly supported, killed by 5 months of silence and private consultations no one disclosed.

Same process, run in opposite directions depending on who was asking.

13/

Chow's own NACK said the quiet part. Previous maintainer additions were "almost always foregone conclusions," the obvious choice.

Dimov was "the first time we have had a maintainer nominee who I did not think was an obvious choice."

Translation: the others were decided before the meeting. Dimov wasn't pre-approved, so he didn't pass.

https://pbs.twimg.com/media/HLqUCiVWIAAu1lv.png

14/ Dimov's read:

"Gloria's was pre-arranged, decided upfront, and the IRC meeting and PR discussion was just democracy theater."

Existing maintainers decide privately, then announce it as a nomination. He skipped that step. He just raised it in the open. That was the disqualifying move.

https://pbs.twimg.com/media/HLqUS4iXEAAGsL4.png

15/

None of this rests on a hidden source. Every quote is from the public GitHub threads and IRC logs, linked in the article.

The takeaway sits in the contrast: Core's real selection test isn't the merit of the PR, it's whether you were pre-approved in private before the public process began.

Zhao was. Dimov wasn't. That's the whole difference.

citadel21.com/the-lever

原始 JSON

{
  "kind": 1,
  "id": "6914a4e9a60d5fa419f9ed7a211b71cc6f9826649bf35965431ab42d6084efae",
  "pubkey": "77f56243a824d22573fb755dd52c73c14986d15c0c98512d45f4deb08e9f879a",
  "created_at": 1783508775,
  "tags": [
    [
      "imeta",
      "url https://pbs.twimg.com/media/HLqMuiQWkAA10c0.png",
      "m image/png",
      "x 27565de1760ba1750e090a645ba963374902f439c2af456c9efda7475ba5225f",
      "size 182067",
      "dim 884x960",
      "blurhash TASF:^M@xyt8a$WAxoj:W9RpWBfR"
    ],
    [
      "imeta",
      "url https://pbs.twimg.com/media/HLqOq7zXIAA6b-6.jpg",
      "m image/jpeg",
      "x 29823b6d07e9da75b16dd3d05160b29bcd4bad8210f37e652a7ef1e58a0926ce",
      "size 287395",
      "dim 887x973",
      "blurhash TGRpBlM]t9s%t7k7W8Rjje%7oga^"
    ],
    [
      "imeta",
      "url https://pbs.twimg.com/media/HLqPHCBWgAASJGJ.png",
      "m image/png",
      "x 52a9d5dcbbf206463f2e0a625f213ffdd86d6834f2f720b5243034a85e35d367",
      "size 471653",
      "dim 865x867",
      "blurhash TAS6SlM^t2ndRiV=xTa}j[D{oixu"
    ],
    [
      "imeta",
      "url https://pbs.twimg.com/media/HLqP7BiWYAAg78A.png",
      "m image/png",
      "x 06750a911fc0d8d933bd47403a5e374bafc7dcb18842f64e1f90af850ac95de8",
      "size 180028",
      "dim 920x994",
      "blurhash TCSPXsM@tA%NW8W9M@j=j_Rfavof"
    ],
    [
      "imeta",
      "url https://pbs.twimg.com/media/HLqQuNpWAAAtxLu.png",
      "m image/png",
      "x 6f77f0a8fe7198a80d8cdd4f5035fe5211ac53361ed1cfa0674bcd082691e4f6",
      "size 237009",
      "dim 878x826",
      "blurhash L8SF@7IQxzoGw{WAoeW9bfa$j_t7"
    ],
    [
      "imeta",
      "url https://pbs.twimg.com/media/HLqSFRsXAAAEI3O.png",
      "m image/png",
      "x 2c3f87b8f39b825ee38c023b58a16c76aaf51829c2f3d41a0a50d2d44eedba16",
      "size 397560",
      "dim 871x809",
      "blurhash L9R:G,DzxzjCtCj[W9bI%9xwW8WR"
    ],
    [
      "imeta",
      "url https://pbs.twimg.com/media/HLqSha9XwAAi9mW.png",
      "m image/png",
      "x 81d45a8ce41cb8ae07de06bbab707cdf0496e93929c64db6847dbb046a445a0f",
      "size 449342",
      "dim 884x893",
      "blurhash T9R:G{DzxxWJWAoh%Gj^WE%Ls=fh"
    ],
    [
      "imeta",
      "url https://pbs.twimg.com/media/HLqTS5BXsAAAX2i.png",
      "m image/png",
      "x d96c6c0bf2f70c1b2f4ea89479fa6efef210cb9773d0070969e8602c172a06c7",
      "size 169626",
      "dim 873x546",
      "blurhash E6SPX:D#xwRNt9j[bjatWJogWEoO"
    ],
    [
      "imeta",
      "url https://pbs.twimg.com/media/HLqTd3AWcAAHBA1.jpg",
      "m image/jpeg",
      "x dc87933b2d1ae058f44db9fded311c8a34ceb6adc4635aa2b6f0606c4bc0cc8e",
      "size 156325",
      "dim 875x913",
      "blurhash TFSF@NM_t7Rdacays|avWBM[j=og"
    ],
    [
      "imeta",
      "url https://pbs.twimg.com/media/HLqUCiVWIAAu1lv.png",
      "m image/png",
      "x e4f734639401d9ffb7be760b92d42f96bd1d2ed5df2625eaba43fbab49d199ab",
      "size 13958"
    ],
    [
      "imeta",
      "url https://pbs.twimg.com/media/HLqUS4iXEAAGsL4.png",
      "m image/png",
      "x 8b184dd8a1a59202d8f14ba5a8b8e8bbd94a10b65749a028bd820240a6261794",
      "size 97947",
      "dim 892x461",
      "blurhash F3R{#?9F~qD%?bIU?b4nt7ofWBt7Rjxa"
    ]
  ],
  "content": "TLDR: The sabotage of Core.\nCore are compromised and corrupted. Core V30+ is a malware and an insider attack on Bitcoin.\n\nBy @hodlonaut\n\n1/ \n\nIn 2022, two developers put their name forward to become Bitcoin Core maintainers. Same project, same year, same process. \n\nOne was waved through in six days. \n\nThe other was worn down over five months and gave up. \n\nThe difference between them tells you how Core actually decides. A thread.\n\n2/ \n\nJuly 2022. Gloria Zhao files the PR to add herself to Core's trusted keys. It draws substantive NACKs. \n\nJames O'Beirne, a co-founder of Bitcoin Optech, no outsider, lays out a specific worry: she'd be maintaining the same mempool area she was actively writing and proposing designs for. A built-in conflict.\n\n3/ \n\nO'Beirne goes further. \n\nHe names a \"virtuous circle of mutual ACKs\" among a cohort of young maintainers tightly linked by funding and social ties, and asks for someone \"more disjoint from the funding and social graph.\" \n\nThe concern is structural, not personal.\n\nhttps://pbs.twimg.com/media/HLqMuiQWkAA10c0.png\n\n4/ \n\nIt doesn't matter. The reservations are noted, then set aside as raised in the wrong venue. \n\nThe PR is merged in six days. \n\nThe conflict O'Beirne flagged is never resolved, just routed past. Speed: one week.\n\n5/ \n\nAugust 2022. Vasil Dimov proposes himself as P2P maintainer. Dimov built Core's privacy networking from the ground up, BIP155, Tor v3, I2P. \n\nThe lead maintainer agrees on sight: \"you've been the most active in P2P development for quite a while.\" Broad support follows.\n\nhttps://pbs.twimg.com/media/HLqOq7zXIAA6b-6.jpg\n\n6/ \n\nThen fanquake files a scope objection, a list of 18 PRs Dimov supposedly wasn't involved in. \n\nDimov answers it with data and offers to narrow his scope to exactly what fanquake asked. \n\nfanquake's response? Nothing. No ACK, no NACK, no acknowledgment of the change he himself demanded. Just silence.\n\nhttps://pbs.twimg.com/media/HLqPHCBWgAASJGJ.png\n\n7/ \n\nThat silence is the weapon. Zhao, now a maintainer, says nothing for five months despite being asked by name, repeatedly. \n\nThe PR can't move without a maintainer signing off, and the maintainers won't speak. \n\nDimov, later: \"The silence was deafening. To me that meant disapproval, for reasons that cannot be publicly stated.\" and \"it was being sabotaged and something was happening behind the scenes.\"\n\nhttps://pbs.twimg.com/media/HLqP7BiWYAAg78A.png\n\n8/ \n\nMichael Folkson says out loud what the record shows: \n\n\"I remember the uproar when Luke didn't merge a PR adding a new BIP maintainer within a month of it being opened. He was hounded on IRC by certain individuals. Here it is fine to have a Bitcoin Core maintainer PR dangling for 5 months. Certain people should be ashamed of themselves.\"\n\nhttps://pbs.twimg.com/media/HLqQuNpWAAAtxLu.png\n\n9/ \n\nWhen contributors ask why it's stalled, the asking becomes the offense. \n\nAJ Towns invokes the CIA's Simple Sabotage Field Manual, against the people requesting an answer, not the people withholding one. \n\nAsked if he's calling Zhao and fanquake saboteurs, sipa replies: \"wtf.\" The question hangs.\n\nhttps://pbs.twimg.com/media/HLqSFRsXAAAEI3O.png\nhttps://pbs.twimg.com/media/HLqSha9XwAAi9mW.png\n\n10/ \n\nThe loop closes on itself. The maintainers won't explain their silence. When pressed, the explanation offered is that the people pressing are \"aggressive.\" \n\nThe demand for accountability is named as the reason accountability can't be given. \n\nYou cannot break it from outside, because trying to is the cited proof you're the problem.\n\n11/ \n\nJanuary 2023, 148 days since Dimov's maintainer PR was opened. \n\nAva Chow flips to NACK, having \"reached out to several contributors privately\" to form it. \n\nZhao finally posts, framing a maintainer as someone who should override \"any number of ACKs,\" and tells critics of Brink's influence to go found their own nonprofit. \n\nDimov closes his own PR: \"Doing so feels like failing all the people who ACKed it, sorry.\"\n\nhttps://pbs.twimg.com/media/HLqTS5BXsAAAX2i.png\nhttps://pbs.twimg.com/media/HLqTd3AWcAAHBA1.jpg\n\n12/ \n\nPut the two side by side. \n\nGloria's PR: NACKed on conflict grounds, merged in 6 days. \n\nDimov's PR: broadly supported, killed by 5 months of silence and private consultations no one disclosed. \n\nSame process, run in opposite directions depending on who was asking.\n\n13/ \n\nChow's own NACK said the quiet part. Previous maintainer additions were \"almost always foregone conclusions,\" the obvious choice. \n\nDimov was \"the first time we have had a maintainer nominee who I did not think was an obvious choice.\"\n\nTranslation: the others were decided before the meeting. Dimov wasn't pre-approved, so he didn't pass.\n\nhttps://pbs.twimg.com/media/HLqUCiVWIAAu1lv.png\n\n14/ Dimov's read: \n\n\"Gloria's was pre-arranged, decided upfront, and the IRC meeting and PR discussion was just democracy theater.\"\n\nExisting maintainers decide privately, then announce it as a nomination. He skipped that step. He just raised it in the open. That was the disqualifying move.\n\nhttps://pbs.twimg.com/media/HLqUS4iXEAAGsL4.png\n\n15/ \n\nNone of this rests on a hidden source. Every quote is from the public GitHub threads and IRC logs, linked in the article. \n\nThe takeaway sits in the contrast: Core's real selection test isn't the merit of the PR, it's whether you were pre-approved in private before the public process began.\n\nZhao was. Dimov wasn't. That's the whole difference.\n\ncitadel21.com/the-lever",
  "sig": "fdfb58dda2261f5c4acfa4697107fcb3b1d5f9531c0eb0cdaa2a5a058ef046649629022fe624f5cc8a90830492d8a8af5e6a461de87e2e32b826b81d25214788"
}