False.

That variable is in place to stop the difficulty from ever getting too low. It serves as the floor for difficulty, basically. There is enough documentation online to prove this.

You have increased that floor from 20 to 1000000. Ergo, you have INCREASED difficulty by an insane amount.

You've already proven yourself to be incompetent. Don't even act like you know a damn thing about how bitcoin works, or coin creation in general.

Perhaps I phrased that poorly. Or in a way that you did not understand. Anyway...

Allow me to rephrase it another way. By using an example. On bitcoin testnet, that variable in particular is decreased in order to reduce the minimum difficulty.

You, however, decided to increase it from it's starting value of 20, to an insane value of 1000000. You are in for some nasty difficulty spikes because of this.

I'm sure many people are still running the 1000000 client.

And it's hilarious that crap like this even gets pushed out. This guy has no idea what he's doing in the code. He's just editing random variables and hoping they do what he wants.

Please read

https://bitcointalk.org/index.php?topic=204829.0

Please read

https://bitcointalk.org/index.php?topic=204829.0

Elacoin dev just rereleased... and pushed a git out with the following value set:


Apparently this fool thinks this controls the starting difficulty. What this variable actually controls is the minimum proof of work value after recalculation.

The funny thing about the proof of work value, is that it's inversely related to difficulty. Meaning, what he has done here will cause difficulty to skyrocket to absolutely insane levels come the first retarget.

Enjoy!

I'd post a windows binary, but there's not much point.

You'll find out soon enough.

No binary! Linux premine only.

Shhhhhhh

That is not how starting difficulty works. At all. That's not even the correct value to edit. Ah, screw it. No one listens to me anyway.

I started that HazardCoin thread as a joke but I'm seriously thinking of developing it, with all the developer incompetence going on lately.

Oh hey, finally someone who gets it!

Elacoin shills just upset that their premining operation was exposed.

ZzZzZzZz

You don't seem to understand what that word means. I suggest you don't use it.

And the 42 trillion is a serious number. Count on it.

The elacoin shills are just upset that I caught them in an attempt to pull off a huge premining operation.

Disconnect your clients before sending them out to be compiled, idiots.

Approximately 42 trillion.

If a 1360 blockchain did not start to download as soon as I fired up the compiled client, this thread wouldn't even exist right now.

Don't try to play dumb.

Yes, my coin specs that took me about a minute to pull off the top of my head... You're an idiot.

Some people are incapable of recognizing various forums of humor.

HazardCoin is not a real coin, and was intended as a joke.

Get over yourselves.

Insiders.

That coin is super serious, and not in any way sarcastic in nature!



Let's face the facts here, if I wanted to premine your coin, I sure as hell wouldn't have posted on the forums about it. I'd have kept my blockchain offline up until the point you released elacoin, and then put my much longer premined blockchain onto the network... Effectively 51% attacking it. That would make the most sense, yeah? So explain why I didn't do that.

Milkshake needs someone to compile elacoin into a windows client because he's too incompetent to do it himself.
I offer to compile it for him, so he sends me source.
I compile into windows binary, start up the client to test.
Get one connection immediately, a 1360 block long blockchain.
He notices this and quickly disconnects. I make forum post about it (https://bitcointalk.org/index.php?topic=203647.420) and release the source.
Milkshake scrambles to release a client with a new genesis block, fails miserably

And here we are!

Because he was an idiot and left his client running after he sent me the source to compile. He noticed it pretty fast and disconnected.