I decided to try this pool a few days ago, thinking it didn't have stratum support. But you sneaked in the support just before I joined . I hope you enable merged mining on stratum soon, though I see the altcoins are accumulating anyway.
|
|
|
I am tentatively elevating the status of 2.11.2 to stable.
It is worth reminding people that on windows+fpgas you will need to install a winusb driver as it says in the fpga readme compared to running versions of cgminer <2.11 which used the old serial interface.
It is also worth mentioning that stability seems to be compromised when built with an older version of libcurl.
What is the first safe version to use?
|
|
|
ra3QBkZeZqoHUXT8K6ekiZ965bq4etjDXL
|
|
|
Why would anyone use their loyalty points on the redeem pool now? $2.5 per GH/s per day is less than 100% PPS.
|
|
|
can workers be sorted alfabeticaly? now its random.
p.s.
correct me if I'm wrong, with EMC disabling NMC mergemining, BitMinter is the single most efficient pool. only one with all 4 efficiency-important features : stratum,NMC,no fee,paying transfer .
This is exactly why I'm staying with BitMinter. But I can't imagine how the pool could stay online if everyone had their fee set at 0%
|
|
|
Oops I forgot to fix the reward graph. Now working properly again.
It was still assuming that blocks should give 50 BTC instead of 25 BTC so our luck looked horrid.
Thanks for the fix! By the way, is the reward page causing a large load on the server every time it's viewed? It loads quite slowly.
|
|
|
Besides p2pool and eligius (and solo), which pools pay directly in mined coins?
Dunno. But being paid at the threshold you set is one of the benefits of mining on a pool. I don't want to be paid in really small BTC fractions. But Eligius does have a payment threshold. I only got coins generated to my address when I exceeded the threshold of 0.67 BTC. How does that work? It might be problematic with large thresholds, eg. in the extreme case that everyone has their threshold set to the block reward amount and start mining at the same time. At first, the pool wouldn't have any users who have exceeded their threshold, so they'd have to generate rewards to the pool's wallet. That can't be used for payments later, though. After users start hitting their thresholds, how can they be paid? Maybe such a system needs a small enough threshold to work in practice.
|
|
|
Why not include merged mining support on the list? It took me a minute to find out which pools support both stratum and merged mining (only Eclipse and BitMinter AFAIK). Namecoins currently add about 3% to my daily rewards. +1
|
|
|
I created a new worker and so far it's accumulated an equal amount of BTC and NMC shares, as expected. Something's clearly wrong with the numbers on the old worker.
|
|
|
I just realized that I have in total about 20% more accepted namecoin shares compared to bitcoin shares. Not speaking of per round shares here, those will obviously be wildly different because the chains don't have same difficulty. Maybe I just don't understand merged mining well enough, but shouldn't the total share numbers be roughly equal? I thought every share is used on both chains.
Isn't that because NMC difficulty is lower than BTC difficulty? So a share that isn't good enough to meet Bitcoin difficulty might be good enough to meet NMC difficulty? I believe that applies for blocks only - each share should be accounted for in both chains, and then checked against the block difficulty of both chains. For example, if you submit a 1M/16 share, your target difficulty was 16, but the actual share difficulty happened to be 1M. That's not enough to solve a BTC block, but it does solve an NMC block. Because the share target was 16, that should increase your accepted share count by 16 for both chains. Whatever the block difficulty of both chains is, that shouldn't affect the amount of accepted shares in any way. Every share should increase the accepted share count of both chains by the same amount, unless I'm missing something here.
|
|
|
I just realized that I have in total about 20% more accepted namecoin shares compared to bitcoin shares. Not speaking of per round shares here, those will obviously be wildly different because the chains don't have same difficulty. Maybe I just don't understand merged mining well enough, but shouldn't the total share numbers be roughly equal? I thought every share is used on both chains.
|
|
|
Ukto announced on IRC that there will be maintenance downtime today.
|
|
|
I also have my payout threshold set to 0.01 BTC, but haven't received a payment even though my balance has been over that for weeks. I know that amount is very low and might not be sensible to pay out, but if that's really the case, you should clearly state what the minimum payment threshold is.
|
|
|
Another similar bug happens sometimes when you rename a receive address. It can also randomly renames some other receive address so that you now have two addresses with the same label. The randomly renamed one will reset back to its original name after restarting.
|
|
|
I'll still take 1 for novelty....let me know your BTC address and how much you want.
You can have bitcoins generated directly to your address by mining at a pool that does it's payouts like that. P2Pool and Eligius might be the only ones, here's an example of an Eligius payout. But that's still not the same as having the whole block reward generated to you.. or is it? I don't really know what's the value-adding thing here.
|
|
|
Nope, I just happened to catch that one as it happened. I'll try using cgminer's sharelog function, but if that rejection only occurs with shares very close to the target, it might be rare and take a while to see again.
|
|
|
juhakall, a 4/4 difficulty proof being rejected sounds strange.. I'll have a look at it. This was with Stratum?
Yes, that's with stratum. The target is the exact same you mentioned previously, so the share should be accepted. Do you have the time when this happened? If so I'll have a look at the logs if there are any errors. Maybe the data is mangled somehow, so when the server hashes it the share doesn't even meet diff 1. Date was 2012-12-20 17:29:06 UTC.
|
|
|
juhakall, a 4/4 difficulty proof being rejected sounds strange.. I'll have a look at it. This was with Stratum?
Yes, that's with stratum.
|
|
|
|