Please read! Worker diff changing, getwork/gbt closing.
2015.07.11 at 10:00 UTC:
Your miners will get disconnected as this change goes live but will be able to reconnect immediately.
Default worker difficulty when miners connect: 512 (was 16)
Minimum worker difficulty: 64 (was 4)
This is to better support fast (1+ TH/s) hardware, some of which is very unhappy with low difficulty.
For old and very slow (40 GH/s and down) ASICs the new difficulty may be a bit high causing the live hashrate on the website to become very inaccurate. This may cause false alarms from the idle worker notifications if you use those. Mining will still work though.
2015.08.01:
Support for getwork and getblocktemplate (GBT) mining protocols will be turned off. Only Stratum will be supported. If you are already using Stratum you will not be disconnected or otherwise affected as this goes live.
What do you need to do if you use getwork/gbt today? Change the URL from http://mint.bitminter.com:8332 to stratum+tcp://mint.bitminter.com:3333
If you need help with this, use the contact form on the website to ask for help.
Topic: Bitminter bitcoin mining pool - shutdown mining 2020-07-01 website 2021-06-01 - page 60. (Read 324945 times)
July 06, 2015, 05:07:06 PM
July 05, 2015, 09:26:05 AM
I can't believe I forgot Slush... especially after I mentioned his pool being basically the first mining pool in another recent post. Thanks for the reminder eleuthria... and thanks for the stats organofcorti.
July 04, 2015, 08:55:34 PM
Well done, Doc. Oh, and congrats on your 4 year anniversary, as well! Does this make you and Eligius the two oldest remaining pools now that eleuthria has shuttered the guild?
Slush, Eligius, then BitMinter, in that order, at least counting the "active" pools. There may be some between Eligius and BitMinter that are still running, but are basically abandoned and simply continue to run the owner and maybe their friends' equipment. There was a big explosion of new pools between May and July 2011 because of the introduction of the pushpool software and the first major Bitcoin bubble.
For shits and giggles, here's the dates I have for when a pool found their first block (not when they opened):
Code:
Pool First block date Status
1: puddinpop 14 September 2010 Closed
2: Slush 16 December 2010 Operating
3: bitcoinPool 24 February 2011 Closed
4: DeepBit 25 February 2011 Closed
5: BTC Guild 26 April 2011 Closed
6: Eligius 28 April 2011 Operating
7: MTRed 10 May 2011 Closed
8: EclipseMC 08 June 2011 Operating
9: Polmine 16 June 2011 Operating
10: Triplemining 02 July 2011 Closed
11: BitMinter 03 July 2011 Operating
July 04, 2015, 02:48:13 PM
Well done, Doc. Oh, and congrats on your 4 year anniversary, as well! Does this make you and Eligius the two oldest remaining pools now that eleuthria has shuttered the guild?
Slush, Eligius, then BitMinter, in that order, at least counting the "active" pools. There may be some between Eligius and BitMinter that are still running, but are basically abandoned and simply continue to run the owner and maybe their friends' equipment. There was a big explosion of new pools between May and July 2011 because of the introduction of the pushpool software and the first major Bitcoin bubble.
July 04, 2015, 09:28:51 AM
Well done, Doc. Oh, and congrats on your 4 year anniversary, as well! Does this make you and Eligius the two oldest remaining pools now that eleuthria has shuttered the guild?
July 04, 2015, 09:15:53 AM
Some of you may have heard about a blockchain fork today, with F2Pool and Antpool mining on the wrong side of the fork.
In case anyone is worried:
Bitminter has been mining version 3 bitcoin blocks for a while now, our bitcoin nodes are the latest version, and we only mine on top of blocks we have validated locally - we do not trust others to validate blocks for us.
So you can safely continue to mine at Bitminter.
In case anyone is worried:
Bitminter has been mining version 3 bitcoin blocks for a while now, our bitcoin nodes are the latest version, and we only mine on top of blocks we have validated locally - we do not trust others to validate blocks for us.
So you can safely continue to mine at Bitminter.
June 30, 2015, 03:53:54 PM
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.
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.
Happy 4 years !
Happy belated birthday and congratulations!
June 29, 2015, 12:48:13 AM
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.
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.
Happy 4 years !
June 28, 2015, 03:16:08 AM
I wish you "bugless" future Doc 
For another 4x10 years at least....
Best
For another 4x10 years at least....
Best
June 27, 2015, 07:35:42 PM
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.
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.
June 27, 2015, 04:42:04 PM
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.
June 25, 2015, 05:58:54 PM
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.
June 25, 2015, 05:30:15 PM
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.
June 21, 2015, 08:49:56 AM
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?
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
June 21, 2015, 06:02:54 AM
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?
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?
June 18, 2015, 02:11:51 PM
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
June 17, 2015, 02:44:22 PM
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?
June 16, 2015, 10:05:52 PM
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
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
June 15, 2015, 07:19:31 PM
June 15, 2015, 07:01:20 PM
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.
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.
Jump to: