Author Topic: What happened at launch of Dynamic  (Read 108 times)

Orestes

  • Global Moderator
  • Newbie
  • *****
  • Posts: 28
  • Karma: +0/-0
    • View Profile
What happened at launch of Dynamic
« on: May 21, 2017, 08:22:00 AM »
What actually happened at launch of Dynamic:

1. Windows memory use buildup caused by threads 2/3/4 of the Argon2d mining algorithm not being cleared correctly.

2. Due to the retarget algorithm not readjusting, but hashrate increasing, around 3 blocks every 10 seconds were being created.

These issues were very quickly rectified and we had to hardfork to implement the DELTA retarget algorithm to correctly space the blocks and Dynode rewards were adjusted to reduce liquidity on the market.

The company and developers didn't benefit from this period as the team was busy working on rectifying the issue and ensuring that the community of users were supported.

Due to the fact that we had public testing groups for Dynamic, months in advance of launch, meant that people had plenty of information on how to build OSX, Linux and Windows binaries from the source, not that they had to as we provided binaries as well for testing.

This is not to say that the launch could of gone smoother, but all in all we survived 5 days of what was a nightmare for the team, with the constant worry of the chain forking and having to do a rollback, which would of meant repaying ICO payments, as well as a plethora of other tasks.

So, all in all, we handled the situation as best we could and ensured the stability of the network and the investment of the users, which is our priority.
Aristotle - 'All paid jobs absorb and degrade the mind.'