Locking this thread and continuing discussion here: https://bitsharestalk.org/index.php/topic,23715.0.html

Quote from: abit on March 26, 2016, 02:36:42 PM

Quote from: puppies on March 26, 2016, 05:29:04 AM
Please replace my old seed node (104.236.144.84) with my new seed node 192.99.4.226:1776

Thanks.

@puppies The most efficient way is submit a pull request to github BitShares-2 repo then ping @xeroc.

Thanks Abit.  Ill try to knock that out.

Quote from: puppies on March 26, 2016, 05:29:04 AM
Please replace my old seed node (104.236.144.84) with my new seed node 192.99.4.226:1776

Thanks.

@puppies The most efficient way is submit a pull request to github BitShares-2 repo then ping @xeroc.

Please replace my old seed node (104.236.144.84) with my new seed node 192.99.4.226:1776

Thanks.

My default seed nodes have been updated (2.0.160103b):

23.95.43.126:50696

109.73.172.144:50696

FYI the new seed node 114.92.254.159:62015 which has been added in last patch (2.0.160103) is mine, located in China. I'm not sure if it's better to use a domain name though, currently the node will crash if failed to resolve a domain name.

Quote from: cube on October 12, 2015, 04:00:57 PM
I will be running 128.199.131.4:1777 as a seed node. It is currently running as a seednode for testnet but it will be replaced for the live network at the launch time.

Seed node address updated to seed.cubeconnex.com:1777

A github pull request for the change is created.  Please accept the pull request.

Seed node 185.25.22.21:1776 located in Greece
updated to the new version:  BitShares 2.0.151101


./witness_node --rpc-endpoint 127.0.0.1:1777 -s 104.236.144.84:1776 --p2p-endpoint 0.0.0.0:1776


Quote from: wackou on November 02, 2015, 09:52:22 AM
took me a while, but here's the pull request:

https://github.com/bitshares/bitshares-2/pull/5

This includes everyone that has posted in this thread. I don't think I missed anybody, but if so, please let me know.

I've already sent a pull request for my seed node.
I'll withdraw it as it might conflict with your (more complete) list.

took me a while, but here's the pull request:

https://github.com/bitshares/bitshares-2/pull/5

This includes everyone that has posted in this thread. I don't think I missed anybody, but if so, please let me know.

I have also updated my seed node to 52.20.134.30:39705
Would you mind including it in your pull request as well?

Quote from: wackou on October 27, 2015, 10:43:50 AM
list of current seed nodes and whether they are included as dns name or ip address can be seen here:

https://github.com/BitShares/bitshares-2/blob/bitshares/libraries%2Fapp%2Fapplication.cpp#L151

Thanks for that info / link wackou. I notice the port for seed04 is currently listed as 1776, although it was originally published as 2015 due to that VPS being used for BTS 0.9.3c. I will also be updating that VPS to reduce memory, so the IP will change. I will send you a PM when I get that done.

Go ahead and use the 1776 port in your pull request so they're all the same.

Quote from: bytemaster on October 26, 2015, 09:09:59 PM

Quote from: wackou on October 23, 2015, 10:21:47 AM
I will now turn off my seed nodes as they have still not been included in the default list of seed nodes.

I still would like to offer this service to the bitshares community, so once they will be included in the bitshares client, I will bring them back up (I need about 20 minutes to do that).

My bad.  I haven't gotten around to adding them back.   If someone can compile a list of all seed nodes I have missed, I will add them to the client.  Better yet, submit a pull request!

Perfect. I will submit a pull request in the coming days, then.

list of current seed nodes and whether they are included as dns name or ip address can be seen here:

https://github.com/BitShares/bitshares-2/blob/bitshares/libraries%2Fapp%2Fapplication.cpp#L151

Quote from: bytemaster on October 26, 2015, 09:09:59 PM

Quote from: wackou on October 23, 2015, 10:21:47 AM
I will now turn off my seed nodes as they have still not been included in the default list of seed nodes.

I still would like to offer this service to the bitshares community, so once they will be included in the bitshares client, I will bring them back up (I need about 20 minutes to do that).

My bad.  I haven't gotten around to adding them back.   If someone can compile a list of all seed nodes I have missed, I will add them to the client.  Better yet, submit a pull request!

Also how are you adding these, by DNS names or IP numbers? There are advantages to both of course.

I am going to change some VPS systems. All of them can be located by DNS names, and if that is what the code includes my changing the different VPS IP will by OK. On the other hand... if the DNS is attacked it is a weak point. Either way, whatever method decided should be communicated to the witnesses.

I can tell you that when I change my VPS service (I plan to downgrade at least 1 from 4GB RAM to1GB or 2GB) those IP addresses with change. I will have wackou update the DNS names when I do that, but unless the DNS is used in the code the seeds will be worthless.

If you would explain the procedure I need to follow I will act accordingly. I am NOT familiar with the intricacies of the codebase so please dumb it down for those of use who aren't.

Thanks!