I know this is very late but I missed this. Eruptor, all litecoins of blade subreddit solo follow the Modiquette. Some devices will never be able to work on them, some work fine, and some require hacks to workaround the problem. Who cares about roi mining you mine for free. Jul 4, compat.
It does not take into account difficulty increases correctly. Turn spidevc into lowl-spi to fix building the knc driver wit…. Disable OpenCL by default Nov 22, adl. We suggest to prevent the control board to be powered up before hash boards be powered up. It's going to fluctuate, and can fluctuate wildly depending on how many people try to all jump on the already full ship. Drop custom hexdump logging. C reserves identifiers beginning with an underscore and upper… Feb 23, iospeeds.
I blade sell at least 10 XBT mining knowing the market is stupid and blade and willing to overpay I will sell at mining the market price desires. Is there a GUI version? Raspberry Pis have hardware defect s which affect USB devices to varying degrees. The source code for MultiMiner is publicly available and regularly updated. Solo your GPU will melt your laptop even faster. Solo every litecoins weeks, you get less bitcoins with the same hash eruptor mining power based litecoins what the difficulty eruptor are.
Avoid leaking devname when detecting claimed devices Nov 28, driver-nanofury. Add no-goffset support to scrypt kernels Nov 24, driver-opencl. Add "goffset" setting to override detection of support for gl… Nov 24, driver-proxy. Propagate proxy-share difficulty changes to established connections Jul 4, driver-rockminer. Replace mess of encoding proxy into pool URI with a --pool-pro… Sep 13, findnonce.
Add a simple "fullheader" kernel interface Nov 18, findnonce. Teach findnonce to behave based on kernel interface rather th… Nov 18, gc Replace bashism "here string" Jul 12, httpsrv. C reserves identifiers beginning with an underscore and upper… Feb 23, iospeeds. Portability fixes, including big endian compatibility Jun 30, libztex. C reserves identifiers beginning with an underscore and upper… Feb 23, linux-usb-bfgminer Merge commit 'a6a' into bfgminer Feb 13, logging.
Drop custom hexdump logging Sep 30, lowl-ftdi. Rename files to lowl-ftdi. Support for Monarch devices on Windows using new "mswin" lo… Jul 23, lowl-mswin.
Support for Monarch devices on Windows using new "mswin" lo… Jul 23, lowl-pci. Never set timeout to 0, since it disables the timeout… Jul 9, lowlevel. Add device ids to vfio-pci even if they didn't ha… Jul 20, sha2.
Drivers should not be doing fulltest on their own, so remove it Nov 14, start-bfgminer. Shell script to re start bfgminer in a background… Apr 22, test-bfgminer. Jul 4, windows-build. Sanitise lock situation for work2d Jan 30, This code is provided entirely free of charge by the programmer in his spare time so donations would be greatly appreciated.
Please consider donating to the address below. If you specify the --socks-proxy option to BFGMiner, it will only be applied to all pools that don't specify their own proxy setting like above After saving configuration from the menu [S],[W] you do not need to give BFGMiner any arguments, it will load your configuration instead.
Any configuration file may also contain a single "include": Writing the configuration will save all settings from all files to the output configuration file.
You may run BFGMiner from the build directory directly. When you are ready to build BFGMiner, you may need to point the configure script at one or more pkg-config paths. You can then run from any terminal. Run "bfgminer --help" to see options: This varies by operating system. By default, BFGMiner will scan for autodetected devices.
If you want to probe all serial ports, you can use "-S all"; note that this may write data to non-mining devices which may then behave in unexpected ways! To force the code to only attempt detection with a specific driver, prepend the argument with the driver name followed by an "at" symbol. To use these devices, you must download the proper bitstream from the vendor's website and copy it to the "bitstreams" directory into your BFGMiner application directory.
FPGA for more information regarding these. The following options are available while running with a single keypress: Current pool management strategy: The running log shows output similar to that below: The 2 diff values are the actual difficulty target that share reached followed by the difficulty target the pool is currently asking for.
If BFGMiner has a working block notification source, the protocol will be prefixed by a plus sign. If not, a minus sign. If you are mining on multiple pools at once, the pool display instead shows: The block display shows: The BFGMiner status line shows: The number of devices and processors currently mining Hottest temperature reported by any processor 20 second exponentially decaying average hash rate configurable with --log option An all time average hash rate An all time average hash rate based on actual nonces found, adjusted for pool reject and stale rate The number of Accepted shares The number of Rejected shares and stale shares discarded never submitted , and the percentage these are of total found.
The number of HardWare errors, and percentage invalid of nonces returned Each device shows: A number of different strategies for dealing with multipool setups are available. Each has their advantages and disadvantages so multiple strategies are available by user choice, as per the following list: The default strategy is failover. This means that if you input a number of pools, it will try to use them as a priority list, moving away from the 1st to the 2nd, 2nd to 3rd and so on. If any of the earlier pools recover, it will move back to the higher priority ones.
This strategy only moves from one pool to the next when the current one falls idle and makes no attempt to move otherwise.
This strategy moves at user-defined intervals from one active pool to the next, skipping pools that are idle. This strategy sends work to all the pools on a quota basis. By default, all pools are allocated equal quotas unless specified with --quota. This apportioning of work is based on work handed out, not shares returned so is independent of difficulty targets or rejected shares.
While a pool is disabled or dead, its quota is dropped until it is re-enabled. Quotas are forward looking, so if the quota is changed on the fly, it only affects future work. If all pools are set to zero quota or all pools with quota are dead, it will fall back to a failover mode. See quota below for more information. The failover-only flag has special meaning in combination with load-balance mode and it will distribute quota back to priority pool 0 from any pools that are unable to provide work for any reason so as to maintain quota ratios between the rest of the pools.
This strategy monitors the amount of difficulty 1 shares solved for each pool and uses it as a basis for trying to doing the same amount of work for each pool. To use this mode, you need to specify the URL of your bitcoind node using the usual pool options --url, --userpass, etc , and the --generate-to option to specify the Bitcoin address you wish to receive the block rewards mined.
When you run Bitcoin Core on the same computer as your miner, the pool itself will be automatically configured for you on the default goal. Please be aware that solo mining via GBT is at this time only supported for Bitcoin.
If you are solo mining with more than one instance of BFGMiner or any other software per payout address, you must also specify data using the --coinbase-sig option to ensure each miner is working on unique work. Note that this data will be publicly seen if your miner finds a block using any GBT-enabled pool, even when not solo mining such as failover.
If your bitcoin node does not support longpolling for example, bitcoind 0. Note that solo mining does not use shares, so BFGMiner's adjusted hashrate third column may suddenly drop to zero if a block you submit is rejected; this does not indicate that it has stopped mining.
Example solo mining usage: This is Joe's block! Example multi-blockchain solo mining usage: The quotas handed out by default are equal, but the user is allowed to specify any arbitrary ratio of quotas. Quotas can be changed on the fly with RPC, and do not act retrospectively.
Setting a quota to zero will effectively disable that pool unless all other pools are disabled or dead. In that scenario, load-balance falls back to regular failover priority-based strategy. While a pool is dead, it loses its quota and no attempt is made to catch up when it comes back to life. To specify quotas on the command line, pools should be specified with a semicolon separated --quota or -U entry instead of --url. Pools specified with --url are given a nominal quota value of 1 and entries can be mixed.
Writing configuration files with quotas is likewise supported. To use the above quotas in a configuration file they would be specified thus: In other words if you would normally use: There is also the -m option on linux which will spawn a command of your choice and pipe the output directly to that command.
The WorkTime details 'debug' option adds details on the end of each line displayed for Accepted or Rejected work done. An example would be: The previous hash is followed by the getwork mode used M: X where X is one of P: The argument to the option may be "-" for standard output not advisable with the ncurses UI , any valid positive number for that file descriptor, or a filename. To log share data to a file named "share.
On UNIX-like operating systems, you often need to run one or more commands to reload library caches, such as "ldconfig" or similar. In this case, you can usually add it like this: BFGMiner segfaults when I change my shell window size. Older versions of libncurses have a bug to do with refreshing a window after a size change.
Upgrading to a new version of curses will fix it. I have multiple USB stick devices but I can't get them all to work at once? Very few USB hubs deliver the promised power required to run as many devices as they fit if all of them draw power from USB.
Devices may use up to 2. You can estimate how much power your USB hub can provide by multiplying its power supply's output amps by volts so, if it says 12V 2. Some USB hosts cannot deal with polling as often as miners may need for quick delivery of shares. On Linux, you can request putting VCOM devices in "high latency" mode or rather, disabling the default "low latency" mode using the setserial command: I've plugged my devices into my USB hub but nothing shows up?
Can I mine on servers from different networks eg smartcoin and bitcoin at the same time? No, BFGMiner keeps a database of the block it's working on to ensure it does not work on stale blocks, and having different blocks from two networks would make it invalidate the work from each other. No such feature has been implemented to support this. Can I put multiple pools in the config file? Yes, check the example. The build fails with gcc is unable to build a binary.
Can you implement feature X? I can, but time is limited, and people who donate are more likely to get their feature requests implemented. Work keeps going to my backup pool even though my primary pool hasn't failed? BFGMiner checks for conditions where the primary pool is lagging and will pass some work to the backup servers under those conditions.
The reason for doing this is to try its absolute best to keep the devices working on something useful and not risk idle periods. You can disable this behaviour with the option --failover-only.
Is this a virus? As BFGMiner is being packaged with other trojan scripts, some antivirus software is falsely accusing bfgminer. If you installed BFGMiner yourself from a reputable source then you do not have a virus on your computer. Complain to your antivirus software company.
They seem to be flagging even source code from BFGMiner as malicious now, even though text source files can't do anything by themselves. Can you modify the display to include more of one thing in the output and less of another, or can you change the quiet mode or can you add yet another output mode? Everyone will always have their own view of what is important to monitor.
The defaults are very sane and I have very little interest in changing this any further. Efficiency simply means how many shares you return for the amount of bandwidth used.
It does not correlate with efficient use of your hardware, and is a measure of a combination of hardware speed, block luck, pool design and many other factors. Most user defined settings lead to worse performance.
What happened to CPU mining? CPU for more information. Is there a GUI version? Name Website Operating system s EasyMiner http: Is there a "bare-metal" version? Yes, there are a few dedicated mining operating systems built on BFGMiner: Genesis Mining offers three Bitcoin cloud mining plans that are reasonably priced. Zcash mining contracts are also available. Hashing24 has been involved with Bitcoin mining since They have facilities in Iceland and Georgia. Minex is an innovative aggregator of blockchain projects presented in an economic simulation game format.
Users purchase Cloudpacks which can then be used to build an index from pre-picked sets of cloud mining farms, lotteries, casinos, real-world markets and much more. Offers both pool and merged mining and cloud mining services for Bitcoin. Hashnest is operated by Bitmain, the producer of the Antminer line of Bitcoin miners. HashNest currently has over Antminer S7s for rent.
You can view the most up-to-date pricing and availability on Hashnest's website. Bitcoin Cloud Mining Review: Currently all Bitcoin Cloud Mining contracts are sold out. NiceHash is unique in that it uses an orderbook to match mining contract buyers and sellers. Check its website for up-to-date prices.
Eobot claims customers can break even in 14 months. Some miners available for rent include AntMiner S4s and S5s. We want to spread knowledge about Bitcoin everywhere, do you think you can help us increase our content or translate for those who don't speak English?