4456
中文 (Chinese) / Re: bts上运行基金设想及内外盘搬砖基金实验
« on: January 03, 2015, 05:51:57 am »
搬到后来,钱包里都是bitcny,外盘账号里都是bts没有CNY
bitcny打到时代就亏千分之五,找咕噜就亏千分之三周末还不上班。
纠结啊。
bitcny打到时代就亏千分之五,找咕噜就亏千分之三周末还不上班。
纠结啊。
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.
"blockchain_head_block_num": 1247158,
"blockchain_head_block_age": "2 seconds old",
"blockchain_head_block_timestamp": "2014-12-12T19:24:10",
"blockchain_average_delegate_participation": "42.62 %",
We implemented a change in how we check for duplicate transactions. Tested it. It worked.Ah this is the reason. So the 0.4.25 went wrong.
We applied the change to the main network and discovered that there was one transaction that was considered a duplicate under the new system that was processed by the old system.
Vikram disabled duplicate checking until the scheduled fork block so that we could validate the old chain.
Vikram tested syncing up with the old chain and it worked.
Vikram tested producing a block with the upgraded version and it worked.
Announce upgrade.
Delegates started upgrading. Duplicate transaction checking was "disabled" until the specified fork block. Delegates started producing blocks that included duplicate transactions and thus were rejected by the non upgraded clients.
So the testing we needed was "dev share" test net because the bug was is the "handoff / upgrade" code that didn't reveal itself until after we had a chain with multiple delegates running the new code.
In retrospect the issue could have been easily avoided with a little thinking, but we were rushing to get a security fix in.
We are reviewing our options, but the conclusion is clear. DevShares needs to come out as soon as possible because it is the most likely way we would have caught this bug.
v0.4.26 has been released with a checkpoint to address the blockchain fork: https://bitsharestalk.org/index.php?topic=7067.msg161432#msg161432
Delegates and seed nodes should upgrade ASAP.
riverhead-del-server-1 is v0.4.25?My (standby) delegate a.delegate.abit running on v0.4.25-RC1 now..
blockchain_average_delegate_participation 16.64%
is it okay?
Ya. People are slowly switching over.
Downloading.My (standby) delegate a.delegate.abit running on v0.4.25-RC1 now..
blockchain_average_delegate_participation 16.64%
is it okay?
Ya. People are slowly switching over.
0.4.26 is out for delegates and seed nodes. It has checkpoints to resolve the fork and should be compatible with 0.4.24.1 and 0.4.25-RC2 forks of the chain.
All users who haven't upgraded to the pre-release are on the minority fork.Actually all 0.4.24.1 clients are on
All delegates should downgrade to the last (Hot Fix) 0.4.24.1 immediately to rejoin the majority of users and start confirming that network.
0.4.25-RC2 had an intractable issue.
Vikram knows the details. We are working on a new upgrade but want to get the network back to a stable condition for users as soon as possible.
All valid transactions have been applied to both networks.