one thing i noticed while browsing the git repo late last night is that the acceptable time drift is ± 24 hours....thats rather HUGE!
whoops, now indeed I'd say that is somewhat lavish... i think, even an hour is rather liberal...
I think a little fine tuning couldn't hurt for a next release...
haven't put hands on any coin related code for a while and never went too deep into the mechanics, so I'm not that save in telling what changes would imply that a hardfork needs to be performed... but my first guess would be that - as it belongs to the accept/reject negotiation kind of parameters - it might again be necessary to make sure all clients are updated... and to avoid that non updated clients don't move along building their own, forked network... which atm seems to hapen almost automatically if no countermeasures are taken
one thing that springs to mind: checkpoints.
I'll definitely need to check out the code and get a look into it... will happen as soon as I'm behind my workstation again, it'd be a bit tedious on this machine, tho...