Quote from: Zenith Developer on July 14, 2018, 08:50:39 AM

Quote from: marathonic on July 14, 2018, 08:48:23 AM

Quote from: Zenith Developer on July 14, 2018, 08:42:37 AM

And to say this code is inferior when the old Stipend coin is set to produce infinite blocks but claim a max supply of 19 million is laughable.

else if (pindexBest->nHeight+1 > 840001 && pindexBest->nHeight+1 <= 1890000) {
   // end game - further discussion needed
   nSubsidy = 3 * COIN;
   } else if (pindexBest->nHeight+1 > 1890000) {
   // end game - further discussion needed
   nSubsidy = 3 * COIN;
   nSubsidy >>= ((pindexBest->nHeight + 210000) / 1050000);
   }

There is a mandatory hard fork required in the Stipend code, or it will produce an infinite number of blocks. THIS is unfixed code.

There is a mandatory hard fork also required in the Stipend Zenith code, but much, much sooner (although after your masternodes are sold which is probably all the concerns you). THIS is unfixed code.

When I reveal the issue I'm aware of in your code, you'll see how the Stipend Zenith code issue is much, much more basic - and will cause problems a hell of a lot sooner. I wouldn't expect the issue I'm aware of in a school project, never mind an officially released cryptocurrency.

Personally, I haven't reviewed the Stipend code so cannot comment on the above.

Nope, I've tested all methods in the code PoW is functional, Masternodes are operable, Zercoin tech is working, and PoS functions perfectly. You are Nick and you're mainly upset that I won't tell you how to integrate a blockchain into your site. Which is incredibly simple for any competent developer.

Did you also 'test all methods' prior to the chain come crashing down? Every coin has potential code bugs - you just have to look at the Github of any of the top coins to realize that code fixes are put in place pretty frequently.

It's only the worst developers that claim their code is 100% perfect and don't even try to obtain details of the issue - instead claiming your coin as the first in history that is without potential issue. The unbelievable part is that such a claim was made on day 1 and is still being made after a reset of the chain was required and all miners balances on the previous chain were 'nullified'. I laughed at that comment from you on Discord. It just slid off the tongue as if nullifying the coin balances of all your miners was nothing to be in the slightest bit concerned about.

You consistently call me Nick (I believe one of the Stipend developers). That is not me. There is a big difference between 'obsession' and getting burned in a masternode presale before and wanting to help others avoid the same when you spot a blatantly obvious scamcoin.