📅 Original date posted:2015-09-24
📝 Original message:I considered that as well, but it seemed to me that other software on the
network (say, different wallet implementations) might prefer the option of
being able to bump up their protocol version in the future to pick up some
other change, without having to also opt-in to receiving
headers-announcements for blocks.
In particular, inv-based block announcements aren't going away (even in my
implementation of headers announcements, there are some edge cases where
the code would need to fall back to an inv announcement), so forcing all
software on the network to upgrade to supporting headers announcements,
whether now or in the future, seems too drastic -- I could imagine some
software not being very concerned about optimizing block relay in this
particular way.
On Thu, Sep 24, 2015 at 2:41 PM, Peter Todd <pete at petertodd.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
>
>
> On 24 September 2015 14:37:40 GMT-04:00, Suhas Daftuar via bitcoin-dev <
> bitcoin-dev at lists.linuxfoundation.org> wrote:
> >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).
>
> You can enable the behaviour based on advertised p2p network version.
> -----BEGIN PGP SIGNATURE-----
>
> iQE9BAEBCgAnIBxQZXRlciBUb2RkIDxwZXRlQHBldGVydG9kZC5vcmc+BQJWBEO5
> AAoJEMCF8hzn9Lncz4MH/3ztGWdFvMWWcwQsjIRH+eP6PH57WaEru1smmFYOmKrj
> djdiRVdxfChxRqP3adO21RUKKchjl8DNjrFJHPFz75FSM0cDcD0QAGAHilVdnICE
> LEIlTEoiIc0f1z9f/EJHSHPhiUXMnjpl/l7PYJFZV3Lt2Bl30yLsNnrp9qxjR30n
> 3nykZjyRad4JSavdTP6Evd3qaqwGXNUWsdObXNI+WPKlrw6hczlhFDKQ7RC1FPQU
> Rbgb21pavtqLUTwbBZGUisAAc94e2Gama1p3ioUFklbVtLTdw+FtxPgV/0ZS75OR
> V9pCXIbg9VM6QY4+9gYnP635+qCkqAJ4tBsYGmsT8yA=
> =cF4B
> -----END PGP SIGNATURE-----
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150924/dd34cc2a/attachment-0001.html>;
Suhas Daftuar [ARCHIVE] /
npub1ss…e0am4
2023-06-07 17:41:18
in reply to nevent1q…kgtu
Author Public Key
npub1ss2s89s938xfh3zzz0j2mhp25tlrlcrj0duljr0ne0t8v2r4cv0q5e0am4Published at
2023-06-07 17:41:18Event JSON
{
"id": "2aa4c79001560c0de4f7c1e79723cde97f7a1cfa673724daad36f7d3c1e14d66",
"pubkey": "841503960589cc9bc44213e4addc2aa2fe3fe0727b79f90df3cbd6762875c31e",
"created_at": 1686159678,
"kind": 1,
"tags": [
[
"e",
"0d3a1931bd697f6fdba192bdfb96df952fa8adcb12f2b0a69fc88dd7e7da3fb3",
"",
"root"
],
[
"e",
"ec5073b95567af30d1d5f504749c0c91595d6ff7041bb25f62ddeb6d49f5a88f",
"",
"reply"
],
[
"p",
"daa2fc676a25e3b5b45644540bcbd1e1168b111427cd0e3cf19c56194fb231aa"
]
],
"content": "📅 Original date posted:2015-09-24\n📝 Original message:I considered that as well, but it seemed to me that other software on the\nnetwork (say, different wallet implementations) might prefer the option of\nbeing able to bump up their protocol version in the future to pick up some\nother change, without having to also opt-in to receiving\nheaders-announcements for blocks.\n\nIn particular, inv-based block announcements aren't going away (even in my\nimplementation of headers announcements, there are some edge cases where\nthe code would need to fall back to an inv announcement), so forcing all\nsoftware on the network to upgrade to supporting headers announcements,\nwhether now or in the future, seems too drastic -- I could imagine some\nsoftware not being very concerned about optimizing block relay in this\nparticular way.\n\nOn Thu, Sep 24, 2015 at 2:41 PM, Peter Todd \u003cpete at petertodd.org\u003e wrote:\n\n\u003e -----BEGIN PGP SIGNED MESSAGE-----\n\u003e Hash: SHA512\n\u003e\n\u003e\n\u003e\n\u003e On 24 September 2015 14:37:40 GMT-04:00, Suhas Daftuar via bitcoin-dev \u003c\n\u003e bitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e \u003eOn Thu, Sep 24, 2015 at 2:17 PM, Tier Nolan via bitcoin-dev \u003c\n\u003e \u003ebitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e \u003e\n\u003e \u003e\u003e\n\u003e \u003e\u003e Is there actually a requirement for the new message? New nodes could\n\u003e \u003ejust\n\u003e \u003e\u003e unilaterally switch to sending headers and current nodes would be\n\u003e \u003e\u003e compatible.\n\u003e \u003e\u003e\n\u003e \u003e\n\u003e \u003eI don't believe that unilaterally switching to headers announcements\n\u003e \u003ewould\n\u003e \u003ework for all network participants -- both for users running older\n\u003e \u003eBitcoin\n\u003e \u003eCore versions (anything before 0.10, which I believe all ignore headers\n\u003e \u003emessages) and for non-Bitcoin Core software that participates on the\n\u003e \u003enetwork (which may ignore headers messages too, I'm not sure what all\n\u003e \u003eis\n\u003e \u003eout there).\n\u003e\n\u003e You can enable the behaviour based on advertised p2p network version.\n\u003e -----BEGIN PGP SIGNATURE-----\n\u003e\n\u003e iQE9BAEBCgAnIBxQZXRlciBUb2RkIDxwZXRlQHBldGVydG9kZC5vcmc+BQJWBEO5\n\u003e AAoJEMCF8hzn9Lncz4MH/3ztGWdFvMWWcwQsjIRH+eP6PH57WaEru1smmFYOmKrj\n\u003e djdiRVdxfChxRqP3adO21RUKKchjl8DNjrFJHPFz75FSM0cDcD0QAGAHilVdnICE\n\u003e LEIlTEoiIc0f1z9f/EJHSHPhiUXMnjpl/l7PYJFZV3Lt2Bl30yLsNnrp9qxjR30n\n\u003e 3nykZjyRad4JSavdTP6Evd3qaqwGXNUWsdObXNI+WPKlrw6hczlhFDKQ7RC1FPQU\n\u003e Rbgb21pavtqLUTwbBZGUisAAc94e2Gama1p3ioUFklbVtLTdw+FtxPgV/0ZS75OR\n\u003e V9pCXIbg9VM6QY4+9gYnP635+qCkqAJ4tBsYGmsT8yA=\n\u003e =cF4B\n\u003e -----END PGP SIGNATURE-----\n\u003e\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150924/dd34cc2a/attachment-0001.html\u003e",
"sig": "dfb87ccb6029a9fae82e7ec8d404115a0ff216ec6a720014964a01a5d1b66df85c42c3bfb3edb890ad8ccca77af87a7eb9a849493181f4295815b6774742dd9b"
}