Test Net for Advanced Users

[puppies]

Thanks puppies. I will review those posts.

I just now started a witness node using:

Code: [Select]

./witness_node --rpc-endpoint "127.0.0.1:8090" --resync-blockchain -d test_net -s 45.55.6.216:1776
./cli_wallet -w test_wallet  --chain-id 081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6

and the chain-id reported by the cli_wallet in the info api call is "a629fd737e0b4d8becc25e33b90984840723b38cd4430049693059f6e396b89c", not what was provided on the cmd line. Is that b/c I'm connecting to your seed?

Again, just trying to be on the same page as everyone testing here, but I'm not sure I am, which is why I am asking all these questions.

Also, is it necessary to do the set_password every time you start the wallet? Where is the wallet folder stored? It doesn't seem to be in the same folder as cli_wallet. I have reviewed the "cli wallet cookbook" but it didn't answer that. Every time I start the cli_wallet I have to set the password, why?

Witness questions

I am surprised to hear delegate.verbaltech is already registered as a witness. When did that happen? I was under the distinct impression from reading xeroc's doc that getting to that stage took a number of steps, like migrating balances, upgrading to lifetime member status etc.

I found the info on how to I specify the witness id, there may be a problem on using the signing keys for delegate.verbaltech. I'm sending you a PM about that issue, which may be the last huddle to jump over.

Youre getting the wrong chain id because  you're not launching with the --genesis-json aug-14-test-genesis.json (typed from memory so double check syntax)

as far as the wallet goes the -w is the name of your wallet.  If you change it you will need to create a new pw.  I am pretty sure its saved as a file in the cli_wallet dir.

[puppies]

and now my node with my personal delegate seems to have forked.  This should be the relevant log

Code: [Select]

h_items_loop ] beginning an iteration of fetch items (0 items to fetch) node.cpp:1104
2015-08-18T16:27:33 p2p:message read_loop           on_message ] handling message block_message_type 1a3a73d360660de01a4b1f9dfcc5add8d5ee3aa4 size 173 from peer 114.92.254.159:62016 node.cpp:1651
2015-08-18T16:27:33 p2p:message read_loop process_block_during ] received a block from peer 114.92.254.159:62016, passing it to client node.cpp:3087
2015-08-18T16:27:33 p2p:message read_loop process_block_during ] Successfully pushed block 118179 (id:0001cda313b6a140c0f384624e632c95fbed9804) node.cpp:3109
2015-08-18T16:27:33 p2p:message read_loop process_block_during ] client validated the block, advertising it to other peers node.cpp:3133
2015-08-18T16:27:33 p2p:message read_loop  clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:62016: removing 0 items advertised to peer (0 left), and 0 advertised to us (82 left) peer_connection.cpp:479
2015-08-18T16:27:33 p2p:message read_loop  clear_old_inventory ] Expiring old inventory for peer 45.55.6.216:1776: removing 0 items advertised to peer (12 left), and 0 advertised to us (108 left) peer_connection.cpp:479
2015-08-18T16:27:33 p2p:advertise_inventory_loop advertise_inventory_ ] beginning an iteration of advertise inventory node.cpp:1175
2015-08-18T16:27:33 p2p:advertise_inventory_loop advertise_inventory_ ] peer->peer_needs_sync_items_from_us: true node.cpp:1188
2015-08-18T16:27:33 p2p:advertise_inventory_loop  clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:62016: removing 0 items advertised to peer (0 left), and 0 advertised to us (82 left) peer_connection.cpp:479
2015-08-18T16:27:33 p2p:advertise_inventory_loop advertise_inventory_ ] peer->peer_needs_sync_items_from_us: false node.cpp:1188
2015-08-18T16:27:33 p2p:advertise_inventory_loop advertise_inventory_ ] inventory_to_advertise: [{"item_type":1001,"item_hash":"1a3a73d360660de01a4b1f9dfcc5add8d5ee3aa4"}] node.cpp:1196
2015-08-18T16:27:33 p2p:advertise_inventory_loop advertise_inventory_ ] *peer->inventory_advertised_to_peer.find(item_to_advertise): {"item":{"item_type":1476398304,"item_hash":"847f0000000000000000000078a30558847f0000"},"timestamp":"2016-10-13T22:37:12"} node.cpp:1200
2015-08-18T16:27:33 p2p:advertise_inventory_loop advertise_inventory_ ] advertising 0 new item(s) of 0 type(s) to peer 45.55.6.216:1776 node.cpp:1218
2015-08-18T16:27:33 p2p:advertise_inventory_loop  clear_old_inventory ] Expiring old inventory for peer 45.55.6.216:1776: removing 0 items advertised to peer (12 left), and 0 advertised to us (108 left) peer_connection.cpp:479
2015-08-18T16:27:33  p2p:fetch_items_loop     fetch_items_loop ] beginning an iteration of fetch items (0 items to fetch) node.cpp:1104
2015-08-18T16:27:33 p2p:message read_loop           on_message ] handling message item_ids_inventory_message_type e8c9515d4e56d73cbb49ed5d56eedf4d6901b073 size 25 from peer 114.92.254.159:62016 node.cpp:1651
2015-08-18T16:27:33 p2p:message read_loop  clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:62016: removing 0 items advertised to peer (0 left), and 0 advertised to us (82 left) peer_connection.cpp:479
2015-08-18T16:27:33 p2p:message read_loop on_item_ids_inventor ] received inventory of 1 items from peer 114.92.254.159:62016 node.cpp:2613
2015-08-18T16:27:33 p2p:message read_loop on_item_ids_inventor ] adding item ac3580aa78a43aa6cab5e0599c05aa65a0818117 from inventory message to our list of items to fetch node.cpp:2647
2015-08-18T16:27:33  p2p:fetch_items_loop     fetch_items_loop ] beginning an iteration of fetch items (1 items to fetch) node.cpp:1104
2015-08-18T16:27:33  p2p:fetch_items_loop     fetch_items_loop ] requesting item ac3580aa78a43aa6cab5e0599c05aa65a0818117 from peer 114.92.254.159:62016 node.cpp:1123
2015-08-18T16:27:33  p2p:fetch_items_loop         send_message ] peer_connection::send_message() enqueueing message of type 5004 for peer 114.92.254.159:62016 peer_connection.cpp:365
2015-08-18T16:27:33  p2p:fetch_items_loop send_queueable_messa ] peer_connection::send_message() is firing up send_queued_message_task peer_connection.cpp:354
2015-08-18T16:27:33 p2p:send_queued_messages_task              counter ] entering peer_connection::send_queued_messages_task() peer_connection.cpp:279
2015-08-18T16:27:33 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task() calling message_oriented_connection::send_message() to send message of type 5004 for peer 114.92.254.159:62016 peer_connection.cpp:291
2015-08-18T16:27:33 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task()'s call to message_oriented_connection::send_message() completed normally for peer 114.92.254.159:62016 peer_connection.cpp:294
2015-08-18T16:27:33 p2p:send_queued_messages_task send_queued_messages ] leaving peer_connection::send_queued_messages_task() due to queue exhaustion peer_connection.cpp:326
2015-08-18T16:27:33 p2p:send_queued_messages_task             ~counter ] leaving peer_connection::send_queued_messages_task() peer_connection.cpp:280
2015-08-18T16:27:34 p2p:message read_loop           on_message ] handling message item_ids_inventory_message_type 273c1c45d465267877955f6a74879444f50acb87 size 25 from peer 45.55.6.216:1776 node.cpp:1651
2015-08-18T16:27:34 p2p:message read_loop  clear_old_inventory ] Expiring old inventory for peer 45.55.6.216:1776: removing 0 items advertised to peer (12 left), and 1 advertised to us (107 left) peer_connection.cpp:479
2015-08-18T16:27:34 p2p:message read_loop on_item_ids_inventor ] received inventory of 1 items from peer 45.55.6.216:1776 node.cpp:2613
2015-08-18T16:27:34 p2p:message read_loop on_item_ids_inventor ] adding item 68653fd811768cb6bb2ef6a63d73bdf9298beb95 from inventory message to our list of items to fetch node.cpp:2647
2015-08-18T16:27:34  p2p:fetch_items_loop     fetch_items_loop ] beginning an iteration of fetch items (1 items to fetch) node.cpp:1104
2015-08-18T16:27:34  p2p:fetch_items_loop     fetch_items_loop ] requesting item 68653fd811768cb6bb2ef6a63d73bdf9298beb95 from peer 45.55.6.216:1776 node.cpp:1123
2015-08-18T16:27:34  p2p:fetch_items_loop         send_message ] peer_connection::send_message() enqueueing message of type 5004 for peer 45.55.6.216:1776 peer_connection.cpp:365
2015-08-18T16:27:34  p2p:fetch_items_loop send_queueable_messa ] peer_connection::send_message() is firing up send_queued_message_task peer_connection.cpp:354
2015-08-18T16:27:34 p2p:send_queued_messages_task              counter ] entering peer_connection::send_queued_messages_task() peer_connection.cpp:279
2015-08-18T16:27:34 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task() calling message_oriented_connection::send_message() to send message of type 5004 for peer 45.55.6.216:1776 peer_connection.cpp:291
2015-08-18T16:27:34 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task()'s call to message_oriented_connection::send_message() completed normally for peer 45.55.6.216:1776 peer_connection.cpp:294
2015-08-18T16:27:34 p2p:send_queued_messages_task send_queued_messages ] leaving peer_connection::send_queued_messages_task() due to queue exhaustion peer_connection.cpp:326
2015-08-18T16:27:34 p2p:send_queued_messages_task             ~counter ] leaving peer_connection::send_queued_messages_task() peer_connection.cpp:280
2015-08-18T16:27:34 p2p:message read_loop           on_message ] handling message block_message_type 68653fd811768cb6bb2ef6a63d73bdf9298beb95 size 173 from peer 45.55.6.216:1776 node.cpp:1651
2015-08-18T16:27:34 p2p:message read_loop process_block_during ] received a block from peer 45.55.6.216:1776, passing it to client node.cpp:3087
2015-08-18T16:27:34 p2p:message read_loop process_block_during ] Failed to push block 118181 (id:0001cda58068604136998b1998eb09a3b8b3fa56), client rejected block sent by peer node.cpp:3198
2015-08-18T16:27:34  p2p:fetch_items_loop     fetch_items_loop ] beginning an iteration of fetch items (0 items to fetch) node.cpp:1104
2015-08-18T16:27:34 p2p:message read_loop           on_message ] handling message block_message_type ac3580aa78a43aa6cab5e0599c05aa65a0818117 size 172 from peer 114.92.254.159:62016 node.cpp:1651
2015-08-18T16:27:34 p2p:message read_loop process_block_during ] received a block from peer 114.92.254.159:62016, passing it to client node.cpp:3087
2015-08-18T16:27:34 p2p:message read_loop process_block_during ] Successfully pushed block 118180 (id:0001cda4fff8b59d6242e9cfbb706492a6b250ea) node.cpp:3109
2015-08-18T16:27:34 p2p:message read_loop process_block_during ] client validated the block, advertising it to other peers node.cpp:3133
2015-08-18T16:27:34 p2p:message read_loop  clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:62016: removing 0 items advertised to peer (0 left), and 0 advertised to us (83 left) peer_connection.cpp:479
2015-08-18T16:27:34 p2p:message read_loop  clear_old_inventory ] Expiring old inventory for peer 45.55.6.216:1776: removing 0 items advertised to peer (12 left), and 0 advertised to us (108 left) peer_connection.cpp:479
2015-08-18T16:27:34 p2p:advertise_inventory_loop advertise_inventory_ ] beginning an iteration of advertise inventory node.cpp:1175
2015-08-18T16:27:34 p2p:advertise_inventory_loop advertise_inventory_ ] peer->peer_needs_sync_items_from_us: true node.cpp:1188
2015-08-18T16:27:34 p2p:advertise_inventory_loop  clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:62016: removing 0 items advertised to peer (0 left), and 0 advertised to us (83 left) peer_connection.cpp:479
2015-08-18T16:27:34 p2p:advertise_inventory_loop advertise_inventory_ ] peer->peer_needs_sync_items_from_us: false node.cpp:1188
2015-08-18T16:27:34 p2p:advertise_inventory_loop advertise_inventory_ ] inventory_to_advertise: [{"item_type":1001,"item_hash":"ac3580aa78a43aa6cab5e0599c05aa65a0818117"}] node.cpp:1196
2015-08-18T16:27:34 p2p:advertise_inventory_loop advertise_inventory_ ] *peer->inventory_advertised_to_peer.find(item_to_advertise): {"item":{"item_type":1476398304,"item_hash":"847f0000000000000000000078a30558847f0000"},"timestamp":"2016-10-13T22:37:12"} node.cpp:1200
2015-08-18T16:27:34 p2p:advertise_inventory_loop advertise_inventory_ ] advertising 0 new item(s) of 0 type(s) to peer 45.55.6.216:1776 node.cpp:1218
2015-08-18T16:27:34 p2p:advertise_inventory_loop  clear_old_inventory ] Expiring old inventory for peer 45.55.6.216:1776: removing 0 items advertised to peer (12 left), and 0 advertised to us (108 left) peer_connection.cpp:479
2015-08-18T16:27:34  p2p:fetch_items_loop     fetch_items_loop ] beginning an iteration of fetch items (0 items to fetch) node.cpp:1104
2015-08-18T16:27:35 p2p:message read_loop           on_message ] handling message item_ids_inventory_message_type 7961814825b2c7f2b262b8e14426da647ff4b137 size 25 from peer 45.55.6.216:1776 node.cpp:1651
2015-08-18T16:27:35 p2p:message read_loop  clear_old_inventory ] Expiring old inventory for peer 45.55.6.216:1776: removing 0 items advertised to peer (12 left), and 1 advertised to us (107 left) peer_connection.cpp:479
2015-08-18T16:27:35 p2p:message read_loop on_item_ids_inventor ] received inventory of 1 items from peer 45.55.6.216:1776 node.cpp:2613
2015-08-18T16:27:35 p2p:message read_loop on_item_ids_inventor ] adding item f2420b4d7371ddf4aa1cb07d5561a0b65e6f1014 from inventory message to our list of items to fetch node.cpp:2647
2015-08-18T16:27:35  p2p:fetch_items_loop     fetch_items_loop ] beginning an iteration of fetch items (1 items to fetch) node.cpp:1104
2015-08-18T16:27:35  p2p:fetch_items_loop     fetch_items_loop ] requesting item f2420b4d7371ddf4aa1cb07d5561a0b65e6f1014 from peer 45.55.6.216:1776 node.cpp:1123
2015-08-18T16:27:35  p2p:fetch_items_loop         send_message ] peer_connection::send_message() enqueueing message of type 5004 for peer 45.55.6.216:1776 peer_connection.cpp:365
2015-08-18T16:27:35  p2p:fetch_items_loop send_queueable_messa ] peer_connection::send_message() is firing up send_queued_message_task peer_connection.cpp:354
2015-08-18T16:27:35 p2p:send_queued_messages_task              counter ] entering peer_connection::send_queued_messages_task() peer_connection.cpp:279
2015-08-18T16:27:35 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task() calling message_oriented_connection::send_message() to send message of type 5004 for peer 45.55.6.216:1776 peer_connection.cpp:291
2015-08-18T16:27:35 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task()'s call to message_oriented_connection::send_message() completed normally for peer 45.55.6.216:1776 peer_connection.cpp:294
2015-08-18T16:27:35 p2p:send_queued_messages_task send_queued_messages ] leaving peer_connection::send_queued_messages_task() due to queue exhaustion peer_connection.cpp:326
2015-08-18T16:27:35 p2p:send_queued_messages_task             ~counter ] leaving peer_connection::send_queued_messages_task() peer_connection.cpp:280
2015-08-18T16:27:35 p2p:message read_loop           on_message ] handling message block_message_type f2420b4d7371ddf4aa1cb07d5561a0b65e6f1014 size 172 from peer 45.55.6.216:1776 node.cpp:1651
2015-08-18T16:27:35 p2p:message read_loop process_block_during ] received a block from peer 45.55.6.216:1776, passing it to client node.cpp:3087
2015-08-18T16:27:35 p2p:message read_loop process_block_during ] Failed to push block 118182 (id:0001cda68df8d489ac600fa93f814b7cf7a18a94), client rejected block sent by peer node.cpp:3198
2015-08-18T16:27:35  p2p:fetch_items_loop     fetch_items_loop ] beginning an iteration of fetch items (0 items to fetch) node.cpp:1104
2015-08-18T16:27:35 p2p:message read_loop           on_message ] handling message item_ids_inventory_message_type 273c1c45d465267877955f6a74879444f50acb87 size 25 from peer 114.92.254.159:62016 node.cpp:1651
2015-08-18T16:27:35 p2p:message read_loop  clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:62016: removing 0 items advertised to peer (0 left), and 0 advertised to us (83 left) peer_connection.cpp:479
2015-08-18T16:27:35 p2p:message read_loop on_item_ids_inventor ] received inventory of 1 items from peer 114.92.254.159:62016 node.cpp:2613
2015-08-18T16:27:35 p2p:message read_loop on_item_ids_inventor ] adding item 68653fd811768cb6bb2ef6a63d73bdf9298beb95 from inventory message to our list of items to fetch node.cpp:2647
2015-08-18T16:27:35  p2p:fetch_items_loop     fetch_items_loop ] beginning an iteration of fetch items (1 items to fetch) node.cpp:1104
2015-08-18T16:27:35  p2p:fetch_items_loop     fetch_items_loop ] requesting item 68653fd811768cb6bb2ef6a63d73bdf9298beb95 from peer 114.92.254.159:62016 node.cpp:1123
2015-08-18T16:27:35  p2p:fetch_items_loop         send_message ] peer_connection::send_message() enqueueing message of type 5004 for peer 114.92.254.159:62016 peer_connection.cpp:365
2015-08-18T16:27:35  p2p:fetch_items_loop send_queueable_messa ] peer_connection::send_message() is firing up send_queued_message_task peer_connection.cpp:354
2015-08-18T16:27:35 p2p:send_queued_messages_task              counter ] entering peer_connection::send_queued_messages_task() peer_connection.cpp:279
2015-08-18T16:27:35 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task() calling message_oriented_connection::send_message() to send message of type 5004 for peer 114.92.254.159:62016 peer_connection.cpp:291
2015-08-18T16:27:35 p2p:send_queued_messages_task send_queued_messages ] peer_connection::send_queued_messages_task()'s call to message_oriented_connection::send_message() completed normally for peer 114.92.254.159:62016 peer_connection.cpp:294
2015-08-18T16:27:35 p2p:send_queued_messages_task send_queued_messages ] leaving peer_connection::send_queued_messages_task() due to queue exhaustion peer_connection.cpp:326
2015-08-18T16:27:35 p2p:send_queued_messages_task             ~counter ] leaving peer_connection::send_queued_messages_task() peer_connection.cpp:280
2015-08-18T16:27:35 p2p:message read_loop           on_message ] handling message block_message_type 68653fd811768cb6bb2ef6a63d73bdf9298beb95 size 173 from peer 114.92.254.159:62016 node.cpp:1651
2015-08-18T16:27:35 p2p:message read_loop process_block_during ] received a block from peer 114.92.254.159:62016, passing it to client node.cpp:3087
2015-08-18T16:27:35 p2p:message read_loop process_block_during ] Successfully pushed block 118181 (id:0001cda58068604136998b1998eb09a3b8b3fa56) node.cpp:3109
2015-08-18T16:27:35 p2p:message read_loop process_block_during ] client validated the block, advertising it to other peers node.cpp:3133
2015-08-18T16:27:35 p2p:message read_loop  clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:62016: removing 0 items advertised to peer (0 left), and 0 advertised to us (84 left) peer_connection.cpp:479
2015-08-18T16:27:35 p2p:message read_loop  clear_old_inventory ] Expiring old inventory for peer 45.55.6.216:1776: removing 0 items advertised to peer (12 left), and 0 advertised to us (108 left) peer_connection.cpp:479
2015-08-18T16:27:35 p2p:advertise_inventory_loop advertise_inventory_ ] beginning an iteration of advertise inventory node.cpp:1175
2015-08-18T16:27:35 p2p:advertise_inventory_loop advertise_inventory_ ] peer->peer_needs_sync_items_from_us: true node.cpp:1188
2015-08-18T16:27:35 p2p:advertise_inventory_loop  clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:62016: removing 0 items advertised to peer (0 left), and 0 advertised to us (84 left) peer_connection.cpp:479
2015-08-18T16:27:35 p2p:advertise_inventory_loop advertise_inventory_ ] peer->peer_needs_sync_items_from_us: false node.cpp:1188
2015-08-18T16:27:35 p2p:advertise_inventory_loop advertise_inventory_ ] inventory_to_advertise: [{"item_type":1001,"item_hash":"68653fd811768cb6bb2ef6a63d73bdf9298beb95"}] node.cpp:1196
2015-08-18T16:27:35 p2p:advertise_inventory_loop advertise_inventory_ ] *peer->inventory_advertised_to_peer.find(item_to_advertise): {"item":{"item_type":1476398304,"item_hash":"847f0000000000000000000078a30558847f0000"},"timestamp":"2016-10-13T22:37:12"} node.cpp:1200
2015-08-18T16:27:35 p2p:advertise_inventory_loop advertise_inventory_ ] advertising 0 new item(s) of 0 type(s) to peer 45.55.6.216:1776 node.cpp:1218
2015-08-18T16:27:35 p2p:advertise_inventory_loop  clear_old_inventory ] Expiring old inventory for peer 45.55.6.216:1776: removing 0 items advertised to peer (12 left), and 0 advertised to us (108 left) peer_connection.cpp:479
2015-08-18T16:27:35  p2p:fetch_items_loop     fetch_items_loop ] beginning an iteration of fetch items (0 items to fetch) node.cpp:1104


[Thom]

Thanks puppies. I will review those posts.

I just now started a witness node using:

Code: [Select]

./witness_node --rpc-endpoint "127.0.0.1:8090" --resync-blockchain -d test_net -s 45.55.6.216:1776
./cli_wallet -w test_wallet  --chain-id 081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6

and the chain-id reported by the cli_wallet in the info api call is "a629fd737e0b4d8becc25e33b90984840723b38cd4430049693059f6e396b89c", not what was provided on the cmd line. Is that b/c I'm connecting to your seed?

Again, just trying to be on the same page as everyone testing here, but I'm not sure I am, which is why I am asking all these questions.

Also, is it necessary to do the set_password every time you start the wallet? Where is the wallet folder stored? It doesn't seem to be in the same folder as cli_wallet. I have reviewed the "cli wallet cookbook" but it didn't answer that. Every time I start the cli_wallet I have to set the password, why?

Witness questions

I am surprised to hear delegate.verbaltech is already registered as a witness. When did that happen? I was under the distinct impression from reading xeroc's doc that getting to that stage took a number of steps, like migrating balances, upgrading to lifetime member status etc.

I found the info on how to I specify the witness id, there may be a problem on using the signing keys for delegate.verbaltech. I'm sending you a PM about that issue, which may be the last huddle to jump over.

[puppies]

Last night when I was able to successfully start the witness node and connect the cli wallet to it I had to change the chain-id to what the witness reported rather than the value in the OP. In looking at the puppies post today (quoted by abit) the chain-id is back to original in OP.

The 2 values I've seen follow. Would someone explain what is the chain-id and why does it keep changing? Are we running separate tests on each chain or is it simply a test of stamina to make sure "advanced" people can keep up with changes here

1) 081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6
2) a629fd737e0b4d8becc25e33b90984840723b38cd4430049693059f6e396b89c

I suspect the chain-id I connected with last night was some temporary chain puppies ran for a time. I'll use the value in the OP if that's where we're all converging. I now need to create an account, migrate a balance so it can be upgraded to lifetime membership and then register it as a witness. Is all that covered by xeroc's doc linked in the OP? Has anything changed in that process?

For example, should I use puppies seed IP or the one in the OP? Does that even matter? My mind is buzzing with all these details 

Your current delegate is already set up as a witness

Code: [Select]

get_witness delegate.verbaltech
{
  "id": "1.6.1530",
  "witness_account": "1.2.22307",
  "signing_key": "GPH52ms1dYJko2v5vS3rCdVLzQBogjeDRc1CpkaZ4seC4J4H7Uc71",
  "next_secret_hash": "5c00bd4aca04a9057c09b20b05f723f2e23deb65",
  "previous_secret": "0000000000000000000000000000000000000000",
  "vote_id": "1:1530",
  "total_votes": 0,
  "url": ""
}
You need to launch the witness node with your id 1.6.1530.  your public signing key, and the corresponding private key.  Init delegates have 0 votes so you can be voted in with limited funds.  let me know when you're up and running and I can vote you in.

Xeroc's instructions on becoming a delegate explain how to find your private key and launch, but some of syntax appears to be incorrect.(not sure if the wiki has been updated yet)  I would re read the first 4 pages of this thread, as there are numerous examples of how to launch the witness node correctly.


EDIT
in regards to the chain id.  I thought I would have to change it when I relaunched the test net, but when I launched with the correct genesis it used the same chain id.  I am guessing that the chain id is derived from the genesis block.  Hopefully BM can explain.

In regards to the -s node, I do not know if BMs node is connected to my test net, as I havent found a way to check peers within the wallet, and I havent dug through the logs to see all connected nodes.  I would suggest that you use 45.55.6.216:1776 until BM posts a new test net (which will probably require a rebuild of the executables)

[Thom]

Last night when I was able to successfully start the witness node and connect the cli wallet to it I had to change the chain-id to what the witness reported rather than the value in the OP. In looking at the puppies post today (quoted by abit) the chain-id is back to original in OP.

The 2 values I've seen follow. Would someone explain what is the chain-id and why does it keep changing? Are we running separate tests on each chain or is it simply a test of stamina to make sure "advanced" people can keep up with changes here

1) 081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6
2) a629fd737e0b4d8becc25e33b90984840723b38cd4430049693059f6e396b89c

I suspect the chain-id I connected with last night was some temporary chain puppies ran for a time. I'll use the value in the OP if that's where we're all converging. I now need to create an account, migrate a balance so it can be upgraded to lifetime membership and then register it as a witness. Is all that covered by xeroc's doc linked in the OP? Has anything changed in that process?

For example, should I use puppies seed IP or the one in the OP? Does that even matter? My mind is buzzing with all these details 

[abit]

The network is still up and generating blocks on at least three different systems. 

Code: [Select]

  "head_block_num": 113869,
  "head_block_id": "0001bccd0acdf8b05c58b6cc5e6e36d717de523c",
  "head_block_age": "2 seconds old",
  "next_maintenance_time": "4 minutes in the future",
  "chain_id": "081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6",
It seems like your node did fork and now wont accept the proper chain.

Code: [Select]

get_block 72042
{
  "previous": "000119696d1d31776e6431586e14fd2e4c0b4f58",
  "timestamp": "2015-08-18T02:07:59",
  "witness": "1.6.1435",
  "next_secret_hash": "72dcf0475fa5d0c145a235f590b5be3597c17753",
  "previous_secret": "2813946aacd0bfda5541bf243f5bc47aee51e314",
  "transaction_merkle_root": "0000000000000000000000000000000000000000",
  "extensions": [],
  "witness_signature": "201506e5034d1df8627196bc97b5293eed3efbb6391a256789ca4a6912f169b45b51045f55f9be468a2db485bfcc4952996e10d1f4be0cc1c0eef2764470649035",
  "transactions": []
}
locked >>> get_block 72043
get_block 72043
{
  "previous": "0001196a1eb9d0e2021fd4f6ac9fe452ea46d4b3",
  "timestamp": "2015-08-18T02:08:00",
  "witness": "1.6.0",
  "next_secret_hash": "031a792684e0d99dab315ce6aea4fa92c85c6707",
  "previous_secret": "cd722b49f39a4b7160e081ae2c26cdf71f8e9194",
  "transaction_merkle_root": "0000000000000000000000000000000000000000",
  "extensions": [],
  "witness_signature": "1f64cf6d9e48683ed2259772c5006c0a1ec195dc280c59b5941250fa1581e8b86c0d32ed49d47d9d57cc87b3088e2f52bc15c7dc500955fa334864a3ed7b08be63",
  "transactions": []
}
locked >>> get_block 72044
get_block 72044
{
  "previous": "0001196bf9cf506fb01511e20c8566694b952a7d",
  "timestamp": "2015-08-18T02:08:01",
  "witness": "1.6.4",
  "next_secret_hash": "42899548ec99624cb2102330c429562510ef09a0",
  "previous_secret": "2777b474efe4774a69d716f61b5cf156deb3a232",
  "transaction_merkle_root": "0000000000000000000000000000000000000000",
  "extensions": [],
  "witness_signature": "1f02312f66e1dcf78335d1c5ee999181cd3a0191d927d48376fa5702a493d418514d01eb530328c2dee956d5824103b8576e7974049e0d414eab142fd3ddbbe991",
  "transactions": []
}
locked >>>
im curious is your block 72042 matches mine.

Looks like my node produced a #72042 block but failed to broadcast it in time (networking issue) then got stuck. It got #72043 and following blocks but failed to push them into chain database, because those blocks are linked to another #72042, but it didn't request for that #72042.
There could be an issue in code. Maybe current code just throw out an exception in this case. Maybe it's better to temporarily save the new block and request for it's previous block if it's not same as the one in current fork.

Just restarted my node and catching up.

The node is in China, network condition will be OK in next 8 hours or so (mid-night), and may go bad again after that. 

//update: my node should have produced a #72042 block but not #72043.

[betax]

@Bytemaster are you going to launch a new test net or shall we all stick with puppies ?

[betax]

For those getting error messages about your "clock" being out of sync, the issue was a bad error message.   Once every maintenance interval the blockchain skips some slots (currently configured to be 3) so that nodes can perform computational tasks that may take longer than a fraction of the normal block interval to complete.   These tasks include tallying votes among other things.    I have revised the error message to be a status message indicating that it is probably just a maintenance interval.

https://github.com/cryptonomex/graphene/issues/244

 

[puppies]

The network is still up and generating blocks on at least three different systems. 

Code: [Select]

  "head_block_num": 113869,
  "head_block_id": "0001bccd0acdf8b05c58b6cc5e6e36d717de523c",
  "head_block_age": "2 seconds old",
  "next_maintenance_time": "4 minutes in the future",
  "chain_id": "081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6",
It seems like your node did fork and now wont accept the proper chain.

Code: [Select]

get_block 72042
{
  "previous": "000119696d1d31776e6431586e14fd2e4c0b4f58",
  "timestamp": "2015-08-18T02:07:59",
  "witness": "1.6.1435",
  "next_secret_hash": "72dcf0475fa5d0c145a235f590b5be3597c17753",
  "previous_secret": "2813946aacd0bfda5541bf243f5bc47aee51e314",
  "transaction_merkle_root": "0000000000000000000000000000000000000000",
  "extensions": [],
  "witness_signature": "201506e5034d1df8627196bc97b5293eed3efbb6391a256789ca4a6912f169b45b51045f55f9be468a2db485bfcc4952996e10d1f4be0cc1c0eef2764470649035",
  "transactions": []
}
locked >>> get_block 72043
get_block 72043
{
  "previous": "0001196a1eb9d0e2021fd4f6ac9fe452ea46d4b3",
  "timestamp": "2015-08-18T02:08:00",
  "witness": "1.6.0",
  "next_secret_hash": "031a792684e0d99dab315ce6aea4fa92c85c6707",
  "previous_secret": "cd722b49f39a4b7160e081ae2c26cdf71f8e9194",
  "transaction_merkle_root": "0000000000000000000000000000000000000000",
  "extensions": [],
  "witness_signature": "1f64cf6d9e48683ed2259772c5006c0a1ec195dc280c59b5941250fa1581e8b86c0d32ed49d47d9d57cc87b3088e2f52bc15c7dc500955fa334864a3ed7b08be63",
  "transactions": []
}
locked >>> get_block 72044
get_block 72044
{
  "previous": "0001196bf9cf506fb01511e20c8566694b952a7d",
  "timestamp": "2015-08-18T02:08:01",
  "witness": "1.6.4",
  "next_secret_hash": "42899548ec99624cb2102330c429562510ef09a0",
  "previous_secret": "2777b474efe4774a69d716f61b5cf156deb3a232",
  "transaction_merkle_root": "0000000000000000000000000000000000000000",
  "extensions": [],
  "witness_signature": "1f02312f66e1dcf78335d1c5ee999181cd3a0191d927d48376fa5702a493d418514d01eb530328c2dee956d5824103b8576e7974049e0d414eab142fd3ddbbe991",
  "transactions": []
}
locked >>>
im curious is your block 72042 matches mine.

[bytemaster]

For those getting error messages about your "clock" being out of sync, the issue was a bad error message.   Once every maintenance interval the blockchain skips some slots (currently configured to be 3) so that nodes can perform computational tasks that may take longer than a fraction of the normal block interval to complete.   These tasks include tallying votes among other things.    I have revised the error message to be a status message indicating that it is probably just a maintenance interval.

https://github.com/cryptonomex/graphene/issues/244

[abit]

Got stuck in puppies' chain yesterday:

Code: [Select]

  "head_block_num": 72042.

Unable to sync today:

Code: [Select]

2015-08-18T14:46:05 p2p:terminate_inactive_connections_loop terminate_inactive_c ] Disconnecting peer 45.55.6.216:1776 because they didn't respond to my request for sync item 00000064848aa88b1476bf797ad9560c08b4b239                 node.cpp:1307


[betax]

I finally managed to get it working on puppie's test net. I'm embarassed to say what was causing all of my difficulties, so I won't! 

Tomorrow is another day, and I will have much better luck I'm sure.

Don't worry, as you have seen we all have struggled. Apologies I could not point you directly to my post as I was sneaking a few responses before travelling

[Riverhead]

I finally managed to get it working on puppie's test net. I'm embarassed to say what was causing all of my difficulties, so I won't! 

Tomorrow is another day, and I will have much better luck I'm sure.

We've all been there. Don't beat yourself up .

[Thom]

I finally managed to get it working on puppie's test net. I'm embarassed to say what was causing all of my difficulties, so I won't! 

Tomorrow is another day, and I will have much better luck I'm sure.

[abit]

I was producing blocks, but every so often I had the ntp error.

I have seen that NTP error from time to time myself.  We will look into it.

Vikram and I have reviewed the testnet and have identified a patch that would allow us to revive the existing test net by specifying a checkpoint.  Once we are sure we can revive the testnet we will start a new network with at least 100 witness slots so that it is less likely for a few bad apples to result in this issue.

It could be that you produced blocks on a fork.  If any of you have evidence that you were on a fork (have a block that wasn't included in the main chain) then that is something I am very interested in.

Looks like I'm on a fork right now, stopped syncing and stopped producing blocks. Logs of production witness are here. It perhaps caused by slow network connection to other peers.

Code: [Select]

2015-08-18T02:04:12 th_a:Witness Block Production block_production_loo ] slot: 1 scheduled_witness: 1.6.6 scheduled_time: 2015-08-18T0
2:04:13 now: 2015-08-18T02:04:13                  witness.cpp:239
2015-08-18T02:04:13 th_a:invoke handle_block         handle_block ] Got block #71842 from network                       application.cp
p:342
2015-08-18T02:04:13  th_a:invoke get_item             get_item ] Request for item {"item_type":1001,"item_hash":"000118a2245ede2df39a1
f4ae6da4e12f62f8232"}                     application.cpp:437
2015-08-18T02:04:13  th_a:invoke get_item             get_item ] Serving up block #71842                        application.cpp:445
2015-08-18T02:04:13 th_a:Witness Block Production block_production_loo ] slot: 1 scheduled_witness: 1.6.5155 scheduled_time: 2015-08-1
8T02:04:14 now: 2015-08-18T02:04:14                       witness.cpp:239
2015-08-18T02:04:13 th_a:Witness Block Production block_production_loo ] Witness 1.6.5155 production slot has arrived; generating a bl
ock now...                        witness.cpp:242
2015-08-18T02:04:13 th_a:Witness Block Production block_production_loo ] Generated block #71843 with timestamp 2015-08-18T02:04:14 at
time 2015-08-18T02:04:14                  witness.cpp:255
2015-08-18T02:04:13  th_a:invoke get_item             get_item ] Request for item {"item_type":1001,"item_hash":"000118a30cd6a49579d36
ad1217b098a544a798a"}                     application.cpp:437
2015-08-18T02:04:13  th_a:invoke get_item             get_item ] Serving up block #71843                        application.cpp:445
2015-08-18T02:04:14 th_a:Witness Block Production block_production_loo ] slot: 1 scheduled_witness: 1.6.1439 scheduled_time: 2015-08-1
8T02:04:15 now: 2015-08-18T02:04:15                       witness.cpp:239
2015-08-18T02:04:15 th_a:Witness Block Production block_production_loo ] slot: 2 scheduled_witness: 1.6.1 scheduled_time: 2015-08-18T0
2:04:16 now: 2015-08-18T02:04:16                  witness.cpp:239
2015-08-18T02:04:16 th_a:Witness Block Production block_production_loo ] slot: 3 scheduled_witness: 1.6.0 scheduled_time: 2015-08-18T0
2:04:17 now: 2015-08-18T02:04:17                  witness.cpp:239
2015-08-18T02:04:17 th_a:Witness Block Production block_production_loo ] slot: 4 scheduled_witness: 1.6.5 scheduled_time: 2015-08-18T0
2:04:18 now: 2015-08-18T02:04:18                  witness.cpp:239
2015-08-18T02:04:18 th_a:Witness Block Production block_production_loo ] slot: 5 scheduled_witness: 1.6.4 scheduled_time: 2015-08-18T0
2:04:19 now: 2015-08-18T02:04:19                  witness.cpp:239
2015-08-18T02:04:19 th_a:Witness Block Production block_production_loo ] slot: 6 scheduled_witness: 1.6.1435 scheduled_time: 2015-08-1
8T02:04:20 now: 2015-08-18T02:04:20                       witness.cpp:239
2015-08-18T02:04:20  th_a:invoke get_item             get_item ] Request for item {"item_type":1001,"item_hash":"000118a30cd6a49579d36
ad1217b098a544a798a"}                     application.cpp:437
2015-08-18T02:04:20  th_a:invoke get_item             get_item ] Serving up block #71843                        application.cpp:445
2015-08-18T02:04:20 th_a:invoke handle_block         handle_block ] Got block #71844 from network                       application.cp
p:342
2015-08-18T02:04:20 th_a:invoke handle_block         handle_block ] Error when pushing block:
10 assert_exception: Assert Exception
itr != _index.get<block_id>().end():
    {}
    th_a  fork_database.cpp:51 push_block

    {"new_block":{"previous":"000118a3ca0d1e6e5737f248ddb53836aa6212e4","timestamp":"2015-08-18T02:04:16","witness":"1.6.1","next_secret_hash":"6449e9c56a67b58d886f2064e929f17f94fe78f1","previous_secret":"68c24af208df75b7b3d6570206492ef3bee5c5b9","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f4becadfa61a394b550ce6d086fb5d9eb3da8c883ac703048c7baee139414089f6777d1c03787d982160d23ecef7df3df3ea8713c15441247c30c4ef5568e22ac","transactions":[]}}
    th_a  db_block.cpp:173 _push_block                  application.cpp:364
2015-08-18T02:04:20 th_a:Witness Block Production block_production_loo ] slot: 7 scheduled_witness: 1.6.2 scheduled_time: 2015-08-18T02:04:21 now: 2015-08-18T02:04:21                  witness.cpp:239
2015-08-18T02:04:21 th_a:invoke handle_block         handle_block ] Got block #71845 from network                       application.cpp:342
2015-08-18T02:04:21 th_a:invoke handle_block         handle_block ] Error when pushing block:
10 assert_exception: Assert Exception
itr != _index.get<block_id>().end():
    {}
    th_a  fork_database.cpp:51 push_block

    {"new_block":{"previous":"000118a4b95f7448500f912995feeffe47e61773","timestamp":"2015-08-18T02:04:17","witness":"1.6.0","next_secret_hash":"6449e9c56a67b58d886f2064e929f17f94fe78f1","previous_secret":"68c24af208df75b7b3d6570206492ef3bee5c5b9","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"2041523e0275f0ce506c797145c86f2b5ed5fb7d9eb9cff0f1cb9364e5a06c327e535dfd76846d56824d41ad69e502d2b88679b7060b33200128991dacf92f97ae","transactions":[]}}
    th_a  db_block.cpp:173 _push_block                  application.cpp:364


The observer witness node is stuck as well, haven't find related log yet.

//EDIT: console log of observer node is here.

Code: [Select]

251230ms th_a       application.cpp:342           handle_block         ] Got block #71840 from network
252602ms th_a       application.cpp:342           handle_block         ] Got block #71841 from network
253600ms th_a       application.cpp:342           handle_block         ] Got block #71842 from network
253998ms th_a       application.cpp:342           handle_block         ] Got block #71843 from network
440984ms th_a       application.cpp:486           get_blockchain_synop ] reference_point: 0000000000000000000000000000000000000000 num
ber_of_blocks_after_reference_point: 0 result: ["000018a317c85eac7ed13615354fcef049951d86","000098a3e1624c807fd57d019d0dcf58844905ac",
"0000d8a3f2164ee15e1d2404cf5815daaf024091","0000f8a34a36120b0ccf1ed468f1e5c1a0b81239","000108a338ff000b4ea31a71938f19d6668a330e","0001
10a3079a6cdffeb63507c7c4a44406221c1b","000114a31f31315fe4d4f9a3c18923029b506111","000116a318c63b35c2dbdd46e674b4c49dcf0673","000117a3c
2bdf2658c7d67a5f9040e65ac98a02d","00011823272051adb5851eb6617b11145a03979e","0001186341115fddf7f06780b5164e5254324f96","000118833ab2b2
fc44045ebb63376313df4cf712","0001189332e4dc39800f335bbd4cf10135617a33","0001189b4b78dec8eb8efebeb5b9fab06e6647ad","0001189fcd7f19f8469
b604041fd14a225ce5bae","000118a1ac5579df7e3f7952bf3889e7f6cc8413","000118a2245ede2df39a1f4ae6da4e12f62f8232","000118a30cd6a49579d36ad1
217b098a544a798a"]
466784ms th_a       application.cpp:486           get_blockchain_synop ] reference_point: 0000000000000000000000000000000000000000 num
ber_of_blocks_after_reference_point: 0 result: ["000018a317c85eac7ed13615354fcef049951d86","000098a3e1624c807fd57d019d0dcf58844905ac",
"0000d8a3f2164ee15e1d2404cf5815daaf024091","0000f8a34a36120b0ccf1ed468f1e5c1a0b81239","000108a338ff000b4ea31a71938f19d6668a330e","0001
10a3079a6cdffeb63507c7c4a44406221c1b","000114a31f31315fe4d4f9a3c18923029b506111","000116a318c63b35c2dbdd46e674b4c49dcf0673","000117a3c
2bdf2658c7d67a5f9040e65ac98a02d","00011823272051adb5851eb6617b11145a03979e","0001186341115fddf7f06780b5164e5254324f96","000118833ab2b2
fc44045ebb63376313df4cf712","0001189332e4dc39800f335bbd4cf10135617a33","0001189b4b78dec8eb8efebeb5b9fab06e6647ad","0001189fcd7f19f8469
b604041fd14a225ce5bae","000118a1ac5579df7e3f7952bf3889e7f6cc8413","000118a2245ede2df39a1f4ae6da4e12f62f8232","000118a30cd6a49579d36ad1
217b098a544a798a"]