Topic: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes) - page 94. (Read 243376 times)

Have you ensured the system time and timezone is correct within 10 seconds also?

After doing that - *If* its still not working, try this from the rpc type: addnode 95.216.127.254 onetry

Please post the log if it still does not work.


EDIT: Please confirm the BBP Version is 1.4.4.8+ in the about page?  Pre 1448 will get rejected by the network.

Hello MIP. I'm reaching out this way as this seems to be a re-occurring issue. My BBP client was happy until this last mandatory upgrade. After upgrading, it will not connect to any peers. I have gone as far as completely removing BBP off of my system and deleting the residual files/folders and then re-installing as if I were a new user. Even without my wallet.dat and config file, it will not connect to any peers. I have attempted disabling Windows Defender firewall (Win10) and have also added the two IP addresses in my config file for the nodes you mentioned the last time I had connection issues. Any ideas what to try next? Thank you for you time and consideration on this matter.

Hello ppl. Someone help me, my RPi node has frozen in block 148240 since yesterday (version 1448). Already compiled in another and does not load any blocks. What could be wrong? Thanks for any help.

Please tell him to email me his CPK and his receive address from his official email address and Ill manually enter it.

A user on Twitter outside of the USA is having trouble using the pool faucet:

"pool.biblepay.org has a faucet for which one needs to verify their mobile by providing their carrier information,
but what about people not based in usa, i have a carrier not available in the options could i get some help!?"
https://twitter.com/hellboi697/status/1178536740551675904

*** Christian Spaces / DSQL Thread ***

https://bitcointalksearch.org/topic/new-feature-launch-biblepay-christian-spaces-dsql-decentralized-sql-5188626

SX is open again for deposits.  There was a technical issue that needed worked out.

Thanks!, That's what I thought but I wanted to confirm it.

They are upgrading now; they took it down to move to 1.4.4.8.

BBP offline in Southxchange..., Any info about that?

*** HOW To:  Cameroon One additional Payment option directly from the core wallet ***


We already have about 12 children being sponsored in POOM.

Now you can pay in BBP using a dedicated command!

From the rpc type:

exec paycameroon childid USD_AMOUNT test
(Note: To find your childid, type listchildren).

Specify the amount in USD, for example:
exec paycameroon 123aaa 40 test

The console will show you the amount in BBP (at the midpoint of our current market rate) that will be sent to Cameroon.
If you authorize it, re-execute the command with "authorize" at the end:
exec paycameroon 123aaa 40 authorize

Cameroon will be able to run a report that shows the TXID and the ChildID and amount - this way it will be easy for them to match up the childid-payments for BBP.

1.4.4.8-Mandatory Upgrade for Entire Network Please upgrade before block 148,000


https://github.com/biblepay/biblepay-evolution/releases/tag/1.4.4.8

- Increment Sanc protocol version to enforce upgrade, Enforce protocol version and peer version at block 148000, Enforce 1447 immediately Add network monitor for use by devs to diagnose excessive bandwidth by message type
- Add CheckGSCHealth - this lets the node check its GSC health once every 4 hours - if it fails it calls out for a gobject resync. It also reassesses the chain (IE unwinds any forks) once every 4 hours. You can disable this with 'disablereassesschains=1' in the biblepay.conf. (This is only necessary if you believe your node is down, optional. Type exec gschealth to see the output). Our primary tool is still 'exec health'
under normal circumstances; this shows the health of the GSC system.
- Allow non-standard Sanctuary port numbers (based on outcome of sanctuary vote). This will allow us to create Sancs with nonstandard port numbers, and allow Apollon to use this if approved.
- Added 'exec paycameroon childid amount dry'. This allows you to pay cameroon one for a sponsored child. It automatically converts the USD rate for you and includes the ChildID-CPK-TXID on the cameroon payment information. Once you run it, then re-run it with 'authorize' to complete the transaction. Cameroon will see this payment on their reports.
- Add ddos for non compliant nodes sending strange messages Change syncing timeout for gobjects to 60 seconds Delete old GSC data in the delete thread (once every 5 mins); this removes approx 75% of old orphaned votes and decreases ram usage and gobject file size
- Add dedicated RPC command for readverse: readverse book_name chapter language verse_number.
- Ensure 'exec readverse' defaults to English. (We plan on honoring the wallet language setting in the future).
- Add dedicated RPC command for 'sins'. This shows the 39 mortal sins that could send a person to Hell.
- Added dedicated RPC command: versionreport: Shows the software version running on the network by users ranked by percentage (over the last 205 blocks).
- Added dedicated RPC command for 'bookname short_book_name' (Shows the long name corresponding to the book abbreviation).
- Added dedicated RPC command for 'books' (Shows the books of the bible).
- Create dedicated command for 'datalist'. Type 'datalist objtype' for the list (IE datalist prayer 7) to receive the last 7 days of prayers.
Added 'leaderboard (nickname || all) height'. This allows a user to see the exact reward breakdown per superblock height. It also allows anyone else to audit a breakdown per nickname.
- Add Chinese Language Translations for BiblePay QT Bible Reader (Allows the user to read the CNV from the Read Bible Menu) Enhance 'exec readverse' to support both Chinese and English Fix OneClickMining initial crlf issue (Meaning that biblepay.conf will not be corrupted if user starts with one-click-mining config).
- Add Payment Option 4 for Cameroon-One, and fix BIO URL Apollon Integration for Deterministic Sancs: Add 'exec blscommand mnppriv blsprivkey'. This allows the user to set the deterministic masternodeblsprivkey in the sanc biblepay.conf file. NOTE: The
EncryptAES256 and DecryptAES256 were added to support this feature (this is so no other node can discover your mnprivkey or your mnblsprivkey during transmission or initialization).
- Update Health feature for Sanctuaries only: Set healthupdate=1 to enable, healthupdate=0 to disable, default is Enabled on Sanctuaries only. If this is enabled, you will see your Sanctuaries health status (IE Best Block Hash, GSC voting level) in the pool. This will be valuable when we host with Apollon.
- Fix governance.dat bloated file size, on boot. Reindex governance.dat on boot if > 35 megs.

Note: Although most users will see an improvement in RAM and network usage in 1448, the full impact for gobject propagation will appear at block 148,000. At this height, this version will become mandatory and all old nodes will drop off, thereby creating an environment that only shares the official gobjects (increasing qos). Theoretically our network utilization should drop by 70% after this height as nodes will not continually ask for objects repeatedly.


** All binaries have been deployed **

BiblePay Pool listed on miningpoolstats:

https://miningpoolstats.stream/biblepay

If anyone wants to set up a Sanc in MainNet (Prod) on a non-standard port, it's OK to do so now, since we pushed this feature in the new mandatory and the vote has won.

To do this:
On the Sanctuary, pick a nonstandard port # (IE like 10000).
Set "port=10000" (or your chosen #) in the biblepay.conf.
On the controller, change the ":40000" in the masternode.conf file to the correct port # chosen above.
Everything else should work as previously described.

I love the names and allusions "BiblePay", "Proof of BibleHash", "Proof of Giving", "BiblePay Evolution". Way funnier than Doge and for a good purpose. So you have my blessing

MacOS and linux binaries are ready.

** Orphan Letters - Outbound **

Help:  We have 7 letters written in the pool and they have no votes, please vote.

Everyone, I'd like to announce my intended release schedule and expectation of real world usefulness for Christian Spaces and give an overview of what we are trying to accomplish:

First, you can get acclimated with what Christian Spaces is here:
https://wiki.biblepay.org/Christian_Spaces_Functional_Design

Next, you can start by listening to some of the technical explainer videos at the bottom of the wiki (there are over 10).

Feel free to ask any questions about what the idea is, or why we are doing this, etc.

So first I plan on creating a "New Feature" thread in bitcointalk for Christian Spaces (and its constituent features like DSQL).  What I'd like to accomplish is turning it into a testnet thread, bringing seasoned users and devs into the discussion, running 5-10 nodes of BMS, using it from a user perspective, refining it to become something useful (for approximately 3-4 months - then probably for 5 years as we need to add more to it).  Then I plan on enabling some of the useful features *by* the end of the year in prod Biblepay.  As I feel a few are valuable now, and can be enabled towards November/December.

Some of the enhancements I really want to release for BiblePay before the end of the year include these features:
- A decentralized prayer blog.  The idea here, is to have a full page to be able to type a longer prayer, and then when you post it, it appears in blog format sorted by votes ascending.  This will allow us to pray more effectively as a group, if we can see important prayers get upvoted, and also, more personal prayers (for example if someone has a relative in need etc).  The 'novelty' of the feature however will be that we store the blog as a table in our decentralized sql server across many nodes (DSQL), and serve the blog from our BWS (BiblePay decentralized Web server).
- An accounting system.  Id like to see a page for debits/credits per user CPK, so we can see the DSQL balance, and see accounting entries affecting the user.
- Our gospel links table, ported to be decentralized with voting.  This will allow people to post new Gospel Links and let these get upvoted/downvoted etc.
- All of our DR (disaster recovery) tables be ported to DSQL and be browsable.
- Ability for the core wallet to sign transactions and browse the decentralized web.  This basically means easy to use interface for the user, who just wants to see a prayer blog and vote on a prayer, etc.  Without knowing anything technical.
- The Christian Treasure Trove (IE saving data at risk of being scrubbed on the web that should be available/valuable for all humans).
- Ability to host an HTML5 site in a decentralized way, from BBP.
- BBP Leasing/freshening of documents.
- A true GDPR/RIAA/Inappropriate takedown request process.

We have most of this solution (with the above features) very close to being ready for testnet (its very close to checking in, and compiling for use by testers). 
I believe we can start testing by October 1st.

That looks pretty awesome!  If I think of anything else I will post.

DSQL is too big of an animal to add to it at this moment, but I'm starting to work on the info for Bitcointalk now and I suppose we can handle that separately.

"BiblePay — Updates for 2019: July, August and September"
https://medium.com/biblepay-news/biblepay-updates-for-2019-july-august-and-september-dfe3ac5abeab

Please let me know if anything is missing or incorrect, all feedback welcome!