bitcoin-development@lists.sourceforge.net
Sent: Wednesday, June 19, 2013 3:20 PM
Subject: Re: [Bitcoin-development] Missing fRelayTxes in version message
If you want to criticise the Bitcoin protocol for sloppyness, the variable
length of some messages isn't where I'd start.
Note that ping
bitcoin-development@lists.sourceforge.net
*Sent:* Wednesday, June 19, 2013 3:20 PM
*Subject:* Re: [Bitcoin-development] Missing fRelayTxes in version message
If you want to criticise the Bitcoin protocol for sloppyness, the variable
length of some messages isn't where I'd start.
Note that ping has
:* Wednesday, June 19, 2013 3:20 PM
*Subject:* Re: [Bitcoin-development] Missing fRelayTxes in version message
If you want to criticise the Bitcoin protocol for sloppyness, the variable
length of some messages isn't where I'd start.
Note that ping has the same issue, its length has changed over
turkeybre...@yahoo.com
Cc: bitcoin-development@lists.sourceforge.net
bitcoin-development@lists.sourceforge.net
Sent: Wednesday, June 19, 2013 11:39 AM
Subject: Re: [Bitcoin-development] Missing fRelayTxes in version message
It has to be optional because old clients don't send it, obviously.
Why
@lists.sourceforge.net
*Sent:* Wednesday, June 19, 2013 11:39 AM
*Subject:* Re: [Bitcoin-development] Missing fRelayTxes in version message
It has to be optional because old clients don't send it, obviously.
Why is this even an issue? There's no problem with variable length
messages in any codebase that I'm
: [Bitcoin-development] Missing fRelayTxes in version
message
It's not a bug (although there was recently a change to make bitcoind/qt
always send this field anyway).
I don't know where Amir is going with BIP 60. Version messages have
always been variable length. There's nothing inherent
-development@lists.sourceforge.net
bitcoin-development@lists.sourceforge.net
Sent: Wednesday, June 19, 2013 11:39 AM
Subject: Re: [Bitcoin-development] Missing fRelayTxes in version message
It has to be optional because old clients don't send it, obviously.
Why is this even an issue
It's not a bug (although there was recently a change to make bitcoind/qt
always send this field anyway).
I don't know where Amir is going with BIP 60. Version messages have always
been variable length. There's nothing inherent in the Bitcoin protocol that
says all messages are fixed length,
needs to be
optional anyway.
From: Mike Hearn m...@plan99.net
To: Turkey Breast turkeybre...@yahoo.com
Cc: Bitcoin Dev bitcoin-development@lists.sourceforge.net
Sent: Tuesday, June 18, 2013 9:48 PM
Subject: Re: [Bitcoin-development] Missing fRelayTxes in version
9 matches
Mail list logo
