Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Harvey

Pages: 1 ... 4 5 6 7 8 9 10 [11] 12 13 14 15 16 17
151
唉,不知道3i什么时候解决未写入创世块的id问题,pm了bm、hackfisher结果都没有给任何答复,伤心啊 :'( :'(

坦白说 基本上没指望了

除非更新世纪快 重头在发布一次 BitsharesX的链块.

152
我的客户端打开以后 还看不到怪兽图.  :'(

153
General Discussion / Re: Hey, BTSX delegates, come here.
« on: July 23, 2014, 06:00:43 pm »
It seems that the command 'wallet_account_rename' allows the transaction of renaming a registered name to another registered name.

For example, I have the account 'A'. And alt has the account 'B'.
After
Code: [Select]
wallet_account_rename A B
The results of
Code: [Select]
wallet_list_my_account will say that I have a registered account with name 'B' which should be belong to alt.
 

154
中文 (Chinese) / Re: Bitshares感谢计划
« on: July 23, 2014, 05:07:07 pm »
龙门客栈创始人, 募集资金 投资DACs 帮助社区成长.

龙门矿业创始人, 长期参加BTSX测试 建立代表节点 维护DPOS网络正常运行.


btc: 1ARqveHT48TTBaPeyrYqHTV2E5mjxPj76W
pts: Pa5x1dhQ5UqqTPfzojnpUP5FBU1Antrtdv
btsx: harvey

155
sounds like a plan!  +5%

156
I found the reason, the ntp servers are down for all Digitalocean nodes in Singapore.
https://www.digitalocean.com/community/questions/droplet-in-singapore-can-t-sync-ntp-server

157
After I install the ntpd and add the server 0.asia.pool.ntp.org, my delegates still have 7 seconds latency compare to the network.
Check it out:

Code: [Select]
harvey (unlocked) >>> getinfo
{
  "blockchain_head_block_num": 24750,
  "blockchain_head_block_age": "7 seconds in the future",
  "blockchain_head_block_timestamp": "20140722T034610",
  "blockchain_average_delegate_participation": 97.115384615384613,
  "blockchain_delegate_pay_rate": 230755,
  "blockchain_blocks_left_in_round": 96,
  "blockchain_confirmation_requirement": 1,
  "blockchain_accumulated_fees": "279,121.57802 BTSX",
  "blockchain_share_supply": 199972087824121,
  "blockchain_random_seed": "c76adb033d918e656613f24c6965d2b36d48e751",
  "blockchain_database_version": 115,
  "blockchain_version": 109,
  "network_num_connections": 18,
  "network_num_connections_max": 100,
  "network_protocol_version": 104,
  "ntp_time": null,
  "ntp_error": null,
  "wallet_open": true,
  "wallet_unlocked": true,
  "wallet_unlocked_until": "31 years  in the future",
  "wallet_unlocked_until_timestamp": "19100221T114701",
  "wallet_block_production_enabled": true,
  "wallet_next_block_production_time": "77 seconds in the future",
  "wallet_next_block_production_timestamp": "20140722T034720",
  "wallet_version": 100
}

The age of last lock is:
Code: [Select]
"blockchain_head_block_age": "7 seconds in the future"
And the ntp_time display:
Code: [Select]
"ntp_time": null,
 "ntp_error": null,

My vps is a 2GB digitalocean node locates in Singapore. Any suggestion will be really appreciated.

158
遇到更诡异的的情况了 安装了0.2.1版本以后 正常使用了一天 转账数次都正常

今晚重启了一次电脑以后 再次打开 BTSX 就出现传说中的闪退现象了.

参考本帖中的建议 删除补丁 闪退依旧.

唉~

------------------------------------------------------------
找到原因了 启动BTSX之前 随手关掉了一个windows的系统服务 结果就导致了闪退不止

在重启一次以后 BTSX恢复正常

那些遇到闪退问题的 可能也是windows系统服务进程没有正常运行的原因

关掉的是什么系统服务?

在任务管理器里中止了一个占CPU的 svchost.exe 进程.
同名进程有很多个, 不确定这个进程具体代表了什么系统服务.

但你们应该可以重现这个bug.

159
欢迎大家给龙门矿业投票

龙 dragon
狮子 lion
冰原狼 direwolf
乌鸦 raven

细针 needle 
长爪 longclaw
守誓者 oathkeeper
守夜人 nightswatch


160
遇到更诡异的的情况了 安装了0.2.1版本以后 正常使用了一天 转账数次都正常

今晚重启了一次电脑以后 再次打开 BTSX 就出现传说中的闪退现象了.

参考本帖中的建议 删除补丁 闪退依旧.

唉~

------------------------------------------------------------
找到原因了 启动BTSX之前 随手关掉了一个windows的系统服务 结果就导致了闪退不止

在重启一次以后 BTSX恢复正常

那些遇到闪退问题的 可能也是windows系统服务进程没有正常运行的原因

161
I installed ntpd on the server of the delegate lion.
Hope it will reduce the latency.

163
中文 (Chinese) / Re: Bitshares X正式发布
« on: July 19, 2014, 07:29:46 pm »
兼容性或许又待改进 在win7下打开 启动报错:

Code: [Select]
There is no disk in the drive. Please insert a disk into drive \Device\Harddisk1\DR1

164
Wait for 10 hours, still stuck at block 888.

Code: [Select]
(wallet closed) >>> getinfo
{
  "blockchain_head_block_num": 888,
  "blockchain_head_block_age": "10 hours old",
  "blockchain_head_block_timestamp": "20140715T191420",
  "blockchain_average_delegate_participation": 2.8378758078111828,
  "blockchain_delegate_pay_rate": 30136187,
  "blockchain_blocks_left_in_round": 21,
  "blockchain_confirmation_requirement": 1,
  "blockchain_share_supply": 199996956227035,
  "blockchain_random_seed": "5f626e10fdc76cf6e2e310a5b95b88f3d8b49ce7",
  "blockchain_database_version": 114,
  "blockchain_version": 107,
  "network_num_connections": 4,
  "network_num_connections_max": 200,
  "network_protocol_version": 104,
  "ntp_time": null,
  "ntp_error": null,
  "wallet_open": false,
  "wallet_unlocked": null,
  "wallet_unlocked_until": null,
  "wallet_unlocked_until_timestamp": null,
  "wallet_block_production_enabled": null,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null,
  "wallet_version": 100
}

165
It seems that my node can not sync with the network.

Code: [Select]
harvey (unlocked) >>> wallet_list_my_accounts
NAME (* delegate)                  KEY                                                             REGISTERED            FAVORITE       APPROVED       BLOCK PRODUCTION ENABLED
harvey-xts                         XTS6bp1riWPpUr3v4VGbKRambXQU3JypHwncVryGjFoVouCT6oT8z           NO                    NO             0              N/A
longclaw *                         XTS5BxLgYL7czZJ2nH5HEbGyXcGuRQyAqRvxgYjmuASuVaSBgqhst           2014-07-15T17:25:30   NO             1              YES
raven *                            XTS8dUTpfgjUae3jDJcUrJXUxzYnt51pQRLXfJn7uPeCV8QuVh8rY           2014-07-15T17:32:50   NO             1              YES
harvey (unlocked) >>> getinfo
{
  "blockchain_head_block_num": 801,
  "blockchain_head_block_age": "6 minutes old",
  "blockchain_head_block_timestamp": "20140715T185940",
  "blockchain_average_delegate_participation": 73.722627737226276,
  "blockchain_delegate_pay_rate": 71475283,
  "blockchain_blocks_left_in_round": 7,
  "blockchain_confirmation_requirement": 1,
  "blockchain_share_supply": 199992780978243,
  "blockchain_random_seed": "9e7efcd2b987d48cb3cb3a29f4e3960b7519e789",
  "blockchain_database_version": 114,
  "blockchain_version": 107,
  "network_num_connections": 10,
  "network_num_connections_max": 200,
  "network_protocol_version": 104,
  "ntp_time": null,
  "ntp_error": null,
  "wallet_open": true,
  "wallet_unlocked": true,
  "wallet_unlocked_until": "3 years 2 months in the future",
  "wallet_unlocked_until_timestamp": "20170915T045019",
  "wallet_block_production_enabled": true,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null,
  "wallet_version": 100
}


after I wipe the ~/.BitsharesXTS, it will catch the latest block and stuck again:


Code: [Select]
(wallet closed) >>> getinfo
{
  "blockchain_head_block_num": 850,
  "blockchain_head_block_age": "3 minutes old",
  "blockchain_head_block_timestamp": "20140715T190800",
  "blockchain_average_delegate_participation": 84.87394957983193,
  "blockchain_delegate_pay_rate": 43895392,
  "blockchain_blocks_left_in_round": 59,
  "blockchain_confirmation_requirement": 1,
  "blockchain_share_supply": 199995566547318,
  "blockchain_random_seed": "233b6dc83c73f21c677298759b90a4db9a177bcf",
  "blockchain_database_version": 114,
  "blockchain_version": 107,
  "network_num_connections": 9,
  "network_num_connections_max": 200,
  "network_protocol_version": 104,
  "ntp_time": null,
  "ntp_error": null,
  "wallet_open": false,
  "wallet_unlocked": null,
  "wallet_unlocked_until": null,
  "wallet_unlocked_until_timestamp": null,
  "wallet_block_production_enabled": null,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null,
  "wallet_version": 100
}

Pages: 1 ... 4 5 6 7 8 9 10 [11] 12 13 14 15 16 17