Unfortunately I found once my delegate name "coolspeed" is registered. I guess it is registered in genesis block. But I couldn't export my private key that time. But I have backed up all my recent datadirs.

How can I find back my private key (or wallet) of "coolspeed"? Which file should I overwrite, if it is possible?
Thanks.

=====================================================
UPDATE:

I've solved it. I copyed my old wallet dir, opened it in the new client, and then dumped my private key.

In my experience the network code is completely botched right now.  I am working with Eric to track down the cause.  Very frustrating. 


Sent from my iPhone using Tapatalk

bytemaster, plz take it easy. Take a good sleep, forget all the f**king things.

I believe what should come will come, and what deserves be resolved will be resolved. By now, it's probably you. But no one should rush.

In the long run of DAC career, we really don't need to rush.

May the best DACs win. May all of us enjoy.

Quote from: coolspeed on June 09, 2014, 11:22:34 am

HELP!!

My first 4 importing of private keys were all OK. But when I import my 5th private key, it reported the following errors:

Code: [Select]

10
registered_account:
    {}
    th_a  wallet.cpp:787 import_private_key

    {"account_name":""}
    th_a  wallet.cpp:824 import_private_key

    {"account_name":""}
    th_a  wallet.cpp:844 import_wif_private_key

    {}
    th_a  common_api_client.cpp:212 wallet_import_private_key

    {"command":"wallet_import_private_key"}
    th_a  cli.cpp:576 execute_command


Can anyone tell me how I can fix this, or whether fixing this is a must.
Since the document syas:

Code: [Select]

If you want to stay voted in, you should probably create a new delegate to campaign as, as a nameless initial delegate is unlikely to stay a delegate for long.and the "DPOS Registering Names And Delegates " is not completed yet.

FYI, my fifth public key is:

Code: [Select]

XTS7XDCb4BEeEtbPtHWGCvx9xW3r5SGTrHr8PjnH3VbhtUFWsjArm

dan imported 4keys for one account

Thank you.
If I did not get you wrong, you mean it is all OK.

How to validate my Keyhotee founder ID public key is exactly the same as what I registered?
Cuz I think It will be too late after the real XT chain started.

Location: San Francisco, USA.
CPU: 4 core precessor
RAM: 8GB
SSD hard disk.

Public keys:

coolspeed-delegate-1 : XTS6DitjvvENF6Frfvb1jiUCNAGNwH6PMjYVEGCxAvV4cZXRVbwmp
coolspeed-delegate-2 : XTS7AeUKLhpn2J5rekbFdCt3xsJ5SznRL5bR5kEBT7JSbCB9AQFka
coolspeed-delegate-3 : XTS6uVAGPTgbrdVnx9b5qMRqoVakVBMZymVWWDJy6QmuMrDnySHmg
coolspeed-delegate-4 : XTS5kJVSkqGbPXUCfyz2kfXj6ZSBeV7xbXdhmBsJ8FQ8kjY4iANmM
coolspeed-delegate-5 : XTS7XDCb4BEeEtbPtHWGCvx9xW3r5SGTrHr8PjnH3VbhtUFWsjArm

In order to provide high availability and faith about the network, and not to be fired for missing blocks in their turn, Delegates must have some DevOps process. I want to discuss some processes from scratch with you all.

As the development lasts, there will always be need to upgrade Delegate program versions. Or you will be fired. And you'd better upgrade on-the-fly.

After every shuffle, the order of next 100 blocks' forgers is determined. So most of the delegates may have time to tear the node down for a while and relaunch it. At this time, another instance needs to be already pulled from GitHub and built. In fact, you may always need a 'left' instance and 'right' instance, just like a seesaw. The left instance and right instance can share the same data directory, which is ~/.BitSharesXTS by default.

If I did not miss something, Delegates can miss no block at all in this way.

Quote from: sfinder on June 04, 2014, 02:31:40 am

目前比较彻底的解决方法是让AGS流动。否则在领取第3方DAC时都要提心吊胆的。

可以流动的的话对ptser来说不公平吧。

法理上一切你拥有所有权的东西都是可以转让的。AGS用户经受了很大的不确定性的风险——关于何时价值可以兑现（为 DACs 股权）以及何时可以流动起来，而进行投资。
AGS 也比 PTS 少一份对第三方 DAC 启动者的吸引力。这也是区别。
PTS 与 AGS 的单价差异是市场合理的。