0 Members and 1 Guest are viewing this topic.
Quote from: puppies on March 26, 2016, 05:29:04 amPlease replace my old seed node (104.236.144.84) with my new seed node 192.99.4.226:1776Thanks.@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:1776Thanks.
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.
./witness_node --rpc-endpoint 127.0.0.1:1777 -s 104.236.144.84:1776 --p2p-endpoint 0.0.0.0:1776
took me a while, but here's the pull request:https://github.com/bitshares/bitshares-2/pull/5This includes everyone that has posted in this thread. I don't think I missed anybody, but if so, please let me know.
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: wackou on October 23, 2015, 10:21:47 amI 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!
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).
is the current set of seed nodes as can be seen here considered sufficient for now?https://github.com/BitShares/bitshares-2/blob/bitshares/libraries%2Fapp%2Fapplication.cpp#L151It looks like seed nodes in this thread after and including triox's post (https://bitsharestalk.org/index.php/topic,18908.msg243607.html#msg243607) have not been included yet. If the current set is considered sufficient for now, then I'll probably decommission the 3 that I'm maintaining, as their resources could probably be better spent elsewhere. If they will (soon) get included, then I'm happy to keep maintaining them.
Quote from: liondani on October 16, 2015, 11:16:31 amIs it a problem if we are running our seed-nodes on our VPS on a local---rpc-endpoint like this?:./witness_node --rpc-endpoint=127.0.0.1:1776why are many suggesting: 0.0.0.0for example:./witness_node --rpc-endpoint=0.0.0.0:1776. ?rpc-endpoint will open up the rpc port eg for your cli-wallet. This is not the right port. It should be p2p-endpoint./witness_node --p2p-endpoint=0.0.0.0:1776This means other peers can connect to your seed.
Is it a problem if we are running our seed-nodes on our VPS on a local---rpc-endpoint like this?:./witness_node --rpc-endpoint=127.0.0.1:1776why are many suggesting: 0.0.0.0for example:./witness_node --rpc-endpoint=0.0.0.0:1776. ?
its very complicated i downloaded the genesis file but what is the next step? i want really participate but i docent know exactly how to setup a witness
Quote from: puppies on October 12, 2015, 02:27:55 pmMy live network seed node will be 104.236.144.84:1777how do you run your node to have this port dedicated?
My live network seed node will be 104.236.144.84:1777
# Endpoint for P2P node to listen onp2p-endpoint = 0.0.0.0:1776