I think Luke-Jr is planning to release support soon but as far as I know right now you need to build the "compac" branch on his github if you want compac support on bfgminer. Yep, I'll try to get 5.3.0 released before any deliveries take place. Note I merged and deleted the "compac" branch, so just the main "bfgminer" branch is fine now. Windows users can get git-built bleeding-edge binaries from: http://luke.dashjr.org/tmp/code/webisect/webisect.php?dobuild=bfgminer
|
|
|
I hadn't thought of that. It's a good idea, albeit one that would complicate starting Hashmal (e.g. compiling the C++ extension). The current method of stepping through scripts - via re-implementing EvalScript() from python-bitcoinlib - is rather inelegant. I'm also relatively unfamiliar with C++ (as opposed to C) extensions in Python. Anyway, there probably should be a better implementation of script evaluation, so that's currently the only option on the table. libbitcoinconsensus, while it does use C++, exports only a C API Should be able to just use ctypes I would think (with stock libbitcoinconsensus lib). (Of course, this only works with #6178 merged )
|
|
|
Can you test that the working production units are good to go with BFGMiner's "compac" branch on GitHub?
|
|
|
Is bfgminer support on track? Yeah, might be a bit bumpy initially, but I can at least commit to it mining reliably (disclaimer: I've only tested in --benchmark mode so far :p). Thanks Luke-Jr! Looking forward to it. Will there be pre-built Mac OS X binaries? If not then I can build them myself. Just want to know what I'm up against... Usually nwoolls does the Mac binaries - but I haven't heard from him lately, so not sure if he'll continue to do so.
|
|
|
Is bfgminer support on track? Yeah, might be a bit bumpy initially, but I can at least commit to it mining reliably (disclaimer: I've only tested in --benchmark mode so far :p).
|
|
|
Sending me to Reddit (puke) is just plain dirty I see your point. I said essentially the same thing to both CK and Luke probably a year ago. I'd prefer there be peace among the lot of you. But it ain't my affair. I'm happy to leave Kano and CK alone. I consider it unfortunate that I continue to have occasions where I need to call them out on lies, and would welcome this stopping.
|
|
|
AFAIK the project is abandoned. First step I think needs to be convincing someone to be willing to work on it...
|
|
|
Hells yeah! Getting keen!!!
Damn you Luke! Thanks for the nostalgia! Now where's my old 286... Who needs a 286 when DOSBox works great on a Novena? At least, that's how my children play Keen on a regular basis...
|
|
|
Hells yeah! Getting keen!!!
|
|
|
Is this a correct setup if I want to solo mine against my own wallet? bfgminer.exe --stratum-port 8330 -o http://localhost:8332 -u user -p x --generate-to 1QBajsQ8wGHkBgJEhHikKvm1kqvtJdYE53 The reason I ask is that my hashing from the client is all Diff x/1 where x can be anything from 1 through 128k. When I mine against a pool, the Diff adjusts. No, just run BFGMiner without any options. If your hardware needs to connect via stratum, add just the --stratum-port 8330 option.
|
|
|
Yes, this is looking straight-forward enough to hopefully have in BFGMiner before delivery.
|
|
|
remove Slush's and any other pools that have ceased to provide Bitcoin pooled mining.
I don't think they have ceased anything - rather they're offering a choice between version 3 and version 0x20000007 signing (the back-end details of which haven't been mentioned). I realised this after I posted, and emailed slush requesting details of what his pool is actually doing.
|
|
|
Should just run a full node and solo mine for real ...
|
|
|
Bitcoin pool running Bitcoin XT v0.11a.
This list should not only not-add yours, but should probably also remove Slush's and any other pools that have ceased to provide Bitcoin pooled mining. Edit: Slush's pool is still Bitcoin, so strikethrough'd it.
|
|
|
Further off-topic discussion of Windows will be split/deleted or something. Please keep this thread at least remotely related to BFGMiner... Thanks
|
|
|
Any way to overcome the wiki's 5000 change limit for RecentChanges? I've fallen behind...
|
|
|
More GPUs = losing money faster...
|
|
|
|