Right now there aren't any pool fees on this. The 10% charity are inherent in the coin/blockchain itself and have nothing to do with any pool etc.

Awesome, Lichtsucher, thanks a bunch! Looks nice and clean and up to now seems to work perfectly.

I immediately reverted all the machines I could manage now from the original pool to your pool, in general I think they occured in my personal statistics after no more than 2 minutes, although these are small miners.
One thing about the (general) statistics page: the graph for blocks found has a strange y-axix (why would the value ever be < 0?).

Let's see how many users we can bring there and when the first block hits.


In your biblepay.conf the line should say "pool=https://pool.purepool.org". Don't forget the "pool." before the URL!

LOL, the minute BBP is back on MN.Pro the price starts climbing (and probably another round of pump-and-dump begins). Rob, don't forget to cash in some of that orphan money at the higher price levels.

yep, all my miners are gone from the pool, and judging by the leaderboard I'm not the only one^^. What I don't understand is: why on earth do almost all pool users lose their miners except for capulo, demonko and some others who are still going at full sails? Seems really strange to me...

I sent you 10001 tBBP, have fun.

Lol, I think you mixed something up here. I mined these amounts in tBBP, which are not real Biblepay coins, but just imaginary BBP in testnet (hence tBBP) for testing new upcoming features in a closed environment. These thousands of tBBP aren't worth anything and cannot be converted to anything else.
Btw: I just received another payment of the exact same amount of 75418.58 tBBP...

P.S.: My mining outcome in real  BBP is also not a lot these days.

Lowering the difficulty definitely had some effect. All the small miners (even Raspberry Pis) are constantly in double digits share-wise. However my two strong DualXeon machines show huge inconsistencies regarding their HPS2 and shares, one of them (running 1089) even drops to 5-6 shares from time to time, which is completely ridiculous. So the low difficulty seems to level down all miners to a certain level of "uniformity" and give a big malus to the stronger machines.
The pool itself seems to hit a bit more blocks (10 currently for 24h), but I'm not sure how this would be a result of lowering the diff; it probably is a coincidence.

Regarding the PODC: I ran BOINC for maybe 30 hours now on my Xeon 1230v3 (half of the time besides a cryptonight miner) and right now I'm sitting at RAC 503 and mag 55. Over the last couple of hours I received 3 mining payments with exactly 75318.58 tBBP each. Is this some kind of bug? It seems quite strange to me to receive 3 mining credits in 5 hours. Or is this the accumulated credits for all my BOINC mining (but then it would also be strange to have thrice the exact same amount...)?

I just wanted to check out the BOINC mining and started a testnet-wallet on my standard PC. I also created a BOINC account and joined the Biblepay team on Rosetta@Home (and right now I'm solving my first Rosetta@Home project).
Now my problem is that when I wanted to associate my BOINC account with the BBP wallet (in the DC section) I got a message "balance too low to advertise DCC, 1 BBP minimum is required". So I think someone would need to send me some tBBP.

Receiving address: yNQVjP53HjrrjSVP8KtgdQgHLPNXMH1fEb

Thanks in advance.

Long post, (kinda) short answer:
Miners fall back to solo mining if the pool is down, has no connection, does not send packages etc. In case of solo mining, your "worker id" is ignored and every machine you have is mining for itself (hence "solo"). That means the machine with the dove symbol for the mined block was the actual (and only) machine that luckily hit it. The block mining reward is directly transfered to the miner (no extra identification necessary).
To force solo mining you just have to comment the pool= line in the config (like this: #pool=...), the worker line will be ignored anyways. You'll see if you run solo or not by typing "getmininginfo" in the debug console; there it should say "poolmining=false". Hope that helps.

P.S.: Indeed hitting solo blocks is pure luck, so it could very well be that you go on to mine for - let's say - another week before hitting one again...

Yep, pool seems to be down or at least have a major hickup right now. All my miners are "gone" from my leaderboard, but some of my hash power miraculously shows up in the overalls.
But then again the same thing happened yesterday and after that the pool had a nice run in finding lots of blocks, so we'll see...

There's a website ranking hundreds of cryptos according to their code (github) activity. Currently BBP is ranked 153.

https://www.cryptomiso.com/

Indeed over night the pool saw a siginificant increase in solved blocks so there were definitely some improvements going on. *thumbs up*
I also realized the huge drop in HPS2 yesterday in the evening (not sure about the block height) where almost all of my miners dropped to zero or 1-2 shares. Since then it seems like HPS2 and shares have taken a leap. The only strange thing is that now there seems to be no significant difference between all the machines. From my Raspberry Pis to my rented DualCore machines up to my Dual-Hexacore Xeons they all seem more-or-less equally strong (maybe the Xeons roundabout twice as strong as the Raspis).

Just a quick question regarding this offer (sorry if it's a stupid question^^): assuming one would send you the 155000 BBP, what "security" does he have to receive the payments and/or get his share back? Of course we are a Christian community and I shouldn't assume anyone would use this to scam other's BBP, but I was just wondering about the general rules being applied to this. I'm fairly new in all this crypto stuff, but from my understanding if you send coins to any address you have no tools in your own hand to get them back, right?

That being said, I'm really contemplating getting in on your offer, since POL won't be here for some weeks/months and right now the mining output is ridiculously low :/.

I hate to say it but it seems to me that the critics are somewhat right about the pool. How on earth did we not hit a single block for straight 9 hours??? This is plain right ridiculous. I don't think anybody renting machines can even cover the costs right now, not to mention the PC's power bills from the machines running at home.
I tried going solo with a QuadCore and a Dual-Hexacore over the last couple of days, but didn't have any luck either; going solo with rented 2-core machines is of course completely useless...

Any idea on who hits all these blocks?

Furthermore: the pool "shares" have again dropped so hard that some of my small miners keep appearing and disappearing.

P.S.: If anyone is interested: Yesterday I tried BBP on an ASUS Tinker Board (Raspberry Pi 3 clone) running Armbian and it works too; the reported HPS on the pool is significantly higher than for the Berries, but it's running in serious heat issues right now. I still have to find a better (yet quiet) cooling solution...

Thanks. Just right now the pool logged me out again so I checked my cookies for pool.biblepay.org. There are 3 cookies stored: 1. "ASP.NET_Sessionid" 2. "credentials_username" 3. "credentials_password". Both "credentials" cookies say "session: false" and expire somewhen tomorrow evening; the ASP.NET cookie is "session: true" and its expiration time is always the current date and time...

I'm using Vivaldi 1.13 stable, which is based on chromium afaik. Hope that helps.

The "threadcount" on BBP is not what you usually would think of it compared to -let's say- cryptonight algorithm or something like that. If you are running on windows and want to use your PC for something else while mining BBP, you should go to task manager, assign the lowest priority to BBP and then step-by-step raise your threadcount (e. g. on-the-fly in debug console via "setgenerate true X", X being the thread count). Then wait for your pool output to adjust (maybe 20min) and see if it's getting you higher shares (or HPS2). In the BBP algorithm it is easily possible to assign way more than 1 thread per physical CPU core (or even more than 1 thread per logical core) and still get better results. You have to find a "sweet spot" for this.
Of course you should have a CPU at stable clocks/voltages and proper cooling for all of this, but that should be prerequisite for all mining going on with your CPU.

That being said for people with a physical 64core machine (whatever the heck kind of a monster that is.... ) the max. thread count of 40 seems too low; I'm not sure where this restriction comes from, maybe it's necessary to put a lid on the "overhead" produced by the high amount of threads.



P.S.: @Rob: just 2 very minor things I realized on the pool page:
1. Would it be possible to configure the login page for "hit enter to login"? It is quite strengous with the frequent auto-logoffs to always type your login, password and then move your hand to the mouse and click on the "login" button.
2. The extra column stating "GlobalErrorPercentage" on the Leaderboard is definitely overkill and takes up alot of additional horizontal space. In my opinion it would be better to add this information in the header of the "ErrorPercentage" column (maybe like ErrorPercentage
Global=XX%
or similar).

Thx Rob, it worked perfectly and I sent some BBP to the new address on one of the machines.

Good news with C-CEX indeed. I'm really curious how the market price will react, either way we should see a significant volume spike now.

As long as they are listed in "My Leaderboard" it's all good; the pool just didn't hit any blocks since 27488.

@Rob: I just realized something quite strange while distributing some small amounts of BBP over my miners:
For each miner I read out the address via getaccountaddress "" and sent some BBP to these addresses. However now 2 of my miners received the sum of 2 of my sendings; apparantely they have the same wallet running (despite showing completely different accountaddresses). Is this even possible? I find this quite confusing^^.

Would it be "safe" to simply delete the wallet.dat on one of those machines and let the client re-install a new one? What would be the command for this?

Thx in advance.

P.S.: If it helps, these are the two addresses: BNfy4JU3rquR7LtYUzwNNU9B4W4i8TfAPZ and BFrtFPN9Mxi5ThwrUBJ7LXwEne7jThUjAv

yep, i "third" this; I think even upto 1084 they behave quite stable, only the 1086 ones have completely disappeared from the pool :/

I'm really glad to see that over the last few hours the pool seems to make up on his deficit of hitting blocks; really nice coin output so far and big thanks to Rob for his dedication and his patience in keeping up with all the complaints.

Another big thanks goes out to Lichtsucher for his amazing efforts in generating the BBP apt package, especially the ARM version! I gave it a try on the Raspberry and it works like a charm. Before it took approx. 4-5 hours to install BBP on a Pi 3 (without GUI!) and then 1.5-2 hours for building every update, which was quite exhausting...
Now with the repository in hand I managed to start mining on the Pi 3 in less than 10 minutes! Another big advantage is that the package installation does not need the 1-2 GB "biblepay" folder, so it saves a lot of microSD space. (Unfortunately I am very busy at the moment, but when I find the time I will try to get BBP running on a minimal Ubuntu ARM system, maybe condensing the whole system to a 2 or 4GB SD card).
I see that you started a proposal for your work on the repository and package. I am far away from being a MN owner but I would definitely give you 10 upvotes for that.  

God bless all the people dedicating time and effort on this project!


Regarding the pool "shares": I think right now they are at the absolute minimum of what they should be (I'm sorry, I have no clue about the technical or mathematical aspects going into this...) because from time to time my weak miners (DualCores or Raspberry Pi) disappear completely (but then show up again some time later...).