Fixed solo mining via GBT, but it really needs a couple of competent code reviews and some good testing (I suggest on testnet for now). I've built a Windows ZIP (note that this is NOT compatible with the libblkmaker DLL in 2.8.2!): http://luke.dashjr.org/tmp/code/bfgminer-e333074-win32.zip - the code is in the "gbt_solo" git branch. To test solo mining, run a recent bitcoind or Bitcoin-Qt (I suggest next-test for longpolling support) and start (this branch of) BFGMiner similar to this: bfgminer -o localhost:8332 -O rpcuser:rpcpassword --coinbase-addr 1bitcoinaddress
|
|
|
I think all pools should be shut-down immidiatelly and code put in place to prevent formation of any sort of groups. This isn't possible even in theory. Issues with Luke you posted are nothing but minor incidents. They also didn't happen, or are being presented by Kano out of (important) context. For other stuff you posted, I'll wait to see Luke's reply. What in specific would you like a response to? Kano spouts so much lies and nonsense that I generally ignore his posts.
|
|
|
Ok, got my issues resolved with BFG not detecting BFL single, an error in BFL driver install.
But still having issues with BFG crashing and freezing computer. Seems to be heat related, everytime GPU reach 81C , BFG shut down GPU's then shuts down or freezes computer.
From what I read 81C is warm, but not hot. If I keep the GPU temps below 80C(open window wider here in Canada) the miner software runs fine
Is there a way to correct this? would like to close window and heat part of the house with the heat. I don't think BFGMiner should be trying to shut down the computer by default - are you sure it isn't the GPU hardware overheating and doing crazy things?
|
|
|
As the owner of www.bahtcoin.com I feel obliged to drop my 5 cents into the discussion. There is no BTC sign in the website at all. Um, sure there is. Right there at the top of the page to the left of "bahtcoin". I don't see any other symbol for Bitcoin either.
|
|
|
Proof-of-stake (at least all existing attempts I know of) also allows miners to use it for attacks in parallel to the legitimate blockchain. That is, there is no cost to attempt to fork the blockchain. Incentively speaking, this means rational miners should mine every chain that does not hurt them personally.
|
|
|
I've had problems trying to figure out cgminer quickly. It seemed like it would be simple, but setup was not intuitive to me and the help file were poorly made (I think the format examples in the help file were wrong). I had no idea from where to run it...command promt or a window. And trying to disable the GPU using helpfile examples didn't give me any indications it was working in the DOS window (though I still wasn't even sure was the right place to run the program).
Anyway, it didn't take long at all to lose patience with it. A friend told me he used bitminter, and found it from a link on BFL's website. Starting it was just toooo easy and using it's interface was intuitive. So, I've been using it ever since with no real problems. You should try BFGMiner. Generally, you can simply run it, enter pool info, and it just works. Um, cgminer is the same way. It's quite powerful and configurable, but defaults work well there too. Except cgminer stopped merging FPGA updates (except when people bribe Con), so it doesn't really "just work" in many cases. Except that's your opinion of the matter. And seeing as you are in charge of BFGminer, your opinion holds a certain amount of bias. Cgminer does in fact work with many FPGAs, as mdude said. ... and after spending many hours last night going through the modminer driver in cgminer that luke-jr wrote and submitted into cgminer Yes we can check the date ... after modminers were out and running I've found that the code that was committed into cgminer doesn't work with ModMinerQuads (and found out why) I rewrote all the I/O code like in Icarus and still could not see the (obvious in front of my face) reason why it didn't work until I got the errors that the OS returns displayed (rather than ignored as the code does) ... and then tracked down why those errors were occurring. Simple answer, the code cannot work - the device type of the /dev/ttyACM0 is not a tty according to linux and thus termios timeouts wont work. Next step will be: rewrite all that to something that works with windows and linux (or 2 versions of it - one for each linux and windows) coz no doubt we'll need that shortly ... and the actual fix in the 'other' git to make the code work (rather than having something that didn't work at all) was never sent to cgminer ... Also we didn't know it didn't work - no one ever said that it never worked and neither of us had an MMQ I do now ... so I can see the problem ... that's why I'm annoyed about the code ... also why It's taken a while - until I had enough time to attack the code and debug it rather than spending time tuning it ... it doesn't work at all for me on either computer I have, but mpbm works fine ... coz python implements it's own timeouts, so that works on all serial devices Though all this hacking with termios has found what hopefully will be a fix for the rare problem I got when transferring an FPGA from windows to linux and having to run a python command to clear the problem (unrelated to the problem above where mining always fails even after stopping a working mpbm) The irony here is that you're wrong on almost all of this. It's a shame you get rewarded for all your constant trolling, despite having basically no coding skills.
|
|
|
@Doff It's standard version of Bfgminer 2.8.1 2.8.1 only worked with fixed-frequency bitstreams, not the new dynamic-frequency ones, FYI.
|
|
|
The new ASIC-needed getblocktemplate mining protocol is intentionally designed to be decentralized, moving the block creation back from the mining pools into the individual miners. Mining with GBT enables doing several automated security security audits of pools in realtime, and the same level of control for miners who are willing to run a local bitcoind instance. Furthermore, ASICs are available to any consumer who wants to buy one, at more than reasonable prices as low as $150 - about as cheap as the average GPU. On the other hand, there is currently a major problem of centralization on software for Bitcoin nodes and wallets. This is also being dealt with, but at a slower pace. Hopefully the new Bitcoin Foundation will help move things along quicker: I imagine once Bitcoin-Qt and/or bitcoind reach 1.0, Bitcoin will be bigger and people will have more time for multiple independent implementations.
|
|
|
I've had problems trying to figure out cgminer quickly. It seemed like it would be simple, but setup was not intuitive to me and the help file were poorly made (I think the format examples in the help file were wrong). I had no idea from where to run it...command promt or a window. And trying to disable the GPU using helpfile examples didn't give me any indications it was working in the DOS window (though I still wasn't even sure was the right place to run the program).
Anyway, it didn't take long at all to lose patience with it. A friend told me he used bitminter, and found it from a link on BFL's website. Starting it was just toooo easy and using it's interface was intuitive. So, I've been using it ever since with no real problems. You should try BFGMiner. Generally, you can simply run it, enter pool info, and it just works. Um, cgminer is the same way. It's quite powerful and configurable, but defaults work well there too. Except cgminer stopped merging FPGA updates (except when people bribe Con), so it doesn't really "just work" in many cases.
|
|
|
I've had problems trying to figure out cgminer quickly. It seemed like it would be simple, but setup was not intuitive to me and the help file were poorly made (I think the format examples in the help file were wrong). I had no idea from where to run it...command promt or a window. And trying to disable the GPU using helpfile examples didn't give me any indications it was working in the DOS window (though I still wasn't even sure was the right place to run the program).
Anyway, it didn't take long at all to lose patience with it. A friend told me he used bitminter, and found it from a link on BFL's website. Starting it was just toooo easy and using it's interface was intuitive. So, I've been using it ever since with no real problems. You should try BFGMiner. Generally, you can simply run it, enter pool info, and it just works.
|
|
|
Let me know if there's debug options/versions/etc I can try to identify the issue. What strikes me as useful is testing: - after 2.8+proxy goes bad, restart ONLY cgminer
- cgminer 2.7 with proxy
- cgminer 2.8 without proxy
|
|
|
My Cairnsmore1 displayed dead one chip after the other by BFGMINER from time to time (after start BFGMINER around 5 to 20 minutes) today. When this occur you'll need disconnect the power to restart Cairnsmore1. But that wouldn't help this situation. What could be caused this? Could you make a debug.log file with this failure and upload it somewhere? Add to the end of your bfgminer command: --debuglog 2>debug.log
|
|
|
Would "a target of 13 shares per minute would keep variance most consistent with a 1gh/s connection" be a valid conclusion? I gathered this primarily from the last chart in your blog. I don't know if that is Inaba's goal anyway, but someone mentioned a desire for something to that effect.
The exact number is 13.969838619232177734375 shares per minute: 60 seconds ÷ (2 32 nonces-per-pdiff1-share-on-average ÷ 1,000,000,000 hashes-per-second)
|
|
|
Can someone please explain the difference between CPPSRB and RSMPPS to me? RSMPPS still uses the notion of mining "rounds", and divides the earnings of a long round proportionally among all shares in that round (assuming no buffer to cover the difference). CPPSRB is more like PPLNS: the last N unpaid shares are paid. It has no notion of specific rounds; if it takes more shares than average before a block is found, the earlier shares just don't get paid by that block (and remain on the "unpaid shares" stack for potential future short blocks).
|
|
|
I'm helping soniq out, and you asked him to try: The output is: [2012-10-09 14:57:43] bfgminer.exe: -d: requires an argument There's a question mark in that command:
|
|
|
I've prepared a pre-beta "stratum" branch on the git repository with some minor cleanups and enhancements. It also contains a workaround (in the form of improved RPC backward compatibility) for Puppet Master's "switching back and forth between pools rapidly" issue that cgminer has had since adding Stratum support. Test this at your own risk, and report problems (and successes) on this thread. I probably won't merge it into mainline BFGMiner until the 2.9.0 release. Windows EXE (drop in directory with the DLLs from the usual 2.8.2 ZIP): http://luke.dashjr.org/tmp/code/bfgminer-ba17775.exe
|
|
|
It's amazing how many commodores and apples still exist and work. Excluding hard drives, floppy drives and the like.
Every one of the laptops I have owned eventually shit the bed yet I still have a working Commodore 4plus, apple IIe, Commodore 64, pong, and the atari 2600 (Sears version), Wyse terminal, VT100 terminal, and more geeky old shit that used a lot of power. I hold on to a 13 inch color tv just to plug these things in, wait tens of minutes for it to start and 10s more minutes to load a game just so we can point and laugh at an 8 bit world. (Loaded from cassette with a modern boom box, holy shit, those things are 32 years old and they still work) Back then, they built computers to last. Who wants to pay $20,000 for a piece of equipment that dies in a few years? Nowadays, people replace their computers so often for upgrades that it doesn't really make sense to build them to last more than a few years.
|
|
|
Incorrect All the software I use on my desktop except for the nVidia driver is open source. No trust issue with anything I use - just a 'lazy' or 'not lazy' (to read the code) issue. then you have to trust the open source programers not to code bullshit into it Or, more likely, trust that the number of other third-party developers who have reviewed the code would have caught anything stupid. My main system is 100% open source, except for BIOS and firmware. Yay for Intel APUs. My Radeon GPUs can be locked down nicely inside KVM.
|
|
|
Is it possible to support stratum? I'm currently using a proxy. Better to use a pool that supports standard GBT, but Con wrote Stratum support for cgminer, and it seems like it isn't too much trouble to merge it in for some future BFGMiner version.
|
|
|
|