Nostr Web Client

Fellow #Bitcoin node runners:

If you are running Bitcoin Core 26.0 please enable this in your bitcoin.conf file:

v2transport=1

This will enable BIP324 v2 transport protocol which as I understand it causes communication to be encrypted between nodes that have v2transport enabled. I can see from my own node that there are very few other nodes have have BIP324 enabled! Lets bring those numbers up! You can check your own node with:

bitcoin-cli getpeerinfo | grep transport_protocol_type

and hopefully you see a few "v2".

Reply to this note

Please Login to reply.

Discussion

Citizen 2y ago 💬 1

Let's go #Bitcoin BIP324 people!

nostr:nevent1qqs9v99hj5kyq0sxx4vkjlhvytsc4yzlfjt8jp99zs6rdkvu5r9t6ugpz3mhxue69uhhyetvv9ujuerpd46hxtnfdupzpd5jln3mhfaal6g0hk06yjepre2ve74zqw5yr3rwhnn46hw72sslqvzqqqqqqy43dnk7

Bitcoin Samurai 2y ago

I will check and update my Umbrel node runner. Thanks!

Bitcoin Samurai 2y ago

No can do, running Bitcoin Core 24.0.1

BitcoinLizard 2y ago

I currently have 198 peer connections to my #Bitcoin node and have only 1 peer with whom I have a v2 Transport connection. At least I know it works but we have a long way to go!

Deleted Account 2y ago

💜

HODLBurger 1y ago

That's actually not a bad rate if it needs to be manually turned on, especially considering how relatively recently it was released.

vnprc 1y ago

YESSSSSSS

The Fishcake (nostr.build) 1y ago

Done! 🐶🐾🫂🫡

TKay 1y ago

I should do this. Thanks for the reminder.

Enki 1y ago

I still have yet to upgrade to v26.

Enki 1y ago

Ill stop being lazy, read the change log and update soon though. V2 transport sounds useful.

goodcharity 1y ago

None of my peers are using it ☹️

BitcoinLizard 1y ago

I had to have it running for a day or so before I got any v2 connections.

Hazey 1y ago

Useful

MaxMaxi 1y ago

Have not heard about it. Thanks for the heads up. I will do some research on this and get educated.

Misty Mountain 1y ago

any links to further reading on the topic?

BitcoinLizard 1y ago

It's mention in the release notes under "notable changes":

https://bitcoincore.org/en/releases/26.0/

humble 1y ago

nostr:npub126ntw5mnermmj0znhjhgdk8lh2af72sm8qfzq48umdlnhaj9kuns3le9ll this would be a great feature to add!

Niko 1y ago

Does this still allow comm between node thats havent activated the « v2 » ?

Erik 1y ago

Yes

Erik 1y ago

Last time I've checked, we had ~500 V2 enabled nodes. If I remember, I'll check again

atori 1y ago

Doing my part!

₿harat 1y ago

nostr:npub1aghreq2dpz3h3799hrawev5gf5zc2kt4ch9ykhp9utt0jd3gdu2qtlmhct will this be easy to change or set by default when we move to Bitcoin Core 26.0?

BitcoinLizard 1y ago

If you aren't familiar with the inner workings of Umbrel AND the bitcoin.conf file, it doesn't seem very easy/safe. Here are some people discussing making changes to bitcoin.conf on Umbrel:

https://community.umbrel.com/t/umbrel-5-0-update-where-is-bitcoin-conf/8060/2

I just run Arch Linux and run Bitcoin Core as a program on my system.

₿harat 1y ago

Thanks very much for looking into this.