please, look up and read.  This was just discussed.

The amount left over has to do with long-maturity coins....  if they take a long time to confirm, the same goes for selling on the exchange because it happens a lot later than the other coins get sold.

The only thing you can pick is:
1) what algo to mine
2) what coin to be paid in.


The rest, like what coin to mine; is automated and controlled by the stratum services.

three?  power pins?

The power on button location?

example password:

RigWorkerName,c=BTC,scrypt


Cheers!

Not a problem.  Simple mistakes can be the most annoying sometimes.

stratum+tcp://sha256.mine.zpool.ca:3333#xnsub
<BTC Wallet>
c=BTC,sha256

probably dead pool cause its not receiving an algo type flag in the password for the port you are connecting to, and its seeing BTC as a algo flag which is not available; and since sha256 was not on the list, it leaves the stratum line dead as to get you on the algo it wants you on.

Yeah, +1 to this.

More GPU's coming online (assuming at 1/4 of all just-hit-the-shelf 1080ti make it into a miner) the overall network hashrates will skyrocket, and the profitability will be divided up to the same ratio....    Just like the day the new A3's hit people's homes.  $400 the first day, $300 the second, etc.....

Hashrate saturation rears some teeth for sure.

I see erratic miner connections;  very few shares.

http://zpool.ca/?address=iSEYT4b5LZiRjCiJgAEoQsbZDQ6gRdxsME
right now shows a due balance of: 0.01334860 INN

So when it hits the required threshold and matches up with the payout schedule, you should get your payment.

You need to be patient;  lots of different coins take time to mature, then be sent to the exchange, then find a buyer, etc.  Things take time =)


are they high density or low density miners?  sounds like a stratum proxy on your end may be beneficial for both parties.    I have a feeling this may be some fallout from the people with a million low diff miners that flooded from the nicecrash.

yes, DGB address as username, password will be c=DGB

Ok guys, I now have a new and improved manual batch finally working with auto-updates functioning.

It's the same as the manual batch, but now comes with all miner apps, and can self-update itself as well as any miner apps as-necessary.

Trying to make this all one step easier for you guys.   I still have heaps to do like migrating to a github repository and whatnot, but here is the foundation work.


Such a nice feeling to push an update to my miners remotely now.


Enjoy

Click here for the thread and download links.

The link can also be found through the batch link in my signature.

Here it is finally.  This batch now has the ability to be updated remotely.  Designed in Windows 10.  Should work on Vista or later builds that have Powershell version >= 2.0.

I've hit a few speed bumps along the way but have finally been able to get a version that I can finally release that works as I expect it to.

Currently it's almost identical in function to the original manual farm control batch except for a few key points:

The miner package now has a name (mminer), and comes with all associated miner apps that I am presently using with it.
The batch can now update itself to a newly released version of the code; as well as download any needed/necessary miner applications required for the new updated version.
The batch now stores it's key variables in text files for ease of configuration and the ability to update the batch itself.


Please view README.txt in the application folder for more descriptions on the modifiable variables.


Future plans:
1) Incorporate the automatic algo switching functions into this batch.  So if for instance you would set your requested algo to be "auto", the miner would do the regular stratum controlled mining like my original automatic batch file does.   This is going to happen, but not started as of yet.
2) Add static variable for update URL for easier end-user updates; as well as disabling the update feature.
3) Get the project onto github for ease of file distribution as well as peace of mind.   My old tripod URL will only handle soo much traffic, and I know the second I have to upload a 30+Mb file to pass onto who knows how many miners;  things could get ugly quick.  I have not 100% fully tested a lack of internet connection to the miner, or lost connection at different times of the script running aside from updating.  Trying to figure out a reasonable amount of retires before starting over or simply bypassing the update features.
4) Add AMD Rx card support (Big thanks to phil for making this possible)
5) Combine all app variables into a single text file
6) Create auto-normalization script to only be run once;  This will only be for the automatic miner batch once its incorporated.  I am still considering making a template for each generation of card.  Looking for more user input on this.  My initial thoughts are to have the batch retrieve the hashrate results in a way that a 'grep' works in linux.  Currently researching Windows alternatives.


As always, I am always willing to update to a newer and better miner app;  just please provide me with a download link and the information about it (why its better, etc).   If it seems like the right route to go, I will incorporate it into an update to mminer after I get it tested for stability at least on one of my machines.

Download mminer 2.0 Here: https://mega.nz/#!VaYyib6Y!g5h51YtFFSOBwSl41ZxIXL1aVG9kakZ87dFGu98ZKj0

*NOTE:  If you are getting powershell errors and the miner never launches, download this updated mminer.bat, and replace the one in your mminer folder.  Should fix it.  If not, let me know.   This hotfix will be applied to all future versions: https://mega.nz/#!gPIj2BxK!DrKgS92Z68bdTCybLKVf8084AbLRjFO8QOgiXlELe_Y

Known issues:  
02/18/2018: Some ccminer variants included are not playing well with the new release of windows 10, or the new nvidia drivers.   I am seeking more versatile replacements for these apps.  Specifically ccminer180.exe.  In my next update, it will probably be superseded by ccminerxevan.exe as it has been working for me.

Mminer version history:
2.0:  Initial public release version.
1.9:  Final test of update to test heuristics. *was successful*
1.5:  First successful update
1.1:  second test update version
1.0:  Alpha version;  initial code for auto-updates

A link to the original batch and thread: Here.
A link to the second batch and thread: Here.
A link to the original manual control batch: Here.
A link to the xmr-stak-JK no-devfee build: Here.
A link to the system and app rebooter batch: Here.
A link to the internet connection monitor/restart batch: Here.

Donations not necessary but always welcomed: 1pz4yZ6DAjn4ho7x2FiEqE6VVEvefFxK9  I rarely check this address.

I just amazon or ebay the part number on the fan's sticker on its backside.

Then I spend ~$20-30 on the replacement fan(s) and put it/them on the card.

I bought a GTX980 brand new years back when the 980Ti wasn't released yet.    It's fans barely failed in November of last year.  Not bad for a GPU that was run at full load and 70+% fan speeds the entire time.  It earned the $ for its new fans.

2% is not .8


You are extremely mistaken in how the pool code works;  and doubly mistaken on how math works


Follow the code, and show us this is how it happens;   I bet you can't....  cause it isn't.


Tell me, which exchange were the coins sold on by the pool?  Cause it could be one of many.....

FWIW the first page of withdraw history of mine:
https://imgur.com/a/Ua9Ee

I suspect problems caused by stuck deposits and withdraws are probably non-normal circumstances;  such an example being the previous person mentioning the funds being a part of a smart contract feature this exchange doesn't use....

But;

There have been problems in the past.
So as with ANY 3rd party;  there's always some sort of blind trust from you that they will manage your inputs/outputs correctly and honestly.

crackfoo;  I am seeing two ninja coins on the nist5 port.  both have different blockheights and network diff?!?  Little confused here... lol

or just a one wire jumper between the main and secondary PSU's PS_ON line so they can be fully shut down if wanted.

pls.  seeing the wallet addresses in your account when clicking receive, etc... as well as seeing the pending lines below the accounts helps link the tx to the account.

Its a strange situation...

I dont understand why they would need a deposit to change a withdraw.   Usually a failed Tx, just gets dropped after some amount of hours/days and the system will re-send the tx...  but I have no clue how they configured their servers/service.

are you trying to withdraw to a new segwit address (not beginning with a 1 or 3)?  I could see this being an issue by guessing blindly...

but frankly;  it makes zero sense to need an incoming tx of .1 for any reason whatsoever..... to fix anything.



So let me try and straighten the details out:

https://blockchain.info/address/1GeW43Q1ZCsQJcYmgTaGBrYiAEXo2i4E7P

1GeW43Q1ZCsQJcYmgTaGBrYiAEXo2i4E7P is your personal wallet?  
or is it the exchange's wallet in your exchange account?

Assuming it's the exchange's address and you sent from: 1LfMRFEtGevbwiqeY3TLeHvrw6J6w9Jgm7
The tx of just over .1 was received as over .1....  so I am unsure why it could be seen to them as being less than .1


much confusion.    I'm in for more info;  hopefully I can help figure out whats going on.


My last withdraw of almost .1 went through just fine a few days ago.

https://imgur.com/a/WBAFg

*edit* simply wow.


I have no idea.... they never mentioned a fee for the system fucking up or anything.... or in the support requests considering they asked for .1, not .102, never mentioned a fee, etc.


I do not understand why.....    and, frankly, this is very disheartening to see it.... I am kind of at a loss for words.


Can you get any reasoning for the need to send a payment?  Can they explain it to you logically at all?  Because I see no logical reason to need a payment in order to get your payment.    They are seriously dropping the ball big time.    There's no excuse for this $hit.


So yeah.  I feel your pain right now for sure.....   

The moment I can get a part number for a card edge connector that can support the wattage;  Ill be drafting up a PCB which will be stupid simple.  Probably make it like the typical breakout boards you see;  maybe with a voltage readout, but probably bare and basic to keep costs down.    Should be able to happen with a simple single sided design, or at the worst with a double sided board.

At first I planned on scavenging the second half from an old AT 16 bit slot;  but its too much work to desolder, etc.... plus, i'm not sure how much wattage you would be able to cram through a connector from the 80's.


if you wanted to solder it properly, you would probably have to have a reflow table set near 200, and use a solder gun (like for automotive) to tin the contacts;  but those boards have THICK ass traces and eat up the heat pretty quick.  The other PSU I soldered to was even worse;  and it was fingers instead of a card-edge.    All the soldered cables, (including the PS_ON line) ended up just not adhering fully.  Removing that connector on the not pictured PSU;  I wasn't able to do because I lack the hot rework station and have no room at my home for one.

Hopefully I have time to revisit this in the next few months.
Working on rewriting my batches, daily life, taking care of my chameleon, trying to keep healthy/not bed ridden and keeping myself fed has been a chore in of itself... lol

use imgur;  its anonymous and quick   you can just post the pic links here.


Having trouble making sense of what you are saying...

The last several .01BTC tx's I have sent to yobit have been credited and used... so I am unsure why they are requiring a .1 minimum for anything.... some details of this situation are still eluding me.

I guess I do not understand what you mean by a partial payment.....   as all TX into the wallets are blind, and denomination independent....