Pages:
Author

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

newbie
Activity: 28
Merit: 0
Yes very useful. Sadly a day earlier I named my newest machine without a number, thinking if have to clump all new ones on the same. So thank you Smiley
member
Activity: 104
Merit: 10
Thanks Doc!  That'll be super useful!
sr. member
Activity: 351
Merit: 250
Need more workers? You can now have 10 workers without the team effort perk.
Thank you!
donator
Activity: 1890
Merit: 1010
Parental Advisory Explicit Content
Need more workers? You can now have 10 workers without the team effort perk.

Great Smiley

Hopefully this will lead into a increase in pool hashrate a bit and removes the little barrier for some miners to add more workers.
legendary
Activity: 2730
Merit: 1034
Needs more jiggawatts
Need more workers? You can now have 10 workers without the team effort perk.
zvs
legendary
Activity: 1680
Merit: 1000
https://web.archive.org/web/*/nogleg.com
I don't understand how any block can be stale today. There have been periods of no blocks today from 20-30+ minutes, new to the blockchain. Something has to be wrong or the difficulty is too hard.

Well, here's a chart:

https://blockchain.info/charts/n-orphaned-blocks?timespan=1year&showDataPoints=false&daysAverageString=7&show_header=true&scale=0&address=

More stale blocks in the last month than any other month blockchain.info has stats for.

Check the 60 day:

https://blockchain.info/charts/n-orphaned-blocks?timespan=60days&showDataPoints=false&daysAverageString=7&show_header=true&scale=0&address=

........ some of these *pools based in China really need some work on their peering.
sr. member
Activity: 276
Merit: 250
Nice to get a string of blocks just before the difficulty increased!
legendary
Activity: 2730
Merit: 1034
Needs more jiggawatts
newbie
Activity: 5
Merit: 0
Wow... four blocks in 7 hours.  Big fan.
legendary
Activity: 2730
Merit: 1034
Needs more jiggawatts
+1 I had high hopes for an Asia server for a while

Do you get a high reject ratio with the american servers, or is there another reason for this?
legendary
Activity: 1358
Merit: 1001
https://gliph.me/hUF
I'm just checking out options if I add capacity in China
*troll mode*

+1 I had high hopes for an Asia server for a while, either HK, KR or SG. Don't matter now. There's plenty of pools in China now. Missed opportunity.
sr. member
Activity: 294
Merit: 250
I'm just checking out options if I add capacity in China
legendary
Activity: 2730
Merit: 1034
Needs more jiggawatts
Are there only the two US servers?

And is anyone mining in China on bitminters?

Yeah, currently 2 in the US and 1 in Europe.

Are you getting a high rate of rejected work? Reducing that a little is really the only difference between close and remote servers.
sr. member
Activity: 294
Merit: 250
Are there only the two US servers?

And is anyone mining in China on bitminters?
legendary
Activity: 2730
Merit: 1034
Needs more jiggawatts
The difficulty starts at 16 when you connect. But yeah, it goes up quickly, so setting a minimum difficulty isn't really necessary.

Setting a minimum diff is very useful for dragonminers since they violate the stratum specification and ignore the difficulty the server tells them to use. For those miners you should set the minimum diff at Bitminter to the same as the diff in the dragonminer configuration.
legendary
Activity: 1638
Merit: 1005
I've got a new Spondoolies SP20, I'm fairly new to mining, and I'm using bitminter. I noticed there are custom worker settings. Is this something I would need to set to get the best performance? My current hash rate is 1.45Th/s. I wasn't sure if I should set the minimum difficulty or not.

The pool will adjust the diff by himself but you can set one in the worker if you want. Doc could give you the exact behaviour but I think the pool start it at 256 (As Doc corrected me it's 16) and will increment it for your hashrate over time (it's quick).

Min diff. for my SP20 are not set. I'm just loosing a bit of speed when the worker stop and start. It's no big deal Tongue

I think there is somekind of magic number like 1450 GH / 1.x = min diff to set. I just don't remember what is it. But this only an approximate.

I guess 1000 should be fine.

Doc will tell you exactly what to use I guess ;-)
newbie
Activity: 4
Merit: 0
I've got a new Spondoolies SP20, I'm fairly new to mining, and I'm using bitminter. I noticed there are custom worker settings. Is this something I would need to set to get the best performance? My current hash rate is 1.45Th/s. I wasn't sure if I should set the minimum difficulty or not.
legendary
Activity: 2730
Merit: 1034
Needs more jiggawatts
Interesting, I didn't know that. Did it already happen here ?

Possibly, but it's a rare event.
legendary
Activity: 1638
Merit: 1005

Do stale blocks also skew CDF calculations? I.e. the full stats show the duration on mining since the stale block. However the stale block took 20 hours to find and we got nothing from it. So shouldn't the current CDF be calculated from: (time it took to find the stale block) + (time mining on the current block)?
We could have a block go orphan and then later be on the longest chain again (no longer orphan).

Interesting, I didn't know that. Did it already happen here ?
legendary
Activity: 2730
Merit: 1034
Needs more jiggawatts

Do stale blocks also skew CDF calculations? I.e. the full stats show the duration on mining since the stale block. However the stale block took 20 hours to find and we got nothing from it. So shouldn't the current CDF be calculated from: (time it took to find the stale block) + (time mining on the current block)?

Yes, the following block would have a higher CDF if you didn't count stale blocks. So the CDF tells you how much work it took to find a block solution, not how much work it took to find a block and get it accepted in the block chain.

We could change this so a new round is not started when finding a stale block. But CDF still wouldn't be the amount of work it took to get a paying block. That's because of orphans. We could even get two orphans in a row. We could have a block go orphan and then later be on the longest chain again (no longer orphan). To make CDF only count paying blocks the data would have to be changed when blockchain reorganizations happen. It's doable, but I don't know if it's worth the effort.
Pages:
Jump to: