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

[HerbPean]

Let's all thanks lady Luck !

[1714506885]

1714506885

[1714506885]

1714506885

[1714506885]

1714506885

[not.you]

Glad I resisted the urge to bail over the weekend.  I strongly suspected that bad luck streak had to end soon but that was a loooooooooooooong block.  

[Darthswan]

Glad I resisted the urge to bail over the weekend.  I strongly suspected that bad luck streak had to end soon but that was a loooooooooooooong block.  

Same here.

[lim_1]

My worker difficulty seems to be stuck at around 200, even though I set the minimum difficulty much higher on the worker settings page.

[DrHaribo]

My worker difficulty seems to be stuck at around 200, even though I set the minimum difficulty much higher on the worker settings page.

Do you mean it is stuck at exactly 256 all the time?

Bitminter worker difficulties are powers of 2, with a current minimum of 64. So 64, 128, 256, 512, 1024, and so on. If you don't set a minimum then you will be started on 512 currently.

The mining server will adjust up your difficulty if it makes sense for your hashrate. The aim is to see roughly 20 work results per minute from your worker. You can change this number in the worker settings. You can also set a difficulty minimum which is mostly useful to make the initial difficulty ramp-up faster when you connect to the mining server to start mining.

Note that from you change difficulty settings on the website until you see it active on your workers can take up to 20 minutes (worst case).

Mostly you shouldn't need to set minimum difficulty or the work results per minute target. The mining server will start you at 512 and adjust your difficulty as necessary when it sees how fast you are mining.

[lim_1]

Basically i use the counter on the website to measure how often i am submitting work. I just watch the counter as it updates every half second or so. So to submit around 10000 units. the counter updates about fifty times. So that means on average each work submitted is worth 200. Correct?

Well why dont i just look at what difficulty shares cgminer is submitting? I plan to but i dont have direct control to the miner at the moment.

quote author=DrHaribo link=topic=788753.msg13484430#msg13484430 date=1452254062]

My worker difficulty seems to be stuck at around 200, even though I set the minimum difficulty much higher on the worker settings page.

Do you mean it is stuck at exactly 256 all the time?

Bitminter worker difficulties are powers of 2, with a current minimum of 64. So 64, 128, 256, 512, 1024, and so on. If you don't set a minimum then you will be started on 512 currently.

The mining server will adjust up your difficulty if it makes sense for your hashrate. The aim is to see roughly 20 work results per minute from your worker. You can change this number in the worker settings. You can also set a difficulty minimum which is mostly useful to make the initial difficulty ramp-up faster when you connect to the mining server to start mining.

Note that from you change difficulty settings on the website until you see it active on your workers can take up to 20 minutes (worst case).

Mostly you shouldn't need to set minimum difficulty or the work results per minute target. The mining server will start you at 512 and adjust your difficulty as necessary when it sees how fast you are mining.

[/quote]

[DrHaribo]

Basically i use the counter on the website to measure how often i am submitting work. I just watch the counter as it updates every half second or so. So to submit around 10000 units. the counter updates about fifty times. So that means on average each work submitted is worth 200. Correct?

Well why dont i just look at what difficulty shares cgminer is submitting? I plan to but i dont have direct control to the miner at the moment.

The quick updates on the livestats are extrapolations based on your hashrate. There is an adjustment from the server once per minute.

If you send in one proof of work at difficulty 256 then your proof of work counter on the server will go up by 256. And that happened in a single work submit.

Since the server updates your data approx. once per minute you could look at the workers page where there is no extrapolation, wait one minute, click the little refresh button there, and see how much the accepted count goes up. It will be some multiple of the worker difficulty you are on currently. But you wouldn't be able to tell two work submits at diff 256 apart from a single one at diff 512.

Try having a look at cgminer when you are able - much easier.

[lim_1]

I see, that makes sense then. Thanks!

Basically i use the counter on the website to measure how often i am submitting work. I just watch the counter as it updates every half second or so. So to submit around 10000 units. the counter updates about fifty times. So that means on average each work submitted is worth 200. Correct?

Well why dont i just look at what difficulty shares cgminer is submitting? I plan to but i dont have direct control to the miner at the moment.

The quick updates on the livestats are extrapolations based on your hashrate. There is an adjustment from the server once per minute.

If you send in one proof of work at difficulty 256 then your proof of work counter on the server will go up by 256. And that happened in a single work submit.

Since the server updates your data approx. once per minute you could look at the workers page where there is no extrapolation, wait one minute, click the little refresh button there, and see how much the accepted count goes up. It will be some multiple of the worker difficulty you are on currently. But you wouldn't be able to tell two work submits at diff 256 apart from a single one at diff 512.

Try having a look at cgminer when you are able - much easier.

[DrHaribo]

Website issues right now. Working on it. Mining functioning as normal.

[DrHaribo]

Website operational. Live hashrates are coming back now.

[not.you]

AOL liveID login is failing.  Just FYI.  I'm sure you'll get it sorted.

Also Doc you may want to clean up the list of exchanges on the website.  Camp BX is incompetent if they even exist any more, vicurex was hacked and lost a bunch of user funds and do they even exist anymore, and cryptsy is now claiming to have been hacked and lost everything too and how long are they going to exist?

[DrHaribo]

AOL liveID login is failing.  Just FYI.  I'm sure you'll get it sorted.

Also Doc you may want to clean up the list of exchanges on the website.  Camp BX is incompetent if they even exist any more, vicurex was hacked and lost a bunch of user funds and do they even exist anymore, and cryptsy is now claiming to have been hacked and lost everything too and how long are they going to exist?

AOL login appears to be working. If you are experiencing problems try running your browser without plugins or using a different browser. Sometimes browser plugins can break the login.

Thanks, I will have a look at the exchange links. Indeed it looks like some changes are needed.

What is the problem with Camp BX? Except for low activity?

[not.you]

AOL login worked the second time.

Camp BX held my bitcoin hostage for months like a year ago.  I had transferred one over to sell back when BTC had hit $1000 and it never hit my account on their exchange.  Months of ignored support tickets and lots of complaining on their facebook later and I got it back but the value had dropped to something like $600 by then.  That was the last time I ever dealt with them but I have since seen plenty of other complaints in the service discussion section describing the same kind of thing.

[DrHaribo]

Vircurex isn't on the list. Did you mean a different one?

[RobertoDaChef]

Hey Doc! What's your opinion of the fork issue? are you planning on keeping the pool on bitcoin core or do support the Classic proposal (or something else). I'm very happy with this pool BTW (and I'm for remaining on Core).

[not.you]

Vircurex isn't on the list. Did you mean a different one?

You know I think my brain must have created it from virwox and bitcurex.  Now that I look more closely I see that it isn't there.

[HerbPean]

I Really hate Stale block 

[Fatman3001]

Hey Doc! What's your opinion of the fork issue? are you planning on keeping the pool on bitcoin core or do support the Classic proposal (or something else). I'm very happy with this pool BTW (and I'm for remaining on Core).

Third option: Side with the winner after the results are in.

This is a suggestion, not an attempt at hijack.

[DrHaribo]

I think 2 MB blocks are needed. I think Gavin Andresen and Jeff Garzik sounds like a dream team. I think Bitcoin Core has problems making decisions about anything.

We could get banned from Bitcointalk for even talking about this. There could be some serious DDoS attacks if we support Bitcoin Classic. Some people think that if it isn't Core then it isn't Bitcoin. They will call you an altcoin supporter and enemy of bitcoin, and they will do what they can to stop you.

On the other hand.. Bitcoin Classic appears to have support from over 50% of the hashrate and plenty of bitcoin services. Maybe it can succeed?

[organofcorti]

I think 2 MB blocks are needed. I think Gavin Andresen and Jeff Garzik sounds like a dream team. I think Bitcoin Core has problems making decisions about anything.

We could get banned from Bitcointalk for even talking about this. There could be some serious DDoS attacks if we support Bitcoin Classic. Some people think that if it isn't Core then it isn't Bitcoin. They will call you an altcoin supporter and enemy of bitcoin, and they will do what they can to stop you.

On the other hand.. Bitcoin Classic appears to have support from over 50% of the hashrate and plenty of bitcoin services. Maybe it can succeed?

XT also appeared to have a lot of support, but not many of those who supported it actually created XT compatible blocks (eg KNC Miner). I'm not sure public support is a good a measure as eg making a coinbase statement to that effect.

It would be good way to get some feed-back from block makers about what they support, and I like this proposal regarding codifying coinbase voting: https://bitcointalk.org/index.php?topic=1335691.0