Maxcoin fans might find this interesting:
https://bitcointalksearch.org/topic/m.8494357
Topic: [ANN][MAX] MAXcoin - PoW, ASIC Resistance, Keccak GPU Mining - page 44. (Read 914218 times)
September 23, 2014, 01:37:50 PM
September 23, 2014, 10:59:27 AM
The networkhashps is around 1T, why difficulty can be several million? Obviously the retarget algorithm have bug, it must be more smooth.
September 23, 2014, 05:11:34 AM
where is old good MaxCoin? 
Look what is happening. It will never back to previous glory. It is sad i liked this coin.
September 23, 2014, 04:12:29 AM
Block chain up and running again. 
September 23, 2014, 03:19:25 AM
where is old good MaxCoin?
Look what is happening. It will never back to previous glory. It is sad i liked this coin. September 23, 2014, 02:48:43 AM
The problem is not easy to solve. Best to just wait a bit.
September 23, 2014, 02:29:10 AM
Too irresponsible..
September 23, 2014, 01:53:37 AM
Is this on time wrap attack?
Screnn shot: http://prntscr.com/4pgp6z
At this time, the difficulty was over 60K.
So weird.
http://www.coinssource.com/kimoto-gravity-well-exploit-exposed/
Time Warp Exploit, basically takes advantage of KGW’s method for difficulty retargeting, allowing an attacker with sufficient hashing power to mine at a much lower difficulty level. If such an attack occurred, the attacker would be able to mine all of the blocks at an artificially low difficulty while the blockchain would appear frozen or stuck to the rest of the miners. Then once the attacker released the block chain it would take a long time for the miners to re-synchronize with the blockchain and to validate the attacker’s blocks.
Please change re-target algorithm. KGW is not enough.
Screnn shot: http://prntscr.com/4pgp6z
At this time, the difficulty was over 60K.
So weird.
http://www.coinssource.com/kimoto-gravity-well-exploit-exposed/
Time Warp Exploit, basically takes advantage of KGW’s method for difficulty retargeting, allowing an attacker with sufficient hashing power to mine at a much lower difficulty level. If such an attack occurred, the attacker would be able to mine all of the blocks at an artificially low difficulty while the blockchain would appear frozen or stuck to the rest of the miners. Then once the attacker released the block chain it would take a long time for the miners to re-synchronize with the blockchain and to validate the attacker’s blocks.
Please change re-target algorithm. KGW is not enough.
The blockchain seems to be stuck again at #639064.
In cgminer screen, the difficulty is 4.67M.
September 23, 2014, 01:07:26 AM
Well, good way to stop inflation in its tracks. haha.
September 23, 2014, 12:56:32 AM
Is this on time wrap attack?
Screnn shot: http://prntscr.com/4pgp6z
At this time, the difficulty was over 60K.
So weird.
http://www.coinssource.com/kimoto-gravity-well-exploit-exposed/
Time Warp Exploit, basically takes advantage of KGW’s method for difficulty retargeting, allowing an attacker with sufficient hashing power to mine at a much lower difficulty level. If such an attack occurred, the attacker would be able to mine all of the blocks at an artificially low difficulty while the blockchain would appear frozen or stuck to the rest of the miners. Then once the attacker released the block chain it would take a long time for the miners to re-synchronize with the blockchain and to validate the attacker’s blocks.
Please change re-target algorithm. KGW is not enough.
Screnn shot: http://prntscr.com/4pgp6z
At this time, the difficulty was over 60K.
So weird.
http://www.coinssource.com/kimoto-gravity-well-exploit-exposed/
Time Warp Exploit, basically takes advantage of KGW’s method for difficulty retargeting, allowing an attacker with sufficient hashing power to mine at a much lower difficulty level. If such an attack occurred, the attacker would be able to mine all of the blocks at an artificially low difficulty while the blockchain would appear frozen or stuck to the rest of the miners. Then once the attacker released the block chain it would take a long time for the miners to re-synchronize with the blockchain and to validate the attacker’s blocks.
Please change re-target algorithm. KGW is not enough.
September 22, 2014, 08:11:34 PM
Current difficulty is 7042400.964355485.
Really? Didn't check, but it must be multipools.
Well, it's not affected by multipool.
Maxcoin is not finding any blocks for a day.
So, I calculated current block's difficulty to see what the matter is.
"difficulty" from console's getinfo command is not current difficulty but previous block's difficulty.
This 7042400 is current block's diff.
Someone with big hash attacked KGW's difficulty change logic and maxcoin is stuck again.
We need some more time to breakthrough this difficulty. As hashes go away, maybe this difficulty could be unsolvable forever if immediate hardfork is not implemented.
Yes, it is affected by multipools:
https://bitcointalksearch.org/topic/anntompoolauto-profit-switching-sha256scryptkeccak-95-coins-282772
http://www.kryptkoinpool.com/
Well tompool looks dead, only forum is running.
kryptkoin multipool has 0 Mh/s for Keccak.
Even with multipool is running, this kind of weird difficulty is not normal.
September 22, 2014, 01:13:19 PM
Finally found block. whew.
However, the re-targeting algorithm should be changed immediately.
However, the re-targeting algorithm should be changed immediately.
September 22, 2014, 11:20:37 AM
Current difficulty is 7042400.964355485.
Really? Didn't check, but it must be multipools.
Well, it's not affected by multipool.
Maxcoin is not finding any blocks for a day.
So, I calculated current block's difficulty to see what the matter is.
"difficulty" from console's getinfo command is not current difficulty but previous block's difficulty.
This 7042400 is current block's diff.
Someone with big hash attacked KGW's difficulty change logic and maxcoin is stuck again.
We need some more time to breakthrough this difficulty. As hashes go away, maybe this difficulty could be unsolvable forever if immediate hardfork is not implemented.
Yes, it is affected by multipools:
https://bitcointalksearch.org/topic/anntompoolauto-profit-switching-sha256scryptkeccak-95-coins-282772
http://www.kryptkoinpool.com/
September 22, 2014, 11:08:58 AM
So I guess this is a way to kill off any old scrypt coin with KGW.. Good to know ;P
September 22, 2014, 11:07:18 AM
September 22, 2014, 10:52:02 AM
How long since last block found?
September 22, 2014, 10:34:50 AM
Current difficulty is 7042400.964355485.
Really? Didn't check, but it must be multipools.
Well, it's not affected by multipool.
Maxcoin is not finding any blocks for a day.
So, I calculated current block's difficulty to see what the matter is.
"difficulty" from console's getinfo command is not current difficulty but previous block's difficulty.
This 7042400 is current block's diff.
Someone with big hash attacked KGW's difficulty change logic and maxcoin is stuck again.
We need some more time to breakthrough this difficulty. As hashes go away, maybe this difficulty could be unsolvable forever if immediate hardfork is not implemented.
I fully agree to your idea.
Even Startcoin uses Digishield. Why with buggy laggy KGW until now?
September 22, 2014, 10:21:46 AM
where is old good MaxCoin?
September 22, 2014, 10:17:12 AM
Current difficulty is 7042400.964355485.
Really? Didn't check, but it must be multipools.
Well, it's not affected by multipool.
Maxcoin is not finding any blocks for a day.
So, I calculated current block's difficulty to see what the matter is.
"difficulty" from console's getinfo command is not current difficulty but previous block's difficulty.
This 7042400 is current block's diff.
Someone with big hash attacked KGW's difficulty change logic and maxcoin is stuck again.
We need some more time to breakthrough this difficulty. As hashes go away, maybe this difficulty could be unsolvable forever if immediate hardfork is not implemented.
September 22, 2014, 09:28:05 AM
Current difficulty is 7042400.964355485.
Really? Didn't check, but it must be multipools.
Jump to: