Author Topic: Delegates  (Read 2102 times)

0 Members and 1 Guest are viewing this topic.

Xeldal

  • Guest
172.31.0.0 - 172.31.255.255  are also private addresses.

Offline nethyb

  • Full Member
  • ***
  • Posts: 197
    • View Profile
  • BitShares: nethyb

seed nodes:
Code: [Select]
...
network_add_node "192.168.0.14:54692" add
...
[/color]


Have you accidentally given us the private address for your second seed node ? i.e. 192.168.X.X is a Class C private address which can not be routed across the internet.

BTW voted for your btsx-singapore1 delegate
 

clout

  • Guest
I am running two nodes on amazon ec2 and additional node on my pc. One instance is running in Singapore and the other in Oregon. Since upgrading to amazon ec2 my delegates have not missed a single block and have a latency of 0s. Both nodes are currently connected to 35 peers. The following info will help you connect to and vote for my delegates.

seed nodes:
Code: [Select]
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

to vote for singapore delegates
Code: [Select]
wallet_approve_delegate btsx-singapore1
wallet_approve_delegate btsx-singapore2
wallet_approve_delegate btsx-singapore3
wallet_approve_delegate btsx-singapore4
wallet_approve_delegate btsx-singapore5

to vote for oregon delegates

Code: [Select]
wallet_approve_delegate clout-delegate1
wallet_approve_delegate clout-delegate2
wallet_approve_delegate clout-delegate3
wallet_approve_delegate clout-delegate4
wallet_approve_delegate clout-delegate5

to vote for backup delegates

Code: [Select]
wallet_approve_delegate btsx-delegate1
wallet_approve_delegate btsx-delegate2
wallet_approve_delegate btsx-delegate3
wallet_approve_delegate btsx-delegate4
wallet_approve_delegate btsx-delegate5
wallet_approve_delegate btsx-delegate6
wallet_approve_delegate btsx-delegate7
wallet_approve_delegate btsx-delegate8
wallet_approve_delegate btsx-delegate9
wallet_approve_delegate btsx-delegate10