Anyone with a (real) Icarus kicking around? Would be nice to test that some recent changes don't break it, if possible... |
|
|
|
Hmm, that makes sense to me. So, there is no way of fighting against mining centralization? I thought p2pool is a decent solution... Sure, there's getblocktemplate, a decentralised client-server mining protocol. Basically all the positives of p2pool without the negatives. Just needs more time to finish implementing it... The difference is a 51% attack on the p2pool chain would be immediately obvious to all miners monitoring it - p2pool finds a block, but no payment is made since the attacker has substituted their own btc addresses into the sharechain, instead of the legitimate miners.
In this event, I imagine miners would just jump ship, if a better solution isn't implemented by then. Until then, though, it still has its advantages.
Just like all the miners jumped ship from Arsbitcoin when it forked off the blockchain? Or when it shutdown? Or like when they jumped ship when 0.8-based pools forked off the main bitcoin blockchain? Or like when they jumped ship from Deepbit when it stopped mining valid blocks? Sadly, most miners don't pay attention. |
|
|
|
But in p2pool the attacker automatically does not get any payout.
Right?
Sure he does. He could even 51% attack p2pool to get up to ~200% PPS (at the expense of everyone else). |
|
|
|
Does block withdraw method work against p2pool?
You mean block withholding. Yes, it does. It's actually worse there because nobody can stop it. |
|
|
|
That means that Arch Linux will be gone and replaced with a full embedded os. This will allow lots of things, simply updates, improve security, allow ASIUC manufacturers to use it etc....
why don't you just use Raspian?  You could then easily support updates not only for your own packages via apt (you could even script/chron this for auto updates) but also for the core supportive packages as well no need to reinvent the wheel Raspbian would obviously only work on Raspberry Pi... |
|
|
|
Is there a current version of this for Ubuntu? The one from the repository is 3.*, but I'm using it with my Rockminer so it needs to be the latest version.
unit3, our PPA maintainer, has stopped mining, so someone may need to volunteer for this job... Ubuntu utopic comes with 4.3.0, though.Note that Debian is maintaining official packages for BFGMiner, so I think it's simply a matter of uploading the source stuff to Launchpad. If someone wants to put together simple instructions, I'd be glad to do it myself. |
|
|
|
I thought I'd mention that it seems BFGMiner will now support The "jingtian" miner, which is essentially the same thing as all the other A1 miner clones. I'm not sure if it is... JingTian has a microcontroller that IIRC they designed themselves. Either way, let me know how this works out.  |
|
|
|
I would like Support for COINTERRA ASICS please.
See cointerra branch for a hack, or help develop cointerra_fresh (it doesn't get full hashrate, and haven't figured out why). |
|
|
|
NEW VERSION 4.4.0, JULY 7 2014Human readable changelog:- getwork and stratum proxy drivers: Proxy-share difficulty is now adjustable using --set pxy:diff=N and/or --set pxy@username:diff=N
- Mac OS X: Support for automatic detection of capable devices at startup.
- jingtian: Support for this new platform. Must be compiled on the Raspberry Pi itself with --enable-jingtian
Full changelog:- lowl-vcom: Added support for auto scanning (-S auto) on Mac OS X
- rockminer: implement --device-protocol-dump for debugging
- README: Update for commandline options
- README: Update configure options
- Bugfix: bfg_gpio_setpin_output: Clear alt-function bits via INP_GPIO macro
- jingtian: Explicitly configure SPI device while opening
- jingtian: Toggle ASIC reset GPIO at startup
- aan: Set defaults as soon as a proc is initialised
- aan: Allow specifying clock as xHEXX for a raw PLL register config
- aan: Include current frequency in RPC status
- aan: Implement --set jtn:clock=MHz
- aan: Logic to calculate PLL configurations for a given frequency
- jingtian: Use SPI enable GPIO to disconnect SPI during chipselect changes
- aan: Set PLL to 850 MHz
- aan: Simplify register buffer
- jingtian: Decode extra temperature bytes in read_reg
- aan: Add a read_reg hook
- aan: Enable configuring nonce diff with (eg) --set jtn:diff=32
- aan: Properly handle nonce_diff
- aan: Implement mining
- DevAPI: Some designs set the main thr tv_poll from secondary thrs, so check it after the loop
- aan: aan_spi_parse_rx implies spi_clear_buf
- jingtian: Do detection asynchronously across all possible chipselects so they complete in parallel
- aan: Refactor aan_spi_cmd a bit
- jingtian: Implement device protocol dump
- jingtian: Detection-only code for new driver
- lowl-spi: GPIO access functions
- lowl-spi: Move knc_spi_txrx to linux_spi_txrx
- SGW: Support for proxy-share difficulty preferences
- SSM: Propagate proxy-share difficulty changes to established connections
- SSM: Track stratum connections for each proxy user
- SSM: Track authorised users for each connection
- SSM: Initialise proxyshare difficulty from --set pxy:diff=N
- proxy: Accept --set pxy:diff=N to set preferred proxyshare difficulty
- proxy: Provide a place to store desired proxyshare difficulty on a per-username basis, and copy it to SSM connections when authorising them
- SSM: Track proxy share difficulties
- Expose target_diff function and add pdiff_to_bdiff macro
- util: double_find_precision function to identify ideal precision for a fp number
- work2d: Expose WORK2D_MAX_DIVISIONS in header
- add_local_gbt: Avoid adding servers already configured
- Bugfix: Avoid writing automatically configured local GBT servers to the config file unless they have been manually enabled
- add_local_gbt: Use rpcconnect when configured
- rockminer: Bugfix: must specify a baud rate (maximum of 115200) to get a read response
- Bugfix: Use atexit() to ensure a final \n is always printed at exit to work cleanly with new logging design
- Restore compatibility with old versions of libblkmaker
- Bugfix: probe for ZeusMiner before probing for DualMiner
- Wait until coinbase-addr is needed again, before updating it following a block change (always using getaccountaddress)
- Don't automatically use #getcbaddr for local bitcoind if the user provided their own
- Bugfix: refresh_bitcoind_address: Check for NULL json (which is not JSON "null")
- Bugfix: add_pool: If no current pool set, initialise it (otherwise pool testing may start a longpoll thread which tries to access currentpool uninitialised)
- devpath_to_devid: *nix: Reject anything that doesn't begin with a /
|
|
|
|
Can someone give me an example of a bfgminer.conf file that has settings on per-device basis? I have a few devices that achieve best results at different speeds. So, based on their serial number I want to configure them to start automatically at the desired speed. (as opposed to me going and adjusting the speeds every time I start them). Ideally I'd like to have one set of global settings with a few exceptions for this and that device. You can use NFY devices as an example - e.g. this is what I currently have: {
"set-device" : [
"NFY:baud=500000",
"NFY:osc6_bits=56"
]
}{
"set-device" : [
"NFY:baud=500000",
"NFY:osc6_bits=56",
"NFY@serial:osc6_bits=58"
]
} |
|
|
|
Thanks for posting this. Now that its been running for a couple days is it stable? I was having issues with the miner dying on me after about 24 hours.
Nope. The R-BOX is not stable at all with BFGMiner 4.2.0. I keep getting the SICK/DEAD problem everyone else is having. It works for a while and then just croaks. BFGMiner 4.3.0 should have addressed all the R-BOX hangs. |
|
|
|
There's a potential issue with the new features for final failover: - URI parameter #getcbaddr to request coinbase address from bitcoind or compatible servers for solo mining.
- When running on systems with a configured Bitcoin Core server, it is automatically configured as a final failover and used for local block submission (GBT pools only) to reduce the risk of a stale block.
I run my own p2pool node locally... and the Bitcoin Core client I have running is using the disablewallet=1 to reduce unneeded resource use. I have my p2pool configuration point to specific address instead for the default payout address. BFGMiner doesn't know this since it sees Bitcoin Core running and instead requests #getcbaddr from Bitcoin Core, which can't because the wallet is disabled. This should cause any practical problems, I think? Is there a way we can configure this or disable the "Final Failover" pool? --no-local-bitcoin |
|
|
|
About how far out is the development for adding support for Avalon2 miners?
The code's pretty much done (avalon2_rig branch), but doesn't work for some currently-unknown reason. xiangfu sent me some debug cables, but we haven't yet managed to meet up so he can tell me how I'm supposed to use them. |
|
|
|
In v4.3.0 of BFGM, is dual mining switched-off for G-Blade, or one has to do so by passing certain command in argument field? It is my understanding that G-Blades do not support dualmining at all. |
|
|
|
Thant's ok luke, neg trust me for your distrust of distrusting you . Hey, it's your reputation that will be ruined by leaving false feedback, not mine.  |
|
|
|
Who the fuck we blame, Luke to take the shit? Why are you so anxious to blame me? I have nothing to do with this. Blame yourself maybe? At least you're involved... |
|
|
|
Yea well why couldn't bfgminer from the dev not rec. my miner but the bfgmniner build from Darkwinde could???
Why hasn't luke responded? Because this isn't my area. nwoolls is the BFGMiner scrypt dev, and he handles the Zeusminer driver. If you (or anyone else) want to send me a sample unit and pay me hourly (I don't have any personal interest in scrypt stuff), I am glad to investigate this. But you're probably better off working with nwoolls. Edit: Note that if another developer wants tips on modifying BFGMiner themselves, I'm certainly open to sensible discussion and advise at no charge. |
|
|
|
|
Done, is that how you wanted it?
|
|
|
|
|
Show Posts
