Author Topic: What is the Reason For 0.4.25 Forks ?  (Read 8442 times)

0 Members and 1 Guest are viewing this topic.

Offline emski

  • Hero Member
  • *****
  • Posts: 1282
    • View Profile
    • http://lnkd.in/nPbhxG
The questions in OP are not answered.
Consider this a bump.

Offline vikram

« Last Edit: December 12, 2014, 06:44:17 pm by vikram »

Offline arhag

  • Hero Member
  • *****
  • Posts: 1214
    • View Profile
    • My posts on Steem
  • BitShares: arhag
  • GitHub: arhag
At least the VOTE presentation went well...

yeh, but these kinds of mistakes can reallllly shake confidence in the whole system.

So can stolen funds...

But yeah, upgrade procedures/protocols should improve and I am sure will be more refined over time as everyone learns from these sorts of experiences.

Offline Empirical1.1

  • Hero Member
  • *****
  • Posts: 886
    • View Profile
At least the VOTE presentation went well...

yeh, but these kinds of mistakes can reallllly shake confidence in the whole system.

 +5% Absolutely, I was being sarcastic.

Offline fuzzy

At least the VOTE presentation went well...

yeh, but these kinds of mistakes can reallllly shake confidence in the whole system. 
WhaleShares==DKP; BitShares is our Community! 
ShareBits and WhaleShares = Love :D

Offline Empirical1.1

  • Hero Member
  • *****
  • Posts: 886
    • View Profile
At least the VOTE presentation went well...

Offline emski

  • Hero Member
  • *****
  • Posts: 1282
    • View Profile
    • http://lnkd.in/nPbhxG
We have seen 0.4.24 and 0.4.25 forked before the predefined block.
Am I correct that this could be identified before release with (simple) testing ?
What procedures were followed prior 0.4.25 release ?

Main questions:
Why we have forking 0.4.24 and 0.4.25 before block 1249400 ?
Wasn't this relatively easy to prevent ?