This will be an optional solution for Gekko, in no way will this be forced upon Gekko's users because nobody can easily check whether the candle data is not messed with.
Thanks for the info whydifficult.... however some of us would still like the option, especially if you decide that it isn't worth hosting one day.Thanks. I am planning on hosting all standard candle intervals (15min, 1h, 4h, 1d, etc.) for all those markets and providing them for free (as long as I can afford it). I could open source it all but storing all the data is not something as small as running a Gekko instance, there is a lot of trade data flowing from all exchanges. Take a look at the mtgox sqlite database for example, it is over 4GB already.
It isn't the standard candles that I am worried about 
Nor am I worried about data storage. However my interest really only expands *if* this data could/would be used by the backtesting system. Who knows what odd candle times might give us. But I guess that depends on how your system works... if it does not store the raw trade data then calculating off-standard candles will be difficult. I see it very much like an electrum server... they are a PIA to setup and take up a lot of space, but some users would like to do that.
That being said.... it is your code and I respect your decision to do with it as you see fit, you have treated us great so far. At the very lease would you consider releasing a bare bones reference implementation so others could do their own implementation?