> In short: brian_trollz made a narrow claim about Luke’s limited activist/organizational role in the 2017 UASF. asanoha_gold responded (in this tweet and the surrounding replies) by explaining the technical relationship between BIP 141 and BIP 148 and rhetorically questioning the other person’s knowledge of it. That explanation is true but orthogonal to the original point. It does not engage with, let alone refute, the claim about lack of lobbying or real work during the UASF itself. It changes the subject to something safer and more definitional while the core disagreement remains unaddressed.Why this tweet is incoherent in context and fails to address the original postIt completely ignores the actual accusation. brian_trollz never said “BIP 148 has nothing to do with BIP 141” or “Luke had zero involvement in SegWit code.” He explicitly distinguished the two:
Technical development of SegWit (BIP 141 era, earlier) ≠ the UASF activation campaign (BIP 148 in 2017). Asanoha’s tweet acts as if Shinobi is denying this basic fact, when Shinobi had already drawn exactly that distinction in prior replies in the thread (“Original Segwit development != UASF”).
It veers into an unrelated (or only superficially related) subject. The tweet reduces the debate to “here is what these two BIPs are — is this not true?” This is a classic goalpost shift. Even if Luke played a significant role in the technical implementation of BIP 141 (which is debatable in degree but granted by many), that still does not address whether he did the lobbying, business outreach, and coordination work that brian_trollz says actually drove the UASF’s success. Explaining the parent-child relationship between two BIPs does not prove Luke was central to the 2017 UASF effort. It’s like responding to “this general didn’t lead the battle” with “but he designed one of the weapons used in the war.” It’s true but irrelevant to the claim.
It comes across as condescending and missing the point. Addressing the “technical editor” of Bitcoin Magazine with a basic BIP 101-level explanation, phrased as a gotcha (“Is this not true?”), makes the reply seem incoherent in the conversation flow. By this point in the thread, Shinobi had already responded to asanoha’s longer list of Luke’s achievements by saying none of them were about BIP 148/UASF work. Repeating the BIP relationship at this stage doesn’t engage; it lectures on something already understood while dodging the substance.
Broader thread context reinforces the disconnect. asanoha had already posted a long list of Luke’s contributions (many from 2011–2013 or general node work) and claimed Luke “figured out the technical approach of SegWit BIP 141 for the 2017 UASF BIP 148.” Shinobi replied that none of it related to BIP 148. asanoha then doubled down on the BIP relationship instead of providing evidence of Luke doing the lobbying/convincing work that brian_trollz said was missing. The specific tweet in question is the continuation of that pivot.