Please add stratum to the main port. I miss the statistics. 
Coming right up.Woohoo! Stats again!
M
Topic: [1050 TH] BitMinter.com [1% PPLNS,Pays TxFees +MergedMining,Stratum,GBT,vardiff] - page 264. (Read 837122 times)
December 03, 2012, 03:50:49 PM
Woohoo! Stats again!
M
December 03, 2012, 03:48:42 PM
All the new changes are now live on the regular ports. Testport has shut down for now.
Variable difficulty ("var diff") settings: minimum 1, maximum 16, and default at 2 when your hashrate is unknown. The maximum will be increased when ASICs come out. The server will adjust your difficulty aiming for 20 submitted proofs of work per minute.
Port 8332 has getwork with difficulty 1 for now. This means you can still use leases from hashpower.com - var diff will be activated for getwork once hashpower supports var diff.
Port 8332 also has GBT with var diff.
Port 3333 and 5050 has Stratum with var diff. New work pushed at 30 second intervals.
If you want to use GBT or Stratum you may want to update your miner config and/or restart bfgminer/cgminer/poclbm to get it running with a new protocol.
BitMinter client will get support for other protocols later. It runs getwork with rollntime now and will use var diff once activated on the server.
Let me know if you have any questions or experience any problems.
Thanks! That was a lot of work and many changes that just went live. Good to finally finish all that and see it running smoothly (knock on wood).
Variable difficulty ("var diff") settings: minimum 1, maximum 16, and default at 2 when your hashrate is unknown. The maximum will be increased when ASICs come out. The server will adjust your difficulty aiming for 20 submitted proofs of work per minute.
Port 8332 has getwork with difficulty 1 for now. This means you can still use leases from hashpower.com - var diff will be activated for getwork once hashpower supports var diff.
Port 8332 also has GBT with var diff.
Port 3333 and 5050 has Stratum with var diff. New work pushed at 30 second intervals.
If you want to use GBT or Stratum you may want to update your miner config and/or restart bfgminer/cgminer/poclbm to get it running with a new protocol.
BitMinter client will get support for other protocols later. It runs getwork with rollntime now and will use var diff once activated on the server.
Let me know if you have any questions or experience any problems.
Congrats on the upgrade Doc!
Thanks! That was a lot of work and many changes that just went live. Good to finally finish all that and see it running smoothly (knock on wood).
December 03, 2012, 03:36:41 PM
Stratum on the main port looks good so far with cgminer 2.9.5,
In case anyone is wondering why cgminer is still showing LP you have to restart it before it detects the stratum
Congrats on the upgrade Doc!
December 03, 2012, 02:31:14 PM
Running good here. One thing I'm seeing is the server can't seem to decide what difficulty to give. Largest miner is ~2.6GH/s. At startup, it's on difficulty 2. Then it switches to 1. Then it switches back to 2. Right now it's on one.
It's changing between 2 and 4 for me. Reject rate is Yes, some users will be on the boundary between two difficulties. This currently gives a lot of rejects in cgminer. But they do no harm and they will disappear in a later cgminer version when it starts using the new stratum way of handling difficulty.
Stratum was recently changed to better handle changing difficulty. We'll have to expect it can take some time before everyone have changed their implementations.
Rewards page isn't working correctly anymore, it seems to assume a 50 BTC block reward for the expected average.
Oops, will look into this.
Please add stratum to the main port. I miss the statistics.
Coming right up.
December 03, 2012, 05:00:32 AM
Thanks for testing, guys! Just restarted with some tweaks to var diff and logging, and fixed the stats issue.
Testing continues. Let me know if you have any issues at all on the test port. So far things are running very well and I'm considering setting this up on the main port very soon.
I forgot to mention the new version also has some decent reduction in CPU usage. It will be interesting to see the effect all these changes will have on CPU usage and reject rates.
Testing continues. Let me know if you have any issues at all on the test port. So far things are running very well and I'm considering setting this up on the main port very soon.
I forgot to mention the new version also has some decent reduction in CPU usage. It will be interesting to see the effect all these changes will have on CPU usage and reject rates.
Please add stratum to the main port. I miss the statistics.
M
December 02, 2012, 08:43:14 PM
Rewards page isn't working correctly anymore, it seems to assume a 50 BTC block reward for the expected average.
December 02, 2012, 06:33:53 PM
Worth revisiting the stratum vardiff discussion and conclusions over the next 4 pages of forum starting here:
https://bitcointalksearch.org/topic/m.1357099
https://bitcointalksearch.org/topic/m.1357099
December 02, 2012, 06:08:00 PM
Thanks for testing, guys! Just restarted with some tweaks to var diff and logging, and fixed the stats issue.
Testing continues. Let me know if you have any issues at all on the test port. So far things are running very well and I'm considering setting this up on the main port very soon.
I forgot to mention the new version also has some decent reduction in CPU usage. It will be interesting to see the effect all these changes will have on CPU usage and reject rates.
Testing continues. Let me know if you have any issues at all on the test port. So far things are running very well and I'm considering setting this up on the main port very soon.
I forgot to mention the new version also has some decent reduction in CPU usage. It will be interesting to see the effect all these changes will have on CPU usage and reject rates.
Running good here. One thing I'm seeing is the server can't seem to decide what difficulty to give. Largest miner is ~2.6GH/s. At startup, it's on difficulty 2. Then it switches to 1. Then it switches back to 2. Right now it's on one.
I'm also confused why cgminer is submitting shares that are under difficulty.
M
It's changing between 2 and 4 for me. Reject rate is
December 02, 2012, 06:04:07 PM
Thanks for testing, guys! Just restarted with some tweaks to var diff and logging, and fixed the stats issue.
Testing continues. Let me know if you have any issues at all on the test port. So far things are running very well and I'm considering setting this up on the main port very soon.
I forgot to mention the new version also has some decent reduction in CPU usage. It will be interesting to see the effect all these changes will have on CPU usage and reject rates.
Testing continues. Let me know if you have any issues at all on the test port. So far things are running very well and I'm considering setting this up on the main port very soon.
I forgot to mention the new version also has some decent reduction in CPU usage. It will be interesting to see the effect all these changes will have on CPU usage and reject rates.
Running good here. One thing I'm seeing is the server can't seem to decide what difficulty to give. Largest miner is ~2.6GH/s. At startup, it's on difficulty 2. Then it switches to 1. Then it switches back to 2. Right now it's on one.
I'm also confused why cgminer is submitting shares that are under difficulty.
M
December 02, 2012, 05:44:02 PM
Thanks for testing, guys! Just restarted with some tweaks to var diff and logging, and fixed the stats issue.
Testing continues. Let me know if you have any issues at all on the test port. So far things are running very well and I'm considering setting this up on the main port very soon.
I forgot to mention the new version also has some decent reduction in CPU usage. It will be interesting to see the effect all these changes will have on CPU usage and reject rates.
Testing continues. Let me know if you have any issues at all on the test port. So far things are running very well and I'm considering setting this up on the main port very soon.
I forgot to mention the new version also has some decent reduction in CPU usage. It will be interesting to see the effect all these changes will have on CPU usage and reject rates.
December 02, 2012, 10:43:56 AM
I have my miners pointing at stratum now. I miss the stats. I assume this is production testing, so I still get paid for my work? 
Yeah, this is a case of that ugly thing called "testing in production".
So yes, you get paid, and work done on the test port shows in most statistics but not current hashrate (worker page, top50 list, etc). But if you refresh the workers page after 10-15 seconds you can see the number of accepted proofs of work go up.
36 Stratum connections at the moment. Everything running smoothly.
I do see the test port reporting statistics wrong, not always counting Stratum users for the current number of users and workers in the pool. I'm working on fixing that. You can't see the wrong numbers now, but I need to fix it before this goes live on the regular port.
December 02, 2012, 10:34:57 AM
I have my miners pointing at stratum now. I miss the stats. I assume this is production testing, so I still get paid for my work?
M
M
It's testing time again!
GBT and getwork testing on port 9000. Stratum testing on port 3334.
Stratum in production will go on port 3333 with 5050 as an option if 3333 is a problem for you.
There's an X-Stratum HTTP header in all responses on port 9000. Looks like cgminer has a --fix-protocol option that makes it not switch to Stratum. But it seems to use getwork in that case. Any way to force GBT? Until the pool supports the more advanced GBT features, I think it makes sense to tell the miner where the Stratum port is.
What's new on testports:
Already 5 Stratum connections active. If you are mining with a Stratum or GBT capable bfgminer/cgminer/poclbm then please join in and help test this.
For Stratum connect to: stratum+tcp://mint.bitminter.com:3334
For GBT or getwork: http://mint.bitminter.com:9000
(you may need to force your miner to use GBT or getwork, whichever you want to try)
GBT and getwork testing on port 9000. Stratum testing on port 3334.
Stratum in production will go on port 3333 with 5050 as an option if 3333 is a problem for you.
There's an X-Stratum HTTP header in all responses on port 9000. Looks like cgminer has a --fix-protocol option that makes it not switch to Stratum. But it seems to use getwork in that case. Any way to force GBT? Until the pool supports the more advanced GBT features, I think it makes sense to tell the miner where the Stratum port is.
What's new on testports:
- Stratum: brand new
- GBT: add workaround for bug in cgminer prior to 2.9.4
- var diff: max diff 16
Already 5 Stratum connections active. If you are mining with a Stratum or GBT capable bfgminer/cgminer/poclbm then please join in and help test this.
For Stratum connect to: stratum+tcp://mint.bitminter.com:3334
For GBT or getwork: http://mint.bitminter.com:9000
(you may need to force your miner to use GBT or getwork, whichever you want to try)
December 02, 2012, 10:11:49 AM
It's testing time again!
GBT and getwork testing on port 9000. Stratum testing on port 3334.
Stratum in production will go on port 3333 with 5050 as an option if 3333 is a problem for you.
There's an X-Stratum HTTP header in all responses on port 9000. Looks like cgminer has a --fix-protocol option that makes it not switch to Stratum. But it seems to use getwork in that case. Any way to force GBT? Until the pool supports the more advanced GBT features, I think it makes sense to tell the miner where the Stratum port is.
What's new on testports:
Already 5 Stratum connections active. If you are mining with a Stratum or GBT capable bfgminer/cgminer/poclbm then please join in and help test this.
For Stratum connect to: stratum+tcp://mint.bitminter.com:3334
For GBT or getwork: http://mint.bitminter.com:9000
(you may need to force your miner to use GBT or getwork, whichever you want to try)
GBT and getwork testing on port 9000. Stratum testing on port 3334.
Stratum in production will go on port 3333 with 5050 as an option if 3333 is a problem for you.
There's an X-Stratum HTTP header in all responses on port 9000. Looks like cgminer has a --fix-protocol option that makes it not switch to Stratum. But it seems to use getwork in that case. Any way to force GBT? Until the pool supports the more advanced GBT features, I think it makes sense to tell the miner where the Stratum port is.
What's new on testports:
- Stratum: brand new
- GBT: add workaround for bug in cgminer prior to 2.9.4
- var diff: max diff 16
Already 5 Stratum connections active. If you are mining with a Stratum or GBT capable bfgminer/cgminer/poclbm then please join in and help test this.
For Stratum connect to: stratum+tcp://mint.bitminter.com:3334
For GBT or getwork: http://mint.bitminter.com:9000
(you may need to force your miner to use GBT or getwork, whichever you want to try)
so far cgminer 2.9.5 is running fine on 3334 with stratum
December 02, 2012, 07:57:16 AM
Stratum in production will go on port 3333 with 5050 as an option if 3333 is a problem for you.
I donated 1 BTC to 15SSRJdHfhjcRU7woXR9sYKPUXNS4ScaaB. Thank you Doc!
December 02, 2012, 07:13:20 AM
It's testing time again!
GBT and getwork testing on port 9000. Stratum testing on port 3334.
Stratum in production will go on port 3333 with 5050 as an option if 3333 is a problem for you.
There's an X-Stratum HTTP header in all responses on port 9000. Looks like cgminer has a --fix-protocol option that makes it not switch to Stratum. But it seems to use getwork in that case. Any way to force GBT? Until the pool supports the more advanced GBT features, I think it makes sense to tell the miner where the Stratum port is.
What's new on testports:
Already 5 Stratum connections active. If you are mining with a Stratum or GBT capable bfgminer/cgminer/poclbm then please join in and help test this.
For Stratum connect to: stratum+tcp://mint.bitminter.com:3334
For GBT or getwork: http://mint.bitminter.com:9000
(you may need to force your miner to use GBT or getwork, whichever you want to try)
GBT and getwork testing on port 9000. Stratum testing on port 3334.
Stratum in production will go on port 3333 with 5050 as an option if 3333 is a problem for you.
There's an X-Stratum HTTP header in all responses on port 9000. Looks like cgminer has a --fix-protocol option that makes it not switch to Stratum. But it seems to use getwork in that case. Any way to force GBT? Until the pool supports the more advanced GBT features, I think it makes sense to tell the miner where the Stratum port is.
What's new on testports:
- Stratum: brand new
- GBT: add workaround for bug in cgminer prior to 2.9.4
- var diff: max diff 16
Already 5 Stratum connections active. If you are mining with a Stratum or GBT capable bfgminer/cgminer/poclbm then please join in and help test this.
For Stratum connect to: stratum+tcp://mint.bitminter.com:3334
For GBT or getwork: http://mint.bitminter.com:9000
(you may need to force your miner to use GBT or getwork, whichever you want to try)
November 30, 2012, 08:32:07 AM
I just mined a block #210275
Total income (minting + fees): 25.52300001 BTC
CDF: 34.7%
https://bitminter.com/block/btc/00000000000000351a6ff160ad066d99eeaf812f936c776c9fd0055120adb39d
Total income (minting + fees): 25.52300001 BTC
CDF: 34.7%
https://bitminter.com/block/btc/00000000000000351a6ff160ad066d99eeaf812f936c776c9fd0055120adb39d
November 30, 2012, 08:17:47 AM
Hmm. So cgminer tries GBT first, and if it sees no Stratum header it stays on GBT?
In order of priority, cgminer will try to mine on stratum first, gbt second and getwork if all else fails, based on what order I think mining should occur. As far as I'm concerned, it's up to the pool operator to decide what they think is most important to prioritise. If you want to put a stratum redirect header in your GBT based pool, that's entirely your choice, knowing that cgminer will then use stratum preferentially. You can see the way cgminer prioritises the different protocols based on what I think is best for miners and pools, and the rest is up to you.Generally I would like to support all 3 options and let the user choose.
I was wondering if by putting a Stratum header on getwork responses but not on GBT responses I have made a choice for the user.
November 30, 2012, 05:07:08 AM
Hmm. So cgminer tries GBT first, and if it sees no Stratum header it stays on GBT?
In order of priority, cgminer will try to mine on stratum first, gbt second and getwork if all else fails, based on what order I think mining should occur. As far as I'm concerned, it's up to the pool operator to decide what they think is most important to prioritise. If you want to put a stratum redirect header in your GBT based pool, that's entirely your choice, knowing that cgminer will then use stratum preferentially. You can see the way cgminer prioritises the different protocols based on what I think is best for miners and pools, and the rest is up to you. November 30, 2012, 04:12:56 AM
Don't forget Doc https://bitcointalk.org/index.php?topic=27062.msg1218046;topicseen#msg1218046
The 5050 is fine
The 5050 is fine
Sure, I'll add one of those ports. What's special about them anyway?
Mining behind a firewall is no joke, I did originally choose Bitminter because you were offering port 80 mining. These ports are the only ones I can reach.
November 30, 2012, 03:39:29 AM
Don't forget Doc https://bitcointalk.org/index.php?topic=27062.msg1218046;topicseen#msg1218046
The 5050 is fine
The 5050 is fine
Sure, I'll add one of those ports. What's special about them anyway?
...
Good to know, I'll just add the header on getwork responses then.
Um - that doesn't make much sense?BFGMiner interprets the Stratum header as "prefer Stratum over the current protocol", so IMO it would be better if it were only offered to getwork requests.
Good to know, I'll just add the header on getwork responses then.
Hmm. So cgminer tries GBT first, and if it sees no Stratum header it stays on GBT?
Jump to: