Topic: Bitminter bitcoin mining pool - shutdown mining 2020-07-01 website 2021-06-01 - page 45. (Read 325004 times)

That is not what I'm seeing, for example here is a reject that just happened as a result of the work restart:

You can see the same type of work rejection in the screen cap I posted a few posts up, too.


Done, I unchecked that box for all my workers.  What are the pros/cons of that check box?  I would hope to eliminate work restarts outright rather than reduce the frequency.  Oh, and the screen cap immediately above was taken 15 minutes after I made this change, so it did not appear to eliminate it.

And no explanation why my gekko stick only mines here at 4-5GH instead of 12-14GH?  It's very odd and I can reproduce easily, just change from kano to bitminter back and forth and note the speed difference.

You mine sha-256 at Bitminter and scrypt at another pool at the same time? And then what happens? I'm not familiar with the term zombie hashes.

Recently I am getting zombie hashes while I am allowed merged mining script coins + BTC on your pool with some of my old Gridseed sets.
Coincidentally, it gets automatically fixed as soon as I stop mining scripts.

Is it having any influence on dual mining?
Or does it need some tweaking?

At Bitminter only a new bitcoin block makes old work get rejected.

But yeah, have a look at the worker options and disable "Merged mining stale flush". That should reduce the frequency of those.

There are still some special cases where the server will ask the client to immediately switch to new work. For instance if the server gets a transaction with an extremely high fee.


And when accepted, all 64 are accepted. Higher diff just means higher variance, both for accepted and rejected work. Remember that you are equally likely to be lucky as you are to be unlucky. Meaning the extra variance could cause a higher accepted count than usual, and lower than usual rejected.

Over time both will even out though.


I don't understand what you mean. The pool started as proportional in late june 2011. After a couple months we switched to PPLNS with shifts.

Bitminter was the first pool to use PPLNS with shifts. A couple other pools had done PPLNS (without shifts) before that. I don't think any of them are still around now. That was in the early days when many different reward systems were being tried out.

Extra work restarts caused by alt-coin merged mining block changes invalidating valid BTC work.

Well one thing you forgot to mention is using a high(er) diff rate, means when you finally submit your work and the time it takes to get there, the data could be old and get rejected. Thing is with a higher diff rating all that work for all 64 shares will be rejected..

But does save on bandwidth..

Icon


PS

Did you change from Proportional Payment mining to full PPLNS? No more not getting paid for older shares?

Thanks you Dr. I'll change them over when I get the chance see what happens.

mint is currently an alias for us1. You can try us2 also, but I don't expect there will be a big difference in reject ratio.


Yep. Should help a little bit. Note that this is no big deal. But yeah, you'd probably earn about 0.05% more.

To illustrate what I am seeing I just ran a single gekko stick at kano and bitminter for the same amount of time (couple minutes), look at the hash rate difference (stick should and has average 12-14GH/s) and also the work restarts when pointed to bitminter.  Note this is not the miner receiving new work, this is something different that I have only experience since pointing the sticks here:
 

I will try the other servers and see if that changes the connection drops, but I've never had that happen at other pools.  I made no changes to my gear or setup (that have been running for months) other than to point them at bitminter.

Hash rate shown in the shift page appears to be more accurate as you stated.  For the first 2 full shifts my total hash was about expected, just a little lower than it has been historically, but the next two look at the loss of hash, this is what I'm trying to figure out.

oops   

Read a couple posts up... Doc stated both us1 and us2 servers are on the US east coast

Very Interesting.  Which one would work best?  Does anyone have any results/tests?

mint.bitminter.com:3333
us1.bitminter.com:3333 (United States) is this West Coast?
us2.bitminter.com:3333 (United States) where is this (East Coast)?
eu1.bitminter.com:3333 (Europe)

I personally have connected to min.bitminter.com and live on the East Coast.  Would us2.bitminter.com:3333 (United States) work better/more efficient for me?


EDIT - EDIT

SORRY DrHaribo, you answered my East Coast / West Coast question in the quote I quoted you.  Thanks for not being condescending!

I would still like to know:  I personally have connected to min.bitminter.com and live on the East Coast.  Would us1.bitminter.com:3333 or us2.bitminter.com:3333 (United States) work better/more efficient for me?

On the subject of servers I've got all my minera pointed at "mint.bitminter" they are registering and hashing but would there be any advantage if I pointed them to the eu server seeing as I'm in the UK?

Hence my caveat:

Connecting to the closest server will decrease your rejected (stale) work by a tiny bit. If it takes you from 0.11% to 0.06% rejected work then you will be earning 0.05% more bitcoins.

Currently both US servers are in the eastern US.

I'd be interested in hearing some stats from people who have tried the different servers for a day or two each and compared reject ratios.

Regarding mining with old USB sticks: the minimum difficulty is currently 64. You can't get below that. But mining will work fine. It will not make your USB sticks fail and need to reset. It will not cause lower actual hashrates. If those things happen then it's for other reasons. What it WILL do is make the website's estimated hashrates very inaccurate. The website will often show you at zero hashrate. Mining still works and your hashrate in the shifts should be closer to reality: https://bitminter.com/shifts (make sure you are logged in to be able to see your hashrate in shifts)


New work from the server is normal. But how often do you get disconnected? Did you try us2.bitminter.com:3333 and eu1.bitminter.com:3333 and do you get a more stable connection there?

Thanks, I'm on the west coast so I will keep using us1.  I am having a few other issues here, maybe you all can help.

Firstly, I am seeing fairly regular "Stratum connection to pool 0 interrupted" and "Stratum from pool 0 requested work restart".  Why all the work restarts all the time?

After about 24 hours on this pool I've noticed my usb sticks do not seem to be performing like the have previously.  One of my gekko compacs constantly gets "no valid hashes for over 10 secs, attempting to reset" and it only hashes at about 1/3 speed of what it should be.  4 of my 6 nanofury sticks are down about 20% in hash speed also.  The worker page on the website constantly shows my miners at 0 hash rate even though they are hashing away, often when I refresh some of the 0s will get replaced with a hash value, but then another miner might show 0.  I think this is all related to the min. difficulty of 64 on small miners that do 2GH-14GH each, but I'm not sure.

I added the easy mode perk for low difficulty and set appropriate difficulties under each worker in the field "minimum difficulty".  I waited for a while (website said it could take 20 mins) then restarted my miners but they do not seem to be mining at the reduced difficulty that I set, did I do something wrong?

I would like to give this pool a shot but if I can't get my miners to cooperate here I'm going to have to move them back to kano.is.  Thanks in advance.

Shake you're money maker!!! 

  haha -  I am trying to shake this bitcoin out of the tree! 

Good enough answer on the server for me.  Nice Aries.  Crush that block.  Diff is going down today too...

Aries, looks like you're determined to crush this block lol