难道只能导入一次？覆盖从新导入就丢失了？不会吧，那惨了

bts1.0钱包由于titan的缘故，一个账号的余额分别在不同的私钥中，导入2.0后 需要一次claim操作将所有币转到一个账号.

reload many times

yes I had reload many times ,but also have this problem , I try to use newest version

Quote from: jakub on October 15, 2015, 06:03:13 pm

It looks like there is yet another bug in the GUI.
The account page fails to display its content when an account name is too short, e.g. k1, k2, a1

When I try this URL
https://bitshares.org/wallet/#/account/k1
or
https://bitshares.org/wallet/#/account/k2
or
https://bitshares.org/wallet/#/account/a1
I get an empty screen.

But when I go
https://bitshares.org/wallet/#/account/k88
or
https://bitshares.org/wallet/#/account/a10
it works fine.

At https://bitshares.openledger.info/#/account/k1 it's displayed ok, this bug was fixed yesterday but maybe wasn't updated at https://bitshares.org/wallet

I have an account named k1 in my bts1.0 wallet ,also there are other account
I import this wallet in bts2.0 , expect k1 other account are showed in wallet -gui
it seems that the account K1 is not imported in bts2.0 ?
but I claim all some of my bts and all asset to K1,

BTS2.0 首先放出来的轻钱包，网络被墙严重，导致很多打开钱包变白板。现在完整一体化的重钱包并没有放出来。 但其实已经可以使用重钱包了。
1.下载windows命令行钱包 BitShares-2.15.286-win64-cli-tools.exe https://github.com/bitshares/bitshares-2/releases/download/v2.15.286/BitShares-2.15.286-win64-cli-tools.exe
    下载 windows 轻钱包 https://github.com/bitshares/bitshares-2/releases/download/v2.15.286/BitShares-light_2.15.287.exe
2.分别安装 命令行钱包 BitShares-2.15.286-win64-cli-tools.exe  和轻钱包BitShares-light_2.15.287.exe
3.找到命令行钱包目录（安装时候选择的） 默认目录为 C:\Program Files\BitShares 2\bin新建个一个批处理文件 start.bat  内容为cd "%~dp0
witness_node -s 104.200.28.117:61705 --rpc-endpoint 127.0.0.1:8090 保存后以管理员方式运行这个批处理文件.
4.打开轻钱包，将API服务器设置为 ws:/127.0.0.1:8090
国内高速服务器(极乐净土提供）：ws://139.196.37.179:8090
欢迎大家加入探讨QQ :424152256  http://shang.qq.com/wpa/qunwpa?idkey=c04deb9f30071097d5f5d138e97e5b53827cbf4c4238abc7b522fb820f4d9258

While laying in bed this morning I had a flash of insight on how to significantly reduce the size of the signatures that prove who a payment is from.

Given Public Information (in blockchain):

Quote

dan => DANS_EXT_PUBLIC_KEY
scott => SCOTTS_EXT_PUBLIC_KEY

Assuming scott wants to send dan a payment anonymously, yet wants dan to know it is from him.

Quote

scott:  Generate OneTimePrivateKey  & OneTimePublicKey Pair
scott:  OneTimePrivateKey * DANS_EXT_PUBLIC_KEY => SECRET
                                        DANS_EXT_PUBLIC_KEY.child( SECRET ) => RECEIVE_PUBLIC_KEY => RECEIVE_ADDRESS
scott:  RECEIVE_PUBLIC_KEY * SCOTTS_EXT_PRIVATE_KEY => CHECK_SECRET
                                                                                    => SHORT_HASH(CHECK_SECRET) == SHORT_SIGNATURE

scott-broadcast:   OneTimePublicKey + RECEIVE_ADDRESS + ENCRYPT( from scott + SHORT_SIGNATURE, SECRET )

Quote

dan:   OneTimePublicKey * DANS_EXT_PRIVATE_KEY => SECRET
                                      DANS_EXT_PRIVATE_KEY.child( SECRET ) =>
                                                                RECEIVE_PRIVATE_KEY =>
                                                                  RECEIVE_PUBLIC_KEY => RECEIVE_ADDRESS

dan:   DECRYPT( data, SECRET ) => "from scott" + SHORT_SIGNATURE )
dan:   SCOTT_EXT_PUBLIC_KEY * RECEIVE_PRIVATE_KEY => CHECK_SECRET => SHORT_HASH(CHECK_SECRET)

HI  BM , I know you are busy recently , if you have spare , can you explain why use EXT_PRIVATE_KEY.child( SECRET ) rather than  EXT_PRIVATE_KEY(SECRET)  , 
generate many child key is the reason of  low inefficiency?

it is seems that you try to connect to local serve,  had you run full witness node on you computer?