Minimum payout on sundays only.......

iif you leave them on the site, you are at the mercy of what chain they pick to keep them on.... unless magically they are courteous enough to give you your coins on both chains.


I can imagine coinbase sticking everyone on the good chain, and taking everything and dumping it off on the bad chain... for inter-company profit.    There's nothing keeping them from doing such a thing.... since they control the funds....

Yeah;  to test, just make a quick batch file that just launches the miner you are testing;  using a very basic batch such as this:

mineskein.bat


be sure to replace the btcaddress with your BTC address.

Once you find a compatible one;  check with minerx on how to integrate it into the powershell scripts.  It may be as easy as just replacing the offending miner app itself, naming the new one just like the old one was....  but he will know best.   I haven't looked at his scripts much.

I know nemosminer right now is using SP_'s pay-for-use/private-build miner app....  the problem with it not working now could be that he switched from the tpruvot version recently... but i am unsure if he originally was serving out the tpruvot version for skunk.

*edit* check my bold highlight;  it should be '-a' as i've corrected it.  your post only had a '-'

try ccminer 1.7.6, or 1.8-dev for algos other than skunk which is only going to be in the newest miner apps since its a new algo;  If i stil had a 7 series, I would test all the copies I have collected over the years...  But for other algos, like X17, skein, etc... try wither of those 2 versions.

should be able to find links to them on github or cryptominingblog.

I like the pico idea... I just broke down and spent some of my BTC to buy one off amazon after seeing your photo citronick... couldn't resist.

A friend has a source on cheap: PWS-1K41P-1R 24Pin 1400W 1U  (I think his price was ~30-40 each or less)

Using a pico would negate the need for soldering up an ATx power connector for the motherboards....  and I had already planned on soldering PCIE cables directly to the 24pin bus bar on the back.... so win win.  I think ill mount it in my rosewell case in place of the coolmax 1600w I currently have in there.... because that coolmax is a massive power supply....  and it will free up space for another exhaust fan in the back where the PSU mounts.

yup.

driver version is different between both machines too.

The machine with the 1070 is running 378.78

It looks like phillipma's test card also crashed;  I presume from the same problem.   I'm not sure if he runs 7 or 10.

happens both with the algo dev's version on the ANN thread, and the SP version.

note to all users mining skunk:

disable stats.  Do not add it to the password string.

I have been having miner crashes upon the pool asking for stats.

Not sure why its happening, but it does... and the miners don't crash when its not in the password string.

adding a pause to the end of the batch, let me see the final sting every time it crashed, and every single time it crashed;  its message was that the pool asked for stats.


At first It was only happening to my maxwell cards, but it seems to be happening to my pascal cards also... albeit takes much longer to crash on pascal cards than on maxwell cards.


I seriously doubt this would be a problem with the pool;  unless the pool sends something erroneous right after asking for stats.....  But you might want to look into it crackfoo if it's something that's added to stratum during the coin/algo setup process.

No clue what your motivation in that reply is....   especially since I am one of the earlier ones making more than basic batch files for the people (not to mention the advanced/complicated ones); and helping them with their own issues.... and as always, I do not OC or UC my miners.   If I need to UC, I typically trim intensity instead.

People "on a mountain" generally don't ask for help because they got there themselves; or they steal others' work and call it their own and try their hardest to profit from it  

Ill assume post count is your motivation.



To add to the original notes:   Reloading the OS on the machine fixed the issue.   Must have been something very strange.

The nvidia driver has everything needed cuda-wise.

Note to all doing nvidia mining:

disable stats reporting to the pool whenever possible if using anything but a pascal card.  Pascal cards don't seem to suffer this problem.

I have confirmed that Maxwell cards will crash the miner when the pool requests the stats for your device.   I'm not sure about earlier cards since I got rid of my last GTX780 and earlier cards.

I have successfully run intensities up to 25 on both maxwell and pascal cards.

If the miner app dev can add the ability to do this automatically or finds the root cause and re-codes it, it will save some users heartache.

cheers.

default;  24.

But;  intensity issues rear their teeth right away.... not 15+ minutes later in all my experiences in the past.  I'm not far from hitting share #54 again, so ill report back if it still happens or not.

*edit*  made it past that point, so ill keep you posted.. but it looks (so far) like disabling the stats function fixed it.

And FWIW, pool is zpool.

I am having issues with your build of ccminer that's on post #1.

Right around share #54ish, three times in a row now;  ccminer crashes.   But it's not the share # causing it.   The last line of text in the window is sending stats to the pool/the pool requested my stats.   Since it crashed 3 times in a row, and all 3 the last line given was sending stats, I'm pretty sure there's a bug in the code related to maxwell cards (maybe requesting sensor data not available compared to pascal cards and there's some issue with handling that error?)


This machine has 3 Maxwell cards only.  2x, GTX960, and 1x GTX 980.

Anyone else getting the same problem?


I am attempting now to disable stats on that machine to see if the problem reproduces itself for a fourth time.


So far on my machine with one Pascal card (EVGA 1070), no issue with stats enabled and I have well over 100 shares accepted.  (zpool enables stats requests via a password string option, so it's easily disable-able)

of all the people in the world;  this would NOT be my problem FYI..... lol, if you only understood who you were asking this to...

All potential settings have been tried, from more or less in the PW string, to intensities of 3 all the way to 26.


but to humor the world:


*edit* tried a whole different PC today.   works like a champ.    Reloading the OS on this one machine.  No clue what the deal is.

Different versions/builds of ccminer and same problem....

The ANN specifically links the first version of ccminer I used..... so, I dont see how you reached your conclusion.

....even tried the version from minerx's github which provides the exact same error, except that version doesn't even give me the first valid share......

care to enlighten me to how you think its the wrong miner??

Apple's main "thing" from the beginning, and still today... has always been hardware... not software.   Thus the forcing devices such as macbook pro's, iphones, ipods.... into obsolescence.  My mother's macbook is a prime example to where in they pushed an OS update to it;  that literally broke it.  Not enough ram to boot.  No support for more system ram to upgrade.  She literally had to go buy a new model the other day.

This is a realistic thought to weigh in the assumption you are making....

Test card: EVGA GTX 1070

Miner app version: ccminer 2.2 signatumd skunk: https://github.com/signatumd/releases/blob/master/ccminer-2.2-skunk.zip

What happens is the first share is accepted by the pool fine.

Every single other one is rejected as an "invalid share".


Anyone else run into this issue?  Badly compiled miner app?

FYI visiting your download link directly in google chrome gives this, and i'm not sure why.  I don't remember seeing it when I went directly to github itself before:





*edit, visiting and clicking from github itself gives the same warning... so I am at a loss for words past my FYI.

agreed;  yet I havent tried ccminer 2.2 yet....

And the reason why skien is chosen, is because there are no ASICS for that algo;  and it has the highest hash to net-hash ratio compared to the other algos.

*edit*  I thought I was crazy and seeing double after posting this, but it seems I just matched you in post count citronick.... lol!

you aren't getting charged a 20% "fee".  Stop calling it that.  Its your imagination of what you "think" it should be....  so take a few steps backwards into reality-land.

Think about the cost of sending coins to the exchange; as well as the exchange's price to send the converted BTC back to the pool....   This is a small part of the situation that you simply ignore flat-out.  Think about how many times this is done per day... do you know?   I seriously doubt it... so how can you be so confident in your assumptions?


We keep trying to point out to you guys that continually scream that he is stealing (which I seriously doubt he is after all this time); you are not even considering all the variables when you make your assumptions, based on either incorrect data, or based on pure assumption alone to begin with.... not to mention the people who treat an estimate as a final sum.  That's not what an estimate is..... far from.


If you exchange the funds yourself;  do you just take the "sale" rate on the exchange, or do you hold out for your price point?    How many times a day do you need to pay yourself?    Etc Etc Etc....

Is this how the pool operates?


This fathomed 20-30% is quite intriguing to be frank.   I myself thought it was actually a problem once, and to be clear, I also felt there was a 20% discrepancy and voiced my opinion in the matter.  I then used my head and did the research on how the process works and what steps would/could/should be involved at a minimum.    I quickly learned that things aren't as I originally perceived and understood the error in my assumptions.  There is history of my personal experience with this issue in the original zpool thread.  Go read and see that I am not BS'ing you on that note.


Maybe one day you will do the same and think past the narrow data-set your mind seems to be locked to...


Also consider the notion that an extremely small percentage of users of zpool report such a "problem" with their "assumptions".   I'm willing to bet on just by calculating based upon regularly active wallet addresses over the last 6 months time;  that the percentage is less than 0.01% of people thinking they are getting ripped off.    And that's being very generous with the side of the ratio favoring the complainers.

Legendary veterans of this site (BCT) have yet to have any reported issues such as yours AFAIK..... and I know there are many that use zpool.

your recommendation is to not throw hashrate at coins?

isn't that exactly what kills coins in quite the same respects?