Quote from: Cassey on September 22, 2016, 09:56:06 PM

Quote from: no-ice-please on September 22, 2016, 07:56:21 PM

Quote from: Chris Sokolowski on September 12, 2016, 03:33:40 AM

Quote from: no-ice-please on September 12, 2016, 03:13:58 AM

33 days without a block mined, that means a person can buy up the exchange and nobody can send coins to sell. People should be cautious if this problem is not fixed, wonder if maybe it is deliberate. I still have a lot of 1credit, and support it, but 33 days without a block is not a credible cryptocurrency. https://chainz.cryptoid.info/1cr/

33 days

Technically, the coin isn't broken. The problem is that the difficulty is currently 344,503, and therefore no one wants to mine it. You could say the difficulty adjustment algorithm is broken, but there's nothing preventing someone from throwing hashrate at 1CRedit to advance the block chain.

I wanted to correct myself. I checked and the current difficulty is 97.51098505. For some reason my pool is reporting it incorrectly. I am looking into the issue right now.

Your post was dated Sept 12th and there had been no blocks produced in the previous 30 some days, or so it seemed.

Now suddenly we have blocks from one day before, like https://chainz.cryptoid.info/1cr/block.dws?56250.htm
and 2 days before, like https://chainz.cryptoid.info/1cr/block.dws?56099.htm
and 3 days before, like https://chainz.cryptoid.info/1cr/block.dws?55936.htm

In fact every day going back to Aug 3rd there are now blocks showing as having existed Huh

I think someone orchistrated the long outage: threw a ton of asic at it to boost the difficulty, then went private for a month or so, then rejoined the network. I noticed the block count jumped ~6000 blocks within a day of the long block being found. I would have anticipated a quick 1024, since that is the depth of the KGW, but not the extra 5000. Of course, once they joined, their own breaker block would register on the chain as valid and they could flood all the private blocks they wanted. The ~6000 is about right for the period we were offline.

I have NO idea how to block against this abuse of power. Very VERY depressed by it - enough to want to say "Enough" and shut things down.

It is not just an "abuse of power".

Somebody convinced part of the network, like Chris, that there was an outrageous difficulty, e.g. 344,503 but other parts of the network did not seem to notice

Quote from: Cassey on September 12, 2016, 05:13:37 PM

For sake of conversation: if the difficulty has jumped from 97.5 to the previously reported 344,503, the only cure is a hard fork after some code work.

I should note that the current difficulty adjustment algo is based on the Kimoto Gravity Well with the Time Warp fix, and uses the last 1024 blocks in its computation.

Per my logs:

2016-08-09 23:28:05 received block 37c2825a528f103cdc5e3fac26ce77a3588f4d572a69ad3a387f3305bee0e2ff
2016-08-09 23:28:05 Difficulty Retarget - Kimoto Gravity Well TW
2016-08-09 23:28:05 PastRateAdjustmentRatio = 1.0484
2016-08-09 23:28:05 Before: 1c02a67a 0000000002a67a00000000000000000000000000000000000000000000000000
2016-08-09 23:28:05 After: 1c02a014 0000000002a014dbc3c543fadb829c672b0f9209df55da10db29383c0f4cf699
2016-08-09 23:28:06 Committing 1 changed transactions to coin database...
2016-08-09 23:28:06 SetBestChain: new best=37c2825a528f103cdc5e3fac26ce77a3588f4d572a69ad3a387f3305bee0e2ff height=50895 log2_work=51.204357 tx=61080 date=2016-08-09 13:07:37 progress=0.998413
2016-08-09 23:28:06 ProcessBlock: ACCEPTED

So in theory, the next block should only be about 5% harder to find than the current block, which had a difficulty of 97.5, so the current block difficulty should be around 102.2. Of course, that was based on a net hashrate of 845MH/s and the devs only have about 26MH/s of ASICs to throw at it. Given that, I would have expected to find a block "On Average" in about 5 hours, not 30+ days.

Is there an exploit to KGW w/TW that yielded the previously mentioned difficulty of 344,503?

We have been running with KGW w/TW using 1024 blocks since block 16175... (check the source on github to verify)

Basically need suggestions and curious what the appetite for doing a hard fork is. Please, constructive replies only...

then

Quote from: Cassey on September 13, 2016, 01:07:35 AM

Quote from: Chris Sokolowski on September 12, 2016, 11:52:14 PM

I wanted to correct myself. I checked and the current difficulty is 97.51098505. For some reason my pool is reporting it incorrectly. I am looking into the issue right now.

Thanks for looking, and posting the correction. You had us scratching our heads for a bit.

Our pool shows a pretty consistant difficultly around that number.