appreciated if could sent me some fund.

XTS393aySU6RQ1sWGJxKX2vMwxbLJwjopVmBpgkREYWYXQvdVZLftsVJhXrMaeyHRg6rdagvrjEUg3hKHr2BM6krSUd2ktqBN

and my node:58.62.197.239, see if anyone can connect to me.

我在想如果ags不能和pts合并，bitshares me可能可以解决这个问题。

I think he means a malicious client stealing private keys. Of course this is a great reason to make AGS liquid.

You can always sign transactions offline and refuse to use a client that doesn't allow you to construct unsigned transactions.

Yes,you got my point of the security issue part,but i am not talking about liquid AGS,just concern for the AGS Security issue.

One thing sure is that more and more DAC will come out in future,but there is a potential security issue that the more times we import the AGS private key to claim the corresponding shares in the DAC,the more risk the private key might be exposed,under the current social contract without AGS Liquid,we even cannot transfer the AGS shares to other address if the private key exposed,is there any consideration or plan to improve the AGS security,please discuss.

Does it work for Windows and Linux？

BM's version should only work on Mac, i build it myself on Win7

will the snapshot be taken as scheduled(end of May)?

Quote from: CrazyBit on May 23, 2014, 05:48:25 pm

review了代码，有个问题不太明白，如何保证产生块的delegate是随机的？现在似乎是从list里随机拿出一个跟自己的id对比，如果match则产生块，不是则跳过，假如我的客户端是custermized的，而我又是delegate,我是否就可以跳过这个 checking直接产生块,如何防止这种情况？

就是 https://bitsharestalk.org/index.php?topic=4164.0 里面提到的算法，每个delegate先publish secret_hash，下一轮reveal secret，由这些secrets哈希值来更新随机数。

之前的实现有一个漏洞，最新的实现每一轮delegate的顺序仍然是随机的，但是只在这一轮开始的时候刷新一下随机顺序，不是随机确定下一个delegate，而是随机确定下一轮delegate顺序。

谢谢解答，但是在块产生代码里我还是没看到你说的实现算法（https://github.com/BitShares/bitshares_toolkit/blob/ab177ba65f4355af9805b4e7451ed9f7dba8a0b7/libraries/client/client.cpp#L70#L104）能否指出具体实现在哪里？