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 - abit

Pages: 1 ... 266 267 268 269 270 271 272 [273] 274 275 276 277 278 279 280 ... 309
4082
还是不对,请教下钱包的问题应该从哪儿找答案?bm等就不管吗?
完整报错信息贴上来看看。应该有很多行。
只有一句话不好诊断。

加西部群吧 247971500 。论坛上的人少。

4083
When talking about disk IO bottleneck, we always check I and O (reads and writes) separately. We can't avoid IO, we just reduce the frequency, at lease reduce random accessing.
There are still rooms available for performance optimizing with the use of leveldb, E.G.
* The optional FilterPolicy mechanism can be used to reduce the number of disk reads substantially.
* Using less quantity of level DB's will hopefully reduce competing on writes/compacts.
* Better design of keys (of values)
* Compressing and caching

Anyway, if we've already chosen another way, please go ahead.

4084
中文 (Chinese) / Re: 0.9的钱包真TM费劲
« on: May 25, 2015, 01:43:26 pm »
钱包同步后退,之前同步完成了73%,后来慢慢的只同步完成69%,一直在同步都不够出块快,真是奇琶了!
清风yeah?好像以前见过这个名字

4085
中文 (Chinese) / Re: 0.9的钱包真TM费劲
« on: May 25, 2015, 01:42:42 pm »
钱包同步后退,之前同步完成了73%,后来慢慢的只同步完成69%,一直在同步都不够出块快,真是奇琶了!
卡块了。如果重启不能解决问题的话,删了peers.leveldb目录重试,还不行就是区块数据坏了,删了区块目录重新同步。可以从网盘直接下载替换,不知道地址的话加西部群。

4086
General Discussion / Re: Open letter to the bitUSD bulls
« on: May 07, 2015, 07:57:36 am »
To bitUSD shorters:
with the new rule, although no need to worry about expiration, new short orders will be margin called at 90% of feed price when price of BTS drop to 66.6% (was 50% yesterday).

4087
General Discussion / Re: BitShares Timeline?
« on: May 06, 2015, 04:47:48 am »
The reason is simple: there is no plan. Everything changes too fast. It's nothing to do with a tool.

4088
General Discussion / Re: BitAsset 2.0 Requirements & Implied Design
« on: May 05, 2015, 05:05:19 pm »
A very important question:

Can the shorts use the collateral to cover their orders?

the longs can directly buy BTS, but the shorts can not use their collateral even the collateral is enough.

THIS IS WHAT I FOUND ON NXT FORUM:

"
Within 9 days my position was down near 10%. I decided I would take the loss and exit the trade.

Well, in attempting to close the trade, I kept getting error messages saying I didn't have enough bitUSD to buy back what I shorted.

I thought maybe this was a bug with one of the updated versions. I went to the forums and posted my problem.

To my surprise I was told I was stuck unless I went and bought more BTS and then bought more bitUSD to cover my existing short even though I had enough BTS locked in collateral to buy near 2 times the amount of BTS I had shorted.
"
See this link: https://bitsharestalk.org/index.php/topic,13782.0/all.html
and this issue: https://github.com/BitShares/bitshares/issues/1499

4089
General Discussion / BitGold.com launched.
« on: May 05, 2015, 02:50:28 am »

4090
General Discussion / Re: BitAsset 2.0 Requirements & Implied Design
« on: May 05, 2015, 12:12:34 am »
tl;dr
HOW to guarantee that each bitUSD could be changed back to one-USD-worth of BTS in a black swan event, especially when there is a daily % set?

Black swan has BitUSD converted to BTS... no more guarantee.
If there is no such guarantee, it means BitUSD is NOT fully backed. When a black swan come, the last one who holds BitUSD will be unable to convert to BTS, because there would be no cover order exists on the market. On other words, in this case one BitUSD doesn't worth one USD. It doesn't make sense to set a hard-coded price floor.

4091
General Discussion / Re: BitAsset 2.0 Requirements & Implied Design
« on: May 04, 2015, 05:11:15 pm »
tl;dr
HOW to guarantee that each bitUSD could be changed back to one-USD-worth of BTS in a black swan event, especially when there is a daily % set?

4092
General Discussion / Re: BitAssets 2.0 (formally 3.0)
« on: May 04, 2015, 03:42:11 pm »
HOW to guarantee that each bitUSD could be changed back to one-USD-worth of BTS in a black swan event, especially when there is a daily % set?

4093
Here's an update:

1) Created a new wallet
2) imported 4 private keys: three TITAN and one non-TITAN
3) imported a bitcoin wallet to one of the TITAN keys
4) rescan blockchain (worked fine)
5) Checking balance, the TITAN balances are good, but the non-TITAN account is not.
6) checking wallet_account_transaction history for the non-TITAN account: only the account registration shows up, no other transactions
7) repair wallet (worked fine)
8) regenerate 10500 keys for the non-TITAN account <-- SEGFAULTS
9) backtrace is the same as before

is something up with the non-TITAN account, perhaps?
I can try a wallet with just the non-TITAN account
I believe that it's no need to regenerate keys for non-TITAN account..
We'd better disable it.

4094
中文 (Chinese) / Re: ubuntu 14.04编译轻钱包教程
« on: April 27, 2015, 06:14:14 am »
git submodule init && git submodule update
新版本里这句要改成
Code: [Select]
git submodule update --init --recursive
不然缺少websocket模块编译不了。

4095
讨论:

如果开通bts交易对,则期货市场会和bts现货市场互相影响。
好处是促进bts本身的价值发现;bts交易对本身有一定市场深度,期货市场可能会发展较好
坏处是如果有人恶意控盘,可能导致系统风险,需定义完善规则

如果不开通bts交易对,则期货市场不会对bts现货价格带来影响
好处是系统稳定;如果市场深度大,会增加bta的使用需求
坏处是初期非BTS交易对市场缺少深度,可能发展缓慢,交易量少,对系统促进作用有限

Pages: 1 ... 266 267 268 269 270 271 272 [273] 274 275 276 277 278 279 280 ... 309