KnC works fine on p2pool with the later firmwares which fixed the slow block change problem (ie >= 0.97).
It works a lot better, but my experience was that I seemed to still end up losing about 40GH/s over time. It's hard to tell what the actual effect of the apparent lower hash rate is with P2pool though - it's possible that I just didn't give it enough time - the dynamics of mining on P2pool are a lot different than on traditional pools. In bitcoin mining, though, difficulty never rests, so time is very much at a premium. I just gave up and moved on. |
|
|
|
Honestly, I think that if anyone is really deeply committed to 'doing your part' to fight decentralization of mining, you NEED to be mining with P2pool, or using your coding skills to help forrestv make it the best pool option available.
P2pool (or some other yet-to-be-invented distributed pool system) is the ONLY chance to really fight decentralization. Expecting miners to altruistically choose their mining pool is NOT a realistic long-term strategy.
I tried to use P2pool, but right now, it simply does not work well enough with the fastest ASIC H/W currently available - or maybe the H/W does not work well with P2pool. Regardless of where the fault lies, miners are going to use the fastest H/W they can get, and P2pool will lose until either it adapts to the H/W, or future vendors adapt to P2pool.
In any case, the point here is that distributed pool mining needs to be the future if decentralization is to be avoided. Anything else is just a losing strategy. Altruism, while admirable, will not save the day here. It will just lose you money in the short term.
I know what you mean I went over to multipool which I used to use for scrypt mining on gpu's as they were trying to get their Bitcoin pool hashrate up. I spent nearly 48 hours there without getting one decimal fraction of a BTC because basically I was like 15% of the hashrate on my own. Effectively it was like solo mining. Whats P2pool like as an experience? It works pretty well if you have enough hashpower, but the variance is very high if you are a low-hashrate miner. Some hardware (like Knc H/W) does not work well with it, at least it didn't the last time I tried. The payout is good - miners get 100% of block reward + transactions. |
|
|
|
|
Honestly, I think that if anyone is really deeply committed to 'doing your part' to fight decentralization of mining, you NEED to be mining with P2pool, or using your coding skills to help forrestv make it the best pool option available.
P2pool (or some other yet-to-be-invented distributed pool system) is the ONLY chance to really fight decentralization. Expecting miners to altruistically choose their mining pool is NOT a realistic long-term strategy.
I tried to use P2pool, but right now, it simply does not work well enough with the fastest ASIC H/W currently available - or maybe the H/W does not work well with P2pool. Regardless of where the fault lies, miners are going to use the fastest H/W they can get, and P2pool will lose until either it adapts to the H/W, or future vendors adapt to P2pool.
In any case, the point here is that distributed pool mining needs to be the future if decentralization is to be avoided. Anything else is just a losing strategy. Altruism, while admirable, will not save the day here. It will just lose you money in the short term.
|
|
|
|
Maybe that's real, and maybe it's just FUD to weaken a strong competitor - I don't know and frankly, neither do you at the moment. I'll give them the benefit of the doubt for now. Irrespective of whether you believe it or not, my recommendation is to at least take into consideration a pool's proportion of the total network before jumping in with them to not make this sort of attack so easy to perform. I concur that that is a reasonable factor in any miner's decision on where to mine. |
|
|
|
Maybe that's real, and maybe it's just FUD to weaken a strong competitor - I don't know and frankly, neither do you at the moment. I'll give them the benefit of the doubt for now. Innocent until proven guilty and all that, you know. |
|
|
|
And please tell me, why do you mine at Eligius? Such an ugly site! That Wizkid and his pool.
I mine at eligius because with 11 Jupiters, 3% Fees would have been over 11 Coins already for me that I would have given to BTCGuild or other pools. Why mine at any other pool when Eligius is 0% Fees? Because you like pretty Stats? Not worth all that lost money. Also 105% PPS NMC helps out, get an extra coin or two per month. Pool basically pays you to mine there  Ghash.io has 0% fee, pays transactions to miners, and merge-mines NMC, IXC, and DVC - and their stats page seems to be very reliable. Do you mine there? Any downsides? Just started mining there, but I see no downside so far... |
|
|
|
And please tell me, why do you mine at Eligius? Such an ugly site! That Wizkid and his pool.
I mine at eligius because with 11 Jupiters, 3% Fees would have been over 11 Coins already for me that I would have given to BTCGuild or other pools. Why mine at any other pool when Eligius is 0% Fees? Because you like pretty Stats? Not worth all that lost money. Also 105% PPS NMC helps out, get an extra coin or two per month. Pool basically pays you to mine there Ghash.io has 0% fee, pays transactions to miners, and merge-mines NMC, IXC, and DVC - and their stats page seems to be very reliable. |
|
|
|
I am still having difficulties setting up. i spent the greater part of last night trying to setup bfgminer on this linux box. it should be very routine but it is not at all. was directed to here eventually, ive copied and pasted the contents here. http://eviltechmonkey.com/bfgsource.html Building and maintaining bfgminer from source on Linux This command should be valid on both Ubuntu and Debian based distributions including Mint, Crunchbang, and others Literally copy and paste the entire line while in your home directory (cd ~) sudo apt-get install git build-essential autoconf automake make libtool pkg-config libcurl4-gnutls-dev libjansson-dev uthash-dev libncursesw5-dev libudev-dev libusb-1.0-0-dev libmicrohttpd-dev -y && git clone https://github.com/luke-jr/bfgminer && cd bfgminer && ./autogen.sh && ./configure && make That does NOT install it system wide. It simple enables to run bfgminer from within that folder. To install system wide (so it can be run as any user from any folder) type 'sudo make install' in the bfgminer directory AFTER the rest. Some systems may require you to run 'sudo ldconfig' to link your libraries. If 'make install' does not work try that. To update your installation follow this step and include 'make install' to install system wide again if wanted: cd ~/bfgminer && git pull && ./autogen.sh && ./configure && make Optionally, once you have the dependencies installed (everything before the "git clone" portion) you can download the prepackaged tar.bz2 files from BFGminer, unpack, cd bfgminer-***, ./configure, make, sudo make install. Either method will work. The 'git-clone' method will just give you the latest source. Lastly, make sure your user is in the dialout group. sudo gpasswd -a yourname dialout Log out, log back in, open a terminal (if you're in a gui) and type 'groups'. You should be set to mine with most every USB ASIC. Head back to the referring page and go mine. when i enter ./bfgminer -o stratum.bitcoin.cz:3333 -u username.worker1 -p password -G --http-port 8080 or (port 8332) i get the following error. --http-port: unrecognized option ive pretty much been stuck there. linux distro ubuntu 12.04 bfgminer 3.0.6 i have the current version of libmicrohttpd-dev everyone in the live help chat at slushes pool is lost too. i really dont know what to do. That is a very old version of BFGMiner that you have built - long before the proxy functionality was added. You should do a git pull of latest sources, or checkout a newer version. You should delete/uninstall that old version. Make a directory where you want to build BFGMiner. cd to that directory, then: $ git clone https://github.com/luke-jr/bfgminer.git will get you the latest git. After that, check the README section on building to make sure you have all the newest dependencies installed. Then you should be able to build the latest with: $ ./autogen.sh
$ ./configure
$ make should build you the latest version. |
|
|
|
Well, everything I can see looks right. As long as your user/pass field is 'user:passe,user:pass', the only other thing I can think of is a firewall issue that is blocking port 8332 between your blade and the proxy machine. If that's not it, I don't have any other suggestions. Well,thanks for trying. Oh and one last question. Could it have anything to do with my OS?(Win8 x64) Well, I guess anything is possible, but I am using Win 7 x64 with no problems. I have not heard of any problems specific to Win 8. One more experiment you might want to try, just to rule out proxy misconfiguration... If you kill the proxy and start bitcoin-qt, the blade should be able to connect directly to bitcoin-qt to solo mine. If that doesn't work, you definitely have a network problem of some sort. If it does work, you have a proxy problem. |
|
|
|
Well, everything I can see looks right. As long as your user/pass field is 'user:passe,user:pass', the only other thing I can think of is a firewall issue that is blocking port 8332 between your blade and the proxy machine. If that's not it, I don't have any other suggestions. |
|
|
|
|
Can you post a screen shot of your blade config window (with your username/pw blanked)?
I have never used that proxy, but it looks like it is connected to the pool and just waiting on a miner to connect.
|
|
|
|
Nope,no other programs running.
Just a shot in the dark here... In the edit box where you enter the server address, you don't happen to have ' http://192.168.1.X' do you? I notice in the screenshot you posted that the proxy is failing to understand an HTTP header. That edit box should just contain '192.168.1.x, 192.168.1.x'. Negative,no HTTP in the address box. Something is trying to talk HTTP to the proxy:  See the protocol error? It is failing to decode an HTTP header. If you don't have any edit boxes in your configuration window with an 'http://' prefix, then I don't get it... |
|
|
|
Nope,no other programs running.
Just a shot in the dark here... In the edit box where you enter the server address, you don't happen to have ' http://192.168.1.X' do you? I notice in the screenshot you posted that the proxy is failing to understand an HTTP header. That edit box should just contain '192.168.1.x, 192.168.1.x'. |
|
|
|
Just received my blade,sailed smoothly through the hardware stuff,however I'm stuck at the configuration page.
What I did was:
1)Open mining proxy(on default settings)
2)Set both the server addresses to my IP(as seen in cmd using /ipconfig)
3)Set the ports to 3333,8332
4)Set the account info to username_workername:password,username_workername:password
Now I'm getting two different results.
On port 3333,mining proxy goes batshit crazy,but the hashrate is still stuck at 0
On port 8332 nothing happens.
Would appreciate any help,thanks in advance.
3333 is a sratum port, 8332 is getwork port, blades use getwork so if you use 8332 twice for your ports you should be good... Hope that helps Thanks for the quick reply. Tried that too,still doesn't work  Current Server: 192.168.1.X:8332 No hashes Do you also have a Bitcoin-QT or bitcoind running on your machine? If so, it will use port 8332 by default and you will be conflicting. I use BFGMiner as the proxy on port 8330. I have never used the slush proxy, but I imagine you can tell it to use a different port than 8332 for incoming connections. |
|
|
|
Thanks for the heads-up  |
|
|
|
I just recently realized that I have not received a NMC payout in almost 2 weeks. I then looked at my MyEligius account, and discovered that my NMC payout address is one that I do not appear to own! How could my NMC address get changed??? I have never changed it since I initially set it - although I have set other options, like BTC payout amount.
Wizkid, can you check and see how/when my NMC address got changed? I am waiting until you look into this before I set it back to my correct payout address.
Address? 1HEVnMzamrnxWGyM56JoAesiHqVqvnqd4g Sorry, should have realized that would be needed... Here are details of all of the stats settings made for your address. All of the signatures pass, so, if you didn't make the changes then someone else has your private key: http://pastebin.com/raw.php?i=Xuni0iDSI made the change of removing my customized payout of 0.25BTC to let it go to default - but I did NOT edit the NMC payout address at that time. It is very likely though, that if it had changed, I would not have noticed it when I edited the payout amount, and would have submitted a signed message with the bad NMC address. That is to say, I have never edited the NMC payout address on my account since I set it initially. It clearly changed at some point, and I signed a couple of changes without noticing that it had changed. I can't imagine any way I might have "accidentally" put in a totally bogus NMC address - which, I might add, does give the appearance of being a valid address - just not one of mine! Is there a blockchain.info-like site for examining NMC addresses? This is pretty scary to me. |
|
|
|
Some geek pr0n with a kink thrown in for added distraction As you can see there is still tweaking to be done. So I got that goin for me Looks neat, may I ask why you did this? Your question suggests you are not a member of the target audience for this pr0n  |
|
|
|
I just recently realized that I have not received a NMC payout in almost 2 weeks. I then looked at my MyEligius account, and discovered that my NMC payout address is one that I do not appear to own! How could my NMC address get changed??? I have never changed it since I initially set it - although I have set other options, like BTC payout amount.
Wizkid, can you check and see how/when my NMC address got changed? I am waiting until you look into this before I set it back to my correct payout address.
Address? 1HEVnMzamrnxWGyM56JoAesiHqVqvnqd4g Sorry, should have realized that would be needed... |
|
|
|
|
I just recently realized that I have not received a NMC payout in almost 2 weeks. I then looked at my MyEligius account, and discovered that my NMC payout address is one that I do not appear to own! How could my NMC address get changed??? I have never changed it since I initially set it - although I have set other options, like BTC payout amount.
Wizkid, can you check and see how/when my NMC address got changed? I am waiting until you look into this before I set it back to my correct payout address.
|
|
|
|
Hello, what is actual queue for Little Single (30Gh\s) in solo? I'm tired of fighting with "Automatic queue" in 3.5.0 and 3.6.0 has the same problem. Now i set manually queue=60 and it still says that staged work underrun...  Do you have coinbase-addr and coinbase-sig set, as in the SOLO MINING section of the README? If not, I imagine you are connecting to bitcoin-qt/bitcoind with getwork which is just not fast enough for ASIC mining hardware. If you set coinbase-addr and coinbase sig, BFGMiner will use GBT, which should solve your problem. |
|
|
|
|
Show Posts
