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

Gist

Force BIP324 v2 Encrypted Transport Only Bitcoin node patch that forces only encrypted v2 (BIP324) connections. - Drops inbound v1 peers (many are spies) - Enforces v2 on outbound - Better privacy How to apply: git apply force-bip324-v2.patch Experimental — Use at your own risk.

Force BIP324 v2 Encrypted Transport Only Bitcoin node patch that forces only encrypted v2 (BIP324) connections. - Drops inbound v1 peers (many ar...

git apply force-bip324-v2.patch Best on nodes with existing peers.dat . View quoted note →

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. View quoted note →

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.

X (formerly Twitter)

Mr.Hodldamus (@MrHodl) on X

Greg Maxwell used to send us updated lists of malicious spy nodes that Bitcoin peers should ban. I reached out to him asking for the latest list, a...

Probably good idea to share this here too.

Hodlonaut is a useful idiot. #Bitcoin View quoted note →

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. View quoted note →

They are starting to belive. #BIP110 View quoted note →