Johnny Vee 🚀

Choose Rich 🍊 💊

[Johnny Vee 🚀 @realjohnnyvee]

@AlgodTrading I was worried I was being too normie just stacking BTC.. 😅

[Johnny Vee 🚀 @realjohnnyvee]

@soapminer1 @sophaller 😍

[Johnny Vee 🚀 @realjohnnyvee]

@BitcoinRebel

[Johnny Vee 🚀 @realjohnnyvee]

@BitcoinRebel Grape blunt wrap 🤦

[Hunter Beast 🕯️ @cryptoquick]

I've been doing a lot of research into 110. My interest is in making sure that we do everything we can imagine to make sure Bitcoin is ready against every conceivable threat.

I still have found no valid technical, social, or financial reason against it, and I have strong arguments for.

I have reviewed Vortex's concerns that people often link to and don't find they hold up against close scrutiny.

I will be providing my own arguments in favor of 110 soon enough.

For now, I have signalled in support, and if anyone takes issue with my strong opinion, just know that I am willing to change my mind based on new input. Are you?

[Johnny Vee 🚀 @realjohnnyvee]

@BitcoinRebel

[Johnny Vee 🚀 @realjohnnyvee]

@BitcoinRebel To strip

[Johnny Vee 🚀 @realjohnnyvee]

@BitcoinRebel @michelleo_21mil Rebel without a cause

[Johnny Vee 🚀 @realjohnnyvee]

@soapminer1 Can’t wait to try it 🍊

[Johnny Vee 🚀 @realjohnnyvee]

@asanoha_gold @brian_trollz The thing that made me instantly dislike this guy is his covidiot mask. Edit for Ethereum or Kaspa Magazine you leftist freak.

[Asanoha | Bitcoin Art Magazine @asanoha_gold]

Shinobi (@brian_trollz), Technical & Opinion Editor at Bitcoin Magazine (heavy emphasis on opinion), is abusing his position of authority by attempting to downplay and smear Luke Dashjr’s historical contributions to Bitcoin. This is notable because Bitcoin Magazine is funded by interests that have long benefited from, and actively promoted, the very data heavy use cases (Ordinals, inscriptions, and large OP RETURN spam) that Luke’s Bitcoin Knots client is specifically designed to filter by default.

Even more concerning is the clear conflict of interest: his employer’s backers have a financial incentive to marginalize developers who prioritize Bitcoin as sound money over turning it into a general data storage layer.

It is shocking that Bitcoin Magazine’s leadership tolerates this level of unprofessionalism and bad faith argumentation from someone they present as an authoritative technical voice. Shinobi repeatedly resorts to calling people “retards” and other insults when anyone calmly tries to reason with him, presents an opposing view, or engages in honest discussion.

Outlined below are the documented facts that directly refute Shinobi’s claims. This is a response to Shinobi’s comments in the tweet below.

Part 1: Luke’s role in BIP 141 (SegWit) technical implementation

- BIP 141 (SegWit) was authored by Pieter Wuille, Eric Lombrozo, and Johnson Lau, but Luke Dashjr played a key technical role in making it work as a soft fork rather than requiring a hard fork.

- In late 2015, Luke described the method to implement SegWit as a soft fork. Pieter Wuille then used this approach (combined with his Elements experience) to build the actual implementation.

- Luke helped design SegWit as a soft fork (the approach that became BIP 141) and updated getblocktemplate (GBT) to support SegWit.

- As a long time Bitcoin Core contributor, he worked on the underlying code changes, reviews, and infrastructure needed to integrate SegWit safely into the main client.

This technical foundation, SegWit as a soft fork, was the direct basis that BIP 148 later used to enforce activation.

Part 2: Luke’s direct code contributions to BIP 148

- Luke created and maintained his own dedicated branch (luke-jr:bip148) containing the working implementation of BIP 148 rules.

- GitHub PR #10532 (bip148 option) was explicitly built on top of his branch. The opening comment states it was based on luke jr’s ‘non dos(100)’ version of the code.

Specific pieces of code Luke wrote or directly contributed include:

- Core BIP 148 UASF enforcement logic
- DoS protection rework (disconnecting rather than banning peers for invalid blocks)
- Definition of a service bit for BIP 148 nodes
- Preferential peering logic with other BIP 148 enforcing nodes
- BIP 148 indicator in user agent comments
- Functional tests (bip148 segwit https://t.co/c4Kv9KUQ3d and related fixes)
- Logic to check BIP 148 rules on historical blocks and handle rewinding if necessary
- Multiple rebases and fixes to integrate with other ongoing Core changes

Luke’s branch provided the practical code foundation that others built upon to add BIP 148 support to Bitcoin Core. While the most widely used UASF client came from the separate UASF group, Luke’s implementation work was real, documented, and directly referenced throughout the development process.

[Jim | RDTS | Bitcoin, not jpegs @venorusprime]

@MichaelDunwort1 I love every chance I get to use this meme

[Johnny Vee 🚀 @realjohnnyvee]

@EmmettLong8 @TheBitcoinTrain @jackmallers @saylor ⬆️

[Johnny Vee 🚀 @realjohnnyvee]

@criscrinkl @elonmusk Mine isn’t for sale

[Johnny Vee 🚀 @realjohnnyvee]

@soapminer1 Best scent?

[Johnny Vee 🚀 @realjohnnyvee]

@AAStack What do you think of Andy Black

[Johnny Vee 🚀 @realjohnnyvee]

@AAStack We need a video tutorial how you prepare your steaks sir

[Alexander Leishman 🇺🇸 @Leishman]

If you think the SpaceX IPO is big just wait until Buc-ee's IPOs.

[Elon Musk @elonmusk]

@zerohedge True.

That is why Bitcoin is based on energy: you can issue fake fiat currency, and every government in history has done so, but it is impossible to fake energy.

[Johnny Vee 🚀 @realjohnnyvee]

@AAStack Sorry bro @mattkratter is the goat. You are mistaken