# eix bitcoin-qt
[I] net-p2p/bitcoin-qt
Available versions: 0.10.2 (~)0.10.2-r1 (~)0.11.0 (~)0.11.1 (~)0.11.2 (~)0.12.0 (~)0.12.1 (~)0.13.0 **9999 {1stclassmsg bitcoin_policy_cltv bitcoin_policy_cpfp bitcoin_policy_dcmp (+)bitcoin_policy_rbf bitcoin_policy_spamfilter dbus +http kde +libevent libressl ljr +qrcode qt4 qt5 test +tor upnp +wallet xt zeromq LINGUAS="ach af af_ZA ar be_BY bg bg_BG bs ca ca@valencia ca_ES cmn cs cs_CZ cy da de el el_GR en en_GB eo es es_419 es_AR es_CL es_CO es_DO es_ES es_MX es_UY es_VE et eu_ES fa fa_IR fi fil fr fr_CA fr_FR gl gu_IN he hi_IN hr hu id_ID it it_IT ja ka kk_KZ ko_KR ku_IQ ky la lt lv_LV mk_MK mn ms_MY nb nl pam pl pt_BR pt_PT ro ro_RO ru ru_RU sah sk sl_SI sq sr sr@latin sv ta th_TH tr tr_TR uk ur_PK uz@Cyrl uz@Latn vi vi_VN zh zh_CN zh_HK zh_TW"}
Installed versions: 0.13.0(06:14:35 PM 08/30/2016)(dbus ljr qrcode qt4 wallet -bitcoin_policy_rbf -bitcoin_policy_spamfilter -http -kde -libevent -libressl -qt5 -test -tor -upnp -zeromq LINGUAS="cs de en -af -af_ZA -ar -be_BY -bg -bg_BG -ca -ca@valencia -ca_ES -cs_CZ -cy -da -el -el_GR -en_GB -eo -es -es_AR -es_CL -es_CO -es_DO -es_ES -es_MX -es_UY -es_VE -et -eu_ES -fa -fa_IR -fi -fr -fr_CA -fr_FR -gl -he -hi_IN -hr -hu -id_ID -it -it_IT -ja -ka -kk_KZ -ko_KR -ku_IQ -ky -la -lt -lv_LV -mk_MK -mn -ms_MY -nb -nl -pam -pl -pt_BR -pt_PT -ro -ro_RO -ru -ru_RU -sk -sl_SI -sq -sr -sr@latin -sv -ta -th_TH -tr -tr_TR -uk -ur_PK -uz@Cyrl -vi -vi_VN -zh -zh_CN -zh_HK -zh_TW")
Homepage: http://bitcoincore.org/
This should get you Bitcoin Knots, which does have a history, but is supposed to filter out walletpassphrase stuff. But... unfortunately, v0.13.0.0-ga402396 (64-bit) doesn't clear the history at all. Where are you getting that version from? That indicates Core, not Knots. :/ Please open an issue here: https://github.com/bitcoinknots/bitcoin/issues |
|
|
|
I see many repeated messages, and I think this is should be honest lottery so I decide that the winner will be selected from Addresses who sent 0.001 btc to this Address: 1FvCk1jTsy7AvmnpeKnrfHSJnfX7om7fNM Bitcoin transactions don't have a "from address". If you will accept my entry at no cost, 12jixsyvXHrKPwWj8XcmvuFYyJzsWpPKAN |
|
|
|
|
You could try increasing the queue size with the -Q option.
|
|
|
|
|
getwork doesn't perform very well since it needs to make a new request for every 4 Gh... so with a S5 that's almost 300 requests per second.
|
|
|
|
|
No, antminer S* use an ugly hack of a custom kernel module.
There is nothing USB about them.
|
|
|
|
|
Looks like it's simply not getting a response from the kernel driver.
Anyone happen to know which kernel driver code the S3 uses?
|
|
|
|
Luke-Jr, are the BFGMiner builds on your openwrt repository compiled with the bitmain drivers included? I see in the openwrt directory of the github, the makefile for openwrt has it disabled. Just wondering if I am wasting my time trying to cross compile for openwrt with bitmain enabled. There is no way to tell from the already compiled BFGMiner packages are there?
Thanks for your help!
Only the ar71xx builds. I wonder if others need it? |
|
|
|
|
You're measuring shares in BTC, but they're not BTC.
|
|
|
|
|
At the very least, you will need --set bitmain:model=S3 or it won't know which protocol to use.
|
|
|
|
Hi All,
I just join your pool with 8ths.
I have a question. When pool find the block, do that pay reward right away for miners?
So long as the conditions (minimum payout, etc) are met, the reward is mined directly to miners. |
|
|
|
Firefox and Chrome have apparently decided Bitcoin (mining?) is malware  |
|
|
|
As miners should be well aware by now, using a CSV-enabled node will be required by block 419328 (~July 4). Miners using centralised pools via stratum need only ensure their pool is upgraded. Miners who are solo mining must upgrade bitcoind to Bitcoin Knots 0.12.1.knots20160629.rc2, which has just been released. Bitcoin Core 0.12.1 is not sufficient due to delays (mostly my fault) in getting GBT updated for CSV upstream. (when released, 0.12.2 and 0.13 will work) Knots can, however, be configured to use Core's policy defaults by simply adding "corepolicy=1" to your bitcoin.conf file (though I do not recommend this; Knots' own defaults are much better for the network). In any case, mining nodes should be configured for a larger-than-default memory pool. For example, "maxmempool=1000". In addition to CSV and BIP9 GBT support, Knots is also backward compatible with current versions of BFGMiner and libblkmaker (using the version/force mechanism), so you do not need to upgrade BFGMiner. (Note that unlike CSV, SegWit will require upgrading both bitcoind and BFGMiner for GBT and solo mining, so plan on this in a few months.) |
|
|
|
Is there a pool with 0% fee like Ghash.io or Eligius but with lower variance (i.e. larger pool)? These 2 pools have been unlucky lately..
Unless you're like >1% of Eligius, variance for you can't really be reduced much more... |
|
|
|
I' not sure what's wrong but mning here with Avalon4 only shows me doing at best 980 gh i have over clocked it to do 1.26th let me go on it's only on this pool it does it i can't get to hash over 1.06 th only on this pool i can go to any other pool no lie and it picks right up and start hashing at 1.26 th or better so it's not the miner .. my setting are stratum+tcp://stratum.mining.eligius.st:3334 the normal stuff after btc address is 13Xb4RvqoeRumYbzNpe4a8jNLb7N3qhFNZ would that effect it if so which one should i use . if i use just CGMiner or minera --lowmem --avalon4-fan 60 --avalon4-freq 550:500:450 --avalon4-voltage 8250 --avalon4-miningmode 0 --avalon4-automatic-voltage if I use there supplied software same setting but they do it, i even have left out some stuff and it got worse . i had this problem one other time and fixed it by using a different firmware from bitmain but that's was a antminer .that was a nice hash fork that didn't like this pool so i went back to butmains fw and it picked right up. but in this case with that Avalon4 i don't have to much pick from and BFG does not support Avalon4 and up that i see or i can't find any support or id use it . i have tried default setting under clocking and etc tried my own complied version of cgminer with just cg,miner and in minera and with the openwrt software they supply untouched. and best it hits is three hour is 724.46 and now it's actually showing it at 128 seconds 1,082.43 Gh/s with that miner and the software is showing Per 5s: 1208GHs Per 15m: 1067GHs but seems to go down as i said it's only on this pool and with the update coming i may buy 2 S7 1 a6 and set here like before sense s9 are beyond what I'm willing to pay or can afford even if i could afford one i wouldn't it's a moral thing with me and S7 and a6s are and im not blaming anyone just looking for tips to try to see if anyone has one i haven't tried yet. and it just didn't start it been going for weeks i never said any thing i was hoping id find out why and apply a fix . Probably the host CPU is too slow. You could try setting --queue N higher. |
|
|
|
Magnitudes slower than I would expect from a U3...
I also think so, may know they have a solution ? Perhaps try a lower clock rate? |
|
|
|
|
Magnitudes slower than I would expect from a U3...
|
|
|
|
|
"set-device" : ["antminer:voltage=x780","antminer:clock=237.5","antminer:chip=BM1382"]
|
|
|
|
Currently it is not practical to solo mine with CSV
Solo mining with it works fine. I'm doing so myself right now. Please don't conflate issues in BFGminer's GBT support with "solo mining" Actually following the spec is not an "issue". |
|
|
|
|
Show Posts
