Recapping the pool issues:
We had two different problems hit the pool at once: instability, this is what Tiras reported days ago, and inconsistent hash readings, this has to do with your shares relative to other people.
Tiras, Tom both reported similar things- where random workers would drop off the list.
I found the root cause of the problem for the instability. Its now fixed, I believe permanently.
Next, Ill check on the HPS relative to others...
Pool issues fixed...
You should not see any missing workers in the pool, if one is missing, before posting here please restart the node once, and ensure it is running 1.0.7.1. 1.0.7.1 is now required by the pool for solutions to be correct.
I'll add two more columns to the pool for easier troubleshooting and for some new information...
Just when the pool was catching up with its deficit (I was about to lower the fee down to .04 from .05) as it was within -400,000 deficit range (for Slovakia thats how much was Lost since inception not counting the faucet that I spent 150K on), someone has hacked the pool last night. There is no trace of entry on the box, or a request for the withdraw in the logs, but this means the pool is not going to be cheap again for a while. If you prefer to solo mine due to the fees, I understand, go for it. Im not out to make a profit.
Anyway, if anyone wants to try to trace the hacker, here is the info for some of the withdraws in the middle of the night around 02:02am CST US time:
https://biblepay-explorer.org/address/BA6wJpAbA4WCNK9X1UwgnweCSCXCGYPZ71Id prefer to work in slack on the finer details. Alex when you wake up please ping me.
unfortunately that means we have to write yet another system that requires withdrawals to go through a whole different server.
Ill work on this all day today and possibly unto the night to try to get the withdraws working again guys.
bible_pay if you using VULTR: they can monitoring loggin to your machine
Yeah, I am using Vultr? Are they known to steal the passwords from crypto configs or config files? If so maybe I should switch hosts.
Either way its going to be so locked down tonight nothings coming out of the box but encrypted traffic, but please fill me in on vultr...
Pool Fees: 18%
I'm a little overloaded right now, but here is a quick update:
Im running a database maintenance script, and had to consolidate your balances owed into one more succinct record (in contrast to thousands of "mining_credit" records), this caused the server to think your balances are immature.
All you have to do is subtract the two numbers and you will see the total owed is still the same as before the script was started.
Ill take a look at putting it back to the way it was by tomorrow, but either way it will work itself out within 24 hours.
Next, I have an idea how we can prevent the pool from being a hacking target.
In the Python pool, they require a valid receiving address in order to mine.
I think what we will do in the future is forcefully send your rewards out every time a block is solved - to your address on file.
Give me a couple weeks to look into that feature, it may take a while to get that completely working, but I think that feature will button down the pool.
The 18% fee is just temporary. Hopefully you realize this is in order to keep the pool running.
