Regarding basic vs. advanced 1bash... I'd like to see it broken into three pieces. - I would love to see the logical functions in the 1bash; choices of logic and add-ons to use (or not, for basic.) Many of us would largely use the same settings on groups of rigs, but the file necessarily changes with every update.
- I would love to see the per-GPU and per-coin OC settings broken out into another stand-alone file; these all need to preserved between versions and rebuilds, but are completely unique to each rig. Persistent but local.
- I would love to see the Addresses, Workers, Pools, Ports section become a stand-alone file; these are all the same on all my rigs, and when I change any, I want to change them on all my rigs. These don't change for rebuilds or for upgrades and need to be copied every time. Persistent and global.
Just a thought. What do you think about CryptAtomeTrader44's idea and my thoughts on how to use it? https://bitcointalk.org/index.php?topic=1854250.msg23380597#msg23380597Would this work for you? I think the best idea would be to have separate conf file for each coin and place all those conf files in new folder. This conf file, lets say ETH.conf will have ETH wallet address, choice of workername, list of ETH pools, proper OC settings for ethash, choice of miner, new variable ALGO="ethash" I know that it will take a bit longer to edit all conf files for the coins you would like to mine, but it will be done only once per coin and it will be preserved during updates. The benefit of doing so is easy and non-confusing setup for newcomers, proper OC settings for the particular algo, easy addition of new coins - just add new coin.conf file. As proposed, having one conf file with all coin addresses, pools, miners and another file with all different algo OC settings won't help much in my opinion. All that will be left in 1bash would be choice of coin, choice to use switchers, temp control, watchdog, etc. I would also rename 1bash to settings.conf For easy addition of new coins, all we would have to add is new conf file with all the pertaining settings and the new ALGO variable. For example, we have all the logic for ETH (ethash) already in 3main. We want to add UBQ (also ethash). 3main reads the $COIN from 1bash then reads the $COIN.conf from the new folder where all the conf files are. Then reads the ALGO variable and apply the ethash logic to mine UBQ. This will also simplify 3main since it will have per algo instead of per coin logic. In rare case if particular algo logic could not apply to the new coin we can always ECHO new_logic > 3main to the end of 3main. Makes sence? Thoughts? totally agree with you, now it's a pain to switch from ETH to ZEC with individual.OC settings. |
|
|
|
I switched from ethermine to nanopool, because nanopool doesn't show stale shares, hahaha...  |
|
|
|
|
need a guide to build, use LLD database and run the wallet on raspberry pi.
|
|
|
|
|
I have the same issue.
Does ethermine pay stale shares? Nanopool says it pays for stale shares if they could produce an uncle. Unfortunately, nanopool doesn't show the stale/reject shares statistic.
|
|
|
|
|
I have the same issue, so I don't mine MONA. ZCoin is also profitable.
btw, the latest tpruvot ccminer has a new switch --submit-stale, did you try it?
|
|
|
|
|
Is it possible to run wallet on raspberry pi? I'm running signatumd on raspberry pi3 to stake SIGT.
|
|
|
|
|
do we need to increase memory clock for zcoin? I always set memory clock -500 for 1080ti, I cannot connect my rig to test it now.
|
|
|
|
|
which CPU do you use? G4560 works well on my nvidia rigs, is it fine with rx vega cards?
|
|
|
|
|
I'm going to build a 3*vega56 rig, how many RAM do I need, Is 8GB OK?
|
|
|
|
|
I don't think you need block time in the formula.
$/day = (hashrateMHs * block rewards *1,000,000 / difficulty) *60*60*24*ETH price.
|
|
|
|
Some ideas for WTM Auto Switch :
WTM AUTO SWITCH is best to set for current profit and current difficulty in whattomine.com as the other 3 whattomine.com options are only show what was in the past.
It is looking for top profitable coin at the moment which usually is the coin with most drop in difficulty.
First of all dont use too many coins as it will make too many switches and you lose time,
WTM auto switch has the option to compare the top coin with current mining coin with the given difference in percent to avoid too many switches for small profits shown.
switching to better coin is good but too many switches means too many miner restarts and each miner get some time to get to optimum speed some thing from 10 to 30 seconds.
So We have some options here.
I tried these 3 combos, each has their own pros and cons, you should try and see which one you like more.
1- Two top coins with no jumpers (10-15 % difference)
This one is the most stable option with least switches as top 10 coins usually dont change too much.
2- Two top coins with 1 jumper (10-15 % difference)
In this strategy jumper is use as a helper to switch between the 2 top coins, because usually those 2 dont get more than 10% difference
so when jumper goes to top from buttom it helps switcher pick the higher coin with less than 10% difference
3- One top coin with 1, 2 or 3 jumpers (20-40% difference)
In this scenario you mine your favorite top coin but when a jumper coin goes hot and drop big difficulty your miner start mining it until its difficulty goes high and become no more profitable
the high difference percent is to avoid jumpers to switch with each other too many times.
I'm sure there are lots of more combos to use, so please share with us your strategies and thoughts .
P.S: Latest WTM Auto Switch does not support multi algo specific overclock (damNmad awesome work) For Now, I'm Workin on to find a workaround for it.
So set damNmad_ALGO_SPECIFIC_OC="NO" and find a mid level OC to cover all the coins you chose to mine.
In the early days of my mining, I always thought that having a WTM switch kind of thing will be suffice to get better yield, but the trouble is WTM json covers only very minimum (probably the famous) on their site when you request for json result. If the whole purpose is to mine coins at low difficulty (or when difficulty dropped)! why can't we just mine and gamble the very new coins? HODL them until they get big? (don't need to completely mine them for days, a day or two should be fine). For eg; PIRL is another ethash coin where the yield by the time of writing this message is 130 odd coins per 100 MH (nearly $10 in fiat currency) B2B is another upcoming coin based on cryptonight, which is also a underrated coin! I know these may get famous or may be scrapped, but my point is even ETH/BTC/XMR also started just like the new coins, if we mine new coins for a day or two and hodl them, i think it would be a best bet on its day. This is just my opinion guys, please feel free to add your thoughts  I have already added almost more than 10 coins after 19.1 update, if anyone thing there is a new coin in the market which is worth of mining for a day or two please do let me know, i will add it to 1bash as well. agree, mine shitcoins and sell them daily. |
|
|
|
I built djm34's ccminer with Cuda9 and found that it was faster than tp ccminer on ZCOIN. If you can confirm that, use djm34's as default zcoin miner.
Would you be willing to share how you compiled? I got a bunch of "BIGNUM" errors when I tried to use -make. How do we upgrade to CUDA9? The instructions on their website didn't work for me: Installation Instructions: `sudo dpkg -i cuda-repo-ubuntu1604_9.0.176-1_amd64.deb` `sudo apt-key adv --fetch-keys http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64/7fa2af80.pub` `sudo apt-get update` `sudo apt-get install cuda` Thanks for your help. download openssl v1.0.2f from the offical website (look archive) then copy the file bn.h (from crypto directory) to /usr/local/include/openssl then try your last command (make or build) again. yes, fix bignum issue this way. for upgradibg to cuda9, I followed the guide in nvidia official website, it worked well, but took very long times. you also need to modify Makefile.am by hand, replace _20 and _21 with _30. Thanks that fixed the bignum error. I'm still getting errors though: nvcc fatal : Unsupported gpu architecture 'compute_60' Is that because of not having Cuda9? edit Makefile.am, replace _60 with _61 |
|
|
|
I built djm34's ccminer with Cuda9 and found that it was faster than tp ccminer on ZCOIN. If you can confirm that, use djm34's as default zcoin miner.
Would you be willing to share how you compiled? I got a bunch of "BIGNUM" errors when I tried to use -make. How do we upgrade to CUDA9? The instructions on their website didn't work for me: Installation Instructions: `sudo dpkg -i cuda-repo-ubuntu1604_9.0.176-1_amd64.deb` `sudo apt-key adv --fetch-keys http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64/7fa2af80.pub` `sudo apt-get update` `sudo apt-get install cuda` Thanks for your help. download openssl v1.0.2f from the offical website (look archive) then copy the file bn.h (from crypto directory) to /usr/local/include/openssl then try your last command (make or build) again. yes, fix bignum issue this way. for upgradibg to cuda9, I followed the guide in nvidia official website, it worked well, but took very long times. you also need to modify Makefile.am by hand, replace _20 and _21 with _30. |
|
|
|
|
looks great, I'll try it.
|
|
|
|
|
I built djm34's ccminer with Cuda9 and found that it was faster than tp ccminer on ZCOIN. If you can confirm that, use djm34's as default zcoin miner.
|
|
|
|
|
I've received the airdrop, but my waves balance is 0, is it normal?
10/6/2017 23:57:06 Incoming Transfer BTCG 3PBcX5ym*******2tg999 You 0.001 WAVES 3000.00000000
|
|
|
|
|
@ocminer
MONA dashboard doesn't show workers, please take a look at it, my user name in the pool is car1999
|
|
|
|
|
yes, I mined zcoin with tpruvot's ccminer.
I built the code easly, just run build.sh, haven't see your errors, maybe tpruvot know how to fix your build issue.
|
|
|
|
|
Show Posts
