Bitcoin : I’d like some clarification on the 32MB P2P protocol limit
I’m not too familiar with the Bitcoin code base specifically, but I understand (that is, I like to think I understand) basic software and coding terminology. My question is this: How come a client can’t just make a TCP socket (or whatever) with a bigger buffer? Where is this stored? In any case, couldn’t it be done with a simple variable change?
I heard this was something to do with threading, but how hard would it be to just create a receive thread for each connection (which pushes things into a buffer), and then have other threads that can pull out and process those messages in parallel?
I also was just reading the Bitcoin Wiki and saw that the “length” field of a message is limited to a 4-byte integer. Does this mean that messages can’t be larger than 2^32 bytes in length? Will this pose another challenge for scaling the network once we hit 4GB blocks?
Thanks in advance for any clarification, this entire Bitcoin code base is extremely complicated. I might start working on a simpler JavaScript version that can still talk with the rest of the BCH network, that’s why I’m inquiring about the network protocol.
PS: Anyone know the “magic numbers” for BCH? Same as BTC?
Bitcoin
Bitcoin is a distributed, worldwide, decentralized digital money. Bitcoins are issued and managed without any central authority.
FindCrypto scans the web for the latest Bitcoin news, so you can find all the latest and breaking news in one convenient location.
Author: UTXONinja
Score: 2
Don’t forget to share the post if you love it !
