Core are compromised and corrupted to their core.

BitcoinIsFuture

npub1wl6kysagynfz2ulmw4wa2trnc9ycd52upjv9zt297n0tpr5ls7dqk5caw8

hex

7d36bbc724ce18a87c0813563d6760e304aabd2531473fc8ea18af08afa6b4fe

nevent

nevent1qqs86d4mcujvux9g0sypx43avaswxp92h5jnz3eler4p3tcg47ntflsprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgs80atzgw5zf539w0ah2hw493euzjvx69wqexz394zlfh4s360c0xsalvuqt

Kind-1 (TextNote)

2026-06-02T14:12:17Z

Core are compromised and corrupted to their core. https://pbs.twimg.com/media/HJw0JP7XQAEogOx.jpg

By hodlonaut

Replying to @ajtowns

Hi Anthony,

Since you did not reply to my DM about right of reply questions for my last article, I will try to reach you here.

On the topic of spam and spammers: May 2, 2025: instagibbs files the OP_RETURN uncap PR #32406. Eleven seconds after the bot announces it in #bitcoin-core-dev IRC channel, instagibbs writes "fanquake please lock for now." fanquake locks the PR within the same minute. You then add the "Needs release note" label to the now-locked PR. Fifteen minutes later you joke on IRC about labels being a way to "inscribe comments via github label edits."

Four operational acts by three devs that were instrumental in the OP_RETURN uncap sequence, inside a sixteen-minute window. The PR was filed, lock-requested, locked, and label-administered before any community engagement could begin. Four questions:

1: Was the sequence prearranged?

2: Do you consider this a proper and responsible way to conduct Bitcoin development on a contested protocol change?

3: Considering the great controversy and polarization, was your inscription joke fitting for the moment?

4: The same three of you, you and instagibbs and fanquake, ACKed and merged PR #27832 in June and August 2023, the documentation amendment that narrowed the scope of -datacarriersize, later used to close Luke's filter patch. The same three then executed the May 2 sequence on and around the PR that would uncapOP_RETURN. Coincidence? https://pbs.twimg.com/media/HJvbgOWWUAEMYJV.png https://pbs.twimg.com/media/HJvegcAXUAA3BGw.png

原始 JSON

{
  "kind": 1,
  "id": "7d36bbc724ce18a87c0813563d6760e304aabd2531473fc8ea18af08afa6b4fe",
  "pubkey": "77f56243a824d22573fb755dd52c73c14986d15c0c98512d45f4deb08e9f879a",
  "created_at": 1780409537,
  "tags": [
    [
      "imeta",
      "url https://pbs.twimg.com/media/HJw0JP7XQAEogOx.jpg",
      "m image/jpeg",
      "x 10891043d8ca0a901574078c25c8fb14135ce2b8359a5b529da28c7bfdc3dd25",
      "size 101254",
      "dim 892x1200",
      "blurhash bTL4sSva*F15xFnnM|V_9%tJ"
    ],
    [
      "imeta",
      "url https://pbs.twimg.com/media/HJvbgOWWUAEMYJV.png",
      "m image/png",
      "x a8f99ccc504107826c4434daa429a323671fb6fe3d4a8effcfc99811813cd8a1",
      "size 9319",
      "dim 542x182",
      "blurhash 83R3NK9D?04ZEU9w-?xKt9"
    ],
    [
      "imeta",
      "url https://pbs.twimg.com/media/HJvegcAXUAA3BGw.png",
      "m image/png",
      "x 0266f4a7d7425f31794d37f9e74e393114ebcb428a14619ff4569a35b5276f42",
      "size 37055",
      "dim 770x243",
      "blurhash 86SY~#4U,_RsR.bE%2-;-;"
    ],
    [
      "t",
      "32406"
    ],
    [
      "t",
      "bitcoin"
    ],
    [
      "t",
      "27832"
    ]
  ],
  "content": "Core are compromised and corrupted to their core.\nhttps://pbs.twimg.com/media/HJw0JP7XQAEogOx.jpg\n\nBy hodlonaut \n\nReplying to @ajtowns\n\nHi Anthony,\n\nSince you did not reply to my DM about right of reply questions for my last article, I will try to reach you here.\n\nOn the topic of spam and spammers:\nMay 2, 2025: instagibbs files the OP_RETURN uncap PR #32406. Eleven seconds after the bot announces it in #bitcoin-core-dev IRC channel, instagibbs writes \"fanquake please lock for now.\"\nfanquake locks the PR within the same minute. You then add the \"Needs release note\" label to the now-locked PR.\nFifteen minutes later you joke on IRC about labels being a way to \"inscribe comments via github label edits.\"\n\nFour operational acts by three devs that were instrumental in the OP_RETURN uncap sequence, inside a sixteen-minute window. The PR was filed, lock-requested, locked, and label-administered before any community engagement could begin.\nFour questions:\n\n1: Was the sequence prearranged?\n\n2: Do you consider this a proper and responsible way to conduct Bitcoin development on a contested protocol change?\n\n3: Considering the great controversy and polarization, was your inscription joke fitting for the moment?\n\n4: The same three of you, you and instagibbs and fanquake, ACKed and merged PR #27832 in June and August 2023, the documentation amendment that narrowed the scope of -datacarriersize, later used to close Luke's filter patch. The same three then executed the May 2 sequence on and around the PR that would uncapOP_RETURN. Coincidence?\nhttps://pbs.twimg.com/media/HJvbgOWWUAEMYJV.png\nhttps://pbs.twimg.com/media/HJvegcAXUAA3BGw.png",
  "sig": "84b8a40df685b3afcc91444e77a3f4ee9b176761f41543b59251e9a802039d281b3979cdbcb1f13718cdcaba7dcfcd8f5f2eaa2d33e7e2ac4334ce943eb1ba68"
}