Quote from: G1ng3rBr34dM4n on August 28, 2014, 07:22:28 pm

Crashed again for me right around 320000 block mark.  And I can't open the client.

.0.4.9-a crashed after opened. On personal computer and VPS.

1) go to your account and check that you registered the same name
2) go to the console, type "getinfo" and check that your are synced (latest block time, second line or so < 20 secs)
3) go to console and check the output of
blockchain_get_account <useraccountnamehere>

last block if im reading it correctly is 2 days old any idea how to fix this ?
>> getinfo

{
  "blockchain_head_block_num": 321978,
  "blockchain_head_block_age": "53 hours old",
  "blockchain_head_block_timestamp": "2014-08-26T14:16:50",
  "blockchain_average_delegate_participation": "0.52 %",
  "blockchain_confirmation_requirement": 1,
  "blockchain_accumulated_fees": "165,130.24441 BTSX",
  "blockchain_delegate_pay_rate": "1.36516 BTSX",
  "blockchain_share_supply": "1,999,935,452.70804 BTSX",
  "blockchain_blocks_left_in_round": 10,
  "blockchain_next_round_time": "at least 2 minutes in the future",
  "blockchain_next_round_timestamp": "2014-08-28T19:44:40",
  "blockchain_random_seed": "a728665aa43b77b4a2dee68fd3085a51cb00005e",
  "client_data_dir": "C:/Users/Woodygar/AppData/Roaming/BITSHA~1",
  "client_version": "0.4.9",
  "network_num_connections": 0,
  "network_num_connections_max": 100,
  "ntp_time": "2014-08-28T19:43:00",
  "ntp_time_error": -1.7011799999999999,
  "wallet_open": true,
  "wallet_unlocked": true,
  "wallet_unlocked_until": "12 days in the future",
  "wallet_unlocked_until_timestamp": "2014-09-09T09:29:26",
  "wallet_last_scanned_block_timestamp": null,
  "wallet_scan_progress": "? %",
  "wallet_block_production_enabled": false,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null
}

Quote from: bytemaster on August 27, 2014, 06:58:01 pm

Quote from: gamey on August 27, 2014, 06:52:52 pm

In fact, a colluding delegate could just ignore transactions when they know they have a loser.  It doesn't even have to be a missed block.  Wouldn't this be simple to do ?  So you now have to expect transactions to go in certain blocks and figure out all the heuristics for this?  Isn't that what is required for bytemaster's missed blocks == house rake approach to work ?

It really isn't missed blocks, it is just not accepting transactions and pushing them off to next block.  This is a harder attack to discover unless you start timestamping transactions etc.  I think this might be required to detect this attack ?

You can keep the "winning/loosing" a secret until after the ticket has been included.  So this is not an issue.

You can reveal winning/losing after ticket has been included, but that requires extra blocks which adds latency in the game if I understand correctly.  Ideally gaming transaction is put on same block as RNG revelation.  Otherwise we add 10 seconds to every game round.

是的，每次备份都是在钱包里的export wallet 备份的，

25号钱包备份，提示错误： Failed to restore wallet backup.Your original wallet has been restored.
                                      Error: Bad cast(7)
                                      Invalid cast from type'string_type' to Object
23号以前的所有钱包备份，提示错误是：  Failed to restore wallet backup .Your original wallet has been restored .
                                                         Error: file not found ()20019 Filename to import from could not be found

To recover your existing backup, open the backup file in a text editor like Notepad and scroll all the way to the end. There is an extra comma at the end of the file; the last two lines will look like this:

Code: [Select]

},
]


黑鱼，可以把你的QQ发给我吗？我不会在论坛贴图，我0.4.7版本运行的时候直接崩溃了，后来装的0.4.8版本，结果没法运行，在APPDATA里删除后可以运行了，导入备份文件，报错了，24，25号备份文件提示无法导入，23号以前的备份文件提示没找到文件，我截了好几张图，请帮我看看~急~

之前的各个版本我都用的好好的，直到这次0.4.8遇到很多麻烦。先是 找不到key，无连接。我就重新安装并恢复了之前的钱包备份，然后发生以下问题。
1.在0.4.7上做的short单不见了，无法取消。
2.历史交易记录每一笔的时间都变成了几万分钟，还不停的来回跳动。
3.bitusd/BTS 市场无法进入 一直处于读取状态。
4.经常崩溃，重新启动有时候要求重新索引区块链。
5.重新安装，删除 替换早前版本等等都无法解决以上问题。