Bitminter bitcoin mining pool - shutdown mining 2020-07-01 website 2021-06-01

[HerbPean]

We are back on the usual server again. If you are mining at mint.bitminter.com you will get back on it again the next time your miners reconnect to the server. Until then your miners will be just fine on the other server.

Apologies for the problems this morning. Your miners probably experienced a few minutes of being disconnected until the switchover took effect.

thanks Doc !

[HerbPean]

235 Billions shares without a block should be a new records for us ?

Might be finally my turn to get one for us !

[DrHaribo]

235 Billions shares without a block should be a new records for us ?

Might be finally my turn to get one for us !

Dude, stop messing around and get the block

[ichtus27]

Bloody @$##,

I took me weeks to build up what i earn and steady add more speed and in about 4 days of no speed(lost more than came in so not able to rent) not getting anything.

Every few days that i rented more and the payout catched up i rented little higher speed, i thought it still counted for if the speed went down that it as slowly went down. Just proven wrong i find out with this last block. Why did you do that doc??

Well, one last time till the little bitcoin cents are gone and than because of this need to stop. Just a little one for a why not..

[HerbPean]

235 Billions shares without a block should be a new records for us ?

Might be finally my turn to get one for us !

Dude, stop messing around and get the block

I tried !! and failed again

[DrHaribo]

Every few days that i rented more and the payout catched up i rented little higher speed, i thought it still counted for if the speed went down that it as slowly went down. Just proven wrong i find out with this last block. Why did you do that doc??

The work you did in the last 10 shifts at the time the block is found is what will get paid. You can see your stats in the shifts here: https://bitminter.com/shifts (to see your own numbers you need to be logged in)

It is rare that we go this long between blocks though. 99.6% CDF on that round. So this is something that happens with 0.4% of the rounds. So one in 250 blocks will be this bad or worse.

This evens out pretty good for constant miners. For part time miners it can be harsh though, when we hit a dry spell.

[ichtus27]

So because i build up the speed so i do not pay to much at miners i am a part time miner.... oke..

Than i am a part time miner for the last .. months or so i think... hmm.

Never mind, i learned my lesson by suprise.. not building up and not putting in much because i lose it en therefor really must stop now.

I am not talking about long blocks or sommething and so i think you do not get what i mean.. again.. never mind..

greetings.

[DrHaribo]

If you need the payout from one day to keep renting your miners the next day, then you will be out of coins the first time the pool hits bad luck. You run out of coins before we get some good luck again, like today with 3 blocks. That's not something I would recommend.

It could perhaps almost work if you kept the coins you earned when we had good luck as a buffer to cover bad luck later. But it will not work if you use the extra coins to rent more and more hashpower so that there is no buffer for bad luck.

The reason I say "almost" is that hashpower is always rented out at a higher price than the average you can earn with it. So the only way to profit is if you have good luck. Over the long term your luck goes towards average though, which means earning less than you pay to rent miners. We did have a lot of good luck. But sooner or later bad luck will strike.

[ichtus27]

aha.... that is sommething i can work with.

Thanx for that answer 

[MoreBloodWine]

HTTP ERROR 404

Problem accessing /500. Reason:

    Not Found
Caused by:

java.sql.SQLException: Connections could not be acquired from the underlying database!
   at com.mchange.v2.sql.SqlUtils.toSQLException(SqlUtils.java:118)
   at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConnection(C3P0PooledConnectionPool.java:690)
   at com.mchange.v2.c3p0.impl.AbstractPoolBackedDataSource.getConnection(AbstractPoolBackedDataSource.java:140)
   at bootstrap.lift

Getting a bunch of this trying to load the site in my browser.

[DrHaribo]

HTTP ERROR 404

Sorry, should work again now.

[AaronS]

What happened during the shift ending 2015-06-16 00:56  (Duration 3h 05m)?

It seems unlikely the pool dropped 20% for that one shift, not to mention my Ghps dropped similarly.  Was there a DDOS or something?

On a related note, it would be nice if the shifts page would show my % of the pool for that shift (like on the live stats page) so I could easily confirm that my decrease in Ghps followed the pool's decrease and my % remained relatively constant.  Also, although I am aware this was discussed at length previously, I find the "Pay/Hour at 1 TH/s" a useless value.  I would be much happier with "Blocks found for which this shift was active" along with my % of the pool.  The zeros listed here would be no worse than the zeros listed in the "Pay/Hour" column.  The "still eligible for pay" could then be changed to "#[of blocks already found] + still eligible for blocks in the next x shifts".

Aaron

[DrHaribo]

What happened during the shift ending 2015-06-16 00:56  (Duration 3h 05m)?

That night one of the central servers went down for about 15-20 minutes. Normally this would only affect the website, while mining servers would be fine. But it looks like we were hashing at a very low hashrate (about 10% of normal) for 10-15 minutes, and after that it took some time for the hashrate to go back up, probably due to miners taking some time to move back from their backup pools. I'm still looking into what the issue was with the main mining server. The website didn't recover right away and was down 30-40 minutes in total. I'm also looking into that.

My apologies for this downtime. A small amount of downtime on the website can happen, but mining should always be available.

On a related note, it would be nice if the shifts page would show my % of the pool for that shift (like on the live stats page) so I could easily confirm that my decrease in Ghps followed the pool's decrease and my % remained relatively constant.  Also, although I am aware this was discussed at length previously, I find the "Pay/Hour at 1 TH/s" a useless value.  I would be much happier with "Blocks found for which this shift was active" along with my % of the pool.  The zeros listed here would be no worse than the zeros listed in the "Pay/Hour" column.  The "still eligible for pay" could then be changed to "#[of blocks already found] + still eligible for blocks in the next x shifts".

Maybe I can squeeze in a "your % of the total work" thing just after the number showing your work (rightmost column today).

If space gets tight I could probably show the difficulty in billions instead of the exact number. So "49.7" instead of "49,692,386,354". Or perhaps the difficulty isn't even that interesting in the shifts list?

Yes, a column showing the number of blocks found would be useful. Perhaps showing "0 (still searching)" or "1 (still searching)" etc, for the 10 latest shifts?

[AaronS]

Maybe I can squeeze in a "your % of the total work" thing just after the number showing your work (rightmost column today).

If space gets tight I could probably show the difficulty in billions instead of the exact number. So "49.7" instead of "49,692,386,354". Or perhaps the difficulty isn't even that interesting in the shifts list?

I would definitely like my % of total work.

I personally don't need the difficulty in the shifts list at all, but rounding it to billions (with a mouse-over of the full value, or a link to somewhere with a list of difficulty over time perhaps) would be fine if others like it.

I definitely like the

... column showing the number of blocks found would be useful. Perhaps showing "0 (still searching)" or "1 (still searching)" etc, for the 10 latest shifts?

I really dislike the current "still eligible for pay" since it should really have the "[amount so far] + still eligible for more" but as stated earlier, the number of blocks found is much better than the "Pay/Hour at 1 TH/s".

Thanks,
Aaron

[PatronDragon]

Help with settings for an asic of CP2102 USB to UART Bridge Controller with this program Gives out 2 mistakes:
1) Antminer (COM7) ERROR: Selftest error. Expected nonce 0xFFFFFE0A but got 0x857A41D4.
2) Antminer (COM7) ERROR: Selftest error. Expected nonce 0xFFFFFE0E but got 0x857A41D4.
What to do?

[DrHaribo]

Help with settings for an asic of CP2102 USB to UART Bridge Controller with this program Gives out 2 mistakes:
1) Antminer (COM7) ERROR: Selftest error. Expected nonce 0xFFFFFE0A but got 0x857A41D4.
2) Antminer (COM7) ERROR: Selftest error. Expected nonce 0xFFFFFE0E but got 0x857A41D4.
What to do?

Bitminter client only supports Antminer U1 and U2, not U3. For U3 try bfgminer or cgminer, see links on frontpage of bitminter.com

[AaronS]

Did we have another glitch with the shift ending 2015-06-25 21:33 (duration 2h 14m)?  I noticed the web server was also having issues.

[DrHaribo]

Did we have another glitch with the shift ending 2015-06-25 21:33 (duration 2h 14m)?  I noticed the web server was also having issues.

The website was unstable for 7 minutes today. I didn't see any problem with the mining servers. But we have a couple big miners who keep coming and going, so the pool hashrate goes up and down a bit.

[DevonMiner]

The website was unstable for 7 minutes today.

Now that's what I call exact details ... nice one Doc.

On other news ... looks like we're paying for a run of good luck, all will come good over time as usual.

[DrHaribo]

Another milestone: On 2015.06.26 Bitminter had been around for 4 years.

In the Bitcoin world this is a long time!

A big thanks to everyone who support Bitminter and all who did in the past. I hope to see you around in the future as well. The Bitcoin adventure is only getting started.