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

Give it a go and see what happens. If the IP gets blocked on DDOS protection it should be able to be allowed through if you contact Dr H.

plural of vps - virtual private server. rented virtual server at some provider.

What is vpses ?

yup, odd. It always worked like a charm. I added a proxy on two VPS that I have and I'm balancing it via DNS.. I will keep it behind the proxy since I prefer to mine on bitminter.com

That's odd. If one can keep mining then the others should work too.


This works fine for me, with other connections already established.

Here the port number is wrong. getblocktemplate and getwork is on port 8332, not 9332. Alternatively Stratum is also on port 5050 and gbt/getwork on port 80.

The stratum proxy doesn't handle any error. Doesn't matter what you send, it forwards. As I told you another problem is, that you introduces a single point of failure. I don't want my whole cluster offline, because my pi proxy is down. From my network, just the first worker is able to connect to mint.bitminter.com. In all the others, the bfgminer switches to a backup pool (it says that mint.bitminter.com is dead) I have 3GB/H going to you and the others 12GB/H going somewhere else :-/ 

What happens when you try with 3 workers?

Did you report the bugs in the stratum proxy?

Currently there are DDoS attacks a couple times per day trying to break through. Normally Black Lotus is able to filter them quite effectively. Sometimes they slip through for a few minutes and lag down the server. The attackers seem to have given up pounding the server with large amounts of UDP packets and are now trying to impersonate normal miners instead. Black Lotus seems to be adapting well so far, but I'm working on my own filtering too, just in case.

If you get filtered you won't be able to make a connection to the mining server at all, you'll just see timeouts. But unless there is a big ongoing attack at the moment, you should be able to connect again in a minute or two. Timeouts have also happened for a short time when the attackers got through. In that case you would be able to connect but the request would not be serviced in time and you'd get a timeout. I'm not sure if you can see the difference in most mining clients. I have seen normal users being filtered after a service restart when everyone are reconnecting at the same time - Black Lotus has since improved their filtering heuristics to prevent this problem.

One problem is that most mining clients are badly programmed and very abusive. Retrying once per second is common, even when authentication fails. If you have 3 computers at your IP address reconnecting or retrying to same wrong name+password 3 times per second, you can imagine how that looks to a server.

I'm having problem to connect more than one client to bitminter. I have 3 workers, that I don't want to put behind the stratum proxy - cause its bugged and it introduces one more point of failure - but looks like now I'm just able to connect with one client. are you filtering the number of connections per ip to help you to fight against the DDoS?

The topic should read [21 TH/s]  

BFGminer should run the BFL single just fine. And you can use the stratum protocol with BFGminer. You could run it something like this:



When a block is found the payments are set up immediately. In the case that you use the prepay perk the payment takes place then. If you don't then the payment takes place if and when the block is confirmed. But the amount you get is always decided when the block is found, and depends on how much of the work in the last 10 shifts is yours (at the time the block is found).

In general it doesn't matter when you choose to do maintenance on your mining equipment. When you put in a proof of work the amount you will get paid for it is impossible to determine in advance. This is why BitMinter is safe from pool hopping. If things didn't work this way then you would see the hashrate going up when the pay is known to be high, or to be completely unknown, and you'd see the hashrate go back down when the pay is known to be low. Seeing the hashrate bounce up and down like this was very common in pools using the proportional reward system, because it was possible to tell in advance when the pay would be low, so "pool hoppers" would avoid the pool at those times. Luckily most pools have stopped using the proportional reward model, which resulted in 24/7 miners getting reduced pay. I think Deepbit is the only proportional pool left, although Slush's pool and BTCmine (score based reward system) can also be abused by pool hoppers.

Some additional info on BitMinter payouts was posted here: https://bitcointalksearch.org/topic/m.2818113

So what up with this week's CFG since the change in complexity!?!  It looked like we got about four good blocks in a row on Wednesday, and precious little else since.  

Every BTC, if we find any, is above 60%.

How long as a basic ETA does it take to solve any block once we see it?   I ask because if we wait for the last ten blocks to closebefore final payoffs, do we move our estimations of block payout out a day or 48 hours?

It would be good to know, because sometime you have to move a miner or do maintenance, and if there are crappy blocks all in a row, then how long should you allow after a good block is found till you know its been paid, in general?

Thanks

Expanding on this, should I bother with Stratum? Im currently using BFGminer, should I switch?

Congrats!!

Finally i have found one.

The usual bad luck. We actually got block 255245 in the middle of the attack, but it worked out fine.

8h 36m and it came out stale the block.
Was that from DDoS holding it up or luck or both?

The mining server is struggling as another DDoS attack is coming in. Working on it.

Situation normal again for the last 33 minutes.

Looks like the DDoS attackers have given up using brute force DDoS against Black Lotus. Now they are trying to look like miners, to slip under the radar, rather than just blindly spamming network data. Someone is quite desperate to take BitMinter down. It's nice to see them putting in some work hours though, instead of just pressing the "usual ddos attack" button.

Finally got my BFL 60Gh single up and running on BitMinter. Got home from college to pick it up.
I'm running it using BFGMiner. Should I use the native bitminter client instead or something else? Any recommendations? Hitting 60-70GH variably so it seems to be good so far.

But I am noticing what looks to be a somewhat terribly long block. Not a good start. Unless I'm reading the statistics on the site wrong.

Thanks.   I noticed that, and came here to check if anyone else did.  Glad to know you are on top of things.  I am new at this mining bit, have only 1 erupter on a macbook pro----guess i'm mining the hard way    I would like to take this opportunity to thank you for developing an easy to use miner for tech challenged folk like myself.