0 Members and 1 Guest are viewing this topic.
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.
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
I'm also running a seed node from the latest master at: 46.226.109.66:1776It is hosted in Luxembourg at http://gandi.net and has the following specs:OS: Debian JessieCPU: dual-core Intel(R) Xeon(R) CPU E5-2650L 0 @ 1.80GHzRAM: 4GBandwidth: 100Mb/s symmetric
A networking fix has been pushed to master branch that fixes a stuck pending transaction problem: https://github.com/dacsunlimited/bitsharesx/commit/621a94f61e9eee50a98d61c15c2e3d9031eb354aAll seed nodes should update to the latest master branch.
Quote from: emski on October 29, 2014, 08:41:28 pmQuote from: vikram on October 29, 2014, 07:58:43 pmA networking fix has been pushed to master branch that fixes a stuck pending transaction problem: https://github.com/dacsunlimited/bitsharesx/commit/621a94f61e9eee50a98d61c15c2e3d9031eb354aAll 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, 07:58:43 pmA networking fix has been pushed to master branch that fixes a stuck pending transaction problem: https://github.com/dacsunlimited/bitsharesx/commit/621a94f61e9eee50a98d61c15c2e3d9031eb354aAll seed nodes should update to the latest master branch.Shouldn't this be an important announcement?Shouldn't there be a tag for this ?
this is my seed node, at JapanCode: [Select]network_add_node "106.185.26.162:1776"
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" addwallet_approve_delegate bitzwillalocal
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/vpsSpecifications: OS: Ubuntu 14.04, CPU type: Quad-Core AMD Opteron(tm) Processor 8387 (2812 MHz) , 2 cores HDD: SSD 40 GBRAM: 4GBUPTIME: 100%
somebody help our new members with seed nodes questions https://bitsharestalk.org/index.php?topic=9009.0PS 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:45:05 amYes I am a hero member and I am asking how to setup step by step a seed nodeknowing 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!
Yes I am a hero member and I am asking how to setup step by step a seed nodeknowing the same time that I am secure enough! Hints @ Tips please
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 pmdoes 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.
does the port need to be opened behind the firewall?
network_add_node "54.254.168.208:443" add
wallet_approve_delegate delegate.cryptoport
Quote from: puppies on July 22, 2014, 10:16:57 pmQuote from: GaltReport on July 22, 2014, 10:06:59 pmQuote from: DACSunlimited on July 22, 2014, 09:24:41 pmThanks 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, 10:06:59 pmQuote from: DACSunlimited on July 22, 2014, 09:24:41 pmThanks 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: DACSunlimited on July 22, 2014, 09:24:41 pmThanks 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?
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.
network_get_info
Seed Node: 61.129.33.213:1776 (Shanghai, China)Please vote for bts.bit365
Seed Nodes in association with minebitshares.com delegateseuseednode.minebitshares.com (Ireland)auseednode.minebitshares.com (Sydney) Code: [Select]wallet_approve_delegate www.minebitshares-comwallet_approve_delegate www2.minebitshares-comApprove www.minebitshares-comApprove www2.minebitshares-com
wallet_approve_delegate www.minebitshares-comwallet_approve_delegate www2.minebitshares-com
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: GaltReport on July 22, 2014, 11:51:09 pmQuote from: puppies on July 22, 2014, 10:16:57 pmQuote from: GaltReport on July 22, 2014, 10:06:59 pmQuote from: DACSunlimited on July 22, 2014, 09:24:41 pmThanks 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.
Quote from: puppies on July 22, 2014, 10:16:57 pmQuote from: GaltReport on July 22, 2014, 10:06:59 pmQuote from: DACSunlimited on July 22, 2014, 09:24:41 pmThanks 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.
Quote from: GaltReport on July 22, 2014, 10:06:59 pmQuote from: DACSunlimited on July 22, 2014, 09:24:41 pmThanks 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#>
network_add_node "84.238.140.192:42577" add84.238.140.192:42577Sofia, BulgariaYou may help by voting for lotto-delegate or angel-delegate.
Seed Node: 23.99.107.38:8901Location: East Asia
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
95.85.33.16:8764
seed nodes: Code: [Select]network_add_node "172.31.21.134:37302" addnetwork_add_node "192.168.0.14:54692" addnetwork_add_node "172.31.11.85:1776" addSingapore, New York and Oregon, respectively.
network_add_node "172.31.21.134:37302" addnetwork_add_node "192.168.0.14:54692" addnetwork_add_node "172.31.11.85:1776" add