This is stange..

1899819 blocks left to fetch


--- syncing with p2p network, 1899819 blocks left to fetch
--- there are now 34 active connections to the p2p network
--- there are now 35 active connections to the p2p network
--- syncing with p2p network, 1907815 blocks left to fetch
default (unlocked) >>> get_info
{
  "blockchain_head_block_num": 9046,
  "blockchain_head_block_age": "14 seconds old",
  "blockchain_head_block_timestamp": "20140704T013415",
  "blockchain_average_delegate_participation": 89.380530973451329,
  "blockchain_blocks_left_in_round": 44,
  "blockchain_confirmation_requirement": 1,
  "blockchain_share_supply": 199999359471140,
  "blockchain_random_seed": "bd3595fbda4450347902205d3ed8d4213a683ab3",
  "blockchain_database_version": 109,
  "blockchain_version": 104,
  "network_num_connections": 35,
  "network_num_connections_max": 200,
  "network_protocol_version": 104,
  "ntp_time": "20140704T013429",
  "ntp_error": -0.038683000000000002,
  "wallet_open": true,
  "wallet_unlocked": true,
  "wallet_unlocked_until": "31 years  in the future",
  "wallet_unlocked_until_timestamp": "19100203T195710",
  "wallet_block_production_enabled": true,
  "wallet_next_block_production_time": "4 minutes in the future",
  "wallet_next_block_production_timestamp": "20140704T013800",
  "wallet_version": 101
}
--- there are now 34 active connections to the p2p network
--- there are now 35 active connections to the p2p network
default (unlocked) >>> about
{
  "bitshares_toolkit_revision": "9ed7cd7ce32914af1cb5055140f30f51351ec1d7",
  "bitshares_toolkit_revision_age": "3 hours ago",
  "fc_revision": "0fced2ddffb380572ed50c181e8496a9d8777a62",
  "fc_revision_age": "3 hours ago",
  "compile_date": "compiled on Jul  4 2014 at 00:28:40"
}


Quote from: bytemaster on July 04, 2014, 01:10:11 AM
I go out to eat dinner and you all take down the delegates and seed nodes, I cannot leave you alone for a second..... *shakes head*...

Seed nodes are building again, but init delegates will have to wait until tomorrow for me to recover the private keys and get active again.

lol  :P

Quote from: toast on July 03, 2014, 11:55:02 PM
We fucked up! All the seed nodes are dead and not coming back.

Working on building new default seeds into the client soon now.

What a convenient opportunity to ask for seed nodes for the Real Thing (wink wink nudge). Please send an IP if you want to be a seed.


In the meantime if you want to connect to the network for the first time:

Code Select Expand

network_add_node "107.170.172.14:46952" add
network_add_node "188.138.107.159:56497" add
network_add_node "146.185.186.245:8701" add
network_add_node "106.185.26.162:8761" add
network_add_node "107.170.30.182:8701" add
network_add_node "107.170.172.14:8701" add
network_add_node "162.243.219.145:8701" add
network_add_node "107.170.170.214:48387" add
network_add_node "95.85.33.16:8764" add
network_add_node "84.238.140.192:8701" add
network_add_node "176.9.234.166:8701" add

network_add_node "162.243.219.145:8701" add



I go out to eat dinner and you all take down the delegates and seed nodes, I cannot leave you alone for a second..... *shakes head*...

Seed nodes are building again, but init delegates will have to wait until tomorrow for me to recover the private keys and get active again.

Quote from: Fox on July 03, 2014, 08:46:52 PM
In the interest of increasing our delegate participation level closer to Bytemaster's goal of 90%, I suggest we vote out current delegates not producing blocks, thereby allowing in new delegates able to produce blocks consistently.  It is my understanding the intended automated delegate voting functionality would down vote a delegate that misses a block(s).

There are two delegate names that stick out:
  init* (4 delegates this round)
  vikram* (13 delegates this round)

Please take a moment to remove them from your approved list:

Code Select Expand

wallet_approve_delegate init3 false
wallet_approve_delegate vikram false


It would be great to have the option to click on a delegate in the "delegates list"
and see a a produced/missed ratio graph (or better a 1-3 days moving everage of that).
I situations like yesterday it would be much easier to make the "right" decisions related with votes. I mean it is much more importand how a delegate behaves in present and the last days compared with what they do in the past....

For example:
1.so yesterday if delegate spartako had 150 produced blocks and has lost only 15    I wouldn't take my vote back
2....and if delegate clout had 150 produced blocks and has lost 120 I would vote him out to help the network...

but what if I could easy see on a graph that the 15 block's that spartako lost was the 15 last blocks?
and for example clout on the other side has produced without problem the 100 last blocks ?

of course I wouldn't take my vote back on clout and maybe I would take my vote back for spartako until he convince me everything is ok again...

Conclusion:
It must be easy for the wallet users to see statistics like that mentionned
so we can make better decisions without the need to spend too much time...and maybe even make bad decisions...
In situation's like yesterday we would "come back" easier and ... sooner!


PS it would be great also , in casse a delegate has lost his last y blocks (for example y=10) that the font color of the delegate get red and is blinking so it will "steal" our attention for further investigation.

PS2 I see the pottential right now for jobs that will only watching close delegates behavior and give advices and a ton of different statistics, via deticated sites for that reason (of course in the future)

Quote from: toast on July 03, 2014, 11:55:02 PM
In the meantime if you want to connect to the network for the first time:

Code Select Expand

network_add_node "107.170.172.14:46952" add
network_add_node "188.138.107.159:56497" add
network_add_node "146.185.186.245:8701" add
network_add_node "106.185.26.162:8761" add
network_add_node "107.170.30.182:8701" add
network_add_node "107.170.172.14:8701" add
network_add_node "162.243.219.145:8701" add
network_add_node "107.170.170.214:48387" add
network_add_node "95.85.33.16:8764" add
network_add_node "84.238.140.192:8701" add
network_add_node "176.9.234.166:8701" add

network_add_node "162.243.219.145:8701" add



Edit:
Works now after wiping the data dir but the sync is very slow with 1000+ for about half an hour.
End of edit.

Didn't work for me with the latest code.

(wallet closed) >>> about
{
  "bitshares_toolkit_revision": "9ed7cd7ce32914af1cb5055140f30f51351ec1d7",
  "bitshares_toolkit_revision_age": "78 minutes ago",
  "fc_revision": "0fced2ddffb380572ed50c181e8496a9d8777a62",
  "fc_revision_age": "80 minutes ago",
  "compile_date": "compiled on Jul  4 2014 at 07:41:33"
}

(wallet closed) >>> network_add_node "188.138.107.159:56497" add
OK
(wallet closed) >>> network_add_node "146.185.186.245:8701" add
OK
(wallet closed) >>> network_add_node "106.185.26.162:8761" add
OK
(wallet closed) >>> network_add_node "107.170.30.182:8701" add
OK
(wallet closed) >>> network_add_node "107.170.172.14:8701" add
OK
(wallet closed) >>> network_add_node "162.243.219.145:8701" add
OK
(wallet closed) >>> network_add_node "107.170.170.214:48387" add
OK
(wallet closed) >>> network_add_node "95.85.33.16:8764" add
OK
(wallet closed) >>> network_add_node "84.238.140.192:8701" add
OK
(wallet closed) >>> network_add_node "176.9.234.166:8701" add
OK
(wallet closed) >>>
(wallet closed) >>> network_add_node "162.243.219.145:8701" add
OK
--- there are now 4 active connections to the p2p network
--- there are now 3 active connections to the p2p network
--- there are now 4 active connections to the p2p network
--- there are now 3 active connections to the p2p network
--- there are now 2 active connections to the p2p network
--- there are now 3 active connections to the p2p network
--- there are now 4 active connections to the p2p network
--- syncing with p2p network, 8797 blocks left to fetch
--- there are now 5 active connections to the p2p network
--- there are now 4 active connections to the p2p network

We fucked up! All the seed nodes are dead and not coming back.

Working on building new default seeds into the client soon now.

What a convenient opportunity to ask for seed nodes for the Real Thing (wink wink nudge). Please send an IP if you want to be a seed.


In the meantime if you want to connect to the network for the first time:

network_add_node "107.170.172.14:46952" add
network_add_node "188.138.107.159:56497" add
network_add_node "146.185.186.245:8701" add
network_add_node "106.185.26.162:8761" add
network_add_node "107.170.30.182:8701" add
network_add_node "107.170.172.14:8701" add
network_add_node "162.243.219.145:8701" add
network_add_node "107.170.170.214:48387" add
network_add_node "95.85.33.16:8764" add
network_add_node "84.238.140.192:8701" add
network_add_node "176.9.234.166:8701" add

network_add_node "162.243.219.145:8701" add



Quote from: vikram on July 03, 2014, 11:18:56 PM
I have just pushed some updates to the new log rotation: https://github.com/InvictusInnovations/fc/pull/34
I believe the old code may have been causing some problems.

Please pull and build the latest bitshares_toolkit and and fc code, and delete all the log files and config.json from your data directory, then start the client.

one of my client can't connect to network, disconnect from every node with same error message:

   20140703T234435.698552       th_a terminate_inactive_c ] Disconnecting peer 106.185.26.162:8761 because they didn't respond to my request for sync item 19af68ebd504e1  fbd41d3b98532772b709412fd0      node.cpp:872


I have just pushed some updates to the new log rotation: https://github.com/InvictusInnovations/fc/pull/34
I believe the old code may have been causing some problems.

Please pull and build the latest bitshares_toolkit and and fc code, and delete all the log files and config.json from your data directory, then start the client.

We have checked in some updates that will significantly reduce the ability of anyone to spam the network and resolved many smaller issues.

If you have not updated recently it might be a good idea, then we can try another massive flood of 100 trx per second and see how things behave.

Quote from: Fox on July 03, 2014, 09:03:37 PM

Quote
Those are all one guy and I know where he is sitting... init12+ is the seed node, init<12 is vikram.... I'll get on his case :)

Not intending to point a finger.  Together we all make this a success.   :)

Respectfully,
Fox

+1    Agreed... he was heads down working on code ignoring his delegates :)

Quote
Those are all one guy and I know where he is sitting... init12+ is the seed node, init<12 is vikram.... I'll get on his case :)

Not intending to point a finger.  Together we all make this a success.   :)

Respectfully,
Fox

Quote from: Fox on July 03, 2014, 08:46:52 PM
In the interest of increasing our delegate participation level closer to Bytemaster's goal of 90%, I suggest we vote out current delegates not producing blocks, thereby allowing in new delegates able to produce blocks consistently.  It is my understanding the intended automated delegate voting functionality would down vote a delegate that misses a block(s).

There are two delegate names that stick out:
  init* (4 delegates this round)
  vikram* (13 delegates this round)

Please take a moment to remove them from your approved list:

Code Select Expand

wallet_approve_delegate init3 false
wallet_approve_delegate vikram false


Those are all one guy and I know where he is sitting... init12+ is the seed node, init<12 is vikram.... I'll get on his case :)

Quote from: Fox on July 03, 2014, 08:46:52 PM
It is my understanding the intended automated delegate voting functionality would down vote a delegate that misses a block(s).

That's all in the client though, and hardly anyone is online.
But yes everyone please check your votes.

In the interest of increasing our delegate participation level closer to Bytemaster's goal of 90%, I suggest we vote out current delegates not producing blocks, thereby allowing in new delegates able to produce blocks consistently.  It is my understanding the intended automated delegate voting functionality would down vote a delegate that misses a block(s).

There are two delegate names that stick out:
  init* (4 delegates this round)
  vikram* (13 delegates this round)

Please take a moment to remove them from your approved list:
wallet_approve_delegate init3 false
wallet_approve_delegate vikram false


Quote from: svk on July 03, 2014, 08:33:20 PM

Quote from: bitcoinerS on July 03, 2014, 08:23:58 PM

Quote from: svk on July 03, 2014, 07:47:26 PM
Anyone able to send me some XTS please?

XTS5UMgDNLkJKpevFxFpK74L72ZrDA1p4HFY444jVt8ok85wKnznz

sent you some play money.

Cheers, well received, approved you as delegate.

I've set up a delegate too: please approve svk-delegate!

Ok, will do. Thanks.