Too many missed and forked blocks due to new wallet

[emski]

It costed me about 20 minutes to download a whole new chain.
How much time is needed for re-indexing?
Estimate, compare, then decide

Depends on network and CPU power. I got re-indexing for 10 minutes. However downloading the new chain might still be faster for me as I have a seed node locally.

[abit]

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

[spartako]

  "blockchain_confirmation_requirement": 99

99 confirms, but a block ain't one

Thanks! now I understand because are PENDING

[monsterer]

The only strange thing it is that I obtain PENDING for all transaction that I do:

Code: [Select]

2014-12-12T10:24:24 PENDING   spartako            spartako            0.00000 BTS             publish version v0.4.25                     0.10000 BTS         688498dc
2014-12-12T10:24:26 PENDING   spartako            spartako            0.00000 BTS             publish version v0.4.25                     0.10000 BTS         6cf54335
2014-12-12T10:33:47 PENDING   spartako            spartako            0.00000 BTS             publish version v0.4.25                     0.10000 BTS         714201f0
2014-12-12T10:40:19 PENDING   spartako1           spartako1           0.00000 BTS             publish price feeds                         0.10000 BTS         3715b4c5
2014-12-12T10:40:19 PENDING   spartako            spartako            0.00000 BTS             publish price feeds                         0.10000 BTS         3ed51614
2014-12-12T10:40:19 PENDING   spartako2           spartako2           0.00000 BTS             publish price feeds                         0.10000 BTS         8e29fc31

Anyway when it was my delegate turn these transactions were put in the block that I signed so actually are no more PENDING

  "blockchain_confirmation_requirement": 99

99 confirms, but a block ain't one

[spartako]

I have just updated my three delegates: spartako,spartako1,spartako2

I'm the right fork now:

Code: [Select]

default (unlocked) >>> getinfo
{
  "blockchain_head_block_num": 1246771,
  "blockchain_head_block_age": "6 seconds old",
  "blockchain_head_block_timestamp": "2014-12-12T10:52:20",
  "blockchain_average_delegate_participation": "64.33 %",
  "blockchain_confirmation_requirement": 99,
  "blockchain_share_supply": "2,498,305,678.95240 BTS",
  "blockchain_blocks_left_in_round": 74,
  "blockchain_next_round_time": "at least 12 minutes in the future",
  "blockchain_next_round_timestamp": "2014-12-12T11:04:40",
  "blockchain_random_seed": "95d3ca3374f0abc728e4ff1c9b9094cbd5f58a7e",
  "client_data_dir": "/home/spartako/.BitShares",
  "client_version": "v0.4.25",
  "network_num_connections": 21,
  "network_num_connections_max": 200,
  "network_chain_downloader_running": false,
  "network_chain_downloader_blocks_remaining": null,
  "ntp_time": "2014-12-12T10:52:26",
  "ntp_time_error": 0.00060700000000000001,
  "wallet_open": true,
  "wallet_unlocked": true,
  "wallet_unlocked_until": "17 weeks in the future",
  "wallet_unlocked_until_timestamp": "2015-04-07T04:15:13",
  "wallet_last_scanned_block_timestamp": "2014-07-24T09:23:30",
  "wallet_scan_progress": "? %",
  "wallet_block_production_enabled": true,
  "wallet_next_block_production_time": "5 minutes in the future",
  "wallet_next_block_production_timestamp": "2014-12-12T10:57:20"
}

The only strange thing it is that I obtain PENDING for all transaction that I do:

Code: [Select]

2014-12-12T10:24:24 PENDING   spartako            spartako            0.00000 BTS             publish version v0.4.25                     0.10000 BTS         688498dc
2014-12-12T10:24:26 PENDING   spartako            spartako            0.00000 BTS             publish version v0.4.25                     0.10000 BTS         6cf54335
2014-12-12T10:33:47 PENDING   spartako            spartako            0.00000 BTS             publish version v0.4.25                     0.10000 BTS         714201f0
2014-12-12T10:40:19 PENDING   spartako1           spartako1           0.00000 BTS             publish price feeds                         0.10000 BTS         3715b4c5
2014-12-12T10:40:19 PENDING   spartako            spartako            0.00000 BTS             publish price feeds                         0.10000 BTS         3ed51614
2014-12-12T10:40:19 PENDING   spartako2           spartako2           0.00000 BTS             publish price feeds                         0.10000 BTS         8e29fc31

Anyway when it was my delegate turn these transactions were put in the block that I signed so actually are no more PENDING

[Markus]

It might be useful to have the .dmg and .exe for 0.4.25 on GitHub for those who can't compile themselves.

[liondani]

If you are on the list please upgrade to v0.4.25  !!!

https://github.com/BitShares/bitshares/releases
https://github.com/BitShares/bitshares/blob/master/BUILD_UBUNTU.md



1246748    
bm.payroll.riverhead
ak
1246745    
delegate-alt
1246742    
delegate-watchman
c.delegate.charity
www2.minebitshares-com
sun.delegate.service
1246739    
delegated-proof-of-steak
1246738    
delegate.bitsuperlab
1246734    
skyscraperfarms
delegate.charity
1246733    
delegate1.john-galt
1246732    
delegate.xeroc
1246729    
delegate.follow-my-vote
dele-puppy
1246726    
dev0.nikolai
1246725    
moon.delegate.service
1246724    
dev-metaexchange.monsterer
1246720    
a.delegate.charity
1246719    
delegate-baozi
1246717    
fox
1246714    
delegate.nathanhourt.com
1246708    
delegate.liondani
1246703    
marketing.methodx
maqifrnswa
delegate.cgafeng
bitcoiners
1246702    
delegate.webber
1246699    
ggozzo.skyscraperfarms
www.minebitshares-com
1246692    
delegate.baozi
delegate.taolje
1246691    
bm.payroll.riverhead
ak
1246688    
delegate.btsnow
1246687    
delegate1.maqifrnswa
1246682    
delegate-alt
1246681    
bits
delegate1-galt
wackou-delegate
1246678    
delegate-watchman
c.delegate.charity
www2.minebitshares-com
sun.delegate.service
1246675    
delegated-proof-of-steak
1246674    
spartako2
delegate.bitsuperlab
1246671    
skyscraperfarms
delegate.charity
1246670    
delegate1.john-galt
1246669    
delegate.xeroc
1246666    
delegate.follow-my-vote
dele-puppy
1246663    
dev0.nikolai
1246662    
moon.delegate.service
1246661    
dev-metaexchange.monsterer
1246657    
a.delegate.charity
1246656    
delegate-baozi
1246655    
fox
spartako1
1246652    
delegate.nathanhourt.com
1246646    
delegate.liondani
1246643    
delegate-alt
1246639    
delegate.baozi
www2.minebitshares-com
1246634    
delegate.follow-my-vote
1246631    
delegate.cgafeng
marketing.methodx
1246630    
c.delegate.charity
ggozzo.skyscraperfarms
dev0.nikolai
1246629    
moon.delegate.service
1246628    
dev-metaexchange.monsterer
delegate-baozi
1246627    
a.delegate.charity
delegate.webber
1246621    
delegate.bitsuperlab
delegate.btsnow
wackou-delega

[liondani]

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?)

[Markus]

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

[svk]

Bitsharesblocks is back up running v0.4.25. Missed blocks don't seem to be updating correctly however, I'm investigating.

I found the reason, was on my backend, missed blocks are now updating correctly.

[arhag]

0.4.25 and 0.4.24 clients report different missed blocks.
And it seems the blockchain is different for my 2 instances.
I'll investigate further.

Yes. Even that the updgrade should've been scheduled for the future the upgrade caused forks between 0.4.24 and 0.4.25.
When I've upgraded I got on a different chain.

Yup, this appears to be the case. I'm guess the changes made to 0.4.25 did not appropriately guard all hard forking changes with "if (get_head_block_num()  >= FORK_25)" conditions, which would effectively make the hard fork happen for each client as soon as it was updated to v0.4.25 and connected to the network.

Certainly code like this

Code: [Select]

...
#define BTS_V0_4_25_FORK_BLOCK_NUM  99999999
#define BTS_V0_4_26_FORK_BLOCK_NUM  99999999
#define BTS_V0_4_27_FORK_BLOCK_NUM  99999999

#define BTS_CHECK_CANONICAL_SIGNATURE_FORK_BLOCK_NUM BTS_V0_4_25_FORK_BLOCK_NUM

#define FORK_25 1249400 // FIXME
...
doesn't inspire much confidence that the forking code was worked out properly before release.


While delegates on v0.4.25 were a minority, they would appear to be the bad actors on a fork. After enough delegates (at least 51) switched to v0.4.25, everyone else became the minority on the wrong fork. At this point at least 55 delegates have switched, so the hard fork has basically already happened before the intended block (well not completely, some important code is still not activated until block 1249400). Everyone else not on v0.4.25 should just upgrade as soon as they can to not miss out on too many blocks.

[monsterer]

we need to upgrade!
https://bitsharestalk.org/index.php?topic=12194.msg161167;topicseen#msg161167

It's not clear whether that upgrade is the cause of all these problems, though.

[liondani]

Restarting my client didn't help. I am slowly dropping though, 39 % now.

Restarting my client didn't help. I am slowly dropping though, 39 % now.

I'm not doing anything until we get some clear advice on the correct course of action from the powers that be.

we need to upgrade!
https://bitsharestalk.org/index.php?topic=12194.msg161167;topicseen#msg161167

[svk]

Bitsharesblocks is back up running v0.4.25. Missed blocks don't seem to be updating correctly however, I'm investigating.

[monsterer]

Restarting my client didn't help. I am slowly dropping though, 39 % now.

I'm not doing anything until we get some clear advice on the correct course of action from the powers that be.