BitShares Forum
Main => General Discussion => Topic started by: bytemaster on October 12, 2015, 12:45:28 pm
-
If you would like to be an official seed node provider for BTS 2.0 please post the IP/PORT that you will run your full node on. We will be including these addresses in all clients by default to connect to on startup.
Those who are running these nodes should probably also be witnesses. (Do not run witness on the seed node).
The job requires that you monitor the seed node for responsiveness and restart it if necessary. New users will depend upon these nodes being reliable.
-
I will run a seed node on a vps located in greece like I did with bts1... (it's ready for use)
can somebody make an example how we define the port when we run the seed-node?
-
I believe it is --p2p-endpoint arg
Just to confirm, the seed node only consists of a running witness binary, the command above with the specified port and the corresponding port open? Is there anything else we need to specify?
-
My live network seed node will be 104.236.144.84:1777
-
My live network seed node will be 104.236.144.84:1777
how do you run your node to have this port dedicated?
-
I have a seed node at: 54.85.252.77:39705 and will run this on the live network too.
You can specify the dedicated port with --p2p-endpoint, for me I launch with the following, but of course your other arguments may vary
./graphene/programs/witness_node/witness_node -d oct5 --genesis-json oct5-genesis.json --rpc-endpoint "127.0.0.1:8090" -s "104.236.144.84:1776" --p2p-endpoint 0.0.0.0:39705
-
My live network seed node will be 104.236.144.84:1777
how do you run your node to have this port dedicated?
I use # Endpoint for P2P node to listen on
p2p-endpoint = 0.0.0.0:1776In my config.ini but it can also be set in the launch command. Lafona is right about the syntax.
-
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.
-
how to defend ddos
when ip is fix
-
I will be using 40.127.190.171:1777 , setting up this server now.
-
My seed node will be this one:
185.25.22.21:1776
located in Greece.
-
My seed nodes:
23.95.43.126:50696
109.73.172.144:50696
-
The list of seed nodes to be available by delegate.verbaltech for production starting tomorrow are:
seed04.bitsharesnodes.com:2015 (45.32.240.134:2015 Sydney Austrailia)
seed05.bitsharesnodes.com:1776 (84.200.17.129:1776 Frankfurt Germany)
seed06.bitsharesnodes.com:1776 (192.169.7.118:1776 Los Angeles, USA)
seed07.bitsharesnodes.com:1776 (128.199.78.89:1776 Singnapore)
These are all up and running now, albeit it is the testnet chainID: 60e21871125ea9995fe498b7f68a87a85c6583725ea5448f6fd969c59a37df83
-
I'll be running 52.28.180.40:35681 as a dedicated seed node.
-
I will maintain the following seed nodes:
seed01.bitsharesnodes.com:1776
seed02.bitsharesnodes.com:1776
seed03.bitsharesnodes.com:1776
-
dedicated seed node:
159.203.101.205:1777
-
84.238.140.192:42570
Sofia, Bulgaria
Dedicated private server.
-
Seed node is up!
46.226.12.230:1984
Physical location: Oslo, Norway
-
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
-
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
make a try with this info:
https://github.com/cryptonomex/graphene/wiki/How%20to%20setup%20your%20witness%20for%20test%20net%20%28Ubuntu%2014.04%29
PS the genesis file is hard-coded on the binaries so it isn't necessary to download anymore
-
ok thx but i run only my mac haven't linux pc here :( maybe i can't do this
-
Seed Node: 191.237.252.181:1776
Location: Sao Paulo, Brasil
-
Seed node: 128.199.143.47:2015
Singapore
-
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:1776
why are many suggesting: 0.0.0.0
for example:
./witness_node --rpc-endpoint=0.0.0.0:1776
?
-
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:1776
why are many suggesting: 0.0.0.0
for 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:1776
This 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:1776
why are many suggesting: 0.0.0.0
for 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:1776
This means other peers can connect to your seed.
I started my seed node 185.25.22.21:1776 located in Greece
using this command:
./witness_node --rpc-endpoint 127.0.0.1:1777 -s 104.236.144.84:1776 --p2p-endpoint 0.0.0.0:1776
after -s (on our example 104.236.144.84:1776) you can put any seed-node you are confident it is on the main-chain and properly started.
any suggestions/comments are welcome... :)
PS If instead 0.0.0.0 after --p2p-endpoint we would put another address, would it not work?
-
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#L151
It 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.
-
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#L151
It 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.
Same concerns about my seed node.
-
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).
-
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!
-
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!
-
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
-
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
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.
-
I have also updated my seed node to 52.20.134.30:39705
Would you mind including it in your pull request as well?
-
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.
-
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.
-
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
-
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.
-
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.
-
My default seed nodes have been updated (2.0.160103b):
23.95.43.126:50696
109.73.172.144:50696
-
Please replace my old seed node (104.236.144.84) with my new seed node 192.99.4.226:1776
Thanks.
-
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.
@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.
-
Locking this thread and continuing discussion here: https://bitsharestalk.org/index.php/topic,23715.0.html