lambs to the slaughter 

Yes you are progressing real time for sure, your getting 15000 blocks a day rather than 720, at that rate your your chains going to constantly split IDK how many orphaned chains your wallets need to process, they will use way too much ram and likley you will soon need a rather large server just to run one node of your coin regardless of how many transactions there are.

Don't you get it, you need fix it, if you put your head in the sand and think I'm someone who's out to get you, you are literally speeding your coins blockchain forward towards a cliff edge.

PM me ill be happy to help you debug it if you want.

Really "block bursts feature" lol....
Why would anyone have a such a feature, "our coin has ridiculously unstable block times, your transaction could be confirmed really quickly or take hours you never know how long, block bursts feature, unstable block times the future of the blockchain  "

If you read the code, its obviously a big oversight bug in your re-targeting algorithm. Your difficulty is permanently at the MIN, your not getting 2 min blocks times as advertised.

I mean you could have released a meme coin "easycoin" where the POS difficulty is always minimum and called it "blocks burst feature"... then sure this would be great, but I don't think it would be viable on any exchange due to security issues with such a design, but sure it would be a funny meme coin.

But you have released a 'professional' coin with "2 min block times, 720 blocks a day".

If your going to start calling this a "feature" rather than own up to your mistake and rectify it (maybe you don't know how to fix it?) then your project is doomed, and i mean literally it does not matter what your investors think or anything this bug is going to break the blockchain of your coin, if you even manage to get on exchanges the wallets will be down for maintenance pretty quickly and very frequently until they will have to be removed as the wallet and transactions simply wont be stable.

Sorry, you need to own this bug and then you *need* to fix it (a hard fork is needed I'm sorry) , if you cannot your project will fail, its a technical inevitability of the bug. Fix it or your coin will fail, regardless of how great your promotion is.

https://github.com/HarvestMasternodecoin/Harvestcoin/commit/227855205021a2cae5e3ee04174317d9890756f5

Oh wow they only added checkpoints 23 hours ago.

That means there are no checkpoints in their currently deployed wallets.
An attacker could start a new genesis block, then potentially thanks to the difficultly bug that keeps the difficulty always as the min level they could move their chain longer.

What a mess really, its like this was released without any testing at all.

You may be right.., with the current bug at least until they fix it I'm not sure if they are going to be able to get on exchanges unless they fix it, the block times are too fast maybe 5 and its permanently  stuck at  minimum difficulty seconds the coin will soon start using ridiculous resources, and its very difficult to properly confirm transactions as will become quite prone to chain splits I would say.
Being stuck at min difficulty poses all sorts of security risks, a high difficulty is exactly what is used to "secure" cryptocurrencies. this has a bug where its suck at the least possible difficulty means anyone with a few coins can generate blocks in seconds (and perform any the attacks that that ability allows)

I suggest they should refund everyone. And fix the bug and open their ICO again to show they are legitimate and competent.

Actually because of the bug with the block times

you will notice if you look at the block explorer that the difficulty is seriously low and will never go high

A lot of the time the same wallet can stake block after block because of the super low difficulty.

So an attacker would not need that many coins to stage a 51% attack because once the attacker gets a block you have a huge advantage that they can already work at the next block which takes sometimes less than 1s before other nodes even know you have the block.

So a would be attacker could do a "cheap" 51% attack on this coin with enough coins staking, the bug makes it insecure.

The block times are about 5 seconds average, (not 2 mins as intended) so basically there is something really wrong with the re-targeting algorithm.
Since its concerning block times ( like block sizes) they have to a hard fork (and I guess coin swap) to fix it, they will need to fix it before they can get on any exchanges too as I think the block times are too crazy, and there is a huge risk of orphaned blocks and chain splits at that speed.

Since its block times just like bitcoin with block size issues its a problem with the difficulty re targeting so its part in the consensus. I think they need to do a hard fork to fix it.

Yeah its not cool that they just ban anyone that talks about it from the slack

The 3500% ROI is because blocks were coming in way to fast for that day, they were calling it a "blockspike"

Actually there is a serious bug in the re-targeting algorithm that means block times can be really fast sometimes (and other times really really slow) which is really not good at all.
As its in the targeting algorithm they will need to hard fork (and likely do a coin swap) in order to fix it.

oops!