Topic: [1050 TH] BitMinter.com [1% PPLNS,Pays TxFees +MergedMining,Stratum,GBT,vardiff] - page 284. (Read 837101 times)

The page currently says 1.10Ghps, not Thps. 

good idea, i like it.

A small website update today:

• Update livestats every 60 sec, both round data and top 50. If you already have the page up then refresh it to get the new one with more frequent updates.
• Link to our friends at bitcurex.com
• Display hashrate in Thps instead of Ghps at the top of the webpages
• Show only number of minutes in the block list for blocks that took less than an hour

The hashrates are still a rolling average, but they are now calculated every minute instead of every 5 minutes. This should make things a bit snappier. Downside is that the hashrate displays may be even more out of whack for the slowest miners.


Yeah, allowing connections on one of those ports should be doable. That's what you have access to through a firewall?


Yep. If we double the shift size it would take 10 hours. It would also take 10 hours of idling before your pay for blocks would be down to zero. Upside is reduced variance for non-24/7 mining, such as like now when your miners were down.

Thanks!

Yeah, just wanted to be part of the party as long as I can. Maybe I'll be able to make a whole BTC before diff increase/ASICs kick in. Will be shutting the miner down then.

~drekk~

Thank You!
This explains everything so after 5 hours or so my payments will be back to normal:)

Best

BitMinter uses PPLNS (pay per last N shares) for its payout method. This means that you're paid for the shares that you submit within the time period specified by N as long as a block is found within that time period. In the case of BitMinter, you're paid for the shares that you submit in the last 10 shifts, found here.

Doc,
Long pool is OK. However tonight my cgminer crashed. It was offline for about 5 hours or so. I started it a couple of hours ago but my payments are still very low.  I mean that guys having equal hash rate get paid 3-4xmore. However on each new block my payment increases. I guess it should back to normal after few blocks. What i am asking you if i shall be worried that something is wrong from my side or that is normal due to algorithm used when payments are calculated. For instance if i fire cgminer right now - and say i never mined here before. Mine from beginning to the end of new block did i get paid same amount like a person who has same hash rate like me (Accepted shares) but he was mining for a week without any interruption?
Thank You

Request: If/When you'll be looking at implementing the Stratum protocol, please consider making it reachable on your server through one of these ports:

1288
1863
5050
5100
5190
5560
6665
6666
6667
6668
6669
6891
6892
6893
6894
6895
6896
6897
6898
6899
6900
6901
8443

This time it's really just a matter of two more lines in the iptables configuration!
Example:


Thank you!

I'm favorable to this change! The higher the share difficulty the better.

For those experiencing high stale rate like me, a restart of the miners seems to do the trick.

Can you provide either the whitelist or blacklist (of the miners and versions) you use?
Edit: nevermind, I just reread your post

You would get lower variance for the 4 hours a day machine. That means more even payments for the work it does, instead of low pay one day and high pay another day. So that might be a plus. But it will also take some hours longer to get paid after it did the 4 hours of work. I don't know if that makes a difference for you.


Hi and welcome to the pool! Nvidia isn't the best for mining. But yeah, bitcoin is pretty awesome, so it can be fun to mine a bit even if the equipment isn't the most efficient.


The two restarts caused a few rejects, but I think most were because of the "ddos bug".

The second restart a short while ago was to get in a new version that automatically puts all requests from cgminer and bfgminer with lower version number than 2.7 on the slow queue. The "slow queue" is contained to 1 cpu core on the server. This should prevent those using old outdated miners from causing problems for users with more recent miners like you have. I'm hoping we'll see much less rejected work in the next round.

1st- upgrade to cgminer 2.7.6
2nd-You need to allow for at least 24 hours of mining to make a determination on rates (many factors affect the numbers including time of day, connection quality, etc.)
3rd-The real number is the effective hash rate shown in the pool stats (in some cases adjusting settings can correct this, look for a default .cgminer.conf and adjust your queue downward, larger queue = more stales on the LP (block change) notification from the pool)

1.6% now
Personally I use cgminer 2.7.5 and went from <0.3% before last update to >1.3% now.
I don't know, something is obviously wrong.

Just wanted to say "Hi!" to everyone, so:
Hi everyone!

I'm mining with BitMinter (pool & client) for about a week now. Just adding my little 160 MH/s with a spare GTX 570, so I'm probably losing money, but that's 24/7. Awesome!

Cheers,
~drekk~

TBH I'm not sure how the difficulty change would affect me, I only hash at about 350mh/s 24/7 and my girlfriends PC about 300mh/s approx 4 hours a day when she leaves her PC on...

1 pro, 1 contra and 1 neutral. Not a lot of interest for this. Perhaps the last increase to N=2x diff was enough?


The bug is fixed but there are still users with buggy miners and my protection against that isn't very successful. When a miner starts attacking the pool with thousands of requests per second the protection doesn't kick in quickly enough. It's actually not an easy problem to solve without blocking out large proxies and other large mining operations. It's hard to tell them apart from a buggy miner if you only have a second to do it.

I'm now thinking about putting buggy versions of cgminer and bfgminer automatically on the slow response list together with cpu miners. Placing them there all the time, not only when they misbehave. I have asked people to upgrade a long time ago both here and on twitter. I think this solution is more fair than letting the buggy miners cause slow response for other users. cgminer 2.7.6 is out and working great. Just upgrade. You don't still use internet explorer 6 do you?

The first few block changes after I put in the new version were awful. Thousands upon thousands of useless requests for several seconds. Then we had something like 10 block changes that were perfectly smooth. And before I wrote this we again had a couple block changes where the pool was effectively DDoSed by its own miners. It's kind of funny when you think about it.

Stale ratio went from <0.4% to <0.8%
Looking forward the next block to see if DrHaribo really fixed the bug

My hashrate votes no on this, simply because I cannot see the benefit, where as taking a quick look at my hashrate during the last 10 shifts now shows me quite accurateley when something is wrong with one of my four workers.

New mining backend is up with rollntime for everyone (again). We even got a block a moment after I started it. Must be a good sign.

If you are running on port 9000 you can move back to 8332 now. Thanks a lot for the help with testing! I will shut down 9000 soon, just giving people a chance to change their setup. Testing on 9000 will probably be back when I have a version with variable difficulty.

By the way, I also noticed there's a new cgminer 2.7.6 out. If you are on cgminer it should be worth a quick upgrade.

Stratum isn't HTTP so it may be more trouble than it's worth to get it running on the same port with HTTP stuff. GBT and getwork is much easier to run through a webserver.