Are DVS Inits OK ?

[emski]

I think all major commits should have separate tag. Especially these that fork the network.
Updating from master should be discouraged.
This is for easier issue identification.

All official releases will have tags and I will announce them. You can run other code but it will not be supported. Toast controls 51% so he can do what he wants.

Of course he can do whatever he wants. However currently the test network is unusable unless you update from master (which is not supported as you said). I just suggest to tag a forking commit in a timely manner. It doesn't need to be an "official" release , perhaps something like 0.6.1.FeatureXTest.

[vikram]

I think all major commits should have separate tag. Especially these that fork the network.
Updating from master should be discouraged.
This is for easier issue identification.

All official releases will have tags and I will announce them. You can run other code but it will not be supported. Toast controls 51% so he can do what he wants.

[emski]

I think all major commits should have separate tag. Especially these that fork the network.
Updating from master should be discouraged.
This is for easier issue identification.

[davidpbrown]

Getting back on the main branch from a fork, is beyond what I understand and I expect then this below is a bad idea..

I wondered seeing this commit detail with checkpoint updated
https://github.com/BitShares/bitshares/commit/be5f2eada1280b0177bd657190482b2e3b1d08a1

if there was a way to resolve forks manually, from bitsharesblocks detail at
http://dvs.bitsharesblocks.com/blocks/block?id=173585
expecting that will usually suggest the main branch and then the hash that could be used as a checkpoint.. but then those hashs don't obviously match the detail in the commit for block 173585


I tried a few changes include recompiling from https://github.com/BitShares/DevShares and resetting peer database and manually changing the checkpoints to match that commit.. but still I see ~ "14.43 %"

I guess I'm missing something as I couldn't obviously get back on the main branch. Perhaps that is only possible, if someone on the  main branch declares a checkpoint?.. or obviously we wait for the next update, which is always easier.

[vikram]

Was doing testing of new features and fixed a bug causing a fork; you can try pulling latest devshares branch if you want to get the fix, or wait until next release 0.6.2 soon.

[emski]

well *my* chain has 77% participation!

You need to update:  https://github.com/BitShares/bitshares/commits/devshares

newer than 0.6.1?
updating to master doesn't look like a good idea...

[toast]

well *my* chain has 77% participation!

You need to update:  https://github.com/BitShares/bitshares/commits/devshares

[emski]

It looks I'm on a fork (or all inits are offline):

Code: [Select]

"blockchain_head_block_num": 173107,
  "blockchain_head_block_age": "29 seconds old",
  "blockchain_head_block_timestamp": "2015-01-27T01:18:00",
  "blockchain_average_delegate_participation": "25.19 %",
  "blockchain_confirmation_requirement": 303,
  "blockchain_share_supply": "2,533,570,172.45915 DVS",
  "blockchain_blocks_left_in_round": 7,
  "blockchain_next_round_time": "at least 61 seconds in the future",
  "blockchain_next_round_timestamp": "2015-01-27T01:19:30",
  "blockchain_random_seed": "c080c02c693c5dc846f1b3aea0acf6b34b1b396a",
  "client_data_dir": "/home/emski/devsharesAltExperimental/DevShares/programs/client/dd",
  "client_version": "0.6.1",


Code: [Select]

173104  2015-01-27T01:13:40 del1.xeldal                     0       166     0       0                0000000000000000000000000000000000000000
MISSED  2015-01-27T01:13:30 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-27T01:13:20 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-27T01:13:10 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-27T01:13:00 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-27T01:12:50 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-27T01:12:40 ?                               N/A     N/A     N/A     N/A              N/A
173103  2015-01-27T01:12:30 zz                              0       166     0       0                0000000000000000000000000000000000000000
173102  2015-01-27T01:12:20 wackou                          0       166     0       0                0000000000000000000000000000000000000000
MISSED  2015-01-27T01:12:10 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-27T01:12:00 ?                               N/A     N/A     N/A     N/A              N/A
173101  2015-01-27T01:11:50 emski                           0       166     0       0                0000000000000000000000000000000000000000
MISSED  2015-01-27T01:11:40 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-27T01:11:30 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-27T01:11:20 ?                               N/A     N/A     N/A     N/A              N/A
173100  2015-01-27T01:11:10 iz                              0       166     0       0                0000000000000000000000000000000000000000
173099  2015-01-27T01:11:00 elmato                          0       166     0       0                0000000000000000000000000000000000000000
MISSED  2015-01-27T01:10:50 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-27T01:10:40 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-27T01:10:30 ?                               N/A     N/A     N/A     N/A              N/A