2907
|
Alternate cryptocurrencies / Pools (Altcoins) / Re: █▓▒░-< [ZPOOL.CA][BTC Multipool] The miners multipool >-░▒▓█ Decred (DCR) Mining
|
on: March 25, 2016, 11:41:22 AM
|
Hi there! Where is a support? Long time my payout not paid! Why? Payouts are made automatically every 3 hours for all balances above 0.0025 and balances less than 0.0001 are paid on Sunday. LfA2MSMLj8vpGdrD3CVhaGxXLVtNhLh8cT 0.01041090 LTC Support, please ask and help me. Asked and answered before and listed on the main page on how payouts work. ZPOOL From the makers of www.xpool.ca we bring you zpool - the miners multipool! No registration is required, payouts are made to the BTC address you mine with as your username. Payouts are made automatically every 3 hours for all balances above 0.0025 and balances less than 0.0001 are paid on Sunday. There is an initial delay before the first payout as coins you mine need to mature then, exchange and get returned to zpool, please wait at least 24 hours before asking for support. My balance is bigger than 0.0025 LTC !!!? I know my problem. Now LTC not mined in zpool. But when i was mined that balance, LTC was included in list of mined coins in scrypt algo. Very sorry. What can i do now? If we continue to get more hash, we'll switch it back on again. Needs to be about 12Gh+ consistantly
|
|
|
2916
|
Alternate cryptocurrencies / Pools (Altcoins) / Re: █▓▒░-< [ZPOOL.CA][BTC Multipool] The miners multipool >-░▒▓█
|
on: March 22, 2016, 09:44:14 PM
|
But I wish he would show real time too. Like all YAAMP forks, zpool offers an api readout for all their algos, which gives current estimates. Not exactly the easiest to parse for a human, but great for a machine; which is what you should have handling switching for you unless you want to spend all day watching profitabilities go up and down. We now have per currency api as well. Not sure if it would help much, but for those looking for some more info to plug into whatever www.zpool.ca/api/currenciesPut it into http://jsonlint.com/ and it's more legible. Also just noticed the "estimate_last24h" , is not the "last" 24h, it should be what we project in the next 24h... I'll fix that.
|
|
|
|