 Show Posts
|
|
Pages: [1]
|
Is there a way to specify an address when solo POW mining? I know it'll take a while for my wallet to run out of keys, but I'd rather not have to worry about it, since I share the wallet with a few computers. I'm thinking of using one address for each computer, so I can easily identify which one mined the block.
Thanks!
Unfortunately no, there is no way to specify the actual key. You would need to run a modified version that picks a specific key from the keypool in the miner (or creates a wallet with one key when the wallet.dat is created). Since we are based on Dash, we create something like 1000 keys when we create the wallet.dat file and the miner uses the next one in the keypool. EDIT: Just to mention however, I recommend PODC mining. It pays approx 10* better than heat mining. Heat mining is just a stipend for our block security. Thanks for confirming this! I do have most of my power running BOINC tasks; only 1 wallet is on 24/7 for the PODC updates, with genproclimit=1, and another wallet that's on for 8-10 hours a day, plus a couple of computers that are on so rarely that it can't complete BOINC tasks before they expire. However, I have gotten 5 blocks in the last 4 days (one actually that just happened as I'm typing this) solo POW, so I worry that I'm on a fork or something, but I checked some of the recent blocks I mined, and they were on 2 of the block explorers. I did a reindex earlier, but is there something else I can do to make sure I'm on the correct chain? |
|
|
|
|
Is there a way to specify an address when solo POW mining? I know it'll take a while for my wallet to run out of keys, but I'd rather not have to worry about it, since I share the wallet with a few computers. I'm thinking of using one address for each computer, so I can easily identify which one mined the block.
Thanks!
|
|
|
|
In case anyone's wondering, unlike setting priority or limiting the number of threads, BES will actually limit the process CPU usage, so if I have 4 threads running on my 4-core i5, setting BES to limit 50% will cause the miner to consume 50% total CPU with all 4 threads, which will typically be 50% usage on each core. Something I noticed with the way I set my miners' process priorities (I'm using TaskInfo persistent priority) is that the miners' threads still run at priorities higher than 1 (like 3 or 4,) which causes a problem with certain software I'm running that have threads at priority 1 for some reason. Instead of dedicating an entire core to this stupid software, I can just limit my miner by 2-5%, leaving enough for those priority 1 threads to fit in, while still giving most of the CPU cycles to the miner. |
|
|
|
I have the following jhPrimeminer commandline: jhPrimeminer-T16v2.exe -u username.XPM_1 -p x -m 31 -m2 37 -m3 43 -m4 47 How can I throttle the mining process to make my CPU still usable, let's say i want to dedicate 50% or 75% of its power to XPM mining. I have an Ivybridge i5. I know I can throttle the mining with "-t 3" or "-t 2" down to less threads, but is there a way to throttle the mining process equally on each thread? I used to use this back when I was doing distributed computing stuff. Just tried it out on jhPrimeminer, and it works fine. |
|
|
|
can anyone tell me the difficulty of this hash
000000000000000001480bf37765db8beb84651395cc36e76e2c4e36fbb51026
I'm curious, too. I figured there'd be a calculator/converter somewhere, but I couldn't find one. |
|
|
|
My last 3 days' earnings:
.023332 BTC/Mh/s/Day
.020711 BTC/Mh/s/Day
.017492 BTC/Mh/s/Day
Your hash rate? My total hashrate is 490kh/s. |
|
|
|
|
My last 3 days' earnings:
.023332 BTC/Mh/s/Day
.020711 BTC/Mh/s/Day
.017492 BTC/Mh/s/Day
|
|
|
|
Hmm ... anyone else have the pool connection drop for them, been down for about a minute now for me  . Yup, down here as well. |
|
|
|
I've got what I think is a simple suggestion for the stats page. Next to "My Est. Earnings" add a column for "this rate over 24hrs" or something along those lines where the time that round took is divided into the amount of time in a 24 hr period and multiplied by the Estimated Earnings column. This gives a normalized view of each round that is easy to compare against previous rounds and other coins. (Plus it will save me from having to do that on my side when a round completes  ) Example: Round # Coin Length M.B. M.C. I.B. I.C. C.P.O. C.A.T. My Est. Earnings 24hrs@rate
693 GLD 00:25:16 0 0 53 2385.6 0 0 0.000265 BTC .01510 BTC
691 GDC 00:09:37 1 1000 25 25000 39.44 960.56 0.000036 BTC .00539 BTC
690 CGB 00:09:53 0 0 4 10 0 0 0.000071 BTC .01034 BTC
687 WDC 00:40:14 59 3702.07 0 0 96.15 3605.92 0.00035 BTC .01252 BTC
easy to see how each of those rounds compare even though they are different intervals of time - also, if you are storing what the Profitability number and difficulty were at the start of each round, this can give you additional data into what those numbers translate into for further tweaking of your handicap system. I had to post this in the newbie forum earlier, but I was thinking the same thing and I saw this post right after I finished a greasemonkey script to do something very similar and make a few other changes based on personal preference. Don't get me wrong--I really like the site, but I figure the admins have higher priority items to work on, so until they get around to it, this script might be useful. Here's what I did: - Difficulty is recalculated as expected number of diff 1 shares. (same as cgminer) - Calculates pool rejected % for current round and compares it to user rejected % (green if you are better than pool average, red if worse.) - Changed estimated earnings to display in uBTC. - Calculates round profitability as uBTC/hr. This is what it looks like: http://imgur.com/3Z3eGdPAnd the code is here: https://github.com/DeckardLain/HashCowMod/blob/master/Hash_Cows_Mod.user.js |
|
|
|
I've been lurking this forum for years now and finally have something possibly useful to contribute. I wanted to post this in the Hashcows thread in response to this: https://bitcointalk.org/index.php?topic=293872.msg3183550#msg3183550That message was posted right after I started working on a GreaseMonkey script to do almost exactly that, along with some other changes that are mostly personal preference. This was mainly a learning experience for me, being my first GM script written, but in case others might find this useful before the site actually gets updated with similar features, I can find a place to make it available (and maybe clean up the horrible looking code a bit.) Anyway, here is what I did so far: - Difficulty is recalculated as expected number of diff 1 shares. - Calculates pool rejected % for current round and compares it to user rejected % (green if you are better than pool average, red if worse.) - Changed estimated earnings to display in uBTC. - Calculates round profitability as uBTC/hr. Here is a screenshot of what it looks like.  |
|
|
|
|
