Main > DAC 委托人

3月受托人新闻

<< < (2/4) > >>

ebit:
 bytemaster

--- Quote ---I work every day from 8:30AM to 7PM along with 5 other developers to make BTS a success and that is just the developers.我和另外5名开发者一起工作，工作时间是早8点半到下午7点。

No one has more to lose from BTS failing than me and when people like wings are upset because they gave money to support a vision that is harder than they thought to achieve. 比特股失败的话，我的损失是最大的。投资者歇斯底里，是因为他们的投资风险超过了自己的承受底限。

If this were a "pump and dump" as wings has claimed then I would have sold when we hit $100M rather than held.   
虽然我们研究的是可预测市场，但波动幅度不是我们所能掌握的。
I am not going to give up and continue to fight and learn.我不会放弃，而是坚持战斗和学习。 
--- End quote ---
https://bitsharestalk.org/index.php?topic=15181.0

ebit:
 theoretical
参与研究0.8.1分叉危机https://bitsharestalk.org/index.php?topic=15218.msg197141#msg197141

ebit:
vikram
解决0.8.1分叉危机https://bitsharestalk.org/index.php?topic=15218.msg197141#msg197141

--- Quote ---I haven't read the rest of the thread but the above is the primary problem, and is common whenever we hardfork because we get long minority chains from delegates who haven't updated.

There is also a second problem where blocks after the hardfork are not necessarily invalid for old clients. So they might upgrade after the hardfork and if they don't reindex, they will have an inconsistent state but cannot tell until they finally start rejecting blocks.

It seems like we can mitigate the most common issues by a combination of:
Force all blocks after a hardfork to be invalid for old clients
Always reindex for hardfork releases
Always release a version with a checkpoint right after the hardfork as soon as possible. And force a reindex on startup if any checkpoints dont match the current state
--- End quote ---

更改数据目录下：checkpiont.json,在头部加入最新区块数据。
linux下，启动时加上 --rebuild-index参数
节点：
addnode 69.90.132.209:1375   delegate.nathanhourt.com at
addnode 85.214.53.224:1375   fubly
addnode 185.25.22.21:1375   liondani
addnode 46.226.109.66:1375   wackou

ebit:
delegate.nathanhourt.com(modprobe)


--- Quote ---You should be able to recover your account on wallet.bitshares.org using your recovery password if the light server fails permanently, but you could also host your own server and edit the javascript in the light wallet to point it to your server as well.

After we get a stable release, I'll look into multi-server modes of operation which should be more fault tolerant.
--- End quote ---
https://bitsharestalk.org/index.php?action=profile;area=showposts;u=8014

ebit:
38PTSWarrior (待命)
在街头积极的散发传单
https://bitsharestalk.org/index.php?topic=11020.105

Navigation

[0] Message Index

[#] Next page

[*] Previous page