Peter Todd [ARCHIVE] on Nostr: 📅 Original date posted:2014-04-10 📝 Original message:-----BEGIN PGP SIGNED ...
📅 Original date posted:2014-04-10
📝 Original message:-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 10 April 2014 07:32:44 GMT-04:00, Pieter Wuille <pieter.wuille at gmail.com> wrote:
>There were earlier discussions.
>
>The two ideas were either using one or a few service bits to indicate
>availability of blocks, or to extend addr messages with some flags to
>indicate this information.
>
>I wonder whether we can't have a hybrid: bits to indicate general
>degree of availability of blocks (none, only recent, everything), but
>indicate actual availability only upon actually connecting (through a
>"version" extension, or - preferably - a separate message). Reason is
>that the actual blocks available are likely to change frequently (if
>you keep the last week of blocks, a 3-day old addr entry will have
>quite outdated information), and not that important to actual peer
>selection - only to drive the decision which blocks to ask after
>connection.
Why not just put an expiration date on that information and delay deletion until the expiration is reached?
Also, its worth noting how the node bit solution you proposed can be done as a gradual upgrade path for SPV client. From the perspective of nodes that don't know about it they just see the pruned nodes as SPV nodes without any chain data at all. The only issue would be if large numbers of uses turned off their full nodes, but that's a possibility regardless. Done with partial UTXO set mode this may even result in an eventual increase in the number of full nodes.
-----BEGIN PGP SIGNATURE-----
Version: APG v1.1.1
iQFQBAEBCgA6BQJTRoPZMxxQZXRlciBUb2RkIChsb3cgc2VjdXJpdHkga2V5KSA8
cGV0ZUBwZXRlcnRvZGQub3JnPgAKCRAZnIM7qOfwhetrCACA02EJQ0VpcYvafuNc
7pvqMVeirJRu3Uv7Wy8rcl9jW5irM5fmNdznARtv2vwpEZN7MU0wp3ZY1FYOCv2f
PvWC7DBCSBs2BuyGkvPuwnXEppTrYmWFT3qjg+99lF1IlOV4yWFacja2RGDuJkea
fYUkODosHJjFVcXi5aMkBPQ5sOFdlUVbC94YV4d4PDSmF2fHLGG8uEfEweYb6Pv+
gj1CsfuAWf8DWzygDeL8x/wOG9HeqYqEbjxyOb9hxlp1ByUof+4WJtz3QfGsR2Xt
fvkmgS8vkUxSIZorMdypj7oLBOnfDW1bEK5He2SlqPdYi5FEQusZ/jMMX3Fw74GV
fJKt
=Wyv8
-----END PGP SIGNATURE-----
📝 Original message:-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 10 April 2014 07:32:44 GMT-04:00, Pieter Wuille <pieter.wuille at gmail.com> wrote:
>There were earlier discussions.
>
>The two ideas were either using one or a few service bits to indicate
>availability of blocks, or to extend addr messages with some flags to
>indicate this information.
>
>I wonder whether we can't have a hybrid: bits to indicate general
>degree of availability of blocks (none, only recent, everything), but
>indicate actual availability only upon actually connecting (through a
>"version" extension, or - preferably - a separate message). Reason is
>that the actual blocks available are likely to change frequently (if
>you keep the last week of blocks, a 3-day old addr entry will have
>quite outdated information), and not that important to actual peer
>selection - only to drive the decision which blocks to ask after
>connection.
Why not just put an expiration date on that information and delay deletion until the expiration is reached?
Also, its worth noting how the node bit solution you proposed can be done as a gradual upgrade path for SPV client. From the perspective of nodes that don't know about it they just see the pruned nodes as SPV nodes without any chain data at all. The only issue would be if large numbers of uses turned off their full nodes, but that's a possibility regardless. Done with partial UTXO set mode this may even result in an eventual increase in the number of full nodes.
-----BEGIN PGP SIGNATURE-----
Version: APG v1.1.1
iQFQBAEBCgA6BQJTRoPZMxxQZXRlciBUb2RkIChsb3cgc2VjdXJpdHkga2V5KSA8
cGV0ZUBwZXRlcnRvZGQub3JnPgAKCRAZnIM7qOfwhetrCACA02EJQ0VpcYvafuNc
7pvqMVeirJRu3Uv7Wy8rcl9jW5irM5fmNdznARtv2vwpEZN7MU0wp3ZY1FYOCv2f
PvWC7DBCSBs2BuyGkvPuwnXEppTrYmWFT3qjg+99lF1IlOV4yWFacja2RGDuJkea
fYUkODosHJjFVcXi5aMkBPQ5sOFdlUVbC94YV4d4PDSmF2fHLGG8uEfEweYb6Pv+
gj1CsfuAWf8DWzygDeL8x/wOG9HeqYqEbjxyOb9hxlp1ByUof+4WJtz3QfGsR2Xt
fvkmgS8vkUxSIZorMdypj7oLBOnfDW1bEK5He2SlqPdYi5FEQusZ/jMMX3Fw74GV
fJKt
=Wyv8
-----END PGP SIGNATURE-----