### A ChainWorks Industries (CWI) Project - CWIgm | Simple Powerful Stable

[pallas]

looks like a very interesting project, but you know I'm a linux guy, so I'll check it again later ;-)

[1715042976]

1715042976

[pp688039]

window 10 X64
GPU driver 384.94
powerlimit 80%
core +140
mem+ 600

cwigm_signatum.bat

cwigm -c sigt -u pp688039.pp688039 -p x --lodiff --max-temp=70
pause



i think it is all fine to the miner...

http://imgur.com/YkXo2ov

may i ask a question...what is the yellow word ([GPU0]invalid nonce)

[chrysophylax]

Trying a single 1070 gpu (+125core/+500mem/60%tdp) with denarius (tribus) on win7.

Immediately noticed a new command in the bat that doesn't exist in the bat for sigt  --mean-net-diff=1.1

Miner reports a speed of 53.  I have never mined this algo before, so nothing to personally compare it to, but i did check yiimp benchs- 53 is pretty damn good

After a few minutes i noticed something weird.  In the right bottom box, a yellow line saying net diff > mean net diff.  The netdiff field in the miner turned red, and the miner just stopped mining.  I could see the card idling in afterburner.  This went on for a few blocks, then the netdiff field turned green, and the miner resumed.   Rinse/repeat every 5-10 minutes or so, with each break lasting about 2-3 blocks.

I guessed that the --mean-net-diff=1.1 was causing this, took it out, and this behavior stopped.  Miner just kept on mining.

I'm not sure what --mean-net-diff=1.1 is meant to do, and it's probably there for a good reason. For me, however, it's pausing the miner and makes the gpu just sit there idling for a bit.  An idling mining gpu is a sin

well - there is a good reason for this ...

--mean-net-diff=1.1 parameter is designed stopping the miner when the weighted mean of the network's difficulty surpasses an upper bound multiplied by a ratio ( in this case 1.1 ) ...

this is made for people who want to mine only when it's more profitable to do so ( low difficulty ) - but they dont want to miss out in case they 'set-and-forget' the miner running for days and the network diff shoots higher than they estimated due to increased demand ...

this saves power from continuously mining - but also stops the miner from mining in these periods ...

in case you ask - there currently is no switcher for the miner to mine elsewhere at such periods of time as these ...

#crysx

[chrysophylax]

Someone told me sigt mining may be make vga die soon because gpu power continuetly up/down 5-10% (not like zec mining only 2-3%). Is this true?

no ...

we have had our graphics cards mining for almost three years non-stop ... prior to that - as we were building and growing theFARM - it was mostly mining - and very little happens to the miner when fluctuations occur like that ...

until recently when a brownout killed theFARM and all the electrical in the entire building - it was mining very well ...

#crysx

[chrysophylax]

any chance the new version work with other coins, like cream?

highly unlikely ...

as creamcoin is an x11 algo coin - and is dominated by asics ...

that doesnt mean we WONT integrate the x11 algo - it just simply means its not on our radar just yet ...

in fact - most asic dominated algos wont be considered for a little while yet ...

#crysx

[chrysophylax]

Okay dev I'm here cause you said you had bested sp_ with your version, where can I download it? Do I need to compile from source?

our private miner has surpassed most of the algorithms sp is only just releasing to you ...

there is no general download link - because we are still in closed beta ...

if you wish to join the closed beta - then pm me with a request ...

and if you are here to maximize the validity of the argument that has been going on with sp for three years now - then dont try ... we wont tolerate it here ... sp and i go a LONG way - and he has been doing what he has been doing for a lot longer than that ...

the beta test is of OUR miner ... not copied code and converted to SELL to you ... there are restrictions in the use and updates of the beta - with new components that far outweight anything he does ...

so you are welcome to pm me - and take it from there ...

#crysx

[soothaa]

PM sent!

[chrysophylax]

the prevvious post reminds me ...

PLEASE request in pm WITH the details of the gpu / gpus you are using and the windows operating system ...

if you send me a pm to just 'give me the miner' like some of you have - there will no longer be a response ...

admittedly - ther have only been a few like this - but we need to know ...

otherwise the same response will be given ...

---

hi ...

what cards do you have and what operating system? ...

#crysx

---

we are NOT trying to restrict the beta testing in any way shape or form ... what we ARE doing is determining whether your rigs are fit to be in the testing ...

many of you have amd gpus - wont work with CWIgm ...
many of you have 750ti nvidia - wont work with CWIgm ...
many of you have older nvidia 780ti etc - wont work with CWIgm ...

CWIgm is now only supporting nvidia based gpus with compute52 or compute61 level gpu ...

this means that higher end 9xx cards - and 10xx cards are usable - with some of the higher end processing cards ( like the titan x in a few cases ) which are of the compute level calibre ... we wish we could open the test up to everyone - but that would not be feasible with the limited resources for compatibility we have ...

like so with the os ... windows 7 / 10 ... most versions will do ( home / pro / ent ) ...

so please pm me with more than a request to join - but with the specs as well - as we can determine right away whether its worth joining the test ...

this is also the other reason why we tie the test miner to OUR pools ... because we have full control over the pool - and the adjustments that are required to be made to all three - miner / pool / stratum ... if we introduce other factors - such as other pools and stratum / diff systems into the equation - it literally throws a spanner in the works and derails our focus on producing the miner we want to produce - due to the external issue that can arise from these other factors ...

the most important part of all this also - PLEASE take the 2.5minutes it takes to read the README contained in the package ...

it contains VERY important information - such as changes to CWIgm - additions to CWIgm - parameter adjustments - and many other things that need to be known BEFORE you mine ...

ill put this up on the op as a core part of the test ...

tanx ...

#crysx

[chrysophylax]

looks like a very interesting project, but you know I'm a linux guy, so I'll check it again later ;-)

so nice to see you here pallas ...

its always good to see decent devs like you here ...

we too are linux based ... but as a test for the core code - we needed to compile and test it on the largest group of users - which is by far the windows users ...

we are working on a linux version ( centos 7 - fedora 26 - ubuntu 16 ) - but until we can compile securely and in a closed method - we cannot test that version of CWIgm in way besides internally ...

aaand you KNOW the reason why ...

tanx for popping by mate ...

#crysx

[steamcloud]

This is my performance rig after testing the program about 4-5 hours

 VC++ 2013 and CUDA 8.0 x64 382.05
CPU:1.65%          ChainWorks Industries beta - Version 0.9.8         [21:43:14]
--------------------------------------------------------------------------------
Algo:Skunk      | Port: 2000 | NetDiff: 15568.1            | Block:      30928 |
--------------------------------------------------------------------------------
Coin:signatum   | POW: 1250  | Estimated coins/day: 210.961                    |
--------------------------------------------------------------------------------
Solved:   0 | Diff:      2.5 | Shares: 499.5   | Rej: 0.249626% | Speed:  114.62
--------------------------------------------------------------------------------
0.EVGA GTX 1080 Ti           : Shares: 239     | Rej: 1    | Speed:   53.69MH/s|
1.MSI GTX 1070               : Shares: 124.25  | Rej: 0    | Speed:   30.16MH/s|
2.MSI GTX 1070               : Shares: 136.25  | Rej: 0.25 | Speed:   31.00MH/s|
--------------------------------------------------------------------------------
0.EVGA GTX 1080 Ti           : T:63C | F:76% | P:218W | I: 25.0 | Core:1879Mhz |
1.MSI GTX 1070               : T:66C | F:84% | P:152W | I: 25.0 | Core:1956Mhz |
2.MSI GTX 1070               : T:62C | F:74% | P:168W | I: 25.0 | Core:2002Mhz |

Stable setting, no error.
this is my setting for my gpu.
GTX 1070, PL 80, Cclock, +100, memClock +500
GTX 1080 Ti, PL 80, Cclock, +100, memClock +500

This program is very nice... more faster than sp mod 3, i will try different oc setting for better performance.
Thank you chrysophylax.

[PikPik]

This is my initial setup. 

http://imgur.com/a/mpmik

[Real_Unhooked]

OS: Win10 x64
GPU: 1070
Settings: +125Mhz core: -500Mem 90% TDP
I get about 29.xx mh/s per card. Faster than anything I have used before.

Excellent job!!

I would suggest adding support for Spreadcoin as well. Another very profitable niche coin without any workable miners except sp_ paid miner

[soothaa]

Liking it so far, just got my smallest rig set up for testing purposes. Currently running well and testing the max I can produce.

One question - the program says I will currently generate 200+ coins per day yet WTM says I will produce only 100. Is the software not correctly picking up the BR halving?

[mINGz]

The miner is work so great.
I got 50 - 53 MH/s on 1080ti various model and 19 MH/s on 1060 3g.
Both model are on 8 VGA rig.

Miner runs very stable in my mine.

Anyway, I have 1 question here.
Is the API Blind function worked for this version?

Please kindly advise, Thank you so much

[astronyu]

Hi, are you still accepting tester for this miner?

[Gongolo]

Just released palgin mod 1.1.1, but cwigm is still faster.
And stable, never crashed in my cfg (win10, multigpu).

[xcougarx]

My results were about 6% better than palgin 1.1 on 1080 tis, similar to other 1080ti numbers here. That was also about 5% better than the klxr (spelling?) source code based x86 compile I made myself.
I have not had to tweak anything to make it go, and it never had a crash/pause/confusion/questionable result. Pool side numbers make more sense than other pools, I pay attention to those. High quality stable experience .

to answer question above:
This line in local text output of miner shows it correctly picks up the 1250/block reward after halving.
Coin:signatum   | POW: 1250  | Estimated coins/day: 210.961
This miner side per day estimate that follows looks about right for me after running overnight, compared to actual earnings, it ramped up within the first hour, dont get put off with low numbers in the first few minutes.
One can not judge this too quickly when blocks take 30-80 minutes.
The server side gui has an estimate that is a bit diffrent, all mpos guis seem to have some similar estimate possibly same code. These are hardly ever accurate, especially hard on a coin where difficulty is moving up and down very fast, network has is all over the place and the past day included a halving,

Liking it so far, just got my smallest rig set up for testing purposes. Currently running well and testing the max I can produce.

One question - the program says I will currently generate 200+ coins per day yet WTM says I will produce only 100. Is the software not correctly picking up the BR halving?

[kleito]

good worker,
my beta is 9.7 9.8? is god?

[Real_Unhooked]

Very impressive work with none of the drama. Support all the way. Any idea when we can be allowed to use our own pool?

[Twod]

A very fast miner. Version 0.9.8, drivers 384.94, GTX 1070*7 Palit SJS / PL 75% (146W) / +60 Core / -502 MEM / -I 25 speed 30-31 MH/s