Dry Run 6: Great Scott!

[emski]

All my delegates are missing blocks.
What should I do about that?

[puppies]

I have 2 strange cases:
1)

dxtr-wallet (unlocked) >>> blockchain_list_blocks 409 3
    HEIGHT                          TIME      TXN COUNT                                                 SIGNING DELEGATE    SIZE LATENCY
----------------------------------------------------------------------------------------------------------------------------------------
       409           2014-06-26T13:28:00              2                                                         scroodge     584       
       410           2014-06-26T13:30:00              1                                                  delegate-dorian     499       1
       411           2014-06-26T13:32:00              0                                                          vikram9     182      25
dxtr-wallet (unlocked) >>> blockchain_get_delegate_block_stats vikram9
[[
    231,{
      "missed": false,
      "latency": null
    }
  ],[
    356,{
      "missed": false,
      "latency": null
    }
  ],[
    411,{
      "missed": false,
      "latency": 25
    }
  ]
]
dxtr-wallet (unlocked) >>> blockchain_get_delegate_block_stats scroodge
[[
    411,{
      "missed": false,
      "latency": 0
    }
  ]
]


One command, blockchain_get_delegate_block_stats says that both scroodge and vikram9 have produced the same block,
another command, blockchain_list_blocks 409 3 lists that block 409 was created by scroodge, not 411.

2) When I send some XTS from one and the same wallet account to another in this same wallet, transaction is processed, but XTS disappears from source and does not appear in target (one of accounts is a delegate, so there is no blockchain rescan afterwards [I think]).

Are those known issues?

I'm not sure about the transfer issue, but it sounds like you are right.  can you manually wallet_rescan_blockchain?  Maybe try turning off block production first.  If neither of those work I would export the private key of the account with funds close the wallet, create another one, and import the key.

As for the blockchain_get_delegate_block_stats that same issue was happening on the last testnet.  I can't remember exactly what Bytemaster said, but it was something along the lines of an issue with delegate ID.  Perhaps its similar to the wallet bug that makes it look like you have access to others accounts.

[alt]

Would someone be willing to send me some testing funds?

XTS79hDqU6eAFSazUcj3i6GWEVT7jTb3zMHtjf4StixLqP7EWUfkZ

thanks!!

100 XTS to you

[cmaje72]

Would someone be willing to send me some testing funds?

XTS79hDqU6eAFSazUcj3i6GWEVT7jTb3zMHtjf4StixLqP7EWUfkZ

thanks!!

[alt]

the nodes which connected  not mean they are on the same chain.
fork happened because some delegates get the block with high latency maybe 6 minutes.
then don't know 2 blocks already generated by other delegate.

This is almost certainly a network / communication issue potentially caused by socket inactivity and TCP/IP connections going stale. 

what you mean ?
take follow fork yestoday occured , I was on the fork chain ,but information show I have 45 connection
1. 45 connections were inactivity,
2. 45 connection were activity ,but all 45 node I connected were on fork chain
which one you mean ?

Code Select Expand

  "blockchain_head_block_num": 2633,
  "blockchain_head_block_time": "20140625T062930",
  "blockchain_head_block_time_rel": "28 minutes old",
  "blockchain_confirmation_requirement": 303,
  "blockchain_average_delegate_participation": 44.888888888888886,
  "network_num_connections": 45,
  "ntp_time": "20140625T065726.868608",
  "ntp_error_seconds": -0.014512000000000001,
  "wallet_unlocked_seconds_remaining": 0,
  "wallet_next_block_production_time": null,
  "wallet_seconds_until_next_block_production": null,
  "wallet_local_time": "20140625T065726",
  "blockchain_random_seed": "736362e9df6cd562307b713aae1eb75c3d11b88d",
  "blockchain_shares": 199999351280463,
  "network_num_connections_max": 200,
  "network_protocol_version": 103,
  "wallet_open": true,
  "wallet_unlocked_until": "20140624T023103",
  "wallet_version": 100

[wackou]

I believe I have fixed this.

Doesn't work for me:

worked for me...

yeah, works for me too, now.

[liondani]

I believe I have fixed this.

Doesn't work for me:

worked for me...

[BTSdac]

This is almost certainly a network / communication issue potentially caused by socket inactivity and TCP/IP connections going stale. 

what you mean ?
take follow fork yestoday occured , I was on the fork chain ,but information show I have 45 connection
1. 45 connections were inactivity,
2. 45 connection were activity ,but all 45 node I connected were on fork chain
which one you mean ?

Code Select Expand

  "blockchain_head_block_num": 2633,
  "blockchain_head_block_time": "20140625T062930",
  "blockchain_head_block_time_rel": "28 minutes old",
  "blockchain_confirmation_requirement": 303,
  "blockchain_average_delegate_participation": 44.888888888888886,
  "network_num_connections": 45,
  "ntp_time": "20140625T065726.868608",
  "ntp_error_seconds": -0.014512000000000001,
  "wallet_unlocked_seconds_remaining": 0,
  "wallet_next_block_production_time": null,
  "wallet_seconds_until_next_block_production": null,
  "wallet_local_time": "20140625T065726",
  "blockchain_random_seed": "736362e9df6cd562307b713aae1eb75c3d11b88d",
  "blockchain_shares": 199999351280463,
  "network_num_connections_max": 200,
  "network_protocol_version": 103,
  "wallet_open": true,
  "wallet_unlocked_until": "20140624T023103",
  "wallet_version": 100

[liondani]

The log-out timeout on preferences didn't work !!!
I update to 999999 seconds 2 times (stated "Preferences Updated") and it log outs both times....

still don't works for me.

[Ggozzo]

Anyone tell me possible reasons why the windows wallet won't open? I get the window that us blue with lines and it says loading configuration at the bottom, then after about 5 seconds it closes and nothing happens. I am sure it is something to do with my computer, but everything I tried doesn't get it to work.

Thanks in advance.

I am running windows 7.

[chono]

This is good news:  the forks that have occurred are not for differences in evaluation logic, but instead purely differences in timing / communication.

+5% .. take your time .. we can go on for another 10 testnets .. I like seeing progress like this!

Can't imaging a product that is as stable and fast and reliable .. as what you are producing here .. !!

+5%

+5% :)

+5%

[dxtr]

I have 2 strange cases:
1)

dxtr-wallet (unlocked) >>> blockchain_list_blocks 409 3
    HEIGHT                          TIME      TXN COUNT                                                 SIGNING DELEGATE    SIZE LATENCY
----------------------------------------------------------------------------------------------------------------------------------------
       409           2014-06-26T13:28:00              2                                                         scroodge     584       
       410           2014-06-26T13:30:00              1                                                  delegate-dorian     499       1
       411           2014-06-26T13:32:00              0                                                          vikram9     182      25
dxtr-wallet (unlocked) >>> blockchain_get_delegate_block_stats vikram9
[[
    231,{
      "missed": false,
      "latency": null
    }
  ],[
    356,{
      "missed": false,
      "latency": null
    }
  ],[
    411,{
      "missed": false,
      "latency": 25
    }
  ]
]
dxtr-wallet (unlocked) >>> blockchain_get_delegate_block_stats scroodge
[[
    411,{
      "missed": false,
      "latency": 0
    }
  ]
]


One command, blockchain_get_delegate_block_stats says that both scroodge and vikram9 have produced the same block,
another command, blockchain_list_blocks 409 3 lists that block 409 was created by scroodge, not 411.

2) When I send some XTS from one and the same wallet account to another in this same wallet, transaction is processed, but XTS disappears from source and does not appear in target (one of accounts is a delegate, so there is no blockchain rescan afterwards [I think]).

Are those known issues?

[wackou]

This is good news:  the forks that have occurred are not for differences in evaluation logic, but instead purely differences in timing / communication.

+5% .. take your time .. we can go on for another 10 testnets .. I like seeing progress like this!

Can't imaging a product that is as stable and fast and reliable .. as what you are producing here .. !!

+5%

+5%

[alt]

This is good news:  the forks that have occurred are not for differences in evaluation logic, but instead purely differences in timing / communication.

+5% .. take your time .. we can go on for another 10 testnets .. I like seeing progress like this!

Can't imaging a product that is as stable and fast and reliable .. as what you are producing here .. !!

+5%

来自我的 HUAWEI P7-L00 上的 Tapatalk

[xeroc]

This is good news:  the forks that have occurred are not for differences in evaluation logic, but instead purely differences in timing / communication.

+5% .. take your time .. we can go on for another 10 testnets .. I like seeing progress like this!

Can't imaging a product that is as stable and fast and reliable .. as what you are producing here .. !!