There is something fundamentaly wrong with protocol.
While running minimum of 2.5Ghz constantly (meaning that i fluctuate between 25% and 8% of total hash minimum) with average of about 14%, in 12 hours i received only 9 blocks. As for the aim time of 90 seconds fluctuations in difficulty aint that big (i mean even with spikes to 35Ghz of total network I should be able to solve at least by 10 times average slower, lets use statistics), including pos double that. Plus observing "nothing happens for 1 hour then lots of stuff happening in 5 minutes" i dont think that i can be attributed to "it has to equal out etc", the jums are to double, not to infinity, meaning blocks should be solved no?
can it have something to do that we for example find that 1/3rd of solved difficulty blocks are rejected (not orphaned, rejected) without reason? while doing well over difficulty requrements? we are running 1.2.3 client.
I am planning on a semi/pro webgame esport head to head and team based website, that we are secretly working for a long time, with adds only with crypto add site and betting and etc, and i was thinking about first coins to add in there, as a launch, so far we have 3 planned and we were searching for fourth, and were thinking to choose from "lower" ones. Can anyone explain how to include this into schema if people have to wait up for one hour for confirmations? its slower than btc...
Lots of questions, will play here for 48 more hours before deciding, but so far doesnt seem so good, without any prospective and work done from devs or opening it up for public.
Disclaimer: we are looking into coin as it had no premine and was fair start. We will not use any of that premine and secret launch coins...
No need to get so upset. There is nothin malicious in the code. I am currently addressing this problem of "nothing happening for an hour and the 10 blocks coming in" -which is also responsible for the rejected blocks.
I already atempted a fix a while back but I failed and had to revert back.
Another fix is on its way, still on testnet atm, its really hard to replicate this problem on testnet btw, that is why its a pain to solve. Could be out this weekend, but in any case it will be a fork months away because of yobits extremely slow wallet update response time (the last fork was set too soon and it took them more than a month to update the wallet, so this time I will give them more time).
But hang in there, this coin started as a cute gift but it actually developed into something.
But we all know how it is here, everybody wants 1BTC just to start talking to you if you ask for some dev help.
I am still doing everything on my own.
Peace!
