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

[lentyna]

My bat file:

Code:

timeout \t 5

cwigm -c sigt -u username.Miner03 -p x --lodiff --max-temp=75

pause

You better use --max-temp=88 to make sure to let nvidia throttling to +83C automatically and avoid mining pauses.

But that is not the reason the pool shows no mining. The pool shows my hashrate at 0 even my miner is on and running.

[xixou]

Try without --lodiff

[pp688039]

may i ask a question?

http://imgur.com/nqvoz8N

what is the "Job not found" and "Invalid nonce" means?

and my bat is

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


thanks

[dandyqb]

may i ask a question?

http://imgur.com/nqvoz8N

what is the "Job not found" and "Invalid nonce" means?

and my bat is

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


thanks

why OC your mem, is there any advantage?what i know SIGT is core extensive...

[huyhoang]

hi Dev,
Recently, I have checked out your 0.9.8. that is awesome, so I try to pull more SIGT miner recently back to the CWI pool, so the speed is getting faster. I would like to have a feedback/request.
- Whenever I go back to the pool website, I need to type all email/pass again. Other pool allow to remember, and the process to login is much more simple. Can you solve it
- Waiting to hear your 0.9.9 release
 thanks

[xixou]

hi Dev,
Recently, I have checked out your 0.9.8. that is awesome, so I try to pull more SIGT miner recently back to the CWI pool, so the speed is getting faster. I would like to have a feedback/request.
- Whenever I go back to the pool website, I need to type all email/pass again. Other pool allow to remember, and the process to login is much more simple. Can you solve it
- Waiting to hear your 0.9.9 release
 thanks

At my side it remembers the login cause I'm logged with my google account on chrome ^^

[bigjee]

                       VC++ 2013 and CUDA 8.0 x64 382.05
CPU:1.64%          ChainWorks Industries beta - Version 0.9.8         [12:30:16]
--------------------------------------------------------------------------------
Algo:Skunk      | Port: 2000 | NetDiff: 21076.7            | Block:      35136 |
--------------------------------------------------------------------------------
Coin:signatum   | POW: 1250  | Estimated coins/day: 269.506                    |
--------------------------------------------------------------------------------
Solved:   0 | Diff:     1.24 | Shares: 3519.78 | Rej: 0.588878% | Speed:  175.84
--------------------------------------------------------------------------------
0.EVGA GTX 1070              : Shares: 589.07  | Rej: 4.91 | Speed:   29.13MH/s|
1.EVGA GTX 1070              : Shares: 620.8   | Rej: 3.86 | Speed:   29.31MH/s|
2.EVGA GTX 1070              : Shares: 618.98  | Rej: 5    | Speed:   29.45MH/s|
3.EVGA GTX 1070              : Shares: 543.51  | Rej: 1.82 | Speed:   29.07MH/s|
4.EVGA GTX 1070              : Shares: 592.34  | Rej: 2.83 | Speed:   29.44MH/s|
5.EVGA GTX 1070              : Shares: 555.08  | Rej: 2.43 | Speed:   29.61MH/s|
--------------------------------------------------------------------------------
0.EVGA GTX 1070              : T:55C | F:57% | P:106W | I: 24.0 | Core:1899Mhz |
1.EVGA GTX 1070              : T:56C | F:59% | P:106W | I: 24.0 | Core:1919Mhz |
2.EVGA GTX 1070              : T:48C | F:49% | P:106W | I: 24.0 | Core:1927Mhz |
3.EVGA GTX 1070              : T:55C | F:57% | P:106W | I: 24.0 | Core:1894Mhz |
4.EVGA GTX 1070              : T:52C | F:53% | P:107W | I: 24.0 | Core:1919Mhz |
5.EVGA GTX 1070              : T:52C | F:53% | P:107W | I: 24.0 | Core:1931Mhz |
--------------------------------------------------------------------------------
[12:27:12]Share: 6c57a501              | [10:31:06][GPU0]:Job not found (=stale
[12:28:08]Share: 7ee05340              | )
[12:28:15]Share: b0dc41c4              | [10:31:09][GPU2]:Job not found (=stale
[12:28:31]Share: c0d5ce9c              | )
[12:29:06]Share: b1511593              | [11:21:43][GPU1]:Job not found (=stale
[12:29:36]Share: a6845026              | )
[12:29:49]Share: 1d6ca931              | [12:05:50][GPU4]:Job not found (=stale
[12:29:52]Share: 3da8d1ab              | )


--------------------------------------------------------------------------------------------

x6 rig is running great. i have mine configured for efficiency over speed, so it may not be producing "record breaking" mhs, but i am very happy at the overall temp/wattage/speed balance this miner gives me.  this is excellent...

that said, my x1 and x2 rigs are still choking on high worker diff, with way too many blocks going by before a share is submitted.


        _________\ \     \____\     /|  \    \_\  \  Y Y  \  __________
                      \______  / \/\_/ |__|\______  /__|_|  / /
                             \/                   \/      \/ /
                        VC++ 2013 and CUDA 8.0 x64 382.05
CPU:   0%          ChainWorks Industries beta - Version 0.9.8         [12:40:58]
--------------------------------------------------------------------------------
Algo:Skunk      | Port: 2000 | NetDiff: 20220.5            | Block:      35151 |
--------------------------------------------------------------------------------
Coin:signatum   | POW: 1250  | Estimated coins/day: 40.8193                    |
--------------------------------------------------------------------------------
Solved:   0 | Diff:     1.12 | Shares: 623.29  | Rej: 0.52666% | Speed:   29.79M
--------------------------------------------------------------------------------
0.EVGA GTX 1070              : Shares: 623.29  | Rej: 3.3  | Speed:   29.03MH/s|
--------------------------------------------------------------------------------
0.EVGA GTX 1070              : T:54C | F:72% | P:107W | I: 24.0 | Core:1950Mhz |
--------------------------------------------------------------------------------
[12:34:17]Mean netDiff: 16873.9        | [06:16:30]Stratum connection interrupt
[12:34:47]Mean netDiff: 16969.1        | ed
[12:35:08]Mean netDiff: 17317.2        | [06:16:32]Failed to connect to stratum
[12:35:37]Mean netDiff: 17448.7        | .chainworksindustries.com port 2000: C
[12:36:31]Share: 86e53529              | onnection refused
[12:37:37]Mean netDiff: 17946.4        | [06:16:32]Retry in 30s
[12:37:59]Mean netDiff: 18027.3        | [06:17:29]Retry in 30s
[12:39:57]Mean netDiff: 18349.9        | [06:19:34]Retry in 30s
-------------------------------------------------------------------------------


for now i'm leaving the x6 rig running the miner/pool combo, but pulling my smaller rigs.  

for me the issue is not the wild hashrate they produce at the pool, or their sharerate etc.  the issue is participation.  and i think it's the low rate of participation of the smaller rigs that's actually harming the pool's ability to find blocks consistently.  

at any point the solution, or part of the solution for a block could be on one of the smaller rigs.  if they don't participate and submit shares, then the pool never stands a chance to find that block.  2-3 blocks here and there is fine, but 6-7-8 blocks without a share is just too much, especially when the latter seems to be the norm.  

multiply that by who knows how many other smaller rigs that are experiencing the same thing, and there are a LOT of blocks that the pool just never has a chance to even compete for.   i believe that the smaller rigs are actually hurting the pool's performance right now.

like i said, my x6 is staying, so i'm not abandoning the project in any way, and as soon as the new version of a miner and/or a pool update that fixes worker diff for smaller rigs is done - i'll be more then glad to bring them back

tanx for the thorough insight ...

what you are mentioning is a common issue at the moment - where the smaller rigs do choke on high diff shares ...

there is a solution i can propose ... but it will mean that EVERYONE has to comply with it ...

here is my proposition ...

1 - lower the difficulty of the lodiff port ( 2000 ) to an acceptable level where small rigs can mine easily without interruption ... this means that ALL smaller machines will be required to enter the --lodiff parameter ... this will allow shares to be distributed fairly and equally among the smaller rigs - no matter how many are on the port ...
2 - lower the difficulty of the hidiff port ( 6000 ) to start at a lower rate - but increase enough to cater for the larger machines and farms alike ... this means that ALL larger machines will be required to REMOVE the --lodiff parameter ... this will allow shares of higher difficulty to be freely shared among all the larger rigs - and still be able to submit enough shares to the pool so ALL miner have a better opportunity to solve a block ...

if this proposal is acceptable - i can have it sorted very quickly ... this will include the denarius pool ( tribus ) for those mining on the dnr pool as well ...

but i must reiterate - ALL miners must adhere to the correct port for their systems ... if a large miner slams the lodiff port and floods the stratum - we will implement a much more aggressive blocking system for the ip that do that ...

this will be in effect for ALL miners mining at our pool - not just CWIgm miners ...

let me know your thoughts - and any better ideas ...

tanx ...

#crysx

it may work, but you would have a hard time pulling it off.  relying on a user to follow directions is always a disaster waiting to happen

i have a different solution, especially since you control the entire environment from miner to stratum - a custom diff multiplier for the miner.

right now the 1080ti is the fastest card out.  it hashes at about 50 mh and the sweetspot for that card is ,let's say,  about a diff of 128, with 64 on the low end for fast blocks, and 256 on the high end for slower blocks.  use that card as the "default" or a value of 1.

1070 hashes at about 60 percent of the speed of 1080ti (1), so it's multiplier will be 0.6.  not sure what the 1060 hashes, but you get where i'm going with this - it would be whatever a ratio of it's speed/1080ti.

the miner knows a which gpu's are in there, and how many.  you could get fancy and make a per-model table to be really precise, or just take the easy way out and go by hashrate - which the miner also, obviously, reports.  if the default of 1 is 50mh, and the miner produces 80 mh, the multiplier is 1.6.  Again, i'm not sure what the 1060 hashes, but let's say it's 15.  an x6 1060 rig would report a hashrate of 90.  90/50 is multiplier of 1.8 etc, etc. etc.

this way you can have your diff logic walk the stratum through the range of diff of 64-256 only, and adjust on the fly when you have fast blocks.  each miner will calculate it's own multiplier based on which type and number and type of gpu's it's seeing ("fancy mode") or hashrate and adjust it's own difficulty accordingly with the stratum.      

i'm guessing that if you just change the difficulty on a miner, without adjusting the same on the stratum per worker, the miner will not submit valid shares.  so you'll need to either implement this multiplier on the stratum per worker, or better yet  - do it on a miner itself and just have the miner pass that info to the stratum.  if each miner is a worker, it would be an ideal way to pass the exact performance of a rig to the stratum.  this would also be really helpful if one of the cards on a multi gpu rig goes down, or throttles and miner hashrate goes down - the multiplier could adjust accordingly.

so let's say i have a x2 rig with 1 1080ti and 1 1070 or 80mh.  the pool starts me off at diff of 128 (sweetspot for 1080ti or value of 1), my miner does the math and figures out that my multiplier is 1.6, multiplies the 128 by 1.6 and tells the stratum - set diff for this worker at 128*1.6=204.8.  then a few minutes/hours later, the pool detects that the blocks are flying by and dumps the pool diff to 64.   my miner does the math again, divides 204.8 by 2, and tells the stratum to set the worker at 102.4.  pool goes to 256, my miner does the math etc. etc. etc.  

usually it's the stratum that tells the miner to adjust worker diff and you could do this on the stratum side, but since you control both ........

i think, if doable,  this would solve this particular problem permanently.  and you could implement this type of a system across any algo you want - just figure out what you want the default to be.  

whao ...

i missed this post ...

serves me right for working right after i get out of bed ...

some great suggestion ... some of which will be very difficult to implement if we go that way - but not impossible ...

tanx for the well though out suggestions ...

#crysx

What if we could get the user to fill out the specs of their worker (just like the other member suggested) BUT at account signup stage.
Say there is a worker equipment section , where they'd fill out number of cards, Card model (1080, 1070, 1060) and optional :clock speed, mem clock and then have the stratum place the miner's username/workername in a certain difficulty category.

I'm assuming users that can fill out the correct username info into batch fill can fill in correct miner equipment specs at sign up.  

When the user wants to make edits to worker equipment they can do so through "My account".
Also I think it will help to show the user in the dashboard what difficulty category their worker has been placed in.

[pp688039]

may i ask a question?

http://imgur.com/nqvoz8N

what is the "Job not found" and "Invalid nonce" means?

and my bat is

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


thanks

why OC your mem, is there any advantage?what i know SIGT is core extensive...

i think  the mem can more or less increase the performance (maybe)

maybe is wrong...just i think...

[sparker327]

Didn't read through entire thread but I'm mining sigt and love testing new miners. Anyway for me to get added to the beta?

Use GeForce GTX1070 8GB cards, win 10. Current drivers for nvidia.

[sparker327]

may i ask a question?

http://imgur.com/nqvoz8N

what is the "Job not found" and "Invalid nonce" means?

and my bat is

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


thanks

why OC your mem, is there any advantage?what i know SIGT is core extensive...

i think  the mem can more or less increase the performance (maybe)

maybe is wrong...just i think...

I'm negative on my mem and up core to OC and get better rates doing that

Example

-180 mem
+215 core

[fhakenzz]

how to join the close beta? i already sent a PM with no reply sad

[pp688039]

may i ask a question?

http://imgur.com/nqvoz8N

what is the "Job not found" and "Invalid nonce" means?

and my bat is

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


thanks

why OC your mem, is there any advantage?what i know SIGT is core extensive...

i think  the mem can more or less increase the performance (maybe)

maybe is wrong...just i think...

I'm negative on my mem and up core to OC and get better rates doing that

Example

-180 mem
+215 core

ok, i try to low down the mem to test it

core +140
mem -502

the mem have to low down to limit?
or a little is enough?

[pr0ximus]

Is it only me or are there no rewards for the last one+ hour? diff :317.44 and a constant 120+ MH/s but no coins? 

[Commie]

Is it only me or are there no rewards for the last one+ hour? diff :317.44 and a constant 120+ MH/s but no coins? 

No, not only you. I just accidentaly noted the same thing. What's the matter, admins?

[blockbasher]

Thanks for adding me to the closed beta all is up and running now.     My speeds are roughly the same as using ccminer 1.1 but they started off higher.    My 8 gpu rig has some cooling issues on a few of the GPU that I need to address and the miner is keeping them at 70C which is hurting their performance.   It started off at about a 8% improvement and has slowly reduced back down but is keeping the GPUs much cooler.    This will force me to actually address the air flow issue.  

How often are the coin added into the unconfirmed?   I have been mining exactly 60min and have not had anything show up there.    I mined for a while yesterday and the same thing, although I logged in today and there was confirmed coin there so it does appear that its being paid out but their must be a long delay before it shows up.  

I love the interface and layout of the miner

Thanks!

[zhulick]

Is it only me or are there no rewards for the last one+ hour? diff :317.44 and a constant 120+ MH/s but no coins? 

pool had a bad run of luck... took like an hour and 50 minutes to find the last block.

this will happen.  usually (and hopefully) rarely, but it will happen once in a while in any pool, especially a small pool.

small pool = large variance.

[Brucelats]

I will write this just. It might be a small bug i seen.

When i started miner several times and after restart also, it always initialized only 2x GPU from 7. 7 were shown in device manager and in after burner, but when i started miner only gpu 2 and 6 shown hashrate, rest were stuck on 0.


Then i cancled miner for 5th time, went alt tab to do something, tried run miner again and it worked. Dunno why it didnt recognized my GPU-s right away.


This is my .bat file:


setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
cwigm -c sigt -u Brucelats.Zotacx7_SIGT -p x --cpu-priority=3 -i 22 --tlimit=65,65,65,65,65,65,65
pause


I used exact same on my other rigs with 5 6 7 GPU-s, only changed temp limits a bit and worker name and they all worked. Only thing that is speciffic to this rig that had problems is, it had all the same GPU-s and that are Zotac GTX 1070 AMP! Extreme. Rest have mix, or at least 1 card is different. Cheers!

first - remove all the setx environment parameters ...

they are really only used for sgminer / amd settings ...

cuda settings are usually set within the environment when you install the nvidia driver - and there is no need to set those environment parameter for nvidia cards ... you will see the same hashrate and results when you remove them ...

second - why --tlimit? ...

CWIgm is a unique miner ... try without that parameter and restart ...

you may want to try adding --lodiff to access the lower difficulty port also ... at least test it -until the port changes take place ( if they take place ) ...

let us know that all goes ...

#crysx

Ok will change parameters. And i forgot --lodiff parameter. I'll add it yeah.



On second note, why not use temp limit?

I cant monitor my rig all the time. In case something happens and gpus start overheating i want my miner to close to prevent any damage. I use Air conditioner coz it's quite hot. In case something occurs with AC temps will start rising, so i want use temp limits to stop miners if that happens.

Unless i am wrong?

If there is no parameter to turn off miner if certain temperature limit is reached it should be added. I would always use it, and everyone should in case something goes wrong. Ok there are parameters to controll GPU usage and such, but i have my fans set on auto, i made a curve. And if i reach some high temperatures, something bad is going on haha. So no point to mine until that thing is resolved, so best idea is just to turn off miner and no harm done.

there is a device called the PID ... it is a controller of sorts - an algorithm ...

https://en.wikipedia.org/wiki/PID_controller#Fundamental_operation ...

the implemented PID controller - at this point - has a racing condition with the internal firmware which controls the fans speed ... which means that if the user has not set the fan speed manually at a desired level - the pid will drop the temperature to the limit set by the user - but the gpu will notice that the temperature is going down and will drop the fan speeds - which will result in a temperature increase which the PID has to readjust and so on ...

ie ... do not use the --max-temp feature with the fans set to auto ...

the temp control and the netdiff parameters are experiential ... the netdiff parameter calculates the netdiff incorrectly - even tho its only about 1% error - we advise NOT using it at all for now ... it is fixed in CWIgm-0.9.9 ...

other than that - great results ...

soon - you will only need the --lodiff parameter for small rigs ... the consensus is overwhelmingly in favour of stratum diff change - so there will be some teething issues there - but we will get through them ...

#crysx

Thank you for the answer, but i havent got answer what i was really looking for? What does --tlimit does? Will it turn off the miner or something if certain temeprature is met?

I have great settings with my auto fan speed in MSI afterburner and all my cards are around 50-57 degrees. I am looking for function that will TURN OFF MY MINER if temeperature reaches certain point. I dont want any throtling or extra control of fans etc. I JUST want to turn off my miner if something messes up and to save my gpu-s or whatever.

IS --tlimit doing that? If not YOU should REALLY implement that function. It should be easy. Just turn off miner if he reads temerature limit is being reached or passed.


Cheers!

[abudfv2008]

any chance you will add XCN  to your pool/miner?  it is a great nvidia coin that has been around forever. 

There are a lot of other algos that are used in many perspective coins like skein or nist5. Which will attract many miners to CWI if they could make faster miner for these algos.
For what do you ask about this almost dead algo used in ONE coin with 0.5btc volume on some shitty exchange and constantly low price for years?

[Leass]

It's possible to use CWIgm miner to mine on other CWI pools or it's currently locked to SIGT and DNR?

[lentyna]

Try without --lodiff

Did not help, it's still not submitting any shares.