📅 Original date posted:2015-09-24
📝 Original message:On Thu, Sep 24, 2015 at 2:17 PM, Tier Nolan via bitcoin-dev <
bitcoin-dev at lists.linuxfoundation.org> wrote:
>
> Is there actually a requirement for the new message? New nodes could just
> unilaterally switch to sending headers and current nodes would be
> compatible.
>
I don't believe that unilaterally switching to headers announcements would
work for all network participants -- both for users running older Bitcoin
Core versions (anything before 0.10, which I believe all ignore headers
messages) and for non-Bitcoin Core software that participates on the
network (which may ignore headers messages too, I'm not sure what all is
out there).
Even for Bitcoin Core versions 0.10 and 0.11, which process headers and use
them to determine what blocks to download, the block fetching logic is not
optimized for new block announcements via headers messages. Part of what
is implemented in the pull request is direct fetching of blocks upon
receiving a headers message; nodes that don't implement block downloading
in response to headers announcements should continue to receive inv's, I
think -- hence this p2p message to opt-in to the new behavior.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150924/dd63b110/attachment.html>;
Suhas Daftuar [ARCHIVE] /
npub1ss…e0am4
2023-06-07 17:41:18
in reply to nevent1q…9q7c
Author Public Key
npub1ss2s89s938xfh3zzz0j2mhp25tlrlcrj0duljr0ne0t8v2r4cv0q5e0am4Published at
2023-06-07 17:41:18Event JSON
{
"id": "71929d53bb1c9136f1396784703d01f35a38534089bcc958ea0fa90ffb8a74f8",
"pubkey": "841503960589cc9bc44213e4addc2aa2fe3fe0727b79f90df3cbd6762875c31e",
"created_at": 1686159678,
"kind": 1,
"tags": [
[
"e",
"0d3a1931bd697f6fdba192bdfb96df952fa8adcb12f2b0a69fc88dd7e7da3fb3",
"",
"root"
],
[
"e",
"49df9b7b68517083b22f4d2312b88af1c4daa0d3b3b28290b9d6b52fc3f760d1",
"",
"reply"
],
[
"p",
"46986f86b97cc97829a031b03209644d134b939d0163375467f0b1363e0d875e"
]
],
"content": "📅 Original date posted:2015-09-24\n📝 Original message:On Thu, Sep 24, 2015 at 2:17 PM, Tier Nolan via bitcoin-dev \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e\n\u003e Is there actually a requirement for the new message? New nodes could just\n\u003e unilaterally switch to sending headers and current nodes would be\n\u003e compatible.\n\u003e\n\nI don't believe that unilaterally switching to headers announcements would\nwork for all network participants -- both for users running older Bitcoin\nCore versions (anything before 0.10, which I believe all ignore headers\nmessages) and for non-Bitcoin Core software that participates on the\nnetwork (which may ignore headers messages too, I'm not sure what all is\nout there).\n\nEven for Bitcoin Core versions 0.10 and 0.11, which process headers and use\nthem to determine what blocks to download, the block fetching logic is not\noptimized for new block announcements via headers messages. Part of what\nis implemented in the pull request is direct fetching of blocks upon\nreceiving a headers message; nodes that don't implement block downloading\nin response to headers announcements should continue to receive inv's, I\nthink -- hence this p2p message to opt-in to the new behavior.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150924/dd63b110/attachment.html\u003e",
"sig": "b471d41628946aed1e5f7b6b5eeaec6ff2f8f40207fc6d49a83fe02e44703787215a4632f57aae176b3c56f3cd57c8a359b491fa8418a7e1ce695f20f04bb2f0"
}