Does Bitcoin Unlimited have its own DNS seed hosts?

[HelloGuy]

When the client is discovering the nodes on the network, one step will involve with finding the peers on the network. And inevitably there have to be some DNS hosts that will give the first batch of addresses that usually have stable peers.

https://en.bitcoin.it/wiki/Satoshi_Client_Node_Discovery

Right now people who are running these DNS seed hosts and have them written in the codes, are:

https://github.com/bitcoin/bitcoin/blob/1b2460bd5824170ab85757e35f81197199cce9d6/src/chainparams.cpp#L112

• bitseed.xf2.org ( Jeff Garzik, founder and employee of Bloq, )
  
• dnsseed.bluematt.me (Matt Corallo, founder and employee of Blocktream)
  
• seed.bitcoin.sipa.be (Pieter Wullie, founder and employee of Blocktream)
  
• dnsseed.bitcoin.dashjr.org (Luke-Jr, founder and contractor of Blocktream)
  
• seed.bitcoinstats.com (Christian Decker, https://who.is/whois/bitcoinstats.com, employee of Blocktream)
• seed.bitcoin.jonasschnelli.ch (Jonas Schnelli, co-founder of Digital Box)

4/6 are related with Blockstream; The only two who are unrelated with Blockstream is Jeff Garzik and Jonas, however now Jeff nearly lose any access to the commit of github of Bitcoin Core.

Only Jonas now is active Core developer that is unrelated with Blockstream.

I think Unlimited team should maintain one or two of its own one DNS hosts for Unlimited nodes and hard coded into Unlimited, to prevent a potential crisis from a potential centralized developer team's attack against Bitcoin network in the future.

 

[Peter Tschipper]

@HelloGuy BUIP018 was merged not long ago and is in this release...when you startup a new node or one without a peers.dat file, it will seed directly from bitnodes...if it can't it will grab from a hardcoded backup list. @bitcartel knows more the details of the backup list...i think we pruned some of the core one's out such as luke-jr etc...

 

[HelloGuy]

@Peter Tschipper Thanks for your reply and please pay attention from this issue. Do you still remember the XT being attacked by a software called Bitkiller, which was written by a hacker living in Russian? (http://www.nytimes.com/2016/01/17/business/dealbook/the-bitcoin-believer-who-gave-up.html?_r=0)

The Core can do whatever they can to stop a competitor, even working with the criminal. So play some tricks on the DNS seeds is a very possible thing they could do.

 

[sickpig]

@HelloGuy do you think that setting up at least another DNS seed under BU control could make us safer? This way we'll get 3 seeders: bitnodes, BU's and Garzik's, as time pass we could set up others.

 

[HelloGuy]

@sickpig Yes, I think it will be enough!

 

[theZerg]

Makes sense, we could use www.bitcoinunlimited.info DNS.

 

[sickpig]

this is the code used by core

https://github.com/sipa/bitcoin-seeder

 

[Roy Badami]

Am I right in thinking that the BU seeders behave exactly like the standard ones - there's no mechanism in DNS seeding at the moment to help BU nodes connect to other BU nodes?

 

[HelloGuy]

@Roy Badami The seeding only works at the beginning of new full nodes starting. The DNS seeders may help to connect to BU at the beginning, but since BU is treating and being treated equally by other peers, the BU nodes will always be able to connecting to other peers equally at the end, no matter it is BU or not.

 

[bitcartel]

Also consider Cartographer from BitcoinJ: https://github.com/bitcoinj/httpseed