{"type":"rich","version":"1.0","author_name":"npub1kf0ppcjaguxekg24yx6smgxlu73qn0k8lm0t2wrqc0scpl7u3sgsmf3f58","author_url":"https://nostr.ae/npub1kf0ppcjaguxekg24yx6smgxlu73qn0k8lm0t2wrqc0scpl7u3sgsmf3f58","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2014-05-15\n📝 Original message:On Thu, May 15, 2014 at 7:50 AM, Andreas Schildbach\n\u003candreas at schildbach.de\u003e wrote:\n\u003e I'm bringing this issue up again. The current Bitcoin DNS seed\n\u003e infrastructure is unstable. I assume this is because of we're using a\n\u003e custom DNS implementation which is not 100% compatible. There have been\n\u003e bugs in the past, like a case sensitive match for the domain name.\n\nWhile I agree that the problem seeds should be fixed, it also sounds\nlike a problem with bitcoinj / other layers, if a malfunctioning seed\nis a problem for your app.\n\nSeeds are fundamentally a backup for peer exchange.  You are going to\nrun into problems if you rely 100% on seeds, always.\n\nFurther, there are multiple seeds so that we are not impacted if a\ncouple seeds malfunction or die.  All bitcoin apps must take this into\naccount.\n\n-- \nJeff Garzik\nBitcoin core developer and open source evangelist\nBitPay, Inc.      https://bitpay.com/"}