1.2.0.1 - BiblePay - Mandatory Upgrade
Android mobile app updated(may take a few hours to propagate to all Google Play servers around the world) |
|
|
|
The older Ubuntu PPA compiles the new release right now. After that is finished, Purepool will be updated (again...)
what about other releases? i was trying some i think 17.04 ubuntu and there was only 1.1.3.8 or so ... Currently Licht's repo maintains packages for 16.04 (xenial), 17.04 (trusty) and 18.04 (bionic). Unfortunately trusty compiles fails for some reason. I can check what's going on and see if I can fix it. The repo that I maintain directly has support for 16.04, 18.04 only, and i386, amd64, armhf, arm64 architectures. If you need it, I can activate for 17.04. (and hope it doesn't have the same problem as Licht's repo, which might happen as we use a different packaging manifesto) |
|
|
|
1.2.0.1 - BiblePay - Mandatory Upgrade
- Disable sanctuary payment verification until a future spork is activated
MacOS version ready Ubuntu PPAs currently building (will take a few hours) I still can't see the Ubuntu Mandatory update available. biblepayd is already the newest version (1.1.9.9g-xeniall).
For some reason it takes some time for the update system to obtain the latest version from the repo, even if compiling finished 1-2 hours ago. In this particular case, right now all my linux nodes have "found" the latest version, so please try now. |
|
|
|
1.2.0.1 - BiblePay - Mandatory Upgrade
- Disable sanctuary payment verification until a future spork is activated
MacOS version ready Ubuntu PPAs currently building (will take a few hours) |
|
|
|
Ill make a leisure release now with:
- Reboot disabled
- Drop all connections below 1199
In the mean time if we can solve a few blocks on the main chain, all these problems will resolve by themself.
Ready for MacOS Ubuntu PPAs compiling (will take 2-4 hours). Correct version number: 1.1.9.9g |
|
|
|
So is everyone stuck on 107030?
getblockhash 107030 f17997e81295b768dc801e8d3a3ca15f7e14dc3161dfec45c32da25d0876b7b5
Yep... we probably don't have enough mining power until diff level goes down. |
|
|
|
BiblePay - 1.1.9.9d
Mandatory Upgrade
- Remove POG in Prod to prevent external attack vectors
- Fix boost::lexical cast error during syncing
- Transition to POBH POW mining only after block 107,000
- Fix difficulty reading on overview and getmininginfo
** Mac/PPA's compiling by MIP **
MacOS version is also ready PPAs will take 2-4 hours |
|
|
|
In my case, my sancs are still running, but daemon process take 99% of the CPU and don't respond to RPC commands. Edit: If I kill daemon process and restart, I get this in debug.log 2019-03-13 08:03:45 init message: Loading block index...
2019-03-13 08:03:45 Opening LevelDB in /home/ubuntu/.biblepaycore/blocks/index
2019-03-13 08:03:45 Opened LevelDB successfully
2019-03-13 08:03:45 Using obfuscation key for /home/ubuntu/.biblepaycore/blocks/index: 0000000000000000
2019-03-13 08:03:45 Opening LevelDB in /home/ubuntu/.biblepaycore/chainstate
2019-03-13 08:03:45 Opened LevelDB successfully
2019-03-13 08:03:45 Using obfuscation key for /home/ubuntu/.biblepaycore/chainstate: 1eb34d7f65bff2b2
2019-03-13 08:03:45 LoadBlockIndexGuts 1552464225.000000 Last Checkpoint Height 63000 block 10000.000000 @ 1552464226.000000 1552464226059.000000 block 20000.000000 @ 1552464226.000000 1552464226801.000000 block 30000.000000 @ 1552464228.000000 1552464228100.000000 block 40000.000000 @ 1552464229.000000 1552464229914.000000 block 50000.000000 @ 1552464232.000000 1552464232195.000000 block 60000.000000 @ 1552464235.000000 1552464235061.000000 block 70000.000000 @ 1552464238.000000 1552464238651.000000 block 80000.000000 @ 1552464242.000000 1552464242992.000000 block 90000.000000 @ 1552464247.000000 1552464247160.000000 block 100000.000000 @ 1552464252.000000 1552464252359.000000 block 110000.000000 @ 1552464258.000000 1552464258150.000000 Finished 1552464258.000000 LoadBlockIndexDB: last block file = 6
2019-03-13 08:04:18 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=14128, size=104215345, heights=93253...106877, time=2019-01-04...2019-03-13)
2019-03-13 08:04:18 Checking all blk files are present...
2019-03-13 08:04:18 LoadBlockIndexDB: transaction index enabled
2019-03-13 08:04:18 LoadBlockIndexDB: address index disabled
2019-03-13 08:04:18 LoadBlockIndexDB: timestamp index disabled
2019-03-13 08:04:18 LoadBlockIndexDB: spent index disabled
2019-03-13 08:04:18 Finished Loading Block Index 1552464258.000000 LoadBlockIndexDB: hashBestChain=1765036da402f00ac8d6bdce3d1a1493284d5fec9c7a8f9ac63179459019bc2e height=106733 date=2019-03-12 12:08:54 progress=0.998181
2019-03-13 08:04:18 init message: Verifying blocks...
2019-03-13 08:04:18 Verifying last 288 blocks at level 3
2019-03-13 08:04:20 No coin database inconsistencies in last 289 blocks (4518 transactions)
2019-03-13 08:04:20 block index 34361ms
2019-03-13 08:04:20 init message: Loading wallet...
2019-03-13 08:04:20 nKeysLeftSinceAutoBackup: 1001
2019-03-13 08:04:20 nFileVersion = 1010905
2019-03-13 08:04:20 Keys: 1016 plaintext, 0 encrypted, 1016 w/ metadata, 1016 total
2019-03-13 08:04:20 wallet 63ms
2019-03-13 08:04:20 init message: Activating best chain...
2019-03-13 08:04:20 [CPID], [VERIFYCPIDSIGNATURE]: End To End CPID Verification Failed, Address does not match advertised public key for CPID 98ae76096c897e844bbfd0f2b4aa207c, Advertised Addr , Addr B82SF1Mhsh1VHtMn1J6p3STwgNYSmJmV5D (elapsed 1552464260.000000)UpdateTip: new best=5f506d71920f0769803df5d2da6ac5d37d43a6ed74a2b12a7ea4ef1c4e8c5ed0 height=106734 log2_work=59.187758 tx=905790 date=2019-03-12 12:13:05 progress=0.998187 cache=0.2MiB(232tx)
2019-03-13 08:04:21 CheckForkWarningConditions: Warning: Found invalid chain at least ~6 blocks longer than our best chain.
Chain state database corruption likely.
2019-03-13 08:04:21
ERROR: Found invalid chain with higher work (ChainState database corruption likely)
Then it starts shutdown sequence. |
|
|
|
Thanks MIP. How do I check it?
The only way is looking at all the current forks and check which one has more chainwork. This is only possible if you have several wallets and some of them are in a different fork, so if you only have one or you have several wallets in the same chain, the only way to know is asking other users  |
|
|
|
11:51:03

getblockhash 105694
11:51:03

7984e0cfc5db2550eb4be7d3bd98790a2746c9ee804bea5a28f7fa43bd32ace9
Am I on the right fork or not?
You are on the right chain. |
|
|
|
BiblePay
1.1.9.8 - Leisure Upgrade
- Honor the pogbuffer setting preventing auto-tithe from constantly
working (this bug affected auto-tithe and the rpc tithe)
MacOS DMG is ready Ubuntu PPAs are building |
|
|
|
Have anyone meet issue with Sanctuary  The wallet auto stop in Linux 16.04 then i need go start manual by CLI for over week ago. That happen very oftenly "version": 1010805, "protocolversion": 70717, "walletversion": 61000, "wallet_fullversion": "1.1.8.5", Beside, the wallet on fork chain for 2 times per weeks. i tired of go there to check everyday. P/s: i find out that Sanctuary can sync chain and crash wallet... I had a similar issue back some days ago. Please upgrade the wallet to the latest version. Then try to run biblepayd -daemon -reindex If that does not work and keeps on crashing try biblepayd -daemon -zapwallettxes=1 |
|
|
|
BiblePay - 1.1.9.5b
Leisure Upgrade
- When tithing from the rpc 'tithe' command, or from the UI send coins page, choose the youngest coin for the difficulty level
- Add best coin age and amount to 'titheinfo'
- In the rpc tithe and in the UI send coins page tithe action, check the tithe conditions first and cancel the transaction gracefully and notify the user (this prevents the orphaned transactions in the transaction list)
- Add ability to remove swear words from peoples nicknames at the spork level
- Modify GetGithubVersion to compare to the last Mandatory release (preventing false upgrade notifications in prod)
- In the miner, verify the tithe will meet the tithe conditions before tithing, and use the youngest coin
- Add 'exec mypogaudit' rpc report. This report shows the tithes you
made in the last 205 blocks, and the status and corresponding error
code, and the sum of the legal vs illegal tithes and counts. Optionally
you may enter a starting block number (and the report will descend from
that block).
MacOS version and Ubuntu PPAs ready. |
|
|
|
1.1.9.4-BiblePay
Leisure Upgrade
- Ensure the auto-tithe feature sends .01 bbp less than the difficulty
level. To prevent illegal tithes.
- Ensure Pog Pool displays full tithe amount scale (and pogpool rpc command).
MacOS and PPAs versions are also available. |
|
|
|
Masternode questions.
I am getting this every few weeks:
"xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx": "NEW_START_REQUIRED"
Why this happens ?
How to resolve this the quickest way ?
It should not happen, unless you have problems with watchman or your wallet stalls or forks. So there is not a single shortcut to find the causes. To check if you are stalled: see last block in http://explorer.biblepay.org:3001/ and compare with your MN wallet (getinfo) To check if you are in a fork: compare the hash of a recent block in http://explorer.biblepay.org:3001/ with the same block hash in your MN wallet (getblockhash) To check if watchman is working: execute on linux cd ~/.biblepaycore/watchman && ./venv/bin/python bin/watchman.py If it returns empty, you are ok. To check if watchman cron tab is running fine sudo grep "CRON" /var/log/syslog|tail -n 5 and see the timestamp of the last lines is within the last 2 minutes. |
|
|
|
BiblePay - v1.1.9.1
Leisure Upgrade
- Release POG Engine Room (MIP)
Mac and PPA's have been released also.
Sure? Hit:1 http://es.archive.ubuntu.com/ubuntu xenial InRelease
Hit:2 http://es.archive.ubuntu.com/ubuntu xenial-updates InRelease
Hit:3 http://ppa.launchpad.net/biblepay/stable/ubuntu xenial InRelease
Hit:4 http://es.archive.ubuntu.com/ubuntu xenial-backports InRelease
Hit:5 http://ppa.launchpad.net/bitcoin/bitcoin/ubuntu xenial InRelease
Hit:6 http://security.ubuntu.com/ubuntu xenial-security InRelease
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
biblepayd is already the newest version (1.1.8.8-xenial1).
0 upgraded, 0 newly installed, 0 to remove and 174 not upgraded.
There is a new PPA repository? Please check this one https://launchpad.net/~biblepay-official/+archive/ubuntu/mainnet |
|
|
|
Hi
Just looked at my wallet and see a notice that I need to upgrade to version 1.1.9.1 so I go over to download the windows 64-bit version, only to find after I have finished installing I am still using 1.1.8.9.
Has the 64-bit windows version been overlooked ?
Windows wallet takes a long time to compile on gitian scripts process, so there is a good chance that Rob has left the machine crunching and gone to sleep... Meanwhile I will compile for MacOS and Ubuntu PPAs |
|
|
|
BiblePay - Mandatory Upgrade - v1.1.8.9 - before Block 103175 - (February 22nd, 2019)
For entire network (including Sanctuaries and Exchanges)
- Prevent crash in POG Leaderboard when chain not synced (MIP)
- Mandatory height @103175 : Prevent POG illegal tithes, Fix POG pool bug, make POG more exact
- Enhance exec pogaudit, and exec istithelegal
- Allow users to pay prayer_threshhold_amount to send a public prayer
MacOS DMG ready Ubuntu PPAs ready. |
|
|
|
Does anybody know a CPU-Only mined coin that is giving a good profit to mine? I have some servers (CPU only) that are not profitable anymore with POBH (heat mining). Since POG was implemented, I'm only getting 110 bbp per block found.  Any tip is welcome. Thanks! This might change if PoDC is finally retired, as PoBH would take 20% of all mining rewards in that case (this is 1000 BBP per block if I am not mistaken). |
|
|
|
btw is it possible to publish realtime pog pool somewhere on web? i'm not sitting 24/7 on wallet vahtis had a tool - https://viisastentori.fi/bbp_test/checkpool.php - but it seems to be offline for now. It showed min coin age, min coin value, and one other statistic. You could do this yourself too by taking the blockchain data. Its all there. Also, on pool.biblepay.org look under Reports > Difficulty History. You'll see PoG difficulty history. What exactly are you looking for and why would it help you to see something on the web? users with how many tithes and just for info, i wanna check if i tithed something and if i'm in next block etc Tool is under rapid development. You can reach it at https://viisastentori.fi/bbp_test/index.php . This will not be final url. I will try to add info from pogpool command today. Information there is a bit misleading as it is contains also tithes from last reward block. At least it will show number of participants. for this i put comments to https://github.com/biblepay/biblepay/issues/69it would be nice to have stats without previous block I will take a look on this one, thanks for the feedback. |
|
|
|
|
Show Posts
