>>3554605I'm not a dev but I can tell you why "some" adjustments is a bad idea.
Thing is, the stats update DAILY, so one certain point in time where you get new numbers to calculate from. This would mean that if we have 4-6 adjustments daily, that the dudes who knew the first adjustment will know the other 3-5 as well, selling accordingly after the first one and getting back in after the last.
Another approach I would suggest is having the broker sell like a player towards the adjusted price, that way it wouldn't immediately be visible on the graph and trigger min-max responses from players and bots alike. Sure you could spot them if you're lucky but if it's a highly traded coin with buys and sells every cycle nobody would be any wiser. Problem is that some coins like Gura would just moon forever like that because adjustments like in this case could only get so far in a day, 24h*4cycles = a mere $960 on average depending on coin count can be moved. If it's more than one buy/sell every cycle it would get noticed easier.
So it's really about finding a balance. One adjustment is bad because it focusses on ONE point in time everyone has to be awake for to make money. "Some" adjustments is bad because we wouldn't have enough data to make them different. Creeping adjustments wouldn't actually adjust much without getting spotted, but I believe they would at least relieve the problem of the timezones.