Quote from: abit on January 10, 2015, 10:15:29 am

Code: [Select]

(wallet closed) >>> blockchain_get_block_signee 1303717
10 assert_exception: Assert Exception
!(c.data[1] & 0x80): signature is not canonical
    {}
    th_a  elliptic.cpp:496 fc::ecc::public_key::public_key

    {}
    th_a  common_api_client.cpp:2323 bts::rpc_stubs::common_api_client::blockchain_get_block_signee

    {"command":"blockchain_get_block_signee"}
    th_a  cli.cpp:579 bts::cli::detail::cli_impl::execute_command

Anybody else get this as well?
Exception raises while querying block 1303717,1303906,1303982 and more, the biggest block number with this issue is 1319180.

After re-downloaded the whole block chain the exception remains still.

I'm running v0.4.27.1@Ubuntu 64bit and v0.4.27.2@Win7 64bit.

Known issue:

https://bitsharestalk.org/index.php?topic=12448.msg164197#msg164197

https://github.com/BitShares/bitshares/issues/1165

On linux you can manually implement the commit vikram made to fix it and recompile to solve the issue, it's a one-line fix.

Thanks!

Then it stopped again and I went to bed shutting down the computer. Now I had a nice sleep and wake up in the hope for the best. Then "critical error, please start again".

It's best to quit the wallet (by clicking menu File->Quit) before shut down the computer.

Quote from: xiahui135 on January 09, 2015, 04:52:57 pm

Quote from: cgafeng on January 09, 2015, 04:44:29 pm

刚创建的钱包需要输入2次一样的密码，这是设置钱包密码，以后你的钱包都需要输入这个密码才能进入

重装了，每次打开，都是解锁界面。让输入密码，然后输入之后软件提示密码错误。
不论选择什么，都是输入密码。。。

那是你之前有设置过密码了，如果钱包里没币的话可以把钱包删了重新创建钱包。
windows开始菜单中选择运行，输入%APPDATA%\BitShares会打开bts钱包目录，如果你确定以前创建的钱包没币的话可以直接把整个BitShares目录删除，再打开客户端。

删除还是小心点好。
把目录改个名字就可以了，或者移动到其他盘。以后要是想起密码可以改回来。

Interesting.. BTSBOTS's batch market transactions are identified as 'Ask'?

BTW transaction types should include 'cancel an order'.

Quote from: vikram on January 08, 2015, 08:23:12 pm

Quote from: xeroc on January 06, 2015, 05:07:48 pm

The feed scripts use float() with %g to format the number .. maybe thats the issue ...

Have a sample code?

I think xeroc is correct, it looks like the exponent at the end of "1.2028997179833209e-05" might be causing the failure.

I don't know where it convert price  from type float to type string
from the output above, it's still float when I call requests.post()

Anyway encoded HTTP post data is a String. You have this in the data:
['ask_order', ['fund.btsbots', 11429.350384438114, 'BTS', 1.202899717
9833209e-05, 'GOLD']]

generated by
json.dumps(payload)


受托人运行过程中，可能遇到服务器重启后，需要自动启动钱包。官方wiki上有说明：
http://wiki.bitshares.org/index.php/Bitshares-x-delegate-how-to#Starting_the_client_after_a_reboot_or_crash

第一步，启动钱包
gdb ./bitshares_client --server --httpport 9989 --rpcuser user --rpcpassword pass
第二步，钱包启动后，在钱包的控制台输入下面的命令
open mywallet
 unlock 999999
 <enter password>
 wallet_delegate_set_block_production user123 true
 network_set_advanced_node_parameters {"desired_number_of_connections":100, "maximum_number_of_connections":200}

但是实际上，如果是服务器异常重启，是没有机会人工输入上述命令的，这样就会导致丢块。

为了解决这个问题，alt实现了一个用expect脚本来自动输入上述命令的方法，代码见 https://github.com/bitsuperlab/operation_tools/tree/master/restart
其他受托人也有各自的做法。

这里介绍的是另外一种方法：直接使用钱包程序的启动参数和配置文件，来实现启动时自动加载命令执行。
第一步，创建一个文件，比如命名为 startup.input ，内容如下
>>> open mywallet
>>> unlock 99999999 <password>
>>> wallet_delegate_set_block_production user123 true
>>> network_set_advanced_node_parameters {"desired_number_of_connections":100, "maximum_number_of_connections":200}
注意，每行以“>>> ”开头，也就是3个大于号加一个空格，后面跟要执行的命令。
命令里的参数，包括钱包名，密码，受托人账号等等，请根据自己情况修改。
至于密码写在文件里怎么让别人看不到，这里不详细讨论，有经验的请补充。

第二步，修改启动钱包的命令，在后面添加一个参数
gdb ./bitshares_client --server --httpport 9989 --rpcuser user --rpcpassword pass --input-log startup.input
这样，钱包启动时，就会自动加载 startup.input 里的命令了。

结束。

欢迎打赏或者拍砖

Q2. wallet2 to get back the bts
@abit, @vikram
as this act involoves more than half of my savings
i have to be really discreet
will it cause any problem
that the due bts was once claimed,later a transaction was made
then import the pts wallet again?
do you think i should import it to the same wallet same account
or a brand new empty wallet with new account ?

If you 'claimed' but didn't transfer all the fund to another account, you left the remaining fund at its original address, it's re-claimable with the private key. So it's safe if you're the only one who know the key.
As vikram answered, claim to a new wallet is better.

For those who lost fund after importing a private key, it may be interesting to check whether the owner key and the active key of the account are same.
While creating a new sub-account with current version of client (v0.4.27.2), the owner key and active_key are different by default. In this case, if one dump out the private key of the account and import it into another wallet, only the active key will be imported, as a result, something strange may happen.

>> wallet_account_create test.abit

"BTS5R1G2iBqAoKAKZCRfJgZA7us7N7xkvSaMwStnY1hkK52s42A56"

>> wallet_get_account test.abit

{
  "index": 52041,
  "id": 0,
  "name": "test.abit",
  "public_data": null,
  "owner_key": "BTS5R1G2iBqAoKAKZCRfJgZA7us7N7xkvSaMwStnY1hkK52s42A56",
  "active_key_history": [[
      "2015-01-07T13:40:53",
      "BTS5j2xL7jKjFprETK1suWfxGEux8gQcuheyaL9nytW9AHtzRDuUz"
    ]
  ],
...
}