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

Pages: 1 ... 281 282 283 284 285 286 287 [288] 289 290 291 292 293 294 295 ... 299
4306
General Discussion / Re: [URGENT] Delegates Please Upgrade to v0.4.26!
« on: December 12, 2014, 08:40:57 pm »
a.delegate.abit upgraded to 0.4.26.

4307
General Discussion / Re: [URGENT] Delegates Please Upgrade to v0.4.26!
« on: December 12, 2014, 07:24:46 pm »
Code: [Select]
  "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 %",

4308
Stakeholder Proposals / Re: What is the Reason For 0.4.25 Forks ?
« on: December 12, 2014, 07:19:53 pm »
We implemented a change in how we check for duplicate transactions.  Tested it.  It worked.
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.
Ah this is the reason. So the 0.4.25 went wrong.
I was wondering why my balance got doubled  :P :P

4309
General Discussion / Re: [URGENT] Delegates Please Revert Upgrade!
« on: December 12, 2014, 06:59:14 pm »
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.
Unable to download the linux binary. Working now.

The windows binary works.

4310
General Discussion / Re: [URGENT] Delegates Please Revert Upgrade!
« on: December 12, 2014, 06:47:06 pm »
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.
riverhead-del-server-1 is v0.4.25?

4311
General Discussion / Re: [URGENT] Delegates Please Revert Upgrade!
« on: December 12, 2014, 06:35:53 pm »
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.
Downloading.

4312
General Discussion / Re: [URGENT] Delegates Please Revert Upgrade!
« on: December 12, 2014, 06:21:36 pm »
My (standby) delegate a.delegate.abit running on v0.4.25-RC1 now..

blockchain_average_delegate_participation 16.64%

is it okay?

4313
中文(Chinese) / Re: [URGENT] Delegates Please Revert Upgrade!
« on: December 12, 2014, 05:20:14 pm »
大意是说:
紧急通知,升级到0.4.25的受托人们,请回退到0.4.25-RC2版本。块链需要重新下载。
    为什么不回退到0.4.24.1?因为0.4.25包含leveldb升级,新数据在老版本(0.4.24.1及之前)里有问题,钱包会打不开。也可以导出钱包私钥到0.4.24.1版本里面导入。
没有升级到0.4.25的不要升级,保持0.4.24.1。

4314
General Discussion / Re: [URGENT] Delegates Please Revert Upgrade!
« on: December 12, 2014, 04:18:52 pm »
I have a backup of the old chain, just need to start it up.
Anyway, I'm totally confused.

4315
All users who haven't upgraded to the pre-release are on the minority fork. 

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.
Actually all 0.4.24.1 clients are on the minority a fork, as well as 0.4.25-RC1 clients.
0.4.25 ones are on another fork..
I don't know 0.4.25-RC2 though.

okay, I am confused.  :-X

4316
DAC 委托人 / Re: BTSX受托人拉票贴
« on: December 12, 2014, 03:26:43 pm »
我也来拉个票 a.delegate.abit 3%的费率

本人技术流,linux系统管理经验5年,懂一点编程。希望能为社区出一份力。

人在上海,跑受托人的机器目前也在上海。

4317
My (standby) delegate a.delegate.abit is running on v0.4.25 now..

"blockchain_average_delegate_participation": "68.71 %"


4318
With 0.4.25 RC2 I seem to be on the fading fork. I am now down to 35 % participation.

Code: [Select]
   FORKED BLOCK              FORKING BLOCK ID              SIGNING DELEGATE      TXN COUNT      SIZE           TIMESTAMP   LATENCY   VALID    IN CURRENT CHAIN
--------------------------------------------------------------------------------------------------------------------------------------------------------------
        1246468
     68b7e003ca08d50843faaddcf696cfff1954ede3         moon.delegate.service              0       166 2014-12-12T09:29:10      1155     YES                 YES
     bf7fe0f13b2fb4e8377d595667156780c6345157                         init0              1      1807 2014-12-12T09:28:50      1179      NO                  NO
REASONS FOR INVALID BLOCKS
bf7fe0f13b2fb4e8377d595667156780c6345157: 30007 duplicate_transaction: duplicate transaction

upgrade to 0.4.25 and delete the "chain" folder (maybe it' not necessary due reindexing?)
It costed me about 20 minutes to download a whole new chain. Not finished yet.. The higher the slower..
How much time is needed for re-indexing? And how much for re-download?
Estimate, compare, then decide ;)

4319
Stakeholder Proposals / Re: Careful when upgrading delegate to 0.4.25
« on: December 12, 2014, 11:48:10 am »
It seems that a fork occurred before expected (<1249400).
All delegates should upgrade. Other users should upgrade as well. Wish the binary releases asap.
@vikram.

4320
Stakeholder Proposals / Re: Careful when upgrading delegate to 0.4.25
« on: December 12, 2014, 07:46:16 am »
EDIT.
Compiling.

Pages: 1 ... 281 282 283 284 285 286 287 [288] 289 290 291 292 293 294 295 ... 299