Prohashing Mining Pool Forums

Good evening!

• A new feature has been created: API key requirement. When API key requirement is enabled, customers must provide their API key as the "k=" password argument for every miner associated with the account. Miners that omit "k=" or which provide an incorrect key will be disconnected. The default is for API key requirement to be disabled, which means that "k=" is ignored.
• This feature was brought to our attention by a customer who complained that his live worker statuses and charts were being polluted by someone who was using harassing worker names. Since the problem can't cause losses of money (in fact, people have to waste money to do this), this will be released along with other fixes on Sunday.
• Chris called the lawyer today and it will likely be at least another week until that issue moves along.
• I was able to reduce the number of support tickets from 148 down to about 95, but 68 of them are in "waiting for customer" state. The remaining 37 are difficult tickets, but some are duplicates like many customers pointing out a single coin that didn't pay out. Our focus this weekend will be on resolving these tickets, rather than adding new features.
• Novaexchange added ETH base pairs to all of its markets, so Chris enabled them. In the first hour, we were only able to make 35 trades in those markets. I encourage everyone to trade in non-BTC base pairs so that we can all save on transaction fees and avoid the unusable bitcoin chain.

The #2 on here made me chuckle.
Really, people complained someone was sending them extra hashing power they didnt have to pay for?
Scroll the page down? Look at a different page and enjoy the free cash?

I accept all free hashing power to my account and I promise I wont complain at all or even look or care what you call the extra miners.

Steve Sokolowski wrote:Good evening!

• A new feature has been created: API key requirement. When API key requirement is enabled, customers must provide their API key as the "k=" password argument for every miner associated with the account. Miners that omit "k=" or which provide an incorrect key will be disconnected. The default is for API key requirement to be disabled, which means that "k=" is ignored.
• This feature was brought to our attention by a customer who complained that his live worker statuses and charts were being polluted by someone who was using harassing worker names. Since the problem can't cause losses of money (in fact, people have to waste money to do this), this will be released along with other fixes on Sunday.
• Chris called the lawyer today and it will likely be at least another week until that issue moves along.
• I was able to reduce the number of support tickets from 148 down to about 95, but 68 of them are in "waiting for customer" state. The remaining 37 are difficult tickets, but some are duplicates like many customers pointing out a single coin that didn't pay out. Our focus this weekend will be on resolving these tickets, rather than adding new features.
• Novaexchange added ETH base pairs to all of its markets, so Chris enabled them. In the first hour, we were only able to make 35 trades in those markets. I encourage everyone to trade in non-BTC base pairs so that we can all save on transaction fees and avoid the unusable bitcoin chain.

Great work! any status on the new exchange?

Jalapan wrote:

Steve Sokolowski wrote:Good evening!

• A new feature has been created: API key requirement. When API key requirement is enabled, customers must provide their API key as the "k=" password argument for every miner associated with the account. Miners that omit "k=" or which provide an incorrect key will be disconnected. The default is for API key requirement to be disabled, which means that "k=" is ignored.
• This feature was brought to our attention by a customer who complained that his live worker statuses and charts were being polluted by someone who was using harassing worker names. Since the problem can't cause losses of money (in fact, people have to waste money to do this), this will be released along with other fixes on Sunday.
• Chris called the lawyer today and it will likely be at least another week until that issue moves along.
• I was able to reduce the number of support tickets from 148 down to about 95, but 68 of them are in "waiting for customer" state. The remaining 37 are difficult tickets, but some are duplicates like many customers pointing out a single coin that didn't pay out. Our focus this weekend will be on resolving these tickets, rather than adding new features.
• Novaexchange added ETH base pairs to all of its markets, so Chris enabled them. In the first hour, we were only able to make 35 trades in those markets. I encourage everyone to trade in non-BTC base pairs so that we can all save on transaction fees and avoid the unusable bitcoin chain.

Great work! any status on the new exchange?

Not right now. Chris is responsible for implementing the exchange, but it has been delayed until late October since we will need to go to Asheville for a wedding next week and he is buried in support tickets this week.

Thanks for the "k=" argument. I am looking forward to using that one!

a

Is this API key requirement option a type of extra security? What is the point of it? And how do you enable it?

jimbo207 wrote:hey Steve, I live in Asheville. lemme know if yall would like to meet for a frothy beverage while youre here. or if you need some local advice

I'd love to meet someone, but unfortunately, I don't think there will be any time to do so. To save time, we're going to arrive as late as possible, go to the wedding, and then around the next day and get back to work. There are too many tickets to do otherwise at this point, and we don't know when or if we will ever be able to get a lawyer to deal with the issue.

AND you deleted my message ? Fuck you guys - I'm done with this fucked up pool