This is kind of a hidden thing in the pool, but when it says HEALTH_DOWN and you are still pool mining, it actually means GENERATED_BLOCK_IS_STALE.  Ill be fixing that over the next 24 hours so you know the pool is not really down.

Ok for those dropping from the pool, I just sent out 1.0.3.5 (Non-Mandatory) as a pre-release.
Please test it and we can burn in overnight then release tomorrow.

Regarding the error Happy reported Im still looking at that, it seems to be going away, so Im still trying to get a true root cause.

I found the root cause of this - basically the biblepayd miner is relying on the cached credentials too much; I made the cached credentials get cleared every 6 minutes (IE the server must report to the pool and get new credentials at least every 6 minutes), so the difference is - instead of seeing "RMC" which means "READY TO MINE WITH CACHE", You will see ONE "RM" and many "RMC" like you do when you do a fresh boot- Ill have a version out that you can test in about 15 minutes, let me know if successful and if so tonight I will release it as the next version.

Those will be explained in testnet soon, for now they are not used.

I was able to write a letter as you and save it (I deleted it of course) - ive only tested Chrome and IE.  I see you were able to save other pages, such as your default withdraw address.  Those use the exact same type of save method.  Interesting that Save a letter wont work.  When you click Save on the letter it should immediately take you to the orphan outgoing letter weblist.  When you click save what error do you get?  Can you try going into Chrome, click f12 (developer console), paste the letter and see if you find any Web alert javascript errors?  Also you can try to disable any plugins (suchas yahoo toolbar, chat, etc).  You can also try to go to Account | Account Settings, change your withdraw address to something like Test, click save, and tell us if that sheds any different light on the problem?

Thanks.

Let me try to reproduce as you, one minute.

Yeah, I read inblue's post this morning, and have been trying to reproduce this issue (with dissapearing linux miners).
For some reason my windows miners (tiny, tiny chickens) stay in but finally, I can see my vultr-4proc is dissapearing regularly now.

Alright, Ill figure out whats wrong...

Yes, its definitely going to be open source, but I think I want to burn it in on Wests system first, until we get to the point that it is not changing every day, then we will expose the link on github.

The specs right now : it requires Windows 2008r2 server, 4 processors, 8 gig ram, Static IP, IIS7, Windows 2016 SQL Server, .NET 4.5 framework, Biblepayd running on the server, and anti-ddos at the ISP.  You can run one for $55 a month at vultr.  This server will probably handle 1000 users.   After that as you can see it slows down.  I think with Wests running, and me running two pools (I plan on opening up a 2nd pool hooked to the same database soon just as a backup pool) I think we could then handle 3000 biblepay users.  Right now we have about 1000.

Yes that would be great if you cover Europe.

HPS2 is just a pool thing: Its roughly 500*SharesSolvedInCurrentRound*ShareAgeDecayFactor

Its what is currently being used for payments, and also to prevent any cheating- it was getting a little hard to manage the original pool code that created a Synthetically measured HPS in the pool and I was getting afraid that someone who starts pool2 would pollute it or cheat themselves so I think this is the fairest way to do it, for what we are doing.

It is cumbersome, to maintain 5 passwords, 5 withdraw addresses and 5 sets of workers.

I agree, not trying to stop them from mining.  Just trying to stop them from polluting all the reports, in specific, the Stats column in block_distribution.

Also, technically if I did add the limit of 20 workers per account, they would have to manage 5 accounts, which is cumbersome, and would definitely slow the pace of the expansion down.

Not sure yet; Im also considering just grouping large accounts by minerid and letting them run rampant.  Its a tough one.

Thanks a lot for the comments!

Yeah, I definitely did not intend to publically beta test on the main chain, LOL, its absolutely horrible.  We have a new testnet thread at forum.biblepay.org, and we "thought" we tested F7000, but we didnt catch this issue, so we were forced to fix it in prod.  I guarantee we are going to test the sanctuaries inside and outside in testnet and add the web governance software before we move it to prod!  Also, we will have a slack team soon, so that should be exciting, bringing on more devs, etc.

This problem will resolve itself over the next 2 days as people upgrade, but if necessary I can move these messages to Debug only, lets see if they go away, weve got 44% upgraded according to 'run versionreport'

Here is something that worked for me, I had a similar problem.  Try creating a subsdir in %appdata%\biblepaycore, called Trash, and Move your blocks,chainstate and database in Trash.  Then restart the wallet and try to mine again.

EDIT: It seems to be something that is hidden and locked in chainstate, that I could not get rid of, some type of berkeleydb .lock file.

Subsidy schedule is on biblepay.org.
Its about 19,000 BBP per block right now.

Pool biblepayd went down around that time (at least it lasted all night til 7am so its on a stretch after the mishap) anyway try withdraw again.

Looking at the error, on the bright side it looks like we are down to one distinct error the one everyone reported early this morning.

Right, I sort of feel you.  The thing is, if they go through the expense of buying a Full node and mining by the rules then they get the equal reward.
However, I might consider limiting the miner count to 20 workers per user address, so we dont break the pool.

Please stop posting derogatory things here - this way you wont be banned.

Yes, I noticed it last night.

It is funny, but Please, please do not abuse the prayer feature.
 
Right now it is available for very serious prayers, what if someone has cancer or has a serious illness and needs us to pray?

They are not going to be very happy when its littered with trash.  This is a serious instrument designed to get our community to pray for others who really need it.

And I think right now in the world with the instability its more of a necessity than ever to have it available and be responsible.

If people do abuse it we will have no choice but to put admin tools around it making it hard for anyone to just send a valid prayer in.

Thanks.

I believe that was just before the pool upgraded to 1.0.3.4.  Should be good now.