📅 Original date posted:2013-06-18
📝 Original 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20130618/b5a7149b/attachment.html>;
Mike Hearn [ARCHIVE] /
npub17t…4qgyd
2023-06-07 15:03:39
in reply to nevent1q…ut0t
Author Public Key
npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgydPublished at
2023-06-07 15:03:39Event JSON
{
"id": "5db0d1fd8bbce5fdfe7f2e1d7d080ab4602992c8bd85e16635d09f42e17d426e",
"pubkey": "f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2",
"created_at": 1686150219,
"kind": 1,
"tags": [
[
"e",
"ceba0091ad9a2fc6abd2e8b950bead35c2f78a7f07c36f1b39214a94ffed3e49",
"",
"root"
],
[
"e",
"e59f6bb8f98322123762e9198e54b669a82bd5c602da7a82447b685f65c5c3fd",
"",
"reply"
],
[
"p",
"0f2093d510aaf88a0e1bf26aa961fff7868f4cf0dbd6154fad9c40c66dda8519"
]
],
"content": "📅 Original date posted:2013-06-18\n📝 Original message:It's not a bug (although there was recently a change to make bitcoind/qt\nalways send this field anyway).\n\nI don't know where Amir is going with BIP 60. Version messages have always\nbeen variable length. There's nothing inherent in the Bitcoin protocol that\nsays all messages are fixed length, indeed, tx messages are allowed to have\narbitrary data appended after them that gets relayed.\n\n\nOn Tue, Jun 18, 2013 at 7:45 PM, Turkey Breast \u003cturkeybreast at yahoo.com\u003ewrote:\n\n\u003e See this BIP. I'm not sure if this is a bug or what, but it would be good\n\u003e if messages always had a fixed number of fields per protocol version.\n\u003e\n\u003e https://en.bitcoin.it/wiki/BIP_0060#Code_Updates\n\u003e\n\u003e This BIP details everything that needs to be done and proposes a protocol\n\u003e upgrade.\n\u003e\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e This SF.net email is sponsored by Windows:\n\u003e\n\u003e Build for Windows Store.\n\u003e\n\u003e http://p.sf.net/sfu/windows-dev2dev\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20130618/b5a7149b/attachment.html\u003e",
"sig": "5e9d6a186d8a2c1dee5c4a003705e5af608f6e6bffd5b7490b2f58ca2e6c2438fdab70566ba28d6ae5b3fd877e7462cdb399d92b723bf0135051a4d6aa0d2306"
}