What is the command about setup config for new POG mode after upgraded BBP version 1.1.8.5b?
If I want to keep using PODC , what's command need to add in related config?
As long as your CPID is still associated, PODC will keep working after block 100,000 with the existing config. You can also run in POG mode in addition to PODC by using the 'tithe=nnnn' key in the config. This will tithe every 'nnnn' minutes (The number should be above 2 btw). I'm going to be testing that today in my windows wallet. 'exec getboincinfo' should still be working after 100,000. |
|
|
|
Hi Togo, Did the new version fix the explorer boot issue? |
|
|
|
Hi everyone! I have allready not update to last mandatory but I think Im mining in fork. Or just Purepool is down? How do I update the wallet on linux? What are the comands to do so?
Thanks!
/biblepay/src cd .. ENTER git pull origin master ENTER make ENTER cd /biblepay/src ENTER ./biblepayd -daemon -reindex Hi everyone, so in upgrade from 1.1.7.9 to 1.1.8.5 I lost more or less 190.000 BBP ..
What I need to do ?
Thanks
Ale
./biblepayd -daemon -reindex Thanks! Seems that Purepool is not synchronized, is 10 blocks late! And how do I update the wallet? Which comands do I have to use in order to update an allready installed version? rm blocks -r rm chainstate -r rm gov* rm mnc* rm mnp* restart wallet |
|
|
|
Solved
What have you done? I need to fix it! im posted for you help....do you know to read? or PM me your IP pass and i can to help you  Yes, thank for the reply. But my problem seems to be something else. Im 10 blocks ahead from Purepool, or Purepool is behind. Please see if your 'exec versionreport' only shows 99% > on 1.1.8.5. If not please re-index. I think purepool is not around to resync the chain. |
|
|
|
1.1.8.5b is already in Ubuntu Launchpad. (PPA repository)
Remember that it just adresses a crash in a RPC (console) command , so it doesn't make any difference to 1.1.8.5 in terms of chain consensus .
after upgrade,still crashed I just checked the windows version ( www.biblepay.org) works and does not crash, maybe its the PPA version? |
|
|
|
|
I believe the pool problems are resolved, please email me if anyone finds a pool problem.
|
|
|
|
Who is on 1147?
19:42:29

exec versionreport
19:42:30

{
"Version": "Popularity,Percent %",
"1147": "1; 0.49%",
"1185": "204; 99.51%"
}
1 bbp'er won't hurt but will get lost after block 100,000 hits. |
|
|
|
Yes that's the one with exec versionreport 1.1.8.5. (Thats the one we want to be on through block 100,000). All my sancs on this chain now. Looks like fork is almost worked out. |
|
|
|
|
Expenses and Revenue updated for this month.
Thanks Gunde for the 500K+ tithe! It went directly to compassion.
|
|
|
|
|
Regarding the 5 dns seeds being bad, I just updated all 5 to point to 5 good nodes at vultr (who didnt go down) however give it about an hour to update (as all 5 are upgrading now).
|
|
|
|
|
Regarding this fork and choosing between the two chains, the diff is so close between the two the wallet is having a hard time choosing one or the other.
One thing I have discovered is chain B is 99% 1.1.8.5 while chain A is mostly the older, non upgraded wallets.
So for a rule of thumb to get us out of this, I recommend doing this from each of your nodes:
exec versionreport
If the report shows > 90% 1.1.8.5 nodes, you are on the right chain.
If the report shows more than a couple lines of info, please rm blocks, rm chainstate and restart the wallet.
If you are not sure, please re-index.
I think after we do this we will resolve the fork.
|
|
|
|
It seems like there are several problems right now. Most of my ARMs are on the apparently correct chain, but I just updated two of them to 1185b and this version does not seem to find peers at all. Also the PODC update system seems corrupt. The pool superblock view shows 0 for a lot of CPIDs and if I look up my CPID here: https://forum.biblepay.org/tools/podcstatus.php?cpid=7c9264559fef3c1c689ee9fc3ff42494it says my last PODC update was on 01/31, whereas my controller wallet constantly keeps sending them (mininmum 6 times yesterday alone). Strangely enough I received a PODC payment just a couple of hours ago.  Also, my Sanc says "expired", but I received a payment for it just 3 hours ago ... [Edit]: nevermind, this one also was on a wrong chain ... @MIP: where do you see this "chainwork" information? Using getblockchaininfo command. You might find all sorts of inconsistencies depending on where you look at (and the fork where that tool is at the moment). Also, as there seems to be some issues with the DNS seed servers, sync gets harder (it also happened to some users with the Android wallet a couple of weeks ago) The reason the 6 dns seeds are down is my sanctuary host went down and these seeds might need updated (depending on how bad the outage is) but its still going on right now. Oh thats horrible that we had android users out of sync also! Man, we are providing terrible service to our users. Maybe it will get worse before it gets better. On the 'horrible inconsistencies' you might find, yes, if there are two chains, depending on which one you look at you will see an entirely different view. In the mean time, MIP one thing you might help with is see if getchaintips shows the two competing chain hashes - you can do a 'reconsiderblock hash' on the chain with more work on one of your nodes that is out of sync, and see if it syncs to the top. That would tell us if that paritcular node has a bad block in its chain (in its view). |
|
|
|
I shut down PODC few days ago. And leave wallet online with 1% CPU mining on pool.biblepay.org... And after few days i got it..
Please check your wallet with the "getblockhash" commands we posted earlier to see if you are on a fork. As already said, this symbol means that you found a block on your own, which is theoretically possible, but with 1% CPU highly unlikely. Btw: the main pool also seems to be on the wrong chain, it constantly changes the given information like "coins mined", "offline workers" etc. and also seems to be quite unresponsive. I believe we were being attacked today. I took pool2 down to give us a chance to take a look at this. I'm working on finding the performance problem now. |
|
|
|
ROBERT thanks you that you deleted my account on your pool ... excellent facepalm i had bbp on pool-wallet  I don't delete random accounts in the pool, but you got my message via e-mail saying I've been helping you correct? What about the e-mail that I sent saying I was restoring the account and the reason you got deleted? Do you want to inform everyone ... that you are in contact ... and things are getting resolved... |
|
|
|
Maybe wrong question. But... where is our dev when everybody has problem with fork, wallet, masternode, mining ... after mandatory update???
Ive been working on biblepay.... |
|
|
|
|
1.1.8.5b-Leisure Upgrade
(Recommended for everyone)
- Fixes bug in getdifficulty (causing a crash)
|
|
|
|
Yes, unfortunately I was able to reproduce this issue. Fortunately the exchanges usually dont use this command by default, so I think we can patch this without wreaking too much havoc.
C-Cex shows difficulty on top-right of the trading BBP/BTC pair page, but I don't know if it comes out from that command or from getinfo. Meanwhile I will compile 1.1.8.5b for MacOS and also prepare ubuntu PPAs BTW I upgraded my sancs to 1.1.8.5 from PPAs without issues, I didn't even need to delete blocks/chainstate data except in one of them (I could have shut it down unproperly). sudo add-apt-repository ppa:biblepay-official/mainnet
sudo apt-get update
Packages for Biblepay mainnet (stable).
Distros: 16.04 (xenial) and 18.04 (bionic)
Architectures: i386, amd64, armhf, arm64
sudo apt-get install biblepayd # daemon and cli
sudo apt-get install biblepay-qt # for QT GUI
For c-cex we got the code in before he upgraded so we are OK there. Great on the re-compile. I'm working on windows now. |
|
|
|
Rob, regarding PoG, some questions that will surely be of interest for our community and investors:
- how will the reward distribution be in terms of %?
- Will tithes replace the monthly 10% superblock for orphans or will it add up?
- Will masternode owners keep on having the same share as miners/tithers?
Thank you for the great job.
I'm gathering the answers for this now. Hi MIP, Thanks for the questions! - how will the reward distribution be in terms of %?
-> From block 100,000 to 106,000:
The reaper (heat miner) receives 20% of the heat mined portion of the block reward (heat mining portion is 3%, reaper receives 20% of this, 80% goes into the pog pool kitty), meaning on a 15,000 bbp block, the reaper receives ~100 bbp while 400~bbp goes into the pogpool.
- Will tithes replace the monthly 10% superblock for orphans or will it add up?
-> The tithe cap restricts total donations to the foundation to approx 1.5MM per month. This amount is added in addition to the current charity superblock but comes from miners donations. So we can expect approx 4 mil from the superblock for charity + 1.5 mil from the donations after POG is live.
- Will masternode owners keep on having the same share as miners/tithers?
-> Yes, the sanc reward stays the same (IE approx 4500 bbp on a 15,000 bbp block).
Deflation remains the same, and the coin emission schedule remains the same. The only difference we realize is the additional 1.5MM being given to the orphan foundation directly from mining tithes.
|
|
|
|
Hey Rob, I believe the command getdifficulty causes wallet to crash, it was last message on explorer daemon debug.log with debug=1, and I tested it on a masternode wallet and it crashed that wallet too
Did you type 'getdifficulty' with no params and how many blocks on the sanc that crashed? On the explorer daemon it seems to set me back to block 0, as if I did full clean On the masternode, when I spin daemon back up and checking with getinfo, its been stuck on Error code 28 "Activating best chain" for the past minute Correct, typed "getdifficulty" with no params for masternode test, Looks like iquidus explorer also uses it with no params Great, thanks for reporting this. Yes, unfortunately I was able to reproduce this issue. Fortunately the exchanges usually dont use this command by default, so I think we can patch this without wreaking too much havoc. I need to create an emergency update for this as a leisure. I'll work on this right now. We need to release a 1.1.8.5b to prod to patch this.
|
|
|
|
i wonder how it is possible to have coin age >.5, especially with automatic podc updates every 4hr
if i send podcupdate, coin age is reset to 0
i tried also pog, same... avg coin age displayed is reset to 0
does not matter what i do, any outgoing transaction takes whole amount and send it back to me (without amount that i'm sending away)
"exec bankroll" rpc command splits large utxo's into chunks so they can age. but will this works with podc? i remember, that i needed to move all chunks to one address in wallet to work with podc i'm still wondering, why there are no clear and simple instructions how this (POG) will work, and how to operate this. please do not delete this post (which only asks for information), it would be bad marketing move. Just be courteous to us and helpful to others and your posts won't be deleted. I'll reply asap; in the meantime, if anyone else will help out with this please do. |
|
|
|
|
Show Posts
