Author

Topic: New, Trying to learn. BTC Pool Setup. (Read 579 times)

member
Activity: 66
Merit: 10
December 29, 2015, 01:39:02 AM
#3
Yes, sorry I did not specify which pool, BTC is what I am tinkering with (SHA256d). So when setting up the "ports" aspect of the bitcoin.json in unompo what are good values to help reduce the load?

Code:
"ports": {
   "3333": {
        "diff": ??,
        "varDiff": {
            "minDiff": ??,
            "maxDiff": ??,
            "targetTime": ??,
            "retargetTime": ??,
            "variancePercent": ??
        }
   }
}
legendary
Activity: 1302
Merit: 1068
December 29, 2015, 12:11:01 AM
#2
Hi all,

Brand new to the whole mining scene. So as with anything, I like to experiment and dig in to gain a fundamental understanding of how everything works. I was able to setup a pool and get it to run successfully, however I am not sure if my pool config is appropriate, as it is based off a LTC example. So I am curious if anyone would share what their pool config looks like or have any suggestions on setting up the vardiff portion of the config.

Thanks for your time and help in this matter.

Sound a bit technical. We're talking about a SHA256d pool?

If you really got pool software to work, then. Generally GH=Diff. Though you would want small miners to have a minimum of maybe 50, or 42 Tongue

Diff does not change performance so basically beside for more accurate reporting, you'll want miners to run at a high enough Diff as to reduce load.
member
Activity: 66
Merit: 10
December 28, 2015, 02:57:41 PM
#1
Hi all,

Brand new to the whole mining scene. So as with anything, I like to experiment and dig in to gain a fundamental understanding of how everything works. I was able to setup a pool and get it to run successfully, however I am not sure if my pool config is appropriate, as it is based off a LTC example. So I am curious if anyone would share what their pool config looks like or have any suggestions on setting up the vardiff portion of the config.

Thanks for your time and help in this matter.
Jump to: