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

Pages: 1 ... 7 8 9 10 11 12 13 [14] 15 16 17 18 19 20 21 ... 59
196
General Discussion / Re: Wallet Not Synching
« on: August 26, 2014, 10:23:43 pm »
I have the same problem. It doesn't work.

In the console : "blockchain_head_block_age": "5 days old"

I have the latest wallet 0.4.8

I tried to uninstall and reinstall, it's still the same.

Some help plz  :D ?

Do you have connections and what your last block?

Can you try "debug_list_errors" in your console?

197
I had same problem but resolved it by deleting everything including blockchain files and then reinstall the client.

If you have connections but no syncing, we suggest to do it this way to resolve it temporarily for now.

If now connections, might be you can try add node.

198
中文 (Chinese) / 客户端0.4.8-b问题收集帖
« on: August 26, 2014, 08:44:59 pm »
请把你遇到的问题写出来,比如
1. 没有连接
2. 无法同步
3. Crash客户端崩溃
其他等等,请把系统和版本描述清楚,如果有抛错也请贴出来。

199
Technical Support / Re: Help, balance is not showing
« on: August 25, 2014, 08:50:53 pm »
Which version are you using?

200
 +5%

201
试一下0.4.7,之前两个版本有一个相关的BUG

202
Try backup your wallet, and re-sync again. There is a known bug about this.

203
BitShares Play(PLAY) is an experiment which should demonstrate and validate how a decentralized, autonomous, and game assets platform is worksing. This is a platform is not only built-in with different provable fair chance games, but also has the ability to integrate with all kinds of third party games and have their within asset system in Bitshares Play PLAY's asset system (CHIP). The Shares of Play(PLS), combined with all the assets in built-in games assets and third party games, form a free marketplace and exchange. Systems like this are also known as Decentralized Autonomous Companies (DAC).
The basic idea of a games asset platform is that there is an inner exchange model on the platform. Each game asset in PLAY is part of the "Contract with the system", which means assets are backed by PLS as collateral. Game assets can be issued by providing PLAY shares as collateral, or be destroyed by covering collateral. The ratio price of issue and destroy is determined by the current total supply and current collateral. So the total supply mechanism of game assets is also part of the contract with the system, for built-in chance games, the total supply changing rules is part of the DAC consensus.(I think you need define "the contract" at once, not using "also part of the contract")
Chance games have come to rely almost exclusively on trusted third parties to provide random feeds. While this system works well enough, it still suffers not only from centralized trust based models, but also from the possibility of cheating by players. Even though some crypto based games on the Internet have provably random feeds which can be verified by the public, hidden players still can can still cheat by submitting selective favorable transactions because they know the random secret in advance. Thus players are forced to trust that the game operator is scrupulous. This will forced trust reduces demand and fun, and prevents those who simply do not want to trust the operator from playing the game.
BitShares PlayPLAY's game assets(CHIP) is are not limited to built-in games and third party games, even.Centralized games can also use using PLAY as the economic system of the their game as soon as they can provide a contract which matches the requirement of PLAY's game assets inner exchange. This contract could be a consensus inside or between DACs, or a smart contract between a DAC and non-decentralized games. This could be achieved by smart contracts technologies like smart oracles or Orisi.
2.0 System Tokens


My two cents on the intro. Because of the plurality of things, saying Bitshares Play's just sounds weird. After you introduce Bitshares Play as PLAY, it should always be referred to as PLAY without Bitshares attached. That way you can make it plural without sounding strange. You also introduced (PLS) as the symbol. You have now given it three different names: Bitshares Play, PLAY, and PLS. I know PLS refers to the shares, but it does cloud the interpretation some.

Also, you need to introduce CHIP as the symbol of the assets the first time. Not after you have mention the BitShares Play Game Assets multiple times. That is why I crossed it out. ****on second thought, leave CHIP out all together. It feels unnecessary. Let me know if you are interested in my edits and I will proof more.


Hi, thanks, you suggestions are very good, agree with you.
Please comment directly on the original google document, it's more efficient.

204
中文 (Chinese) / Re: 请问还有哪些DAC将要发布?
« on: August 24, 2014, 05:51:46 am »
BitShares Play 估计会在1-3个月内Snapshot。

205
中文 (Chinese) / Re: BTSX最终幻想!能实现几步?
« on: August 23, 2014, 05:47:07 am »
6 3I公司被知名IT企业收购如微软 谷歌 苹果 脸书等,或3I公司登录纳斯达克上市成功(对价格影响极大)

 :o

206
Technical Support / Re: BitSharesX 0.4.5 Wallet Crash Windows 7
« on: August 23, 2014, 12:14:42 am »
idk, I am having same problem syncing the last two days' data, stuck at block #275164 ... is the network under attack?

Please try 0.4.6, you may need to wipe your chain data, before that, backup your wallet.

207
中文 (Chinese) / Re: 关于 BitUSD
« on: August 22, 2014, 11:46:50 pm »
Quote
DPOS是钢,BTSX是剑;就算发明剑失败了,炼钢的技术还在就还可以打造出刀、叉、戟
+5%

208
Hm .. just wanted to go over your equations again to try to understand them and now they are gone .. did you remove the whole part in the whitepaper?

I moved the CNS part to another document, and give a link to it as it is not so important for the idea of this white paper.
https://docs.google.com/document/d/1rAxpIK_gD-UbA2OKUq5IxAzykIKjphM5BoUnLs9tSls/edit?usp=drive_web

And beside, I do some re-organize , but most of them should still be there.

209
My delegate CLI crashed.  Missed three blocks.


What can I provide log file was to determine why?


From syslog

Code: [Select]
Aug 21 23:18:30 riverhead-del-server kernel: [110780.687870] bitshares_clien[6724]: segfault at 238 ip 000000000066cec6 sp 00007f58a4222a00 error 4 in bitshares_client[400000+1238000]

Please run it in gdb,

Code: [Select]
gdb ./bitshares_client
run --data-dir=delegate

type "bt" to get the back trace.
Code: [Select]
bt

210
Technical Support / Re: Bitshares X 0.4.5 available
« on: August 22, 2014, 01:37:47 am »
RPC Server Error: In method 'wallet_transfer': AES error (18)

I also have transactions that have been pending forever?

Try rescan, It may indicates that the wallet is in a dirty state that miss the cached key for your balance.

Did you have crash issues before?

yes
You'll be fine after do
Code: [Select]
scan 0 in console, the keys will be back.

Pages: 1 ... 7 8 9 10 11 12 13 [14] 15 16 17 18 19 20 21 ... 59