[ANN][MAX] MAXcoin - PoW, ASIC Resistance, Keccak GPU Mining

[sylph93]

The currently difficulty is at 5 million due, we believe, to a failed timewarp attack. We will be re-enabling ACP once the blockchain begins moving again, which will be an estimated 5 hours, to mitigate from such an attack. If the attack persists as a DDoS we will switch the re-targeting algorithm for something more robust.

Something more robust is really needed. Digishield, Dark Gravity Wave v3.. etc.

[BainbridgeJ]

very unstable difficulty, very low yield.

Any thoughts on whether the time is now right to turn Maxcoin into a purely POS coin?

I don't think pure POS is good idea. Maxcoin is most well known coin is Keccak algo.
However, the difficulty re-target algo. should be changed for smooth operation.

How about Digishield? KGW is too old and buggy.
 
(http://www.reddit.com/r/Digibyte/comments/1yn6t1/digibyte_v_20_code_name_digishield/)

I'm not sure exactly what you mean by "most well known" etc. If you mean that Maxcoin has always been known as utilising Keccak and should remain so, I'm not convinced by that argument. POS would address two fundamental issues that have plagued Maxcoin since its inception: 1) the '51% attack' mining issue (although attacks can be launched at a much lower percentage); and 2) the subversion of the original intention that Maxcoins could easily be created by ordinary users, on ordinary PCs, at home.

POS is economical, using very little electricity and creates coins by doing something that users have to do anyway i.e. sync their wallets. It's that simple. Nothing more would be required than to sync a few times per month. Users would be rewarded by coins automatically credited to their wallets. This should attract more users too.

At the moment, Maxcoin is in the stranglehold of a few mining pools, and that is dangerous. Mining pool squabbles, so prevalent in this thread, could also be eliminated by POS. I believe the time is right to go fully POS. Does anyone have any powerful arguments as to why not?

[dbstmddhks]

what is the next plan Dev team?

Could you explain about the futre plans of maxcoin??

[Vlad2Vlad]

what is the next plan Dev team?

Could you explain about the futre plans of maxcoin??

That's easy.

Wait for Bitcoin to breakout at which point Max the Keiser will get on his big media mic and go crazy; driving mass investor attention and volume to MaxCoin - driving it well past my $5 price target at which point I will sell and go on a much needed vacation.

Any questions?

[dong]

Block chain stop for three hours.

[limbaugh]

At the moment, Maxcoin is in the stranglehold of a few mining pools, and that is dangerous. Mining pool squabbles, so prevalent in this thread, could also be eliminated by POS. I believe the time is right to go fully POS. Does anyone have any powerful arguments as to why not?

Because the current developer lacks the skills to implement it.

[dong]

Block chain stop again, maxcoin is dead.

[Azure]

My wallet won't synch.
 

[LTCMAXMYR]

die again

[miningpoolhub]

Current difficulty is 7042400.964355485.
 

[dbstmddhks]

where is luke??

It's under critical problem..-_-

[Azure]

Current difficulty is 7042400.964355485.
 

Really?  Didn't check, but it must be multipools.

[miningpoolhub]

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.

[Fulis]

where is old good MaxCoin? 

[sylph93]

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? 

 

[CoinProfits]

How long since last block found?

[subSTRATA]

How long since last block found?

35 hours. 

[CoinProfits]

How long since last block found?

35 hours. 

So I guess this is a way to kill off any old scrypt coin with KGW.. Good to know ;P

[Azure]

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:
http://bitcointalk.org/index.php?topic=282772.0
http://www.kryptkoinpool.com/

[sylph93]

Finally found block. whew.

However, the re-targeting algorithm should be changed immediately.