Prohashing Mining Pool Forums

Here's today's status:

• We're proud to announce the rollout of "ignore payout threshold" at the coin level. Previously, "ignore payout threshold" was only available for either all coins, or for none at all. Requested by several customers in January, this feature gives everyone the opportunity to limit transaction fees by not being forced to accept payouts for coins they don't need immediately. The feature is available immediately.
• The "r=" parameter, which skips work restart testing and allows miners to statically define an interval, is now documented and available. This parameter will be useful for miners who rent mining equipment that can't be set to the low difficulty required for work restart testing.
• Worker stats are now available for all miners. When multiple mining rigs are connected to an account, the current status of each of the workers is now available in the new "worker status" box on the "earnings" page. To set the names that identify each worker, use "n=." If you don't specify a name, as most people who don't know about the feature yet probably are, then a random UUID is used to identify workers. The feature is available now.
• Before we implement multiple algorithms, one of the issues Chris and I discussed is how to make use of the enormous amount of data we have in the system (over 100GB now). Rather than just deleting it, we can provide additional services for free that draw in potential miners and also cause more people to become interested in altcoins. It's like the way Google lays down Google Fiber - their goal is to grow the entire Internet, because Internet users inevitably come to Google. If we can use our data to grow the altcoin markets, then market capitalizations will rise and everyone will make more money, including us.
• The first of these interesting features is a "universal block explorer," which should remedy the problem that about 80% of altcoins have - there is no block explorer for the coin. It will take a lot of CPU power to process all the data we need, but once we get it processed, we have a prototype. The flow is that you click on "explorer" at the top of the page, then select the coin you want to view, and then you can follow transactions and blocks and wallet balances. It's simple, provides a key tool that altcoin developers need - and we already have all the data to provide it within a week.

Steve Sokolowski wrote:Here's today's status:

• We're proud to announce the rollout of "ignore payout threshold" at the coin level. Previously, "ignore payout threshold" was only available for either all coins, or for none at all. Requested by several customers in January, this feature gives everyone the opportunity to limit transaction fees by not being forced to accept payouts for coins they don't need immediately. The feature is available immediately.
• The "r=" parameter, which skips work restart testing and allows miners to statically define an interval, is now documented and available. This parameter will be useful for miners who rent mining equipment that can't be set to the low difficulty required for work restart testing.
• Worker stats are now available for all miners. When multiple mining rigs are connected to an account, the current status of each of the workers is now available in the new "worker status" box on the "earnings" page. To set the names that identify each worker, use "n=." If you don't specify a name, as most people who don't know about the feature yet probably are, then a random UUID is used to identify workers. The feature is available now.
• Before we implement multiple algorithms, one of the issues Chris and I discussed is how to make use of the enormous amount of data we have in the system (over 100GB now). Rather than just deleting it, we can provide additional services for free that draw in potential miners and also cause more people to become interested in altcoins. It's like the way Google lays down Google Fiber - their goal is to grow the entire Internet, because Internet users inevitably come to Google. If we can use our data to grow the altcoin markets, then market capitalizations will rise and everyone will make more money, including us.
• The first of these interesting features is a "universal block explorer," which should remedy the problem that about 80% of altcoins have - there is no block explorer for the coin. It will take a lot of CPU power to process all the data we need, but once we get it processed, we have a prototype. The flow is that you click on "explorer" at the top of the page, then select the coin you want to view, and then you can follow transactions and blocks and wallet balances. It's simple, provides a key tool that altcoin developers need - and we already have all the data to provide it within a week.

Great developments guys. Particularly the worker stats...

Regarding the data usage for bring people to alts... what did you have in mind? Or is the universal blockchain explorer the first leg in that strategy?

Steve Sokolowski wrote:Here's today's status:

• Worker stats are now available for all miners. When multiple mining rigs are connected to an account, the current status of each of the workers is now available in the new "worker status" box on the "earnings" page. To set the names that identify each worker, use "n=." If you don't specify a name, as most people who don't know about the feature yet probably are, then a random UUID is used to identify workers. The feature is available now.
  .

Hey Steve -

So I've tried d=8064;n=95 and d=8064; n=.95 and neither seems to have changed the identifier of that particular rig. I must be missing something?

Thanks!

d=8064 is not a valid static difficulty. You need to use a power of 2 for the difficulty, so 8192 would work but 8064 would not. You should also use a space between the password arguments instead of a semicolon. I'm also not sure if . is a valid character in the miner name. See https://www.prohashing.com/help.html#tu ... sswordargs

Chris Sokolowski wrote:d=8064 is not a valid static difficulty. You need to use a power of 2 for the difficulty, so 8192 would work but 8064 would not. You should also use a space between the password arguments instead of a semicolon. I'm also not sure if . is a valid character in the miner name. See https://www.prohashing.com/help.html#tu ... sswordargs

Sorry I meant 8192. Trying without a semicolon now.

EDIT - perfect now. Thanks guys.