https://github.com/BitShares/bitshares/releases/tag/bts%2F0.5.0

Please only use this thread to post constructive feedback that may be useful to the development team.

I am 100% committed to taking BitShares to the moon.

• https://github.com/bitsuperlab/bitshares_play
• https://github.com/NameShares/nameshares
• https://github.com/PTS-DPOS/PTS
• https://github.com/sparkle5/Sparkle

Who else?

I do not expect any forks to keep their codebases in sync with our upstream project due to how rapidly we are developing, but it would be good to have a list that we can notify of important security fixes and other important changes.

https://bitsharestalk.org/index.php?topic=7067.msg161312#msg161312

https://bitsharestalk.org/index.php?topic=7067.msg161432#msg161432

All community members please help spread the word.

开发团队请求所有已经升级到0.4.25的受托人请回到0.4.25-RC2:

 

https://github.com/BitShares/bitshares/releases/tag/v0.4.25-RC2

 

还没升级的受托人请保持现状, 暂时不要升级.

 

0.4.25当中对于区块的验证有问题. 所有0.4.25的用户都在主链上, 但是0.4.25-RC2以前的用户位在支链上. 当初只有受托人才被要求升级到0.4.25, 而且GUI版本还没发布--所以一般的持股人是在支链上. 为了将问题降到最低, 我们要求已经升级的受托人回到施前的版本以加入多数持股人.

 

降级会需要重新同步区块链, 因此打开的时候要加上 --resync-blockchain参数

 

已经升级到0.4.25的受托人需要降级到0.4.25-RC2, 因为LevelDB已经升级了, 因此钱包会无法在旧版读取. 或者受托人可以尝试汇出到钱包备份, 并且汇入到0.4.24.1客户端--不过请注意到这个未经测试

 

我跟开发团队全体为这次的不良升级致歉.

 

阅读英文原文: https://bitsharestalk.org/index.php?topic=7067.msg161312#msg161312

原作者: vikram


作者/译者：cn-members

BTS帐号：cn-members

稿源：比特股之家（http://www.bts.hk/0-4-25-delegates-downgrade-to-0-4-25-rc2.html）

This topic has been moved to DAC Delegates.

https://bitsharestalk.org/index.php?topic=6142.0

Are there any Namecoin thin clients that use SPV or something? I would imagine we will eventually want such a thing.

https://en.bitcoin.it/wiki/Thin_Client_Security

http://letstalkbitcoin.com/too-many-coins/

People really don't know about BitShares. Yet another LTB article describing exactly the type of model we have already been using.