MrHodl

https://x.com/MrHodl/status/2107088418328965427

https://x.com/MrHodl/status/2106514934570123438

OogaBooga.rocks

Are we on the same page yet?

Things took a turn. Light bulb went off and now I can't stop working on this.

I'm building a fully offline personal memory vault. All my notes stay in simple Markdown files, everything gets embedded locally, and no matter which model I load in LM Studio, it actually remembers me and my stuff. Feels like having my own private Grok that never forgets and never phones home.

Never in my wildest dreams did I ever think I can do something like this. Wild times.

I will never forgive Mechanic for making me break my own rule. He's a pathetic liar trying to make it seem that BIP110 is the same thing as BIP148.

TIL that Primal is the enemy of Nostr.

Force BIP324 v2 Only

Bitcoin Core patch that makes your node use only encrypted v2 connections:

• Drops inbound v1 peers (most spies) • Enforces v2 on outbound • Stronger privacy

https://gist.github.com/MrHodlX/2076956bd4eead157ca2742f15c7ce28

git apply force-bip324-v2.patch

Best on nodes with existing peers.dat .

The patch forces your node to only talk to peers using BIP324 v2 encrypted transport. Right now most spies on the network are still using the old unencrypted v1 connections while they request transaction relay and hoover up data. This patch drops those v1 relay peers on inbound and strictly enforces v2 on outbound so the spies get disconnected fast.

At the same time, it pushes the whole network toward real privacy through encryption without breaking blocks only connections or dnsseeds. The network gets stronger and harder to surveil the more nodes run it. That's pretty much it.

Bitcoiners: In the literal sense...

Would you run a Bitcoin Core patch that disconnects v1 peers and only keeps BIP324 (v2 transport) peers?

It advertises NODE_P2P_V2, drops outbound v1 peers, drops relay peers using v1, and drops peers claiming v2 support while connecting via v1.

I think it's exactly what the network needs to speed BIP324 adoption, but I could be wrong.

https://x.com/i/status/2058888274454663221

Probably good idea to share this here too.

I thought all the retarded retards are on twitter with me? 😂

Hodlonaut is a useful idiot. #Bitcoin

Knots version 2.0 😂

Two moments in Bitcoin actually had me sweating bullets.

First: Coinbase announced that basically every major exchange was ready to fork to Bitcoin Classic (total lie, but I didn't know that yet). I'd only been in for 3–4 years. I genuinely thought the network was already captured. My head wasn't fully wrapped around things.

Second one hit even harder: UASF (BIP148). I was staring down the barrel, thinking I'd have to sit my family and friends down and explain: "Hey, your wallets are connected to my BIP148 node. If things split on Aug 1, you'll hold coins on both sides at first... But after that? Any future buys, deposits, or whatever comes in...they'll be BIP148 Bitcoin, not the legacy chain the miners were trying to keep cucked under Jihan & co."

When it comes to BIP110 chmaps..there might be 2 or 3 guys the truly grasp the danger of forking without enough support. The rest are just useful idiots going for a ride.

The guy has been here for probably 10 years and has no idea that OP_RETURN was part of Bitcoin since inception. In bitcoin it has always been uncapped.

Bitcoin Core is NOT Bitcoin.

They are starting to belive.

#BIP110

When you see it you can't unsee it.

Absolutely clueless.

This shitcoiner understands bitcoin better then a taco bell maxi pleb.

Fucking sad.