You can see the difference in % share just by changing the difficulty level; and when it ramped up to where it should have been =)
|
|
|
awesome! I wasnt sure if I could input the difficulty with a comman and the algos after. Ill update my batch now.
BTW: Theres a night and day difference between zpool and xpool. I wont go back!
*edit*
fixed the problem!
|
|
|
I had zero freeze/zombie issues and a "set it and forget it" mentality with this config:
RasPi 2 (with freeze watchdog enabled) MinerA (with auto reboot set when miner stops hashing)
One U3 would be solid hashing then die randomly; and within 5 min it resets itself and bam. back hashing.
I didn't rely on the solid red LED up front because sometimes when it went zombie or simply went to a zero hashrate; the red LED was still lit solid....
|
|
|
cool; no sweat here; I think I timed my miners over the weekend to only leave maybe a few hundred satoshi to die in xpool =) I left worker names on and the pool seemed to ignore them; but ill strip them out today just to be politically correct. I do however have an issue with Zpool; The pool keeps driving my difficulty up slowly; and a large percent of my submitted shares aren't getting acknowledged in my miner; my hashrate on the pool after my machine has been connected for over an hour seems to be half of what it actually is. It feels like I could be loosing out on a percentage from this; take a look at my ccminer screenshot below. With other pools and a diff of 1 or 2; I see an accepted message for every submitted message.... At first the shares are all acknowledged; but after the stratum changes my difficulty a few times; its missing out on a lot of shares. Nothing else has changed otherwise between xpool and zpool. Since the also-switching feature takes up the password slot; I cant force a difficulty level =( Maybe add it so you can just add it to the end of each on the list of algos like is done with the profit level selection?
|
|
|
Sorry for blabbing my misconceptions in the last few pages; But I would have believed that the devs would have implemented some sort of miner security over time to prevent the problem of withheld blocks being able to happen (incorporating a hash on the actual transaction port of the block and rolling that into the final hash to be calced keeping people from using someone else's solve hash)... This would also help keeping the mining houses decentralized and having "control"..... but it must be more difficult to do than just that. I am totally sorry for that guys.
CK, I have a simple question; what type of system/pc/processor config is your pool running on? Curious on how much it takes to run a pool of this size reliably =)
Congrats to the big winner. I had a 1.9B share last round; the biggest hash that S3 has found since I bought it a month and a half ago.
|
|
|
Hey crackfoo, me again. I am wondering 2 things; one; the site doesnt specify but I assume usernames with a "[BTC ADDRESS].workername" is still valid for zpool? Its not posted anywhere that I could find. Second; any chance of a snowball in hell of having final xpool remainder balances transferred to zpool? After a short time trying it; I think I'm sold on zpool. I still kinda miss the graph from xpool though I believe I got working a script in my batch file to refresh my video driver between instances of ccminer to make sure my hashrate doesnt drop if my driver freaks out. Thanks again for your time and services!
|
|
|
See, with NH; they are trying to solve a block with your transaction; so a different hash all together. Theres no way for a renter to withhold blocks like that... you can see the live submissions/hashrate coming through the solo pool. I don't see that being faked at all.... unless the hash renter feeds garbage data to the pool (I would assume the pool would invalidate bad work?)
My one recommendation to people going for rented hash:
Its smarter and more statistically probable if you rent as much hash as possible and run it at once.
More workers working on the same block == greater chance of solving _your_ block in a given amount of time.
If you just space out the hash in smaller amounts over time; you have less hash to find that block in a given time and it is somewhat wasteful.
In the same sense that pointing two antminers at two different BTC payout addresses, will both have the same probability of finding a block; whereas if they are both mining to the same address, they stand twice the chance as find a block as when they are working independent.
I hope people grasp this idea.....
The more hash you cram in that "10 min" gives you a higher actual probability of finding a block.
|
|
|
I never found the precompiled one before. Many thanks. I am however announcing that I am selling my U3 (too much hassle for me not being home enough to keep it 100%) to someone on craigslist, supposedly for testing the gridcoin network, and a new coin for a gaming site... they want to be able to test the network and algo =) Good to know its going to a good use after its leaving me; and I think my ROI is 125% now that Its being sold. I have made just about a few bucks in mining with it on altcoins, and selling it for close to what I paid. So for anyone who said you would never dream of reaching ROI with this miner is sadly mistaken I still recommend the U3 for people who want a lottery machine, and can get it set up on a controller like the R1 with the modded firmware, or my recommendation of a PI with Raspbian and Minera... its VERY consistent. With Minera and defaults (normal cgminer fork); it saw a solid 57Gh average on the graphs. Minera supports auto miner reboots when zombie, and Pi reboots when freezing (os watchdog setting). I had zero problems with Minera until I was stupid enough to not configure bitcoin core properly and it filled up the SD card in a heartbeat; instead of storing and using the blockchain that I had on a USB HDD. I had the best results as well with: --bmsc-voltage 0830 --bmsc-freq 0982
|
|
|
Sounds like a better plan to me. Seems like it will be a little more consistent in the end; and when the diff is low, it wont keep flooding through blocks "wasting hash" and causing issues.... I totally see the idea behind it after explained.
When I get my net connection back at the ranch, ill point my meager amount there =) I am happy about the Lyra2Re addition. I watched my payouts almost double just by transferring my X11 to Lyra.
This is another curious notion: On Nvidia cards it seems there is one individual piece of software that are optimized for only really one type of algo. Would you think that the profit switching "script" on my end will work okay with multiple executables over many directories? I assume I would have to add full paths to the batch file, etc.
I am working with the GTX980; so that's my reason for concern; even though there's a lot better support for my graphics card nowadays,(10+Mh on any algo, months ago i couldn't get more than 6Mh Lyra2re on it) I still must be weary. One major issue for me is the Power state setting in my video card. If I try to force P0 (highest performance); it crashes my pc. The most I can get is P2 when running mining apps; They automatically force P2 state and not P0. But even with P2 I am getting very decent hashrates. The major issue in this is if I am using the machine (viewing a video) [or even unpredictably more often] and simply close the miner and re-start for something like an intensity change, it will force the power state to an even lower level (higher P number) and I wont see more than 3-4MH until I reboot the PC or forcibly re-initialize the driver with an nvidia tool and break most other features in the OS (flash videos, 2d/3d apps, etc).
This is my main concern when profit switching on my machine with a GTX980; when closing and starting a mining app it will often switch to a lower power state and totally chop performance to a fraction of what it should be. When unattended as my pc is when I'm not home; This could spell disaster for my output.
|
|
|
Hi All, I've been reading through this long thread and haven't been able to find a clear answer. I have a U3 working fine on cgminer using Windows 10. I would like to have it work with two U3's at once. Here is my current batch file, could someone please tell me what I need to modify to get it to work with two U3's? cgminer.exe --bmsc-options 115200:0.57 -o stratum+tcp://solo.ckpool.org:3333 -u 1DqnYDCu24ot7JKZwNEvNDMLRH8CTeSHaC.0 -p 123,123 --bmsc-voltage 0830 --bmsc-freq 0982 Would really appreciate any help provide. Thanks! You should download the latest cgminer 4.9.2 instead of using bitmain's old fork with the bmsc junk. https://github.com/ckolivas/cgminerIt was updated to "work better" with the U3, it is much improved over bitmain's old copy. See the readme.asic for new u3 commands instead of the bmsc. He will probably need a link to a site with a precompiled copy for windows..... as most windoes[nt] users won't/cant go through the steps to compile their own.....
|
|
|
Today's xpool.ca multipool payout is 554+ NXT, 36+ BTCD, 2.7+ FIBRE, 144+ BITS, 3+ DASH, 20+ VTC, 156+ VRC, 1.32+ LTC & 0.548+ BTC Additionally 4.1+ DASH was found and sent to X11 miners and 1100+ VTC was found and sent to Lyra2REv2 miners since last payouts Our new pool, the miners multipool is now open for BETA testing: www.zpool.ca Cheers! Crack, what would be the benefits of using xpool vs xpool? I am not quite seeing the difference other then payout schedule, and statistic reporting... maybe im being a little blind... =)
|
|
|
I saw "Bestever" just the other day and was thrilled; I figured this detail would pop up some day or another =) I was wondering if you would add at some point "BestRate" for peak account hashrate? That would be a sort of usefull tool for people using only their own equipment. Anyways; unnecessary, but the changes are well welcomed =) Thanks for the service again, and Ill be donating as soon as I win big!!!
|
|
|
see; for any device that will pull something like a 1200w load; I specifically just create a circuit for what I am going to be running. If it draws that much It will be as close to the POS panel as possible for safety sake.
When we do sound/lighting at private venues, we have a set of power cables hooked to breakers to jam into the locations box and not worry about their power system past the point of service.
I apply that logic at home; but I do it to code.
|
|
|
congrats 18AVhXKPiaG831tEi1pY4XZ2MviwhYFErt stats at the time were {"hashrate1m": "271T", "hashrate5m": "255T", "hashrate1hr": "103T", "hashrate1d": "5.46T", "hashrate7d": "787G", "lastupdate": 1447600199, "workers": 3, "shares": 7749187423, "bestshare": 52959111.491152197} amazing how 62,000,000,000 will pull nothing but a low 52,000,000 finds a block...lol. Wish we were this lucky yesterday By the looks; that doesnt show his winning share; he was able to get a 52m share in the time between winning the block and you looking at his stats!!!
|
|
|
poolling your miners ??
They did a group hashrate buy. so far they pulled a share ~56B..... scroll up. thread link.
|
|
|
When you consider there could be a share worth 2^224 in the endgame... "max target / n" or as it is now; 63B doesn't seem like such a big number...
But there are SOOOOOOOOO many fewer chances to hit those higher shares.
I am surprised I regularly see 20M and 100+M shares on both my antminer U3 and my S3. Must be a lucky address; though I have yet to hit a block myself.
The raffle ticket analogy is great; aside from your number not being called. But the problem is you don't know what number will be on your ticket till you get it. And the number needs to only be equal or greater than a baseline number.
|
|
|
almost looks like my last bestshare; but the decimal place so the 1 is billion Congrats to the lucky lotto winners recently!
|
|
|
I'm going to do the same thing - 1.2Ph.. maybe one of us will get lucky
"hashrate1m": "540T" and climbing
lol, what have I started. Mine should be running out any minute now. No lottery yet =( lol And its officially over.
|
|
|
I have done a couple of 1pH of like 30 mins from nicehash I didn't hit as of yet, currently solo mining with 3 S3s. It will happen! yep, my s3 is dedicated to solo; even thought it would earn me ~ $1/day {"hashrate1m": "1.49P", "hashrate5m": "1.32P", "hashrate1hr": "379T", "hashrate1d": "19.7T", "hashrate7d": "3.22T", "lastupdate": 1447263975, "workers": 12, "shares": 572211924, "bestshare": 4978424250.5065622} first ever share over a billion. Feels good to see an insane hashrate for once. I probably wont do this much... ever. Still; a far shot from the ~62.3B needed.....
|
|
|
|