📅 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 14:56:18
in reply to nevent1q…g3vx
Author Public Key
npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgydPublished at
2023-06-07 14:56:18Event JSON
{
"id": "d13b26edc514d4f717974ed0cd2750a74c99b981431201ce7000d50344f831c3",
"pubkey": "f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2",
"created_at": 1686149778,
"kind": 1,
"tags": [
[
"e",
"29ec2e2b5b2f4dc51eb87cabd53d5f02656fee9d1f600fd1d211680c53c784ad",
"",
"root"
],
[
"e",
"c74f4a2a8ac1c955430cf2be94f5a3dcbaadae19e97df89e8cb2c124f8530662",
"",
"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": "05e4be8a1da3b2d95e792a50b3f12f3f5266ea75b9ccb325e7d92c75e5333c6d91124b230955c81de0bd884c86f22d86da36b66d85a5bc5cdf2ee9f0b6f87492"
}