short reply from me, the guy who released vertminer.

Yes, i had a GPU miner ready at ~17.00 GMT and i mined with 2x 7950.
At 23.00 or 24.00 GMT i decided to spread this to the IRC channel because no pools or GPU miner was public available.
During the next hours there was a massive community support to compile this for windows (many thanks to Aleks) and to setup the first pools so everyone could mine VTC with a GPU miner.
-> a GPU miner + Pools was available for everyone within 24 hours after coin launch, not days or even weeks later.

And as you can see, with 2x 7950s it was not real possible to make such a hugh amount of coins. Believe it or not, i am not even in the Top10.

I do not know who the other guys or groups are, but i am sure this was no one from the dev team (e.g. i have send some VTC to Bushido because he only had a Laptop to mine...)

I know this statement will not stop the FUD but at least everyone can read it and think about the bullshit from IPO and/or premined coin guys.

yes, 340 seems to be OK.
you also can try --thread-concurrency 8191,8191

please add the red marked

Donated 100 more VTC. Let's make progress!

Both. If you want to support, i have no problems with.
But i am also annoyed because it is a alpha and i expect some issues/confusion regarding the --scrypt and --nscrypt options
Some users still use the very first cgminer-vertcoin and with this old miner --scrypt as an options mines only vertcoin (and this behaviour is now changed -> no accepted shares with vertminer-0.5.4pre2 and --scrypt option).
But as this alpha version is now out in the wild you cannot hold it back.
Therefore i had to write this important info.

Also i am still in test regarding some strange behaviour with ultra hot cards and 0 rpm fan (i try to reproduce this error but until now i am not able, i have no such issues).

Are you interested in doing the support for this new version i have not released yet (still in test)?
Regarding compiling: just use autogen.sh, it will do the job (autoreconf, configure, build and strip alltogether).

@All: this new version now supports mining nfactor scrypt and normal scrypt

vertminer.exe --scrypt .....   -->  mine normal scrypt coins
vertminer.exe --nscrypt  ....   --> mine nfactor scrypt coins (e.g. vertcoin)

But as always: you can use your known cgminer .conf for mining normal scrypt coins BUT THIS WILL NOT WORK WITH VERTCOIN (the other way is fine -> use vertcoin config for normal scrypt coins).
For vertcoin, you have to use other (vertcoin, e.g. TC) settings and i am still playing around with something so this version is ALPHA and USE AT YOUR OWN RISK!

which can mine scrypt (--scrypt) and adaptive n-factor scrypt (--nscrypt)

This what i prepare now...
And i really know this will lead to a lot of issues with users just copying their cgminer config and crying why this does not work with --nscrypt

Binaries will come afterwards. But a compilation should really not take hours (ok, if everything is prepared)

Obviously the copy and paste dev did something wrong during copying my github.
But ask the ALTminer dev, i am sure he can explain...

Sorry, my fault.
I did not want to blame you i mean

Yes, i am pretty new. I only created the vertminer and did some help for setting up the first pools.

But of course you should always do what you mean is the best for you!
And always keep your own opinion. no blaming

Lets create a new Logo!
Just filled up the remaining VTC

And lets also create the Press releases.
I filled up the remaining VTC too

I send some VTC to the African Water project too.
Please concentrate on this project now  

If you think a big anonymous investor calling himself "Wolong" and manipulating prices is a better backing then leave Vertcoin too...

First? clone of vertcoin: "Altcoin"
https://bitcointalk.org/index.php?topic=459028.0 

Sorry, i was not exact enough.
From my understanding you use the fan settings from the miner even if fixed or within a defined range, correct?

With 0.5.3 i patched the miner with a ADL6 patch for R9 cards from the litecoin forum.
There are no known issues with this patch, it does only prevent a system crash after exiting the miner when a R9 290/290X is used.
I will check if there is a relation but without a proper use case how to provoke this issue it will be hard to find.

It is always a bad idea to use hardware control from within a piece of software (not only related to the miner).
Because if the SW crashes your hardware is not safe (crash = undefined state). Also there can be (unkown) SW errors.
Using the BIOS is safe but normally also louder.

Please feel free to do so, source is available on github.
I would start with a switch like "--do-not-warp-my-hardware"

I think about releasing a new version with max GPU 400MHz, max MEM 600 MHz, max Intensity 7 and Fan always at 100%.
Everything else must be forced with "--force-because-i-know-what-i-do"

Hm, the settings look safe. My 7950s are at 1000/1500 with 1.012V (at 80°C with BIOS Fan control)

The only relation to the 0 RPM i can see is with the fixed Fan.
Did this happen also before with vertminer < 0.5.2? Or only now with vertminer-0.5.3?

i can only guess.

Are the cards overclocked? Do you use the auto-fan feature of the miner?

FyI: the codebase of vertminer is nearly the same as with cgminer-3.7.2 but the opencl kernel is tweaked -> the cards are pushed harder
My 7950s run since > 1 week without any problem (only yesterday i had to restart because here we had a 2 second power loss)

I am sure the card is not really Ok, at least the custom cooler is not the best as it seems.
And the stock BIOS has really low voltages, this is the main cause of the voltage based crashes.
But i will apply again (even thinner) new compound. Perhaps i applied too much.

But the conclusion is the same: the mining application kicks 100% constant load to the card and this is much more than e.g. normal games and even more than furmark (i could not believer this before my own testings).

A word from my side about crashing miner and hardware

Since some days i have a VTX3D R9 290 X-Edition card and there were and are issues with miner crashes and driver recoveries at stock clocks.

BUT: i know why this happens!

1) after i got the card and put it into my win 7 PC this thing was very very hot. even at 700 MHz i had 93°C with Intensity 14. Higher intensity: crash
   -> issue fixed: the original applied heat compound was crap. air gaps inside and some of the chip was not covered. Now with new heat compound it is much better than before.

2) after this heat compound thing i tried higher clock rates.
max stock 975 MHz and Intensity 15: crash after a few seconds. With Intensity 14 crash after <1 minute.
With 900 MHz: really hot but working, even with Intensity 20.
Test with furmark: with 975 MHz and max settings: no problems, works fine for > 5 minutes (just a short test performed)

Then i started HWInfo and checked the Voltages: with Furmark, the GPU voltage is at min somewhere at 0.98xV @ 975MHz.
With vertminer voltage is at 0.94xV @ 900MHz. Also the temps are not as high with furmark @ stock than with vertminer and lower clocks.

-> my conclusion:
for GPU testing purposes, furmark is a toy. If you want to perform real testing, use vertminer. The opencl kicks the GPU to the max and so everything else (regulators, memory) is used extensive.
And if the cards stock voltages are good enough to play games, this does not mean you can use the card with the same clocks for mining.

--> final word
If you encounter crashes, lower your clocks or increase the voltages! And a good cooling is a must!
The latest opencl kernel for the vertminer is even more optimized than the existing cgminer scrypt kernel. You can try to use the latest vertminer kernel also with scrypt cgminer (but needs some changes to work).
I am sure you will see also some sudden crashes when your card is at its limit...

if you have sync issues please add this node to your vertcoin.conf

addnode=37.187.81.121