Quote from: rav3n_pl on September 23, 2013, 01:39:47 PM

Quote from: PSL on September 23, 2013, 10:11:36 AM

Quote from: rav3n_pl on September 22, 2013, 06:16:42 PM

Bug still present and cause is unknown, but it is "fixed" by https://github.com/terracoin/terracoin/commit/856387e

Was this fix tested? When I check the code, I don't understand it... Is the function GetEmaNextWorkRequired right place for the fix??

Quote from: PSL on September 23, 2013, 11:14:48 AM

Well, it is not a fix but workaround. It is working, blockchain was synchronized till block 190965.

Exactly. This commit allowing affected machines to synchronize w/o any trouble, it also adds additional checkpoint right after "messy" block 137161 to make sure that you are in proper chain.
This is only workaround, not real fix and it is valid only for this block.
If this unknown bug hit again code need be changed again, and again...

except that the EMA thing is not in use anymore, so there's (hopefully) no need to change it again.

i've no time to spend on that, but i'd like to see what previous block somehow borked the ema calculation in the ~2k (?) blocks prior to 137161, and how

I like the alert related changes bring by this release though. I guess alerts will be used to announce the (HOPEFULLY) next major change announced on github issue tracker (shorter retarget window with smaller caps), so the coin returns to a faster block rate.