š
Original date posted:2013-05-03
š Original message:On Fri, May 03, 2013 at 04:06:29PM +0200, Mike Hearn wrote:
> 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.
If you're going to take a step like that, the <current-chain-height>
should be rounded off, perhaps to some number of bits, or you'll allow
DNS caching to be defeated.
Make clients check for the largest "rounded off" value first, and then
drill down if required. Some complexity involved...
> 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.
Maybe I should make my blockheaders-over-dns thing production worthy
first so we can see how many ISP's come at us with pitchforks? :P
--
'peter'[:-1]@petertodd.org
00000000000000142de0244ee8fac516e7c0a29da1eafc0d43f2da8b6388b387
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20130503/b7a549e8/attachment.sig>;
Peter Todd [ARCHIVE] /
npub1m2ā¦a2np2
2023-06-07 14:56:18
in reply to nevent1qā¦6lw9
Author Public Key
npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2Published at
2023-06-07 14:56:18Event JSON
{
"id": "8ebbcd01a42ed30636f606400974009dac8566455096218ea9b83d87da7a7aea",
"pubkey": "daa2fc676a25e3b5b45644540bcbd1e1168b111427cd0e3cf19c56194fb231aa",
"created_at": 1686149778,
"kind": 1,
"tags": [
[
"e",
"29ec2e2b5b2f4dc51eb87cabd53d5f02656fee9d1f600fd1d211680c53c784ad",
"",
"root"
],
[
"e",
"d13b26edc514d4f717974ed0cd2750a74c99b981431201ce7000d50344f831c3",
"",
"reply"
],
[
"p",
"f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2"
]
],
"content": "š
Original date posted:2013-05-03\nš Original message:On Fri, May 03, 2013 at 04:06:29PM +0200, Mike Hearn wrote:\n\u003e That's true, but we can extend the DNS seeding protocol a little bit - you\n\u003e could query \u003ccurrent-chain-height\u003e.dnsseed.whatever.com and the DNS server\n\u003e then only returns nodes it knows matches your requirement.\n\nIf you're going to take a step like that, the \u003ccurrent-chain-height\u003e\nshould be rounded off, perhaps to some number of bits, or you'll allow\nDNS caching to be defeated.\n\nMake clients check for the largest \"rounded off\" value first, and then\ndrill down if required. Some complexity involved...\n\n\u003e This might complicate existing seeds a bit, and it's a bit of a hack, but\n\u003e protocol-wise it's still possible. Of course if you want to add more\n\u003e dimensions it gets uglier fast.\n\nMaybe I should make my blockheaders-over-dns thing production worthy\nfirst so we can see how many ISP's come at us with pitchforks? :P\n\n-- \n'peter'[:-1]@petertodd.org\n00000000000000142de0244ee8fac516e7c0a29da1eafc0d43f2da8b6388b387\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 198 bytes\nDesc: Digital signature\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20130503/b7a549e8/attachment.sig\u003e",
"sig": "89df91c1b65381603eee9f06b8a3d475183edebf24154d3030deb8011617ffebcd991164cd91683d7b2de53936147f5008e710d7371d352402658036fa3a8731"
}