Good news: I think I have stumbled upon the stratum-went-down-related crash people have been reporting while testing BFGMiner in Valgrind. This should give me enough information to get it fixed in the next release.  Ok, I believe this problem should be fixed in the latest git code. For Windows testers... Win32 and Win64 binaries are built (drop them in a directory with 3.0.2 DLLs) Note these builds do not have ZTEX FPGA support due to legal issues with a minor contributor, which I hope to have resolved for the 3.1 release. They do, on the other hand, have experimental CPU mining code. No performance optimizations, but I've done some tweaking for making it more portable. A simple way to test is to run: bfgminer -o luke.dashjr.org/tmp/code/earlyshare2.json -O x -C If you get rejected shares, it works. Ideal testing includes every algorithm, and that the default (fastauto) picks something that works. x86_32 algorithms: c 4way cryptopp cryptopp_asm32 sse2_32- VIA-specific algorithm: viax86_64 algorithms: c sse2_64 sse4_64PowerPC (very old Mac OS X only!): altivec_4wayI do not plan to release 3.1 with CPU mining support enabled in Windows binaries still, mainly due to the threat of malware abusing it. If anyone has any alternative or better ways to prevent malware abuse, I'd love to hear it |
|
|
|
BIP 23 is focussed on pooled mining. Logical services are an important feature for that.
I don't see how merely moving a section to another document helps...?
Ok, I thought BIP 23 was for the feature discussed here. BIP 23 is a collection of optional extensions on top of the base GBT protocol. Part of BIP 23 (transactions/remove and proposals) specifies how this can work. |
|
|
|
Why does BIP 23 include the "Logical Services" section? This doesn't seem to have anything to do with the core part of BIP 23. I think it'd be better to trim the BIP to be specific to the task required to make it more understandable and easier to implement. BIP 23 is focussed on pooled mining. Logical services are an important feature for that. I don't see how merely moving a section to another document helps...? |
|
|
|
Still having trouble.... something about neesing windows drivers... I have the windows drivers for the devices installed tho
BFGMiner should work if you get rid of the Norton malware so you can actually run it... |
|
|
|
|
The plan right now (but subject to revision as needed) is to use BIP 23's "transactions/add" mutation and Block Proposal support to allow fullnode miners to advertise their support for this.
The pool will then just skip sending the bulk transaction data, and expect the miner to send a proposal back with that supplied (fetched from a local bitcoind).
Then GBT mining can continue as normal.
|
|
|
|
Good news: I think I have stumbled upon the stratum-went-down-related crash people have been reporting while testing BFGMiner in Valgrind. This should give me enough information to get it fixed in the next release. |
|
|
|
Had to use zadig to change driver so both BFGMiner and CGMiner could see jalapeno. Bitminter beta needed ftdi type driver instead with VCP. Interesting. Wonder what ASICminer blade and USB need to work  BFGMiner also needs the standard FTDI/VCP driver... |
|
|
|
The 1 satoshi = 1 share isn't completely redudundant in determining number of shares. To prove how many shares you have (which you need to do if you're selling for example) you'd need either the complete dividend amount (is it sent in one transaction?) to work out the percentage, or know what the dividend value per share was. The 1 satoshi per share just simplifies that dramatically.
An ASICMiner-controlled spreadsheet is the right solution for this. not everyone wants everyone else to see how many shares they have. So no, I don't think this is the solution. There has been a talk about asicminer setting up their own exchange (which would make sense) but I guess the engineers and professionals working for ASICMINER have better things to do right now. I have no doubt it will be implemented in the future though. How is this any less private than the transaction spam? The spreadsheet would just contain a number of shares and the address considered to own them... |
|
|
|
The 1 satoshi = 1 share isn't completely redudundant in determining number of shares. To prove how many shares you have (which you need to do if you're selling for example) you'd need either the complete dividend amount (is it sent in one transaction?) to work out the percentage, or know what the dividend value per share was. The 1 satoshi per share just simplifies that dramatically.
An ASICMiner-controlled spreadsheet is the right solution for this. |
|
|
|
Bets are off-the-chain Thank you! |
|
|
|
bfgminer -o http://api.bitcoin.cz:8332 -u elasticband.noobie1 -p blank -S all
|
|
|
|
I downliaded bfminer also but after compiling the .bat nothing happens on start
Did you put the -S all option? |
|
|
|
I am having trouble getting my units to run on cgminer for windows.... no usb device found. Works on bitminter though. Any help would be appreciated!
cgminer doesn't work with standard drivers - if you really want it, you'll need to remove the normal driver and install a non-standard one. BFGMiner works similarly to cgminer, but has better ASIC support (including working with standard drivers). |
|
|
|
So the Avalon uses a TL-WR703N. Those can be had for $25 all day long. Any tried to grab one, reflash the newest CGMiner 3.1.1, and see if it works with other FPGAs or ASICs? Could be a nice, cheap alternative? Avalon uses a modified WR703N, and even then it performs poorly enough to create practical issues in some cases (pools have to implement workaround hacks). Additionally, due to the limited flash size (4 MB), you can only install pre-compressed and unchangable firmwares on it, with little breathing room for things like FPGA bitstreams (some of which are over 4 MB themselves!). Yep I was just looking at the fact that they doubled the RAM, for one thing. I'm not as concerned about FPGAs and their bitstreams,as I'm mostly looking for something that can work with ASICs. I've had good luck with the MK802II, but I was looking for something that's even cheaper. Well, you did ask about FPGAs :p Still, if it were me, I'd want something with enough flash that I can just do a standard OpenWrt install and do opkg upgrade whenever there's a new version, rather than have to fiddle with firmware updates (downtime) which could more easily brick things (more downtime). |
|
|
|
How do I enable BFGminer to see my Jalapeno? I currently am running it on bitminter beta miner but would like to try it on BFGMINER. Thanks! It should autodetect... Be sure you're using 3.0. I am using 3.02 . Not auto detected. Do I need a driver somewhere? Or do I need to enter some code at startup to get it to detect it. Jalapeno is currently on COM3 port (USB). It is auto detected in bitminter beta though. Sounds like you have the driver installed already... Can you run bfgminer -D -T -d? and post the results here? |
|
|
|
How do I enable BFGminer to see my Jalapeno? I currently am running it on bitminter beta miner but would like to try it on BFGMINER. Thanks! It should autodetect... Be sure you're using 3.0. |
|
|
|
So the Avalon uses a TL-WR703N. Those can be had for $25 all day long. Any tried to grab one, reflash the newest CGMiner 3.1.1, and see if it works with other FPGAs or ASICs? Could be a nice, cheap alternative? Avalon uses a modified WR703N, and even then it performs poorly enough to create practical issues in some cases (pools have to implement workaround hacks). Additionally, due to the limited flash size (4 MB), you can only install pre-compressed and unchangable firmwares on it, with little breathing room for things like FPGA bitstreams (some of which are over 4 MB themselves!). |
|
|
|
And these usb's are 2.0 right? Not 3.0 Again, they're USB 1.1. |
|
|
|
|
Show Posts
