Awesome, nice work!

btw: I also read some other coins' threads and it seems like there's a lot of people who think that SouthExchange is a great exchange and no one really knows why they are so "unpopular" volume wise. I think (or I hope) it will get more popular in the upcoming months.

C-CEX on the other hand seems to keep annoying more and more people.

We are less than 80 blocks away from the mandatory upgrade. From my amateur view on the explorer it seems like the majority of the network is still on old versions (mostly 1.1.2.x). Even the main pool is still running 1.1.2.2. Is this gonna be a problem? I mean as long as the sanctuaries are on the new version the whole system should be fine, right? People mining on a fork will (hopefully) sooner or later realize it and upgrade too...

Thank you very much. Unfortunately this did only help half way, because the reindexing seems to be just as slow. Ah well, I'll just leave it running over the next couple of days. Maybe I'll even start mining some coins when I have free resources.

Are you guys kidding? I wanted to start with this coin and downloaded the wallet, but it syncs like forever (more than 20 hours for 4 weeks and now stuck at 15 weeks remaining). So apparently there is a download for the CRP blocks to speed this up/make this possible, but you have to PAY WITH CRP for the download? How in the blue hell am I supposed to do that without a syncing wallet?

This is absolutely ridiculous. You deliberately hamper newcomers (who are willing to support your blockchain by starting a node) for the profit of half a cent? You should seriously rethink your business strategy there.

If your main wallet is a QT wallet you should see the PODCupdates in the transaction tab.

Now that you found the culprit the savest way is:
1. regularly check on you main wallet "exec stakebalance". Wait until it shows your FULL balance.
2. perform "exec podcupdate true" and check if it returns "performed successfully over 1 CPID"
3. Wait at least 6 blocks and check with "exec getboincinfo" if your UTXOweight equals your full balance.

Good luck!



On another note: it seems like both pools took a crap this morning. purepool seems to be back, the main pool slowly also fills up its leaderboard again. Main pool is still running 1.1.2.2. it seems and should be upgraded within the next 2 days or so.

try adding these lines in your wavi.conf (in wavicore folder) and restart your wallet:
addnode=89.40.13.238
addnode=195.181.219.114
addnode=62.77.152.90
addnode=89.47.164.212
addnode=82.135.154.58
addnode=85.214.65.60
addnode=60.124.18.190
addnode=188.120.231.98

Careful, I just now picked those randomly out of my connected peers list, so they might just work now.
Also I'm not sure if WAVI requires the port for those. If so, it's always 9983.


Regarding your hash rate: yes, that looks ok. Bear in mind that this is a notebook CPU and not really intended for mining.

So I can definitely say that my overall hashrate on this ukkey pool was (shown) significantly larger than on suprnova. However this pool seems to perform really bad, constantly at >200% block effort, so that's not good either.
I'm testing the aikapool from the poster above right now, seems like this pool is hitting blocks relatively fast, despite being only 3% of the net hashrate.

btw: all 3 pools (suprnova, ukkey, aika) require registration. But on the aikapool you could choose a random mail address because they don't send a confirmation e-mail.



Edit: ok, seems like both of those small pools perform like sh**. Really don't know what's going on there, but suprnova seems to suck all blocks out of the network and the smaller pools stay dry (currently at 500 and 900 % effort...). It also surely doesn't help that there's one idiot on AikaPool spamming it with thousands of invalid shares...

Edit2: All right, so over night the coin output on aika was extremely low, I left that one for now. The ukkey pool payed much better. It's still on more than 200% round effort, but I think that is a pool error in the hash rate calculation. At least for me this pool shows every worker with approx. twice its actual hash rate, so it would make sense that the whole pool overestimates itself by a factor of 2.

Suprnova has the vast majority of the network (more than 75%), which is not ideal to say the least. I just switched to "ukkey3.space", they have approx. 10-15%. Let's see how the coin output is over there over the next couple of hours.

I personally only download the installer of the new version and install it right "over" the old one, without uninstall etc. Worked for me every time.

What exactly do you mean by "it doesn't do anything"? Do you have peers connected? Is your wallet synced, but just transactions are missing? Or is the wallet not able to sync or connect to the network at all? What was the last version that worked for you? Which Windows are you running? Sorry for the many question.

Ah nice, even better. Maybe BBP can stabilize itself in a range above the 0.0025$ region.

On another note: I sometimes have the problem of Rosetta jobs somehow "hanging". That means they start running and some time in the middle they stop making progess. This results in them "blocking" 1 core for eternity (until I randomly discover them and manually abort). Does anyone else experience this? I cannot remember seeing this with WCG jobs though.

After closing and starting again it seems to work flawlessly. No idea what happened there...

It seems like there were some large buys coming in on C-CEX today. This should have been a good opportunity to sell the orphan funds (if that didn't happen already).

Never have truer words been spoken. 


btt: I just discovered that my Win7 wallet somehow stopped sending automated PODC updates almost 2 days ago so I missed the payment today and also cannot heat-mine for 24 hours.
Wallet was auto-unlocked as always and also manual PODCupdate works just fine. Anyone else had this problem lately?

Thanks for your efforts. Well, that's a pity, because he has other programs running which depend on current openssl versions, so unfortunately downgrading this isn't an option right now.

So basically BBP is still not functional on Ubuntu 18 ( apparently just like many other programs...) and would be best to run on 16.04 LTS, right?



Edit: @Lichtsucher: Any chance of getting a current BBP version on the repository before the fork? My Raspberry Pis would very much appreciate it.
Edit 2: Nevermind; I was on the old repository. The "stable" repo has 1.1.3.8 and works perfectly.

Excellent question; I think I'll have to check back with him to get some more details. If I had to guess I would say "per task" means he is running multiple wallets (which is fine on Ubuntu 16...). I'm not sure if he altered anything else (like libs and stuff).

Thanks for checking that out. Unfortunately I currently don't have any means to compile or test it under Ubuntu 18...



Edit: All right. So he had multiple wallets running and this was "per instance". BUT running only 1 instance, but with more threads (setgenerate true 16) had the same effect. He was pretty quickly at >4GB RAM usage.

He compiled from the old install_biblepay.sh script someone posted on reddit quite a while ago (but this should still be ok). The only thing he changed was some openssl library; he isn't sure, but he thinks it was "EVP_CIPHER_CTX".

Hope that helps.

A friend of mine wanted to start some POW (heat) mining because his RAC is already pretty high. He has Ubuntu 18 running and compiled from the 1.1.3.8 release. The compilation itself worked perfectly, but unfortunately the mining processes still suffer from this strange memory leak. It quite quickly went up to >500 MB per task, at which he stopped it.
Are there any of you who are running BBP on Ubuntu 18? Is the memory leak a known issue? Thanks for your efforts!

I tried 1.1.3.8 and this table looks better.
I still find the "UTXO target" a bit misleading, since this overshoots the minimum required stake without an explanation. This could be confusing (especially with the accompanying note "you have less stake balance available than needed.....") for newer members, but then again they probably don't even know the command "exec totalrac".

btw: The new wallet has the "memorizing prayers" step built into the startup process again and therefore loads veeeeery slowly. Was that on purpose?

No idea how accurate this is, but: https://www.difficultychart.com/stellite

Also, for the last month there is always the trusty hashvault graphs: https://stellite.hashvault.pro/en/#!/

Have fun mining, big dog!

Ah yes, that's maybe a more understandable way to put it. Thank you.

Yes, the table is 20*RAC, but this is NOT how the system currently works (as discussed previously). Take me for an example. I currently have a RAC in the range of 64k-65k. So in theory I would need at least 1280k (1.28 mio) BBP to stake to get 100% weight.
I do not (and did not for the last days and weeks) have this amount, but I never went below 100% stakeweight. The actual percentage you currently need to get to 100% stakeweight is >18.1 bbp*RAC. You can easily test this for yourself. Or you can check my history. I think for the last couple of weeks I've always been right on the edge at factor 18.1 and always got 100% stakeweight.

LOL, I just discovered this too and I think this is the simple solution to my "cosmetic" problem described above. All the transactions I was missing were PODC related. I just sent some BBP from one wallet to another and it immediately shows up under "recent transactions".
But indeed it would be nice if the PODC payments would be re-added to the overview.

The idea of the percentage table in "exec totalrac" is very nice, but unfortunately it shows the "wannabe" percentages and not the "actually-being-implemented" percentages resulting in misleading messages when you are in the range of factor >18. This is unlucky and should be adjusted to the levels that are currently in place. Alternatively it would be of course possible to adjust the levels on the blockchain with the next mandatory.