📅 Original date posted:2013-06-19
📝 Original message:I’m also running into this exact same issue with my parser, now I understand why the relay field behavior I was seeing doesn’tmatch the wiki.
So to parse a version message, you can’t rely on the protocol version? You have to know how long the payload is, and then parse the message accordingly? I agree with Turkey Breast, this seems a bit sloppy to me.
Paul
P.S. I’ve never used a dev mailing list before and I want to get involved with the Bitcoin dev community, so let me know if I’m horribly violating any mailing list etiquette. 😊
From: Mike Hearn
Sent: Wednesday, June 19, 2013 7:43 AM
To: Turkey Breast
Cc: bitcoin-development at lists.sourceforge.net
Bitcoin-Qt on master does send it now although it doesn't affect anything, but as old pre-filtering versions will continue to exist, you'll always have to be able to deserialize version messages without it.
Bitcoin version messages have always had variable length, look at how the code is written in main.cpp. If you didn't experience issues until now all it means is that no sufficiently old nodes were talking to yours.
The standard does not say it should appear. Read it again - BIP 37 says about the new version message field:
If false then broadcast transactions will not be announced until a filter{load,add,clear} command is received. If missing or true, no change in protocol behaviour occurs.
On Wed, Jun 19, 2013 at 12:33 PM, Turkey Breast <turkeybreast at yahoo.com> wrote:
It's a problem if you work with iterators to deserialize the byte stream. Even failing that, it's just sloppy programming. What happens in the future when new fields are added to the version message? It's not a big deal to say that this protocol version has X number of fields, that (higher) protocol version message has X + N number of fields. Deterministic number of fields per protocol version is sensical and how Bitcoin has been for a long time.
And yes, it was a problem for me that caused a lot of confusion why this byte didn't exist in many version messages despite the standard saying it should and the code in bitcoind indicating it should. Nowhere was this written. It doesn't help other implementations to have an unclear behaviour that depends on some magic from one implementation.
From: Mike Hearn <mike at plan99.net>
To: Turkey Breast <turkeybreast at yahoo.com>
Cc: "bitcoin-development at lists.sourceforge.net" <bitcoin-development at 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 aware of. Is this solving some actual problem?
On Wed, Jun 19, 2013 at 12:30 AM, Turkey Breast <turkeybreast at yahoo.com> wrote:
That's me. I never said to make all messages fixed length. I said to make a fixed number of fields per protocol. So given a protocol version number, you know the number of fields in a message. This is not only easier for parsing messages, but just good practice. I don't see why a 1 byte flag needs to be optional anyway.
From: Mike Hearn <mike at plan99.net>
To: Turkey Breast <turkeybreast at yahoo.com>
Cc: Bitcoin Dev <bitcoin-development at lists.sourceforge.net>
Sent: Tuesday, June 18, 2013 9:48 PM
Subject: Re: [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 in the Bitcoin protocol that says all messages are fixed length, indeed, tx messages are allowed to have arbitrary data appended after them that gets relayed.
On Tue, Jun 18, 2013 at 7:45 PM, Turkey Breast <turkeybreast at yahoo.com> wrote:
See this BIP. I'm not sure if this is a bug or what, but it would be good if messages always had a fixed number of fields per protocol version.
https://en.bitcoin.it/wiki/BIP_0060#Code_Updates
This BIP details everything that needs to be done and proposes a protocol upgrade.
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Bitcoin-development mailing list
Bitcoin-development at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Bitcoin-development mailing list
Bitcoin-development at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Bitcoin-development mailing list
Bitcoin-development at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20130619/0831e4ce/attachment.html>;
-------------- next part --------------
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
-------------- next part --------------
_______________________________________________
Bitcoin-development mailing list
Bitcoin-development at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Paul Lyon [ARCHIVE] /
npub1j7…nz4rc
2023-06-07 15:03:41
in reply to nevent1q…7ktj
Author Public Key
npub1j7aht4gsujjs429043y5rz6yn75xm32tm42wunpc5kwp7mdxuscsknz4rcPublished at
2023-06-07 15:03:41Event JSON
{
"id": "d5216d764f74901747b37e00bbfc94103d659e053fe567d154c8be084a7b5931",
"pubkey": "97bb75d510e4a50aa8afac49418b449fa86dc54bdd54ee4c38a59c1f6da6e431",
"created_at": 1686150221,
"kind": 1,
"tags": [
[
"e",
"ceba0091ad9a2fc6abd2e8b950bead35c2f78a7f07c36f1b39214a94ffed3e49",
"",
"root"
],
[
"e",
"c6dac8b110300c9a0c079b3bf70c0f05afc1832dcda01a6ea93a5640427df2de",
"",
"reply"
],
[
"p",
"f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2"
]
],
"content": "📅 Original date posted:2013-06-19\n📝 Original message:I’m also running into this exact same issue with my parser, now I understand why the relay field behavior I was seeing doesn’tmatch the wiki.\n\n\nSo to parse a version message, you can’t rely on the protocol version? You have to know how long the payload is, and then parse the message accordingly? I agree with Turkey Breast, this seems a bit sloppy to me.\n\n\nPaul\n\n\nP.S. I’ve never used a dev mailing list before and I want to get involved with the Bitcoin dev community, so let me know if I’m horribly violating any mailing list etiquette. 😊\n\n\n\nFrom: Mike Hearn\nSent: Wednesday, June 19, 2013 7:43 AM\nTo: Turkey Breast\nCc: bitcoin-development at lists.sourceforge.net\n\n\nBitcoin-Qt on master does send it now although it doesn't affect anything, but as old pre-filtering versions will continue to exist, you'll always have to be able to deserialize version messages without it.\n\n\n\nBitcoin version messages have always had variable length, look at how the code is written in main.cpp. If you didn't experience issues until now all it means is that no sufficiently old nodes were talking to yours.\n\n\n\n\nThe standard does not say it should appear. Read it again - BIP 37 says about the new version message field:\n\n\nIf false then broadcast transactions will not be announced until a filter{load,add,clear} command is received. If missing or true, no change in protocol behaviour occurs.\n\n\n\n\n\nOn Wed, Jun 19, 2013 at 12:33 PM, Turkey Breast \u003cturkeybreast at yahoo.com\u003e wrote:\n\n\n\n\nIt's a problem if you work with iterators to deserialize the byte stream. Even failing that, it's just sloppy programming. What happens in the future when new fields are added to the version message? It's not a big deal to say that this protocol version has X number of fields, that (higher) protocol version message has X + N number of fields. Deterministic number of fields per protocol version is sensical and how Bitcoin has been for a long time.\n\n\n\n\nAnd yes, it was a problem for me that caused a lot of confusion why this byte didn't exist in many version messages despite the standard saying it should and the code in bitcoind indicating it should. Nowhere was this written. It doesn't help other implementations to have an unclear behaviour that depends on some magic from one implementation.\n\n\n\n\n\n\n\n\n\n\nFrom: Mike Hearn \u003cmike at plan99.net\u003e\nTo: Turkey Breast \u003cturkeybreast at yahoo.com\u003e \n\nCc: \"bitcoin-development at lists.sourceforge.net\" \u003cbitcoin-development at lists.sourceforge.net\u003e \nSent: Wednesday, June 19, 2013 11:39 AM\n\n\nSubject: Re: [Bitcoin-development] Missing fRelayTxes in version message\n\n \n\n\n\n\n\nIt has to be optional because old clients don't send it, obviously.\n\n\n\nWhy is this even an issue? There's no problem with variable length messages in any codebase that I'm aware of. Is this solving some actual problem?\n\n\n\n\nOn Wed, Jun 19, 2013 at 12:30 AM, Turkey Breast \u003cturkeybreast at yahoo.com\u003e wrote:\n\n\n\n\nThat's me. I never said to make all messages fixed length. I said to make a fixed number of fields per protocol. So given a protocol version number, you know the number of fields in a message. This is not only easier for parsing messages, but just good practice. I don't see why a 1 byte flag needs to be optional anyway.\n\n\n\n\n\n\n\n\n\n\n\n\n\nFrom: Mike Hearn \u003cmike at plan99.net\u003e\nTo: Turkey Breast \u003cturkeybreast at yahoo.com\u003e \nCc: Bitcoin Dev \u003cbitcoin-development at lists.sourceforge.net\u003e \nSent: Tuesday, June 18, 2013 9:48 PM\nSubject: Re: [Bitcoin-development] Missing fRelayTxes in version message\n \n\n\n\n\n\n\nIt's not a bug (although there was recently a change to make bitcoind/qt always send this field anyway). \n\n\n\nI 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, indeed, tx messages are allowed to have arbitrary data appended after them that gets relayed.\n\n\n\n\nOn Tue, Jun 18, 2013 at 7:45 PM, Turkey Breast \u003cturkeybreast at yahoo.com\u003e wrote:\n\n\n\n\nSee this BIP. I'm not sure if this is a bug or what, but it would be good if messages always had a fixed number of fields per protocol version.\n\n\n\n\nhttps://en.bitcoin.it/wiki/BIP_0060#Code_Updates\n\n\n\n\nThis BIP details everything that needs to be done and proposes a protocol upgrade.\n\n\n------------------------------------------------------------------------------\nThis SF.net email is sponsored by Windows:\n\nBuild for Windows Store.\n\nhttp://p.sf.net/sfu/windows-dev2dev\n_______________________________________________\nBitcoin-development mailing list\nBitcoin-development at lists.sourceforge.net\nhttps://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\n\n\n\n\n------------------------------------------------------------------------------\nThis SF.net email is sponsored by Windows:\n\nBuild for Windows Store.\n\nhttp://p.sf.net/sfu/windows-dev2dev\n_______________________________________________\nBitcoin-development mailing list\nBitcoin-development at lists.sourceforge.net\nhttps://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\n\n\n\n\n------------------------------------------------------------------------------\nThis SF.net email is sponsored by Windows:\n\nBuild for Windows Store.\n\nhttp://p.sf.net/sfu/windows-dev2dev\n_______________________________________________\nBitcoin-development mailing list\nBitcoin-development at lists.sourceforge.net\nhttps://lists.sourceforge.net/lists/listinfo/bitcoin-development\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20130619/0831e4ce/attachment.html\u003e\n-------------- next part --------------\n------------------------------------------------------------------------------\nThis SF.net email is sponsored by Windows:\n\nBuild for Windows Store.\n\nhttp://p.sf.net/sfu/windows-dev2dev\n-------------- next part --------------\n_______________________________________________\nBitcoin-development mailing list\nBitcoin-development at lists.sourceforge.net\nhttps://lists.sourceforge.net/lists/listinfo/bitcoin-development",
"sig": "af515bedcfcd3cf42efb23e6458e4015a56345f3352020b4bfcf5d572a47931e72ed12cf8ae70dedcfecfca6a728d4b27b8859d5a6e2bf748c9337c77b7968db"
}