is PING time to the pool really important?
"live" latency's for alot of miningpools: https://investoon.com/mining_pools/Not as important at prohashing.com as with other miningpools. Read "help"-section at prohashing.com about being paid for parts of "late"-work among other things.
|
|
|
System Uptime 16:58:33 up 1 day, 7:17, load average: 0.58, 0.51, 0.53
Memory Used 244796 kb / 250560 kb 98%
Memory Free 5764 kb / 250560 kb 2%
Cached Used 35448 kb / 58560 kb 61%
Cached Free 23112 kb / 58560 kb 39%
and I have rebooted it... (
When Innosilicon will clear this "issue"?
try prohashing.com and compare! you will not get that memoryproblem using them !
|
|
|
Try running on prohashing.com create account and set it up to payout in BTC or whatever you have today and/or want. do the following and compare results with earnings today.
Install one of the latest firmware's with speedsetting "performace+" available !
restore using factory reset
choose "performance+" in speed settings
it could be wise to try and set fans to 30% to get temps down for board 1
Info on howto do all this should be earlier in this thread.
good luck!
Thanks for your instructions for me performance or performance+ are the same both of them set mhz to 1248 and voltage to 170 and prohashing takes high fee 4.99%!! or isn't more profitability then nicehash or mining directly to pool? AS I said.. CHECK your earnings and COMPARE BECAUSE if you convert to BTC or any other it will be INSTANTANIOUSLY and PERHAPS board 1 will ASLO deliver HIGHER then 10KSols/s and whats the END RESULT compared to now !?!? I really do NOT care if you complain and given an alternative you chose NOT to test it out ! ! ! Don't waste my time!
|
|
|
I've updated the firmware and still fluctuating hash rates. I thinks it's my first board that never goes above 10KSol/s that may be the issues. If it ran as fast as the others I think I would always be close to 50KSol/s overall. Does anyone else have one card that much different from the other 2 cards? I had the same problem until I updated the firmware... no more issues with fluctuating hash rates. Hello,
I just setup my first A9 Zmaster. After 12 hours my hash rates range from 35 to 50, bouncing up and down. Does this ever stabilize?
Do I have a bad board? My first board never goes above 10KSol/s
Miner Info # Hash Rate Status Accepted Rejected HW Temperature 1 7.67 KSol/s Alive 357/21 416 64 ℃ 2 15.01 KSol/s Alive 703/7 64 65 ℃ 3 15.33 KSol/s Alive 751/3 58 63 ℃
Thanks,
Marc
Try running on prohashing.com create account and set it up to payout in BTC or whatever you have today and/or want. do the following and compare results with earnings today. Install one of the latest firmware's with speedsetting "performace+" available ! restore using factory reset choose "performance+" in speed settings it could be wise to try and set fans to 30% to get temps down for board 1 Info on howto do all this should be earlier in this thread. good luck!
|
|
|
Hello , iam having a problem i have apw7 bitmain psu and 2 miners using it, X3 and Z9 mini . but sometimes (mostly after 6 hours) z9 mini goes offline and i cant even connect to it via IP i just have to unplug it. Now its ok for 8.33hrs I cant even copy logs because its not accessible in web browser.. Please help. Thanks https://imgur.com/a/1o80Q4BWhat frequence are you running it on! If running to high it COULD be an explanation! to begin with... If Batch 1 try no more than 668 MHz If Batch 2 or 3 try no more than 637 MHz If problem not solved then go back to 500 MHz and try! If that not works reinstall firmware and "UNcheck settings". If that not works install newest firmware with "UNcheck settings" (you can always go back to may 26 firmware later. If problem not solved try running on the z9 mini on it's own apw7 and reconnect using the power connectors you today have running the X3. if that not works run with only board 1 if that not works run with only board 2 if that not works run with only board 3 If that not work setup solution like timer for controlling power and off after like 6 hours wait a minute and power on. And good luck!
|
|
|
I have miner from batch 2 and this firmware does not work properly on it - showing 0 degree temperatures causing fan speed 100%. I think this modification was made on latest firmware-batch 3, and efudds was made from previos firmware.
https://bitcointalk.org/index.php?topic=5041859.msg46952536#msg46952536This is for Z9 and NOT z9 mini !!! efudd's is for Z9 and NOT z9 mini !!!
|
|
|
Next time... Just buy it ! ![Wink](https://bitcointalk.org/Smileys/default/wink.gif) Sorry you missed it! Sorry I missed it !
|
|
|
While the "a=" password argument is traditionally used to select the algorithm for a miner, an algorithm-specific port can also be used. Algorithm-specific ports cause miners which connect to those ports to be automatically assigned the algorithm associated with the port upon connection. The "a=" password argument can still be used to override the port's algorithm. The port assignments are the following:
This only confused
Url and port OK
Workers and password pls
algorithm Lyra2REv2 port 3337 Z1 number 1 Pool 1: URL: stratum+tcp://prohashing.com:3337 Worker: your_login_name_at_prohashing.com Password: n=z1nr1 Z1 number 2 Pool 1: URL: stratum+tcp://prohashing.com:3337 Worker: your_login_name_at_prohashing.com Password: n=z1nr2 Z1 number 3 Pool 1: URL: stratum+tcp://prohashing.com:3337 Worker: your_login_name_at_prohashing.com Password: n=z1nr3 and so on ... (n=a_name_you_choose) I need Bitcoin directly payouts correct Settings: Payout proportions: Add Bitcoin Payout addresses: Set YOUR BTC payout address Set Tour threshold to Free Threshold (Default): 0.00236155 ($15.00) Click "Save" for "Payout Addresses" NOW Set Payout proportions for BTC to 100% (if thats what you want.) Click "Save" for "Payout proportions"
|
|
|
While the "a=" password argument is traditionally used to select the algorithm for a miner, an algorithm-specific port can also be used. Algorithm-specific ports cause miners which connect to those ports to be automatically assigned the algorithm associated with the port upon connection. The "a=" password argument can still be used to override the port's algorithm. The port assignments are the following:
This only confused
Url and port OK
Workers and password pls
algorithm Lyra2REv2 port 3337 Z1 number 1 Pool 1: URL: stratum+tcp://prohashing.com:3337 Worker: your_login_name_at_prohashing.com Password: n=z1nr1 Z1 number 2 Pool 1: URL: stratum+tcp://prohashing.com:3337 Worker: your_login_name_at_prohashing.com Password: n=z1nr2 Z1 number 3 Pool 1: URL: stratum+tcp://prohashing.com:3337 Worker: your_login_name_at_prohashing.com Password: n=z1nr3 and so on ... (n=a_name_you_choose)
|
|
|
How can configuration prohash to Z1
Help me
Url Address Password
https://bitcointalk.org/index.php?topic=4404847.msg47047579#msg47047579AND Model Zig Z1 from Dayun mining Lyra2REv2 algorithm AND Algorithm-Specific Ports While the "a=" password argument is traditionally used to select the algorithm for a miner, an algorithm-specific port can also be used. Algorithm-specific ports cause miners which connect to those ports to be automatically assigned the algorithm associated with the port upon connection. The "a=" password argument can still be used to override the port's algorithm. The port assignments are the following: Algorithm Port Scrypt 3333 X11 3334 SHA-256 3335 Equihash 3336 Lyra2REv2 3337Neoscrypt 3338 Ethash 3339 Quark 3340
|
|
|
Hey guys finally got my miner up and running for only 2 hours and it seems like it's too hot? It says 88* farenheit. Is it not displaying properly or is there something wrong with the miner? Chan 1 is 111 degrees farenheit Chan 2 is 115 degrees Chan 3 is 117 degrees Chan 4 is 118 degrees And core is 88 degrees farenheit
is that hot? https://www.google.se/search?q=88+degrees+farenheit
|
|
|
has this miner been overclocked yet? what are the results?
No OC so far ... ( or no one say it ! ) Choosing : Performance+ (in Settings - Performance) Thats it AFAIK ! No difference between the modes... nothing :| find best miningpool! try prohashing.com
|
|
|
Hi,
I have doing all of it, reburn key again and again, but always the same thing, can't save the setting.
Do you know where i can change the zig z1 factory setting directly in files tree. perrhaps i can start in doing that without pass by http.(but it don't fix and understanding the pb) but if it work it's ok for me in a first time.
thx for help
Stupid question perhaps: Are you logged in as administrator/root with the rights to write to filesystem that includes ? In the video I can se how they choose something in a menu far to the right BEFORE the can change ip and save ! You also have the threads to people who posted firmware and video. Perhaps ask them because as I said, I don't have one myself and don't know anybody who has! Good luck!
|
|
|
One question ?
Did YOU add in router dhcp lease 192.168.1.4 for the dayun when the router says there already are a valid lease for it at 192.168.1.100 AND the dauym is set to static ip 192.168.1.100 ? ? ?
That will not help!
remove your added 192.168.1.4 and restart router.
|
|
|
Hello, I have a pb for setting my zig z1, i just receive my miner 3 days ago and i've had lot difficulty for booting it, i have finally starting the mining for 12 hours and after that , i have moved the miner for starting production. But this is the big problem, when i have reconnected the miner my setting has been lost and now, I can't set the miner again, i don't know why, but the setting don't save and stay on factory. I have burning firmware again on key, reset miner and router, setting network again, but always the same thing, Unable to save pool adress and new ip (all setting page don't save). I have access to sftp (find the root password in other thread) so, anyone can help me to find why the setting don't want to save after just an electricity disconect and reconnect. I have seen on server and it's cake php used with sqlite, i have access to error log. Just tell me what you need for helping me, i search before 2 days ago and don't find why it don't work. I go take some screenshot for give you more information and post here. My Os Is windows 10, router livebox (Orange fr) and a switch. Miner zig z1 not zig z1+ Thx in advance for helping me. Router setting: https://nsm09.casimages.com/img/2018/10/19//1810190458481137515951718.pnghttps://nsm09.casimages.com/img/2018/10/19//1810190458471137515951717.pngAdvanced IP scanner: https://nsm09.casimages.com/img/2018/10/19//1810190507061137515951728.pngSetting stay like this, can't change anything: https://nsm09.casimages.com/img/2018/10/19//1810190510271137515951737.pngOk, i just change setting and clic save, after i go on Var/www/html/logs And this is the last error in file error.log 2018-10-19 23:00:25 Warning: Warning (512): _cake_model_ cache was unable to write 'default_settings' to Cake\Cache\Engine\FileEngine cache in [/var/www/html/vendor/cakephp/cakephp/src/Cache/Cache.php, line 286] Request URL: /api/dashboard-charts Referer URL: http://192.168.1.5/Client IP: 192.168.1.142 Trace: Cake\Error\BaseErrorHandler::handleError() - CORE/src/Error/BaseErrorHandler.php, line 153 Cake\Cache\Cache::write() - CORE/src/Cache/Cache.php, line 286 Cake\Database\Schema\CachedCollection::describe() - CORE/src/Database/Schema/CachedCollection.php, line 66 Cake\ORM\Table::getSchema() - CORE/src/ORM/Table.php, line 532 Cake\ORM\Query::addDefaultTypes() - CORE/src/ORM/Query.php, line 211 Cake\ORM\Query::__construct() - CORE/src/ORM/Query.php, line 168 Cake\ORM\Table::query() - CORE/src/ORM/Table.php, line 1582 Cake\ORM\Table::find() - CORE/src/ORM/Table.php, line 1182 App\Model\Table\SettingsTable::getSetting() - APP/Model/Table/SettingsTable.php, line 100 App\Controller\AppController::initialize() - APP/Controller/AppController.php, line 61 App\Controller\ApiController::initialize() - APP/Controller/ApiController.php, line 18 Cake\Controller\Controller::__construct() - CORE/src/Controller/Controller.php, line 263 ReflectionClass::newInstance() - [internal], line ?? Cake\Http\ControllerFactory::create() - CORE/src/Http/ControllerFactory.php, line 45 Cake\Http\ActionDispatcher::dispatch() - CORE/src/Http/ActionDispatcher.php, line 90 YiQuLian\Framework\Application\Application::__invoke() - ROOT/yiqulian/Framework/Application/Application.php, line 74 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Slince\Pjax\Middleware\PjaxMiddleware::__invoke() - ROOT/vendor/slince/cakephp-pjax/src/Middleware/PjaxMiddleware.php, line 52 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 YiQuLian\Framework\Middleware\ApiDetectorMiddleware::__invoke() - ROOT/yiqulian/Framework/Middleware/ApiDetectorMiddleware.php, line 30 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 YiQuLian\Framework\Middleware\LocaleMiddleware::__invoke() - ROOT/yiqulian/Framework/Middleware/LocaleMiddleware.php, line 16 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Routing\Middleware\RoutingMiddleware::__invoke() - CORE/src/Routing/Middleware/RoutingMiddleware.php, line 104 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Routing\Middleware\AssetMiddleware::__invoke() - CORE/src/Routing/Middleware/AssetMiddleware.php, line 88 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Error\Middleware\ErrorHandlerMiddleware::__invoke() - CORE/src/Error/Middleware/ErrorHandlerMiddleware.php, line 98 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Http\Runner::run() - CORE/src/Http/Runner.php, line 51 Cake\Http\Server::run() - CORE/src/Http/Server.php, line 81 [main] - ROOT/webroot/index.php, line 40 I don't have one, but... 1. it seems you can export your settings to a file (se bottom of settings) 2. WHY are pool settings addresses pointing to your home network and not pointing to different miningpools on the Internet ? ? ? 3. How come your ipscan show dayun at 192.168.1.5 address but in settings it's set to 192.168.1.100 ? ? ? 4. timezone settings ?
|
|
|
has this miner been overclocked yet? what are the results?
No OC so far ... ( or no one say it ! ) Choosing : Performance+ (in Settings - Performance) Thats it AFAIK !
|
|
|
Do any of my fellow Z9 miners know why?
why what?
|
|
|
I switched my Z9 minis (6) about 2 weeks ago, and happy with BTC :-)
are you saying that your z9's mine zcash and prohashing pays you in btc? At prohashing you can mine zcash only or even better multiswitch between coins for equihash algorithm and you choose which other coins you wan't it converted to like BTC and or LTC and or ... You set this in "settings". The conversion is done at once. You follow this "live" under "earnings". i really like the idea of prohash but i looked and they are giving 13 cents per kwh. a z9 mini at 10 sols = 1.30 perday. what am i missing? They don't pay per kwh ! And what does the pool you use pay per kwh ? what am I missing ? And how many in this forum runs their z9 mini's at 10ksol/s ? Prohashing.com - Expected payouts - Equihash - All time https://imagebin.ca/v/4JcEOoqErUEk![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fimagebin.ca%2Fv%2F4JcEOoqErUEk&t=663&c=hbwMJjV-QeagPA) Prohashing.com - Expected payouts - Equihash - Last 7 days https://imagebin.ca/v/4JcErr5gyG4g![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fimagebin.ca%2Fv%2F4JcErr5gyG4g&t=663&c=8irt487hzwtb2w) go to https://prohashing.com/ and check for yourself plus, i was giving an example of 10ksols to keep it simple ass. i have 200 z9's and spend everyday at my farm tweaking the sols so shut your small pie hole. To begin with... If you take that tone against someone trying to help and answer your questions, then just f_ck off!!!
IF you would READ: https://prohashing.com/help.htmlYou would SEEEEE this: "Make the Most Money Possible Prohashing not only merge mines coins, but distributes users among different coin networks with a custom algorithm that prevents mined coins from crashing in value or soaring in difficulty. Prohashing monitors every coin with every price change and every new block. The algorithm recalculates profitability multiple times per second, ensuring that the pool is always mining the most profitable coin using the most up to date information. Our debt to you is locked in the coin you choose at the time of earning, so you have no risk if the coins we mine with your hashrate decline in value." AND THIS: "Get Paid in Any Coin Choose to be paid in Bitcoins, Litecoins, Dogecoins, Ethereum, Monero, DASH, and over 200 other coins, or have fractions of your income distributed across several payout coins. Other multipools only allow payout in one coin at a time. Our simple system allows you to be paid in the coin you want to be paid" AND THIS: "Work Restart Optimization Prohashing's system considers network latency and "spin up" time in computing the optimal coin for your miners to mine. Some ASICs incur a significant delay after a block is found, during which they perform no mining. This delay can make mining coins with short block times unprofitable for such miners. Prohashing tests your miner and determines the most profitable coin for your specific hardware. Prohashing also automatically determines how many coins to merge mine so that work restarts don't cause losses in primary coin profitability." AND THIS: "c" (setting a specific coin) (If you set this without m=solo mining mode you miss out on prohashing multiswitching) "Since the purpose of static coin mining is to allow customers to mine on a single network, static coin mining is limited to one coin per IP address per period of time. The amount of time required between mining a static coin and being allowed to switch to the next coin varies. Prohashing's terms of service prohibits the creation of automatic software to switch between static coins, because doing so may reduce the profitability of dynamic coin miners. Manually configuring software to mine one static coin for long periods of time is allowed." AND THIS: "m" (setting mining mode) (m=solo mode requires "c=" setting of a specific coin for the algorithm in question) "Sets the mining mode. There are two valid values, "pps" and "solo." "pps" is the default if this argument is omitted, and operates this worker in the normal "pay per share" mode. When "m=solo," the worker functions as a solo miner for this network. It mines at the network difficulty, and each hash is either too easy, or it is a found block. No money is earned for shares that do not find blocks. When blocks are found by this worker, the account is credited with 97.01% of the entire (block reward + transaction fees) for the found block. Merge-mined blocks in solo mode are still paid per share whether you find a solo block or not. In solo mode you should notice that you are continually receiving small amounts of earnings in the primary coin even when you haven't yet found find any blocks. This is due to others finding merge-mined blocks. It's estimated that by the time a user finds a merge-mined block themselves, they will have earned 95.01% of that merge-mined blocks rewards over time in pay per share mode of other merge mined blocks. This percentage will be less if you found a solo block sooner than expected, or more if it took longer than expected to find a solo block due to luck. Pool fees for "solo" mode (2.99%) are lower because the variance is passed onto the miner, and because fewer transaction fees, exchange fees, and other business expenses are incurred. Solo mode provides a simple way to set up miners to support a particular coin network and solo mine without having to install and connect a coin daemon, or go through complex pool setup yourself. Solo mode also provides greater profit than does setting up a single-coin pool because you receive bonuses from coins that were merge-mined. Merge mining usually earns about 5-10% of primary coin mining, so using solo mode at Prohashing will average about 110% of earnings expected with a single-coin pool. When using "solo" mode, payout proportions are ignored for this worker. Merge-mining profits for solo mining are credited immediately. Profits for the primary coin are not credited until the block is confirmed. Some networks require as long as 720 blocks for confirmation, so confirmation time can range between 5 minutes and 3 days. Because solo mining passes on the variance to the miner, orphaned blocks are not credited to earnings. The "c=" parameter must be present to use "m=solo." If c= is not present or if the specified coin does not exist, then this argument will be ignored. If the target coin is not enabled for payouts or is in error, the worker will be disconnected so that it can fail over to a backup pool." AND THIS: "Accomplishing Specific Goals: - To earn as much money as possible: Use no password arguments other than the "n=" argument, which specifies a worker name. The mining software contains a lot of code to detect miner settings and can usually do a better job at optimizing mining than a human can. - In lieu of setting up a pool for your new coin: Use "c=[coin name] m=solo." These arguments are equivalent to installing a daemon on your local computer, and earn more profit than local solo mining because merge-mining rewards are also credited to your account. - To support a coin network without as much risk: Use "c=[coin name]" and set payout proportions to 100% in that coin. In contrast to "solo mode," mining in PPS mode provides constant rewards even if your miner finds no blocks, and still earns merge-mining rewards, in exchange for a higher fee. - Working around KNC Titan limitations: Use "h=3" or "h=5." KNC Titans exhibit poor performance with easy coins that have frequent blocks." AND THIS: "Suboptimal Shares Prohashing has implemented an algorithm to reduce the effect of stale shares as much as possible, even for users with slower internet connections. Since the pool merge-mines coins, and because each network changes blocks at different intervals requiring a work restart each time, the number of work restarts increases in proportion to the number of merge mined coins. Without intervention, the increase in work restarts would increase the number of stale shares, negating much of the advantage of merge mining. To combat this issue, Prohashing allows suboptimal shares to be submitted. In the case of a suboptimal share, instead of completely rejecting the share because the hash for one of the coins was invalid, the pool credits you for the coins for which your work was valid. For example, if you are merge mining CHNcoin and Dogecoin, CHNcoin has a new block while Dogecoin does not, and then you submit an otherwise stale share, you will still be credited for the work on the Dogecoin network since that hash is still valid for Dogecoin. Accepting suboptimal shares allow miners to earn some money for shares that other pools would outright reject. The only time you will see a stale share with Prohashing is when all coins mined have changed blocks before your miner submits a share. You can spot suboptimal shares in your earnings when you see a share where only one coin was mined. You can reduce suboptimal shares the same way you reduce stale shares - by improving the miner's internet connection." AND THIS: "Orphan Bonuses Prohashing provides orphan bonuses, a technique that reduces the pool's rate of orphaned blocks. It is a variation of a system called "selfish mining," which is used by pool operator Clevermining. While selfish mining is not optimal for pools that mine multiple coins, the orphan bonus variation allows Prohashing to increase profitability. In orphan bonus mining, miners receive increased payouts whenever one of Prohashing's blocks is orphaned. The payout for the next block is equal to the value of the previous block at the current price plus the value of the current block. Prohashing attempts to mine the next block on top of its previous orphaned block, therefore earning both the previous block's income and the current block's income if the current block is found. If the second block is also orphaned, then the expected value of the next block will be around three times normal. Miners end up being paid more, and the orphan rate of the pool is reduced, therefore making the coin more likely to be mined in the future. The profitability of a coin in all Prohashing charts is automatically adjusted for the orphan mining state, if it is present. No miner action is required to take advantage of this feature" WHAT DID YOUR 200 Z9 mini's earn: october 15 and 16 WHAT WOULD YOUR EARNINGS BEEN AT PROHASHING.COM ? Prohashing.com - Expected payouts - Equihash - Last 7 days https://imagebin.ca/v/4JcErr5gyG4g![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fimagebin.ca%2Fv%2F4JcErr5gyG4g&t=663&c=8irt487hzwtb2w) It WILL vary from day to day ! ! ! ! ! Donations: Bitcoin (BTC): 1HY5ZvPvx3fx5iA5cQKjw9ZuArse2STuCb Litecoin (LTC): LZPmxZdoe8ZNL8av5CkPPBEEBJVdoFQbS6 Zcash (ZEC): t1d35jvkzKcWybpCqojZmgDZkcFC7iBwe8w Monero (XMR): 48gVGMbZsAD5xtbpEpBKTJiDz6uMrnkTxjMcJGGFtore7i7wckSqmvYKfPVGQGab6U9kK76nGa91fhL SDvPfK4bYKkJaXeW dont be mad that i said what i did to your boy friend. give it up, he/she/it made the first attack...what , are you a snowflake? A snowflake would have been triggered ! Do you FEEL triggered ? ![Kiss](https://bitcointalk.org/Smileys/default/kiss.gif) You could also make donations by pointing your 200 z9 mini's to me: Just follow my instructions: Z9 mini number 1 Pool 1: URL: stratum+tcp://prohashing.com:3336 Worker: imine2 Password: n=thanksforallhardwork001 Z9 mini number 2 Pool 1: URL: stratum+tcp://prohashing.com:3336 Worker: imine2 Password: n=thanksforallhardwork002 . . Z9 mini number 200 Pool 1: URL: stratum+tcp://prohashing.com:3336 Worker: imine2 Password: n=thanksforallhardwork200 And thanks in advance ![Kiss](https://bitcointalk.org/Smileys/default/kiss.gif) nah, half pointed to zcash, some zen, and a bunch towards pirate...look me up tough guy ![Kiss](https://bitcointalk.org/Smileys/default/kiss.gif) nah, I don't do safespaces ! ![Wink](https://bitcointalk.org/Smileys/default/wink.gif)
|
|
|
I switched my Z9 minis (6) about 2 weeks ago, and happy with BTC :-)
are you saying that your z9's mine zcash and prohashing pays you in btc? At prohashing you can mine zcash only or even better multiswitch between coins for equihash algorithm and you choose which other coins you wan't it converted to like BTC and or LTC and or ... You set this in "settings". The conversion is done at once. You follow this "live" under "earnings". i really like the idea of prohash but i looked and they are giving 13 cents per kwh. a z9 mini at 10 sols = 1.30 perday. what am i missing? They don't pay per kwh ! And what does the pool you use pay per kwh ? what am I missing ? And how many in this forum runs their z9 mini's at 10ksol/s ? Prohashing.com - Expected payouts - Equihash - All time https://imagebin.ca/v/4JcEOoqErUEk![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fimagebin.ca%2Fv%2F4JcEOoqErUEk&t=663&c=hbwMJjV-QeagPA) Prohashing.com - Expected payouts - Equihash - Last 7 days https://imagebin.ca/v/4JcErr5gyG4g![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fimagebin.ca%2Fv%2F4JcErr5gyG4g&t=663&c=8irt487hzwtb2w) go to https://prohashing.com/ and check for yourself plus, i was giving an example of 10ksols to keep it simple ass. i have 200 z9's and spend everyday at my farm tweaking the sols so shut your small pie hole. To begin with... If you take that tone against someone trying to help and answer your questions, then just f_ck off!!!
IF you would READ: https://prohashing.com/help.htmlYou would SEEEEE this: "Make the Most Money Possible Prohashing not only merge mines coins, but distributes users among different coin networks with a custom algorithm that prevents mined coins from crashing in value or soaring in difficulty. Prohashing monitors every coin with every price change and every new block. The algorithm recalculates profitability multiple times per second, ensuring that the pool is always mining the most profitable coin using the most up to date information. Our debt to you is locked in the coin you choose at the time of earning, so you have no risk if the coins we mine with your hashrate decline in value." AND THIS: "Get Paid in Any Coin Choose to be paid in Bitcoins, Litecoins, Dogecoins, Ethereum, Monero, DASH, and over 200 other coins, or have fractions of your income distributed across several payout coins. Other multipools only allow payout in one coin at a time. Our simple system allows you to be paid in the coin you want to be paid" AND THIS: "Work Restart Optimization Prohashing's system considers network latency and "spin up" time in computing the optimal coin for your miners to mine. Some ASICs incur a significant delay after a block is found, during which they perform no mining. This delay can make mining coins with short block times unprofitable for such miners. Prohashing tests your miner and determines the most profitable coin for your specific hardware. Prohashing also automatically determines how many coins to merge mine so that work restarts don't cause losses in primary coin profitability." AND THIS: "c" (setting a specific coin) (If you set this without m=solo mining mode you miss out on prohashing multiswitching) "Since the purpose of static coin mining is to allow customers to mine on a single network, static coin mining is limited to one coin per IP address per period of time. The amount of time required between mining a static coin and being allowed to switch to the next coin varies. Prohashing's terms of service prohibits the creation of automatic software to switch between static coins, because doing so may reduce the profitability of dynamic coin miners. Manually configuring software to mine one static coin for long periods of time is allowed." AND THIS: "m" (setting mining mode) (m=solo mode requires "c=" setting of a specific coin for the algorithm in question) "Sets the mining mode. There are two valid values, "pps" and "solo." "pps" is the default if this argument is omitted, and operates this worker in the normal "pay per share" mode. When "m=solo," the worker functions as a solo miner for this network. It mines at the network difficulty, and each hash is either too easy, or it is a found block. No money is earned for shares that do not find blocks. When blocks are found by this worker, the account is credited with 97.01% of the entire (block reward + transaction fees) for the found block. Merge-mined blocks in solo mode are still paid per share whether you find a solo block or not. In solo mode you should notice that you are continually receiving small amounts of earnings in the primary coin even when you haven't yet found find any blocks. This is due to others finding merge-mined blocks. It's estimated that by the time a user finds a merge-mined block themselves, they will have earned 95.01% of that merge-mined blocks rewards over time in pay per share mode of other merge mined blocks. This percentage will be less if you found a solo block sooner than expected, or more if it took longer than expected to find a solo block due to luck. Pool fees for "solo" mode (2.99%) are lower because the variance is passed onto the miner, and because fewer transaction fees, exchange fees, and other business expenses are incurred. Solo mode provides a simple way to set up miners to support a particular coin network and solo mine without having to install and connect a coin daemon, or go through complex pool setup yourself. Solo mode also provides greater profit than does setting up a single-coin pool because you receive bonuses from coins that were merge-mined. Merge mining usually earns about 5-10% of primary coin mining, so using solo mode at Prohashing will average about 110% of earnings expected with a single-coin pool. When using "solo" mode, payout proportions are ignored for this worker. Merge-mining profits for solo mining are credited immediately. Profits for the primary coin are not credited until the block is confirmed. Some networks require as long as 720 blocks for confirmation, so confirmation time can range between 5 minutes and 3 days. Because solo mining passes on the variance to the miner, orphaned blocks are not credited to earnings. The "c=" parameter must be present to use "m=solo." If c= is not present or if the specified coin does not exist, then this argument will be ignored. If the target coin is not enabled for payouts or is in error, the worker will be disconnected so that it can fail over to a backup pool." AND THIS: "Accomplishing Specific Goals: - To earn as much money as possible: Use no password arguments other than the "n=" argument, which specifies a worker name. The mining software contains a lot of code to detect miner settings and can usually do a better job at optimizing mining than a human can. - In lieu of setting up a pool for your new coin: Use "c=[coin name] m=solo." These arguments are equivalent to installing a daemon on your local computer, and earn more profit than local solo mining because merge-mining rewards are also credited to your account. - To support a coin network without as much risk: Use "c=[coin name]" and set payout proportions to 100% in that coin. In contrast to "solo mode," mining in PPS mode provides constant rewards even if your miner finds no blocks, and still earns merge-mining rewards, in exchange for a higher fee. - Working around KNC Titan limitations: Use "h=3" or "h=5." KNC Titans exhibit poor performance with easy coins that have frequent blocks." AND THIS: "Suboptimal Shares Prohashing has implemented an algorithm to reduce the effect of stale shares as much as possible, even for users with slower internet connections. Since the pool merge-mines coins, and because each network changes blocks at different intervals requiring a work restart each time, the number of work restarts increases in proportion to the number of merge mined coins. Without intervention, the increase in work restarts would increase the number of stale shares, negating much of the advantage of merge mining. To combat this issue, Prohashing allows suboptimal shares to be submitted. In the case of a suboptimal share, instead of completely rejecting the share because the hash for one of the coins was invalid, the pool credits you for the coins for which your work was valid. For example, if you are merge mining CHNcoin and Dogecoin, CHNcoin has a new block while Dogecoin does not, and then you submit an otherwise stale share, you will still be credited for the work on the Dogecoin network since that hash is still valid for Dogecoin. Accepting suboptimal shares allow miners to earn some money for shares that other pools would outright reject. The only time you will see a stale share with Prohashing is when all coins mined have changed blocks before your miner submits a share. You can spot suboptimal shares in your earnings when you see a share where only one coin was mined. You can reduce suboptimal shares the same way you reduce stale shares - by improving the miner's internet connection." AND THIS: "Orphan Bonuses Prohashing provides orphan bonuses, a technique that reduces the pool's rate of orphaned blocks. It is a variation of a system called "selfish mining," which is used by pool operator Clevermining. While selfish mining is not optimal for pools that mine multiple coins, the orphan bonus variation allows Prohashing to increase profitability. In orphan bonus mining, miners receive increased payouts whenever one of Prohashing's blocks is orphaned. The payout for the next block is equal to the value of the previous block at the current price plus the value of the current block. Prohashing attempts to mine the next block on top of its previous orphaned block, therefore earning both the previous block's income and the current block's income if the current block is found. If the second block is also orphaned, then the expected value of the next block will be around three times normal. Miners end up being paid more, and the orphan rate of the pool is reduced, therefore making the coin more likely to be mined in the future. The profitability of a coin in all Prohashing charts is automatically adjusted for the orphan mining state, if it is present. No miner action is required to take advantage of this feature" WHAT DID YOUR 200 Z9 mini's earn: october 15 and 16 WHAT WOULD YOUR EARNINGS BEEN AT PROHASHING.COM ? Prohashing.com - Expected payouts - Equihash - Last 7 days https://imagebin.ca/v/4JcErr5gyG4g![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fimagebin.ca%2Fv%2F4JcErr5gyG4g&t=663&c=8irt487hzwtb2w) It WILL vary from day to day ! ! ! ! ! Donations: Bitcoin (BTC): 1HY5ZvPvx3fx5iA5cQKjw9ZuArse2STuCb Litecoin (LTC): LZPmxZdoe8ZNL8av5CkPPBEEBJVdoFQbS6 Zcash (ZEC): t1d35jvkzKcWybpCqojZmgDZkcFC7iBwe8w Monero (XMR): 48gVGMbZsAD5xtbpEpBKTJiDz6uMrnkTxjMcJGGFtore7i7wckSqmvYKfPVGQGab6U9kK76nGa91fhL SDvPfK4bYKkJaXeW dont be mad that i said what i did to your boy friend. give it up, he/she/it made the first attack...what , are you a snowflake? A snowflake would have been triggered ! Do you FEEL triggered ? ![Kiss](https://bitcointalk.org/Smileys/default/kiss.gif) You could also make donations by pointing your 200 z9 mini's to me: Just follow my instructions: Z9 mini number 1 Pool 1: URL: stratum+tcp://prohashing.com:3336 Worker: imine2 Password: n=thanksforallhardwork001 Z9 mini number 2 Pool 1: URL: stratum+tcp://prohashing.com:3336 Worker: imine2 Password: n=thanksforallhardwork002 . . Z9 mini number 200 Pool 1: URL: stratum+tcp://prohashing.com:3336 Worker: imine2 Password: n=thanksforallhardwork200 And thanks in advance ![Kiss](https://bitcointalk.org/Smileys/default/kiss.gif)
|
|
|
|