Please post IP:PORT and server location.
The current list of BitShares seed nodes can be found here: https://github.com/BitShares/bitshares/blob/bitshares/libraries/client/include/bts/client/seed_nodes.hpp
DevShares seed node thread: https://bitsharestalk.org/index.php?topic=13253.0
network_add_node "84.238.140.192:42577" add
seed.bitdelegate.org:42577
84.238.140.192:42577
Sofia, Bulgaria
You may help by voting for angel.bitdelegate (https://bitsharestalk.org/index.php?topic=5331.0).
edited out
Sent from my iPhone using Tapatalk
Seed Node: 23.99.98.183:1776
Location: Hong Kong, China
Seed Node: 180.153.142.120:1777 (Shanghai, China)
Please vote boombastic and agsexplorer as delegates.
Campaign detail: https://bitsharestalk.org/index.php?topic=5944.0
seed nodes:
network_add_node "172.31.21.134:37302" add
network_add_node "192.168.0.14:54692" add
network_add_node "172.31.11.85:1776" add
Singapore, New York and Oregon, respectively.
95.85.33.16:8764
Quote from: clout on July 21, 2014, 06:09:28 PM
seed nodes:
network_add_node "172.31.21.134:37302" add
network_add_node "192.168.0.14:54692" add
network_add_node "172.31.11.85:1776" add
Singapore, New York and Oregon, respectively.
Can not ping your ip from here, are you ready?
Quote from: puppies on July 21, 2014, 06:23:25 PM
95.85.33.16:8764
Your node will be used as seed node, thank you very much.
Quote from: boombastic on July 21, 2014, 06:05:34 PM
Seed Node: 180.153.142.120:1777 (Shanghai, China)
Please vote boombastic and agsexplorer as delegates.
Campaign detail: https://bitsharestalk.org/index.php?topic=5944.0
You node will be used a seed node, thanks.
Quote from: Fox on July 21, 2014, 05:33:18 PM
Seed Node: 23.99.107.38:8901
Location: East Asia
Can not ping.
Quote from: emski on July 21, 2014, 03:42:25 PM
network_add_node "84.238.140.192:42577" add
84.238.140.192:42577
Sofia, Bulgaria
You may help by voting for lotto-delegate (https://bitsharestalk.org/index.php?topic=5368.0) or angel-delegate (https://bitsharestalk.org/index.php?topic=5331.0).
Thank you very much.
Thanks for your contribution, please keep your node stable and not change your port.
If you want to be removed from the seed nodes, please PM me.
Quote from: DACSunlimited on July 22, 2014, 09:24:41 PM
Thanks for your contribution, please keep your node stable and not change your port.
If you want to be removed from the seed nodes, please PM me.
Where is the port set?
Quote from: GaltReport on July 22, 2014, 10:06:59 PM
Quote from: DACSunlimited on July 22, 2014, 09:24:41 PM
Thanks for your contribution, please keep your node stable and not change your port.
If you want to be removed from the seed nodes, please PM me.
Where is the port set?
You set it when you launch with the argument --p2p-port <port#>
Quote from: puppies on July 22, 2014, 10:16:57 PM
Quote from: GaltReport on July 22, 2014, 10:06:59 PM
Quote from: DACSunlimited on July 22, 2014, 09:24:41 PM
Thanks for your contribution, please keep your node stable and not change your port.
If you want to be removed from the seed nodes, please PM me.
Where is the port set?
You set it when you launch with the argument --p2p-port <port#>
Okay, thanks again. I guess if you don't specify it chooses one.
Quote from: GaltReport on July 22, 2014, 11:51:09 PM
Quote from: puppies on July 22, 2014, 10:16:57 PM
Quote from: GaltReport on July 22, 2014, 10:06:59 PM
Quote from: DACSunlimited on July 22, 2014, 09:24:41 PM
Thanks for your contribution, please keep your node stable and not change your port.
If you want to be removed from the seed nodes, please PM me.
Where is the port set?
You set it when you launch with the argument --p2p-port <port#>
Okay, thanks again. I guess if you don't specify it chooses one.
Exactly. You really just need to make sure the port is always the same, so people can connect to you.
Quote from: puppies on July 22, 2014, 11:58:32 PM
Quote from: GaltReport on July 22, 2014, 11:51:09 PM
Quote from: puppies on July 22, 2014, 10:16:57 PM
Quote from: GaltReport on July 22, 2014, 10:06:59 PM
Quote from: DACSunlimited on July 22, 2014, 09:24:41 PM
Thanks for your contribution, please keep your node stable and not change your port.
If you want to be removed from the seed nodes, please PM me.
Where is the port set?
Exactly. You really just need to make sure the port is always the same, so people can connect to you.
You set it when you launch with the argument --p2p-port <port#>
Okay, thanks again. I guess if you don't specify it chooses one.
Does it always choose the same one by default?
Seed Node: 61.129.33.213:1776 (Shanghai, China)
Please vote for bts.bit365
Seed Nodes in association with minebitshares.com delegates
euseednode.minebitshares.com (Ireland)
auseednode.minebitshares.com (Sydney)
wallet_approve_delegate www.minebitshares-com
wallet_approve_delegate www2.minebitshares-com
Approve www.minebitshares-com (http://daslab.io/scheme/btsx/www.minebitshares-com/approve)
Approve www2.minebitshares-com (http://daslab.io/scheme/btsx/www2.minebitshares-com/approve)
OP, can you provide a list with all the available seed nodes?
How do I create one if I am just running the Win GUI?
Quote from: sumantso on July 26, 2014, 09:27:34 AM
OP, can you provide a list with all the available seed nodes?
How do I create one if I am just running the Win GUI?
You can change the seed nodes in the config.json file of your data dir. After you launch once, the config.json file will be auto generated and you can modify it.
Quote from: nethyb on July 26, 2014, 08:58:55 AM
Seed Nodes in association with minebitshares.com delegates
euseednode.minebitshares.com (Ireland)
auseednode.minebitshares.com (Sydney)
wallet_approve_delegate www.minebitshares-com
wallet_approve_delegate www2.minebitshares-com
Approve www.minebitshares-com (http://daslab.io/scheme/btsx/www.minebitshares-com/approve)
Approve www2.minebitshares-com (http://daslab.io/scheme/btsx/www2.minebitshares-com/approve)
Thank you very much, we still need more seed nodes.
Quote from: alwaysjh on July 25, 2014, 05:21:47 AM
Seed Node: 61.129.33.213:1776 (Shanghai, China)
Please vote for bts.bit365
Thank you very much.
Quote from: GaltReport on July 22, 2014, 11:51:09 PM
Quote from: puppies on July 22, 2014, 10:16:57 PM
Quote from: GaltReport on July 22, 2014, 10:06:59 PM
Quote from: DACSunlimited on July 22, 2014, 09:24:41 PM
Thanks for your contribution, please keep your node stable and not change your port.
If you want to be removed from the seed nodes, please PM me.
Where is the port set?
You set it when you launch with the argument --p2p-port <port#>
Okay, thanks again. I guess if you don't specify it chooses one.
The default port now is 1776, if it is used by other program, it will choose a random one, you can get it by calling
network_get_info
does the port need to be opened behind the firewall?
newbie here, just rented vps for running delegate and node
server located at south east asia, domain name: node.cryptoport.io:443
network_add_node "54.254.168.208:443" add
please approve my delegate : delegate.cryptoport , i just want to know how it works
wallet_approve_delegate delegate.cryptoport
network_add_node "89.187.144.203:8764" add
VPS located in the Czech republic
There's no incentive to running a "seed node", unless said node is also being used as a delegate node, right?
Is there incentive to run a bitcoin full node if your are not mining?
Yes, you are supporting the network (decentralization)
But you do not get paid .. right
Quote from: sfinder on July 30, 2014, 06:21:56 PM
does the port need to be opened behind the firewall?
The seed node's port should not behind the firewall, otherwise other nodes can not connect to you.
But the delegate node should behind firewall to avoid potential attack.
thanks. it is good to know
Quote from: HackFisher on August 07, 2014, 03:08:49 PM
Quote from: sfinder on July 30, 2014, 06:21:56 PM
does the port need to be opened behind the firewall?
The seed node's port should not behind the firewall, otherwise other nodes can not connect to you.
But the delegate node should behind firewall to avoid potential attack.
Quote from: xeroc on August 07, 2014, 09:36:04 AM
Is there incentive to run a bitcoin full node if your are not mining?
Yes, you are supporting the network (decentralization)
But you do not get paid .. right
but supporting the network means nothing if i have no quotum
whats a quotum?
you can support the network in the p2p sense .. so that connectivity is increased
and you can support the DPOS network by voting so that the delegates get stronger/weaker depending on your favor
or you do both ..
Due to stability issues with the ISP the seed node 84.238.140.192:42577 will be unavailable for the next 16 hours.
UPDATE:
Downtime of the seed node will be prolonged until Tuesday. Delegates are functioning normally on the backup.
Apparently one of the cables used by my primary ISP was cut by technicians of another ISP...
UPDATE2:
Everything is working properly now!
I have setup a new seed node on a Digital Ocean VPS in Amsterdam, although like the client running for my website it appears to find itself on a fork every now and then and stops syncing. I'll keep checking it to make sure it's on the main fork until the syncing issues get fixed.
178.62.157.161:1776
Could you please add
seed.bitdelegate.org:42577
to the list of seed nodes.
Currently it points to 84.238.140.192:42577 but this will allow me to redirect it if a change occurs.
84.238.140.192:42577 will remain available.
How can i find out my seed node? Sorry for the newb question :-X
somebody help our new members with seed nodes questions ;)
https://bitsharestalk.org/index.php?topic=9009.0
PS since I will run my seed node these days to, I am not considering my self as an expert setting them up, and to be sure I don't give bad advises I am waiting some members that already published their seed nodes to give us more detailed instructions here ;)
Quote from: liondani on September 17, 2014, 06:35:24 AM
somebody help our new members with seed nodes questions ;)
https://bitsharestalk.org/index.php?topic=9009.0
PS since I will run my seed node these days to, I am not considering my self as an expert setting them up, and to be sure I don't give bad advises I am waiting some members that already published their seed nodes to give us more detailed instructions here ;)
Quote from: xeroc on September 17, 2014, 07:13:20 AM
Quote from: liondani on September 17, 2014, 06:45:05 AM
Yes I am a hero member and I am asking how to setup step by step a seed node
knowing the same time that I am secure enough! Hints @ Tips please :)
thats an easy one ..
- install bitsharesx client
- open up firefwall ports/router forwarding (if necessary)
- (optional) increase max number of conections
- post pm to dacsunlimited and tell them the ip (there's is also a thread somewhere about it)
PS: do not run the delegate on a seed node!
I just got my seed node up & running properly:
54.165.9.208
Happy to contribute! :-)
link that helps establishing a see node...
http://wiki.bitshares.org/index.php/Bitshares-x-delegate-how-to
Finally I am very happy to announce my first stable seed node located in Greece !!!
185.25.22.21:1776
A high quality VPS delivered from http://www.pointer.gr/en/vps
Specifications:
OS: Ubuntu 14.04,
CPU type: Quad-Core AMD Opteron(tm) Processor 8387 (2812 MHz) , 2 cores
HDD: SSD 40 GB
RAM: 4GB
UPTIME: 100%
PS KeyID has my stable seed node 185.25.22.21:1777 a couple of days as a default seed node... ;)
this is my seed node, at Japan
network_add_node "106.185.26.162:1776"
Hello everyone,
I´m running an stable BTSX seed node in Frankfurt/Germany :
network_add_node "85.214.53.224:1776" add
wallet_approve_delegate bitzwillalocal
Also an stable BTSX chain server at:
85.214.53.224:1375
(If you have sync problems then edit your config.json file and enter the above ip:port)
Could someone be so kind to donate some bucks? It would be really nice if you`d do since you´re getting to connect with my (high-end) sever for free.
Account: bitzwillalocal
Account Key: BTSX7bgcCPyVDQYUMkX1FT6ZJ6N9PCz2NSqxBGPBKf4nU8o5MZxiQ2
It´d be nice if you`d give me a feedback whether my chain server is working well
ATM: 20. Okt. 2014
Connected Nodes: 50 of 20,000
BSTX Chain_Server: 1
Security State: green
Blockchain Security State: green / 10 seconds for confirmations
network_get_usage_stats
Last minute: 6760 bytes/sec
Last hour: 4033 bytes/sec
By hour: 247041 bytes/sec
Stable seed node for bitshares located in Greece !!!
185.25.22.21:1776
Seednode hosted at a high quality VPS delivered from http://www.pointer.gr/en/vps
Specifications:
OS: Ubuntu 14.04,
CPU type: Quad-Core AMD Opteron(tm) Processor 8387 (2812 MHz) , 2 cores
HDD: SSD 40 GB
RAM: 4GB
UPTIME: 100%
A networking fix has been pushed to master branch that fixes a stuck pending transaction problem: https://github.com/dacsunlimited/bitsharesx/commit/621a94f61e9eee50a98d61c15c2e3d9031eb354a
All seed nodes should update to the latest master branch.
Quote from: alt on October 17, 2014, 12:50:51 AM
this is my seed node, at Japan
network_add_node "106.185.26.162:1776"
Quote from: fubly on October 20, 2014, 05:32:46 PM
Hello everyone,
I´m running an stable BTSX seed node in Frankfurt/Germany :
network_add_node "85.214.53.224:1776" add
wallet_approve_delegate bitzwillalocal
Quote from: liondani on October 27, 2014, 07:30:03 AM
Stable seed node for bitsharesx located in Greece !!!
185.25.22.21:1776
Seednode hosted at a high quality VPS delivered from http://www.pointer.gr/en/vps
Specifications:
OS: Ubuntu 14.04,
CPU type: Quad-Core AMD Opteron(tm) Processor 8387 (2812 MHz) , 2 cores
HDD: SSD 40 GB
RAM: 4GB
UPTIME: 100%
Will be added as default seed nodes in the next release.
Quote from: vikram on October 29, 2014, 07:58:43 PM
A networking fix has been pushed to master branch that fixes a stuck pending transaction problem: https://github.com/dacsunlimited/bitsharesx/commit/621a94f61e9eee50a98d61c15c2e3d9031eb354a
All seed nodes should update to the latest master branch.
Shouldn't this be an important announcement?
Shouldn't there be a tag for this ?
Quote from: emski on October 29, 2014, 08:41:28 PM
Quote from: vikram on October 29, 2014, 07:58:43 PM
A networking fix has been pushed to master branch that fixes a stuck pending transaction problem: https://github.com/dacsunlimited/bitsharesx/commit/621a94f61e9eee50a98d61c15c2e3d9031eb354a
All seed nodes should update to the latest master branch.
Shouldn't this be an important announcement?
Shouldn't there be a tag for this ?
I should have been more clear. This fix is not a required upgrade and this issue has been present for a long time. It has been causing annoyances for some users (particularly those using market bots). We fixed it just after the last release was already out, and so rather than everyone waiting for the next required upgrade, if only the seed nodes update beforehand it would already be sufficient to fix the problem for most users for now.
Quote from: vikram on October 29, 2014, 08:53:33 PM
Quote from: emski on October 29, 2014, 08:41:28 PM
Quote from: vikram on October 29, 2014, 07:58:43 PM
A networking fix has been pushed to master branch that fixes a stuck pending transaction problem: https://github.com/dacsunlimited/bitsharesx/commit/621a94f61e9eee50a98d61c15c2e3d9031eb354a
All seed nodes should update to the latest master branch.
Shouldn't this be an important announcement?
Shouldn't there be a tag for this ?
I should have been more clear. This fix is not a required upgrade and this issue has been present for a long time. It has been causing annoyances for some users (particularly those using market bots). We fixed it just after the last release was already out, and so rather than everyone waiting for the next required upgrade, if only the seed nodes update beforehand it would already be sufficient to fix the problem for most users for now.
Ok. I just feel uneasy using the master. A tag will be better IMHO. Anyway it should be mentioned in the important updates thread because most people are subscribed for it. This thread can be missed. I believe everyone needs to update in order to fix the issue ?
Quote from: vikram on October 29, 2014, 07:58:43 PM
A networking fix has been pushed to master branch that fixes a stuck pending transaction problem: https://github.com/dacsunlimited/bitsharesx/commit/621a94f61e9eee50a98d61c15c2e3d9031eb354a
All seed nodes should update to the latest master branch.
Just for your information my seednode is already updated...
185.25.22.21:1776
I'm also running a seed node from the latest master at: 46.226.109.66:1776
It is hosted in Luxembourg at http://gandi.net and has the following specs:
OS: Debian Jessie
CPU: dual-core Intel(R) Xeon(R) CPU E5-2650L 0 @ 1.80GHz
RAM: 4G
Bandwidth: 100Mb/s symmetric
Quote from: wackou on November 02, 2014, 11:03:14 AM
I'm also running a seed node from the latest master at: 46.226.109.66:1776
It is hosted in Luxembourg at http://gandi.net and has the following specs:
OS: Debian Jessie
CPU: dual-core Intel(R) Xeon(R) CPU E5-2650L 0 @ 1.80GHz
RAM: 4G
Bandwidth: 100Mb/s symmetric
Added to default list for next release: https://github.com/BitShares/bitshares/commit/62201d007f275929a4365d17a2f29658486d7d82
Just so everyone knows, the current list of default seed nodes: https://github.com/BitShares/bitshares/blob/469cd826066b05d4399aaa081eccf783a776c0e6/libraries/client/include/bts/client/client.hpp#L70-L89
Quote from: vikram on November 07, 2014, 05:17:05 PM
Just so everyone knows, the current list of default seed nodes: https://github.com/BitShares/bitshares/blob/469cd826066b05d4399aaa081eccf783a776c0e6/libraries/client/include/bts/client/client.hpp#L70-L89
are they enough ? Would it be better to have more?
Thanks everyone so far. The current list can be found here from now on: https://github.com/BitShares/bitshares/blob/bitshares/libraries/client/include/bts/client/seed_nodes.hpp
It would be helpful if one of you guys could write a short tutorial on running a seed node so others can more easily volunteer. Preferably it could be a page on the wiki (http://wiki.bitshares.org/index.php/Main_Page) I think.
I have had to change my seed node. I am no longer running 95.85.33.16:8764, I am now running 46.101.130.197:1776. I apologize for the inconvenience.
Quote from: puppies on June 04, 2015, 08:46:12 PM
I have had to change my seed node. I am no longer running 95.85.33.16:8764, I am now running 46.101.130.197:1776. I apologize for the inconvenience.
Updated: https://github.com/bitshares/bitshares/commit/7042d321bd1f4964d16197e864179f739f2e79b6