decred hashrate reported on pool is much lower than reported by miner. any reason why?
its an average from the last 5 minutes, so it will always look low after you've just begun mining. even then, it will at times drop below your true hash rate. Generally, so long as you can see your shares being submitted on your miner, take what the website UI displays with a grain of salt. Looking at the graph, website is off from miner by a factor of 2-3x. Reported 5min hash rate similarly off.
|
|
|
decred hashrate reported on pool is much lower than reported by miner. any reason why?
|
|
|
Another feature that i'd like to suggest is a way to for us to identify which card on a rig relates to the GPU number. The only way I can think of doing this would be, for example, if you hit CTRL+0, then it will adjust GPU#0's FAN to 100% while adjusting all other GPU fans on that rig to 5% for 15 seconds, that way we can know that GPU0 will be the card on the rig thats running the fans at full speed. This would be a huge help with troubleshooting hardware.
Can second this - GPU ordering is totally wack in this miner. GPU-Z, Afterburner, etc seem to show the GPUs in a totally different order. True, one can always see temps in the miner and try to match them in gpu-z to see "what's what". I can add to this that claymore miner isn't internally consistent. Order of GPUs shown in mining stats messages doesn't match order of GPUs shown in temperature stats messages. Not the end of the world, but it can be confusing.
|
|
|
Webserver has been a little unstable. Stratum server and bitcoind have been rock solid. Rest assured even if the website and stats pages are inaccessible, your shares are being counted as long as your miner is connected. Webserver instability will be addressed soon.
|
|
|
A hardkernel odroid c2 will probably fit the bill. it is a 64bit arm platform for 40$ USD that can run native 64 bit arch linux (or ubuntu or debian or whatever you like). Better performance than rpi3 but no built in wireless protocols. huge plus is it can use an emmc chip for storage instead of/in addition to micro sdxc. i have my system root on a 8gb emmc module and extra 128gb storage on sdxc class 10 uhs-1. I actually use mine as a desktop right now, but i see no reason it won't work just fine for your needs. the only downside is a lack of hardware accelerated drivers for Xorg, but they should be coming sometime in April. http://odroid.com/dokuwiki/doku.php?id=en:odroid-c2http://www.hardkernel.com/main/products/prdt_info.php?g_code=G145457216438
|
|
|
Announcing a new promotion: fee sharing. See OP for details.
|
|
|
Do you by any chance have a consolidated log of the changes since last tag? (don't asking you to do it, just to see if there's a convenient place already to not waste time).
Read the titles of each commit on bitbucket. Ck and kano seem to provide very descriptive info in the titles of the commits.
|
|
|
so ya I think Im definitely going to start looking at getting my miners hosted somewhere. my ac crapped out last night and is only blowing ambient temps the house is pretty toasty right now.
gotta find a couple more blocks today so I can pay to fix my ac.
I know its OT, but toomim bros and sidehack have good reputations for hosting.
|
|
|
pushing 1.5 PH here until my btc on nicehash runs out. gotta break this block.
edit: up to 1.5 PH that is... Not gonna pay more than 100% expected payout...
|
|
|
Oh I guess unrelated question: any reason not to run on the latest version in the master tree? Is that what you're typically using in production? I know I've asked about the M tags before, but it doesn't seem like they keep up as much, as there hasn't been one in over a month (which isn't a big deal, but just curious).
There was very real instability in there. New tag just hit. recommend M24 then or v0.9.3?
|
|
|
Oh I guess unrelated question: any reason not to run on the latest version in the master tree? Is that what you're typically using in production? I know I've asked about the M tags before, but it doesn't seem like they keep up as much, as there hasn't been one in over a month (which isn't a big deal, but just curious).
|
|
|
Agreed on all counts. Thanks for the input though.
|
|
|
I dug a little deeper and it seems it coordinates with warnings from ckdb about taking a long time to getblocktemplate, which I guess is not surprising. I guess bitcoind is running slow or something. whther or not that could be affected so much by filesystem I know is off topic here, but an interesting thing to inspect I guess.
|
|
|
@ck I'm running on commit f35f54a ( https://bitbucket.org/ckolivas/ckpool/commits/f35f54a6428a99bacad6daedbd7cd8367c985242) from 2/23/16. I recently started noticing the odd occasion where there is a 2-40 second lag between block change of bitcoind/notifier running and ckpool logging a "block hash changed" message. When I was running this on a different box with half as many cores and same amt of RAM, I was getting no lag at all (seeing less than a second between "UpdateTip" from bitcoind to "block hash changed" from ckpool). One difference in the two boxes is file system. Could suboptimal fs performance be causing this? The older, seemingly quicker-to-change setup had the blockchain stored on ext4 while the newer, seemingly laggier-to-change setup has the blockchain stored on btrfs (I wanted to save some physical space with transparent compression... note to all: feel free to berate me on use of btrfs, but I don't want to derail this thread). I can obviously reformat to ext4 and copy the blockchain over and back from a backup volume, but before I go through all that headache, I wanted to get your perspective on if it could be the root cause of the lagginess.
|
|
|
Luckypool.co has been shut down for lack of use Luckypool.co is a new Bitcoin mine that supports BIP109
Luckypool.co currently only supports solo mining.
Come visit us at https://luckypool.co
/Fee sharing/
Luckypool.co now features a unique promotion called fee sharing. At all times, there can be one "Luckyminer" who will recieve 50% (so 0.5% of transaction fees + block subsidy) of collected fees for all blocks found at Luckypool.co. This miner is selected by being the first block finder when there is currently no one sharing fees. This 50% fee share will last through the next two difficulty changes.
Here is an example:
- Miner1 finds a block and becomes the Luckyminer and will begin collecting 50% of all fees. This amount is calculated as: (.005)x(transaction fees + block subsidy). This additional reward is calculated for every block found, starting with the block Miner1 just found, and sent to Miner1's Bitcoin address.
- Approximately 3 days later the network difficulty changes. Miner1 is still sharing fees.
- Approximately 2 weeks after the last difficulty change, the difficulty changes again. Miner1 is no longer sharing fees.
- Until another block is found, fees will not be shared.
- Note that each new fee sharer will share fees from the block which made them the fee sharer.
/Configuration/- Address and port - solo.luckypool.co:3333
- Username - any valid Bitcoin address with optional worker extension (worker extension starts with a period)
- Username Example without worker name - 1PKMYiumvScJhpMTuKoWM6vp5HBqkyrzC8
- Username Example with worker name "worker1" - 1PKMYiumvScJhpMTuKoWM6vp5HBqkyrzC8.worker1
- Password - x
- IMPORTANT NOTE - The validity of the Bitcoin address you use will not necessarily be checked. Please take care to make sure it is valid and belongs to you. Blocks solved to an invalid address will be donated to the admin.
- Example command line for cgminer - cgminer -o stratum+tcp://solo.luckypool.co:3333 -u 1PKMYiumvScJhpMTuKoWM6vp5HBqkyrzC8.worker1 -p x
/Stats/Limited statistics can be found at http://www.luckypool.co/stats/. Stats will refresh once per minute. /FAQ/What payout scheme does Luckypool.co use?There is no payout scheme. If you find a block, the bitcoins (block subsidy + transaction fees) will be initially generated to 1FcxM9zzYceogy2CW3V8LMXpFzmFPa5n1s and from there distributed to the Bitcoin address you are using as a username, less a 1% fee for maintenance of Luckypool.co. Note that at current block subsidy and exchange rate this means if you find a block you will recieve a little over 25 BTC (equivalent to over $10,000 USD). Why would I solo mine here instead of on my own Bitcoin node at home or in my data center?The admin of Luckypool.co has made every effort to ensure it keeps up with block changes. Casual observation of logs has shown that Luckypool.co typically responds to new blocks on the network within less than a second. It's unlikely your node does the same. Mining here removes the overhead (bandwidth, storage, time) of running and maintaining a full node at home or in your datacenter. Are transaction fees included in the amount I will get paid out?Yes. Transaction fees contained in a block will always be contained in the payout for that block when the block is found. Luckypool.co will pass along those transaction fees (less 1%) to the block finder. What is BIP109?BIP109 is a one-time increase in total amount of transaction data permitted in a block from 1MB to 2MB, with limits on signature operations and hashing. BIP109 is currently implemented in Bitcoin Classic. You can read more about it on the official Bitcoin Github. What kind of mining do you currently support?Currently we support solo mining only. We may support pooled mining in the future. How do I mine here?Please see the section labelled "Configuration". Is Luckypool.co affiliated with any existing or former pools?No. At this time Luckypool.co is not affiliated with any existing or former pools, including luckypool.cn[/s]
|
|
|
So what is the point for mindiff? I am just trying to understand all the settings. I am running ckpool locally, just getting started in bitcoin. And interested in the concept as a social and economic disruptive technology.
mindiff is the bottom limit for the vardiff calculated by the pool. read about vardiff here: http://give-me-coins.com/support/faq/what-is-vardiff/(also this is getting a little off topic. Might want to post a new thread for non-ckpool-related questions)
|
|
|
|