📅 Original date posted:2013-05-03
📝 Original message:> Yes, I like that better than broadcasting the exact height starting at
> which you serve (though I would put that information immediately in the
> version announcement). I don't think we can rely on the addr broadcasting
> mechanism for fast information exchange anyway. One more problem with this:
> DNS seeds cannot convey this information (neither do they currently convey
> service bits, but at least those can be indexed separately, and served
> explicitly through asking for a specific subdomain or so).
>
That's true, but we can extend the DNS seeding protocol a little bit - you
could query <current-chain-height>.dnsseed.whatever.com and the DNS server
then only returns nodes it knows matches your requirement.
This might complicate existing seeds a bit, and it's a bit of a hack, but
protocol-wise it's still possible. Of course if you want to add more
dimensions it gets uglier fast.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20130503/98d57696/attachment.html>;
Mike Hearn [ARCHIVE] /
npub17t…4qgyd
2023-06-07 15:01:09
in reply to nevent1q…s87u
Author Public Key
npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgydPublished at
2023-06-07 15:01:09Event JSON
{
"id": "e077d15a531f17f2101bafb2f5815e75aa3e9540139a4af84fe073561f57ad4e",
"pubkey": "f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2",
"created_at": 1686150069,
"kind": 1,
"tags": [
[
"e",
"1092d5ea64142286a0cd5c2b3aebd8da882fcd6a0c7a755bcf6c68f75e2e26e6",
"",
"root"
],
[
"e",
"9b28f99f6475eeb49090a210665d47d01aa912275ba2f4a1dd570b0178bcc5db",
"",
"reply"
],
[
"p",
"5cb21bf5d7f25a9d46879713cbd32433bbc10e40ef813a3c28fe7355f49854d6"
]
],
"content": "📅 Original date posted:2013-05-03\n📝 Original message:\u003e Yes, I like that better than broadcasting the exact height starting at\n\u003e which you serve (though I would put that information immediately in the\n\u003e version announcement). I don't think we can rely on the addr broadcasting\n\u003e mechanism for fast information exchange anyway. One more problem with this:\n\u003e DNS seeds cannot convey this information (neither do they currently convey\n\u003e service bits, but at least those can be indexed separately, and served\n\u003e explicitly through asking for a specific subdomain or so).\n\u003e\n\nThat's true, but we can extend the DNS seeding protocol a little bit - you\ncould query \u003ccurrent-chain-height\u003e.dnsseed.whatever.com and the DNS server\nthen only returns nodes it knows matches your requirement.\n\nThis might complicate existing seeds a bit, and it's a bit of a hack, but\nprotocol-wise it's still possible. Of course if you want to add more\ndimensions it gets uglier fast.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20130503/98d57696/attachment.html\u003e",
"sig": "38af7858411f28f6ff1b66808eb7b9c4683c8f34a9ebf2605c9b95e1e772f83e8ebc6a38100b4dbeeefc2fe5b9253d2b9880457166662300c98d0bb26038d02b"
}