4441
中文 (Chinese) / Re: BTS通胀率警戒线
« on: January 10, 2015, 12:42:48 pm »
技术牛的中国人，比如alt都不愿做100%受托人。
其他人怎么说呢。
谁来带个头吧。
其他人怎么说呢。
谁来带个头吧。
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.
4442
Stakeholder Proposals / Re: Blackwave Labs(黑潮实验室)/Excoin(是币交中心) Delegate Proposal
« on: January 10, 2015, 12:14:39 pm »
@Excoin your delegate is missing blocks again.
4443
中文 (Chinese) / Re: 黑潮实验室
« on: January 10, 2015, 12:03:26 pm »做个受托人都不能稳定出块，说什么技术牛逼呢？toast代跑的那个实习受托人一开始上来还丢了好多块呢。你说toast牛不牛？
EDIT:
好吧我没注意到这个受托人又在丢块了。
实在无法表达。
4444
Technical Support / Re: blockchain_get_block_signee issue
« on: January 10, 2015, 10:34:21 am »Thanks!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.
4445
Technical Support / Re: Critical Error: An instance of Bitshares is already running! Wallet 4.27.1 Please Advise.
« on: January 10, 2015, 10:19:48 am »Now I'm stuck.Delete this directory 'C:/Users/User/AppData/Roaming/BitShares/peers.leveldb' and retry.
Deleting the LOCK files didn't work (there were 44 of them in total) and because this time it didn't happen while upgrading the client I don't have a recent json wallet backup so I'm a bit wary of flushing the whole thing.
Any advice please?
Running the CLI I get this:Code: [Select]C:\Program Files\BitShares\bin>bitshares_client.exe --rebuild-index
Clearing database index
Loading config from file: C:\Users\AppData\Roaming\BitShares\config.json
Using blockchain checkpoints from file: C:\Users\User\AppData\Roaming\BitShares\checkpoints.json
Tracking Statistics: true
Initializing genesis state from built-in genesis file
Please be patient, this will take a few minutes...
Successfully re-indexed 0 blocks in 1 seconds.
Blockchain size changed from 0MiB to 0MiB.
------------ error --------------
10001 db_in_use_exception: Database in Use
Unable to open database C:/Users/User/AppData/Roaming/BitShares/peers.leveldb
Corruption: error in middle of record
{"db":"C:/Users/User/AppData/Roaming/BitShares/peers.leveldb","msg":"Corruption
: error in middle of record"}
p2p level_pod_map.hpp:62 bts::db::level_pod_map<unsigned int,struct bts::ne
t::potential_peer_record>::open
{"dir":"C:/Users/User/AppData/Roaming/BitShares/peers.leveldb","create":true,"c
ache_size":0}
p2p level_pod_map.hpp:67 bts::db::level_pod_map<unsigned int,struct bts::ne
t::potential_peer_record>::open
It's safe.
Don't delete the LOCK files only.
4446
Technical Support / Re: Block download starts from zero after crash/restart
« on: January 10, 2015, 10:16:11 am »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.
4447
Technical Support / blockchain_get_block_signee issue
« 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.
4448
中文 (Chinese) / Re: 求教bitshares钱包该怎么用
« on: January 09, 2015, 05:08:20 pm »删除还是小心点好。刚创建的钱包需要输入2次一样的密码，这是设置钱包密码，以后你的钱包都需要输入这个密码才能进入
重装了，每次打开，都是解锁界面。让输入密码，然后输入之后软件提示密码错误。
不论选择什么，都是输入密码。。。
那是你之前有设置过密码了，如果钱包里没币的话可以把钱包删了重新创建钱包。
windows开始菜单中选择运行，输入%APPDATA%\BitShares会打开bts钱包目录，如果你确定以前创建的钱包没币的话可以直接把整个BitShares目录删除，再打开客户端。
把目录改个名字就可以了，或者移动到其他盘。以后要是想起密码可以改回来。
4449
中文 (Chinese) / Re: BitShares PLAY分配方案
« on: January 09, 2015, 04:22:13 pm »有个问题想请教下 PLAY给BTS分配份额 是不是意味着按照相应比例减少自己的BTS来换取PLS？不是用bts换取，是白给的。
不过如果play上线导致bts跌价那是另外一回事。。
4450
General Discussion / Re: Block Explorer and Delegates Listing
« on: January 09, 2015, 10:48:27 am »
Interesting.. BTSBOTS's batch market transactions are identified as 'Ask'?
BTW transaction types should include 'cancel an order'.
BTW transaction types should include 'cancel an order'.
4451
Technical Support / 99,003.377 BTS of Trx Fee for a cover operation in Block # 1465854 ?
« on: January 09, 2015, 10:34:23 am »
Here is a complaint about fund lost caused by covering a short order.
https://bitsharestalk.org/index.php?topic=13042.0
Please check this block:
http://bitsharesblocks.com/blocks/block?id=1465854
Looks strange.
https://bitsharestalk.org/index.php?topic=13042.0
Please check this block:
http://bitsharesblocks.com/blocks/block?id=1465854
Looks strange.
Code: [Select]
>>> blockchain_get_block_transactions 1465854
...
"deposits": [[
22,{
"amount": 5504026,
"asset_id": 22
}
]
],
"withdraws": [[
0,{
"amount": 9900337696,
"asset_id": 0
}
],[
22,{
"amount": 5504026,
"asset_id": 22
}
]
],
...
4452
General Discussion / Re: api call error
« on: January 09, 2015, 08:31:53 am »Anyway encoded HTTP post data is a String. You have this in the data:I don't know where it convert price from type float to type stringThe 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.
from the output above, it's still float when I call requests.post()
Code: [Select]
['ask_order', ['fund.btsbots', 11429.350384438114, 'BTS', 1.202899717
9833209e-05, 'GOLD']]
generated by
Code: [Select]
json.dumps(payload)
4453
DAC 委托人 / Re: 【技术交流】钱包启动时自动执行一些命令的一种方法
« on: January 09, 2015, 08:06:14 am »在机器不重启的情况下可以这么做。
密码最好不要写在文件中，VPS硬盘很容易被克隆，简单点的办法是自己把密码设置到环境变量中，在GDB中从环境变量中读出密码
或者，创建一个ramdisk，把主贴所述包含密码的文件写在ramdisk上，这样密码只在内存中，克隆硬盘不会导致密码泄露。
机器重启怎么办？我能想到的两个思路：
1. 采用加密的文件系统来存放敏感数据
2. 使用一台“安全的”电脑来远程监控运行钱包的服务器，需要时，自动远程连接，创建包含密码的文件/设置密码环境变量
4454
DAC 委托人 / 【技术交流】钱包启动时自动执行一些命令的一种方法
« on: January 09, 2015, 07:46:45 am »
受托人运行过程中，可能遇到服务器重启后，需要自动启动钱包。官方wiki上有说明：
http://wiki.bitshares.org/index.php/Bitshares-x-delegate-how-to#Starting_the_client_after_a_reboot_or_crash
第一步，启动钱包
但是实际上，如果是服务器异常重启，是没有机会人工输入上述命令的，这样就会导致丢块。
为了解决这个问题，alt实现了一个用expect脚本来自动输入上述命令的方法，代码见 https://github.com/bitsuperlab/operation_tools/tree/master/restart
其他受托人也有各自的做法。
这里介绍的是另外一种方法：直接使用钱包程序的启动参数和配置文件，来实现启动时自动加载命令执行。
第一步，创建一个文件，比如命名为 startup.input ，内容如下
命令里的参数，包括钱包名，密码，受托人账号等等，请根据自己情况修改。
至于密码写在文件里怎么让别人看不到，这里不详细讨论，有经验的请补充。
第二步，修改启动钱包的命令，在后面添加一个参数
结束。
欢迎打赏或者拍砖
http://wiki.bitshares.org/index.php/Bitshares-x-delegate-how-to#Starting_the_client_after_a_reboot_or_crash
第一步，启动钱包
Code: [Select]
gdb ./bitshares_client --server --httpport 9989 --rpcuser user --rpcpassword pass
第二步，钱包启动后，在钱包的控制台输入下面的命令Code: [Select]
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 ，内容如下
Code: [Select]
>>> 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个大于号加一个空格，后面跟要执行的命令。命令里的参数，包括钱包名，密码，受托人账号等等，请根据自己情况修改。
至于密码写在文件里怎么让别人看不到，这里不详细讨论，有经验的请补充。
第二步，修改启动钱包的命令，在后面添加一个参数
Code: [Select]
gdb ./bitshares_client --server --httpport 9989 --rpcuser user --rpcpassword pass --input-log startup.input
这样，钱包启动时，就会自动加载 startup.input 里的命令了。结束。
欢迎打赏或者拍砖
