Quote from: Hippie Tech on May 16, 2014, 03:58:42 AM

Quote from: wirerogue on May 16, 2014, 03:02:33 AM

Quote from: Hippie Tech on May 16, 2014, 02:34:23 AM

GTFO with your knee jerk FUD accusation. Instamining and share/hashpower exploits are very common. Wake up !

Fyi, I have been solo mining random alts non stop for almost a year. (I rarely mine with a pool.) This includes LGC on and off for the past month. I can assure you, this is NOT normal behaviour for ANY coin and should be regarded as highly suspicious.

it's like driving behind that car with all the bumper stickers on it. https://bitcointalk.org/index.php?action=profile;u=31553;sa=showPosts

Really ? Is that the best you can do ?

As you can see by my posts.. we are surrounded by instamined ponzi scheme multipool'd shitcoins. :/

You might also notice that the reactions I'm getting here aren't much different than the ones I saw from the other shitdevs and their socks. Tongue

The first 50 barely took 5 minutes.

Block 1 - 2014-04-12 20:00:25
http://chainz.cryptoid.info/lgc/block.dws?000007dee53b4b1a31fc4ee14e22c6f9e1a992d5b2c37ca309c2615f29f275f9.htm

Block 50 - 2014-04-12 20:05:46
http://chainz.cryptoid.info/lgc/block.dws?0000000065e589fcab040ff736e2808c4a696ee193c21c7fd6af6b38c258a21b.htm

How many more instamine sessions will we find ?

Why are the block explorer's timestamps off by one hour ? Is it using UTC ?

Don't really appreciate those accusations. DGW kicked in at block 60 and if you have been around as long as you say you have then you know exactly what happens to a launch if DGW isn't switched on instantly. Blocks get minted very quickly. Go though the pages after the launch and you will see that a few people have a problem with DGW kicking in so early as it properly adjusts the difficulty and makes it hard for solominers to make much profit in the first few moments of the launch.

Everything has been explained and if you did some research then you would find that it is indeed above board. There's nothing at all I can do about multipools unless I change the code in such a way that it would require custom stratum code to be implemented. This would cause a hard fork and would be alot of hassle for everyone involved, it's not something I can just up and change without prior notice or warning.