BitShares Forum
Main => Technical Support => Topic started by: monsterer on June 11, 2015, 08:49:04 am
-
As I understand it, Bitshares 2.0 is a new blockchain, with new private keys for everyone. So, what happens if 51 delegates decide to keep the old blockchain running?
Or, what if all the current delegates move over, but 51 new delegates fall into place on the old chain?
-
that didn't happened even in the merger .
I doubt it would happen now .
-
that didn't happened even in the merger .
I doubt it would happen now .
The merger was the same blockchain, wasn't it?
-
Then there will be bts1.0 and bts2.0 exist at the same time. And own they 101 delegate separate.
Just like altcoin, nothing more.
BTS and PLAY is the same thing.
-
As I understand it, Bitshares 2.0 is a new blockchain, with new private keys for everyone. So, what happens if 51 delegates decide to keep the old blockchain running?
Or, what if all the current delegates move over, but 51 new delegates fall into place on the old chain?
do you think people would refuse to move from crowded apartment to big villa?
-
do you think people would refuse to move from crowded apartment to big villa?
Do you think the coming bitcoin hard fork will lead to two different bitcoin chains?
-
51 new delegates will take their place
-
that didn't happened even in the merger .
I doubt it would happen now .
The merger was the same blockchain, wasn't it?
for different blockchain that's more easy ....because it will be already forked .... the new system can just initiate new block producers like init01..init02...
-
Actually a single delegate would be enough to keep the old chain alive.
This can be mitigated by publishing a 0.9.9 version that stops creating new blocks after the snapshot date, and requiring delegates to upgrade to 0.9.9.
From our experience with the PTS-DPOS upgrade I can say that it is much more important to coordinate the upgrade with all major external entities, like exchanges, block explorers, CMC, ... - if no one is using the old chain anymore then it doesn't matter if someone keeps generating blocks on it.
-
Actually a single delegate would be enough to keep the old chain alive.
This can be mitigated by publishing a 0.9.9 version that stops creating new blocks after the snapshot date, and requiring delegates to upgrade to 0.9.9.
From our experience with the PTS-DPOS upgrade I can say that it is much more important to coordinate the upgrade with all major external entities, like exchanges, block explorers, CMC, ... - if no one is using the old chain anymore then it doesn't matter if someone keeps generating blocks on it.
I didn't catch all the details but I thought I heard BM say this^. That there would be a final release to 'freeze' the old chain.
-
I didn't catch all the details but I thought I heard BM say this^. That there would be a final release to 'freeze' the old chain.
Ahhh, so it relies on everyone upgrading to this final release before 2.0 can launch. Understood...
-
I would have to 'let them go' and vote for others.
I dont think there is a problem here. Move on.