I'm interested in mining SHA256 on multipool.us, but have some questions regarding Cryptsy integration. Previously I've mined Scrypt on multipools that automatically handle the exchange. I'm hoping to set up a similar kind of "set and forget" configuration because I don't have the time to manage or optimize the exchange process.
I've gone through the Cryptsy integration instructions, including using my API key to populate the wallet addresses in my multipool account. Not all the addresses got populated, but I think that all the SHA256 ones did (which is what I care about). I've also identified the SHA256 coins from the multipool stats page and enabled auto sell (second highest sell bid) for the corresponding coins in my Cryptsy account.
The question is how should I go about setting the autopay thresholds for the non-BTC SHA256 coins on the multipool side? It seems like if there is fluctuation in profitability, these values might become sub-optimal. Further, I'd be concerned that it would be possible for the pool to send to Cryptsy too often, which could be construed as an attack (according to other posts I've read).
Maybe when the Cryptsy integration level is "Full Auto", it handles the thresholds automatically, or otherwise throttles transfers to the exchange? Honestly I don't know what "Full Auto" does nor can I find information about it in the FAQ on the pool site, but I have it enabled for now.
The last question is regarding new coins. When new SHA256 coins are added (which is probably rare nowadays) I assume that any mined coins just sit in the multipool account until such time that I manually add a Cryptsy address. Does the pool notify me about this situation? It would be nice to get an email rather than have to pull the info about added coins from the news feed.
Thanks in advance for any help or suggestions.
Full auto does set the thresholds automatically, but it won't overwrite addresses or set thresholds for addresses that are already populated. You can set up your addresses and thresholds using full integration by deleting your addresses and saving full integration again.
On the help page, it lists the minimum withdraw threshold for each coin. These are in place to avoid overloading of exchanges.
You can also set daily pay which will send your coins once per day as long as your balance is over the threshold.
Thanks for getting back to me. Unfortunately I'm still a little confused.
Since I'm not quite ready to mine (the hardware hasn't arrived yet), I figured I have a little time to do a reset. So I deleted all the addresses and saved the full integration again. The resulting auto-pay thresholds seem odd. Several of the SHA256 coins went to zero for their threshold, which is less (obviously) than indicated on the help page.
Here's the list of the SHA256 coins, with the result of the reset in the second column and the help page suggestion in the third (EDIT: I missed three coins in the table):
Coin | Reset result | Help page |
FRC | 10 | 1 |
MYRH | 0 | 1 |
MZC | 0 | 1 |
PPC | 0.1 | 0.1 |
TRC | 1 | 1 |
UNB | 0 | 1 |
UNO | 0 | 0.001 |
ZET | 2 | 1 |
DVC | 10 | 1 |
IXC | 1 | 1 |
NMC | 1 | 0.1 |
I assume that zero is never correct for an auto pay threshold, even though that's what the saved full integration delivered for some of the coins.
So should I trust the full integration, but change any coins with a zero auto pay to the minimum in the help?
Just to be clear, I'm not interested in holding any of these non-BTC coins. I just want to efficiently get them into the exchange and sold without tripping over any problems with transfer minimums.
Thanks for your continued support.