BiblePay (BBP) | 10% Charity | POW/POS | CPU Only | Masternode | No Premine

[togoshigekata]

WEBSITE | GITHUB | TEAM | ROADMAP | WHITE PAPER (Being Updated)

FORUM | TWITTER | REDDIT | DISCORD | FACEBOOK | TELEGRAM

Language Translations



Proof Of Biblehash (POBH) rewards full node participation, while preventing GPUs and ASICs by requiring full blockchain transaction referencing in the hashing function using chained bible verses

Proof Of Distributed Computing (PODC) allows blockchain energy to be used productively, for humanitarian science research, to help cure cancer and fight AIDS and malaria

Launched July 23rd 2017 by Rob Andrews, with no premine and no ICO, BiblePay describes itself as a decentralized autonomous cryptocurrency that gives 10% to orphan-charity (using Masternode (Sanctuary) governance). The project is passionate about spreading the gospel of Jesus, having the entire KJV bible compiled in its hashing algorithm (POBH). BiblePay (BBP) is deflationary, decreasing its emissions by 19.5% per year.

The project views itself as a utility that provides an alternative method for giving to charity. With Generic Smart Contracts, the project seeks to become the go-to wallet for Christians. In the future, the team intends to lease file space on its Masternodes and release corporate integration features, such as C# access to the blockchain. The BiblePay platform is a derivative of Dash-Evolution. Located in Dallas, TX, the team seeks to help orphans globally. The roadmap can be viewed at: wiki.biblepay.org/Roadmap

Interview | Podcast | Youtube | Medium | Steemit | Newsletter




Accomplishments:

- $200,000+ donated across four Charities!

- Sponsoring 100+ Orphans every month!

- 30,000+ years CPU time donated to Cancer and Disease Research!

Overview: Rob's Resignation from Gridcoin       Nutrition Information Dimensions BiblePay Evolution Dash Coin

New Features: Generic Smart Contracts (GSC) Proof of Orphan Mining (POOM) Christian Spaces Proof of Distributed Computing (PODC) Dynamic Whale Staking (DWS) DashPay Gift Cards

Utility:

DashPay - Instantly Buy Gift Cards with BiblePay (using Dash, InstantSend and Bitrefill)
wiki.biblepay.org/DashPay_RPC




Download Wallet:

biblepay.org/wallet

(How to update and clean wallet?)

=

   

(How to verify Hash)

Windows 32 bit - biblepay.org/biblepayevo32.exe (Hash)
Windows 64 bit - biblepay.org/biblepayevo64.exe (Hash)

=

Mac OSX - biblepay.org/biblepaycore-evo.dmg

=

Linux GUI 32 bit - biblepay-qt-evo-i686-pc-linux-gnu.tar.gz (Hash)
Linux GUI 64 bit - biblepay-qt-evo-x86_64-pc-linux-gnu.tar.gz  (Hash)

Linux CLI 32 bit - biblepayd-evo-i686-pc-linux-gnu.tar.gz  (Hash)
Linux CLI 64 bit - biblepayd-evo-x86_64-pc-linux-gnu.tar.gz  (Hash)

Linux ARM 64 bit - biblepayd-evo-arm-linux-gnueabihf.tar.gz  (Hash)
Linux Arch 64 bit - biblepayd-evo-aarch64-linux-gnu.tar.gz  (Hash)

=

Source Code - github.com/biblepay/biblepay-evolution/blob/master/BuildBiblePay.txt

=

Paper - biblepaywallet.github.io

=

Mobile Wallet:

   

Android - play.google.com/store/apps/details?id=com.biblepaywallet

iOS - apps.apple.com/us/app/biblepay-wallet/id1467714837


Mining Guides:

Proof of Distributed Computing
wiki.biblepay.org/PODC_Setup

RandomX (XMR + BBP)
wiki.biblepay.org/Upgrade_to_RandomX

Pools:

• foundation.biblepay.org
  

MiningPoolStats
miningpoolstats.stream/biblepay


Earn Coins:

FreeFaucet.io:
freefaucet.io/claim/index.php?coin_name=biblepay&faucet_key=freefaucet18&claim=Claim

SouthXchange Faucet:
southxchange.com/Balance/Faucet

Graviex Faucet:
graviex.net/faucets/list

=

Proof of Orphan Mining (POOM):
wiki.biblepay.org/Paying_For_a_POOM_Sponsored_Child

Healing Campaign (Diary Entries):
wiki.biblepay.org/BiblePay_Healing_Campaign

=

Dynamic Whale Staking (DWS):
wiki.biblepay.org/DWS_Setup

Masternode (Sanctuary):
biblepay.org/masternode

=

Bug Bounty Program:
forum.biblepay.org/index.php?topic=408.0

Monthly Budget Proposal System
forum.biblepay.org/index.php?board=5.0


Exchanges:

coinmarketcap.com/currencies/biblepay/markets/

coingecko.com/en/coins/biblepay/trading_exchanges#panel

• SouthXChange
• Tokok
• Graviex

Explorers:

• Chainz Explorer
• explorer.biblepay.org

Specifications:

Launched: July 23, 2017
Algorithm: Proof of BibleHash (POBH)
Mining Strategy: CPU only (GPU/ASIC Resistant)

No Premine / No ICO

Block Target: 7 Minutes
Blocks Per Day: 205
Transaction Speed: Supports InstantSend

Max Supply: 5.2 billion BBP by year 2050

Circulation Characteristic: Deflationary
Emission Rate: -1.5% every month (19% per year compounded deflation)

Emission Schedule:
wiki.biblepay.org/Emission_Schedule

Economics:
wiki.biblepay.org/Economics
wiki.biblepay.org/Economic_Changes_Dec_2019


Block Reward:

  – 20.0% Monthly Budget

        – 10.0% Exchange (Fund Payoff)
        –   5.0% IT (Software Development)
        –   5.0% MISC (Miscellaneous)

  – 38.0% GSC (Generic Smart Contracts)

        – 60.0% PODC (Science Research)
        – 35.0% POOM (Charity)
        –   5.0% Healing (Prayer Diary)

  –  7.0% RandomX (Heat Mining)

  – 35.0% Masternode (Sanctuary)


Masternodes (Sanctuaries):

Governance & Budget System: - Understanding Governance                                                                    Collateral Requirement: 4,500,001 BBP	Statistics: - Masternodes.Online - Masternodes.Pro - MasterNodeCap - Masternode.Live - Masternodes Buzz
Setup: - Step by Step Guide - One Click Install Script - Upgrade Deterministic ____________________________	Monitoring: - NodeCheck.io

Charity:
**  We only partner with charities over 75% efficient, meaning over 75% reach the end-user. **

 



Accountability:
- accountability.biblepay.org
- Public Investigation


Social:

Forum      - forum.biblepay.org
Twitter     - twitter.com/BiblePay
Reddit      - reddit.com/r/BiblePay
Discord    - discordapp.com/invite/yWgbKdM
Facebook  - facebook.com/BiblePay
Telegram  - t.me/biblepay_airdrop

       


CAUTION: "Although BiblePay has a deflationary emission schedule, there is no guarantee of positive investment returns against other major inflating currencies. Past returns are not indicative of future results. We are a utility and not a security. Please do not invest in BiblePay unless you know all of the risks of cryptocurrencies"


Original Announcement

2nd Announcement






Forum Rules:

1. Do not make assumptions or false statements - For example, if you are not 100% sure of a statement being fact, you must state "in my opinion... " or "I believe...", especially with technical posts that could mislead investors.  

2. Talk in a nice tone and manner, be polite and appreciative.  Avoid swearing.

3. Be willing to do work/research/experience, or Find someone who can, and assume other community members are busy.  This is a group effort.

4. Moderators may delete your post if you are argumentative or make mean spirited posts.

5. If you have a problem with the mod team or an official member of the dev team, you must post with an innocent until proven guilty attitude.  The devs aren't out to get you. If you do not receive a response, break the problem up into a simpler problem and post the question again with a positive attitude.

6.  Your primary purpose on this forum is to help others and make constructive posts.  If you are a net negative to the community we reserve the right to delete or report the posts to bitcointalk mods.

7.  Do not post anything that misleads investors.  Proofread your post before posting as it cannot be deleted for 24 hours.  If you are not sure, ask someone else first.

8.  Your posts may be deleted or you may be banned from this thread if you have a history of making offensive posts.

9.  After 3 offensive posts your future posts and/or your account may be banned at the sole discretion of one of our forum administrators.

[1715302258]

1715302258

[1715302258]

1715302258

[enginsev]

https://bitcointalk.org/index.php?topic=2388064.0

Why is the new thread opened?

[togoshigekata]

https://bitcointalk.org/index.php?topic=2388064.0

Why is the new thread opened?

Rob, Creator and Lead Developer controls the Original and 2nd ANN threads,

There have been issues with his moderation (and lack of moderation), but in particular his use of post deletions (censorship)

Im willing to put in the time to moderate and to figure out and set clear rules (with the help of the community)

I offer an alternative place for the community to talk out of reach of Rob's control

[togoshigekata]

Shoutouts:

Masternode Buzz: https://masternode.buzz/

Omni Analytics: https://crypto.omnianalytics.io/

VoskCoin: https://bitcointalk.org/index.php?topic=2683343.0

CPU Miners Club: https://discordapp.com/invite/cc4jCB6

[inblue]

** Warning:  Not official **

This is not our official forum.  Post at your own risk.

This user has gone rogue, and is doing this out of spite.

There is no "official" in a decentralized project. And Togo is one of BiblePay's most loyal users.

Rob, don't spread FUD that it's "risky" to use this thread, when he posted all information correctly, all links go where they should, I checked. It's actually more "risky" to use your thread where you don't update it for months and a new user could go to an old link, see old information and generally get dizzy from the jumbled mess the post is.

[bible_pay]

** Warning:  Not official **

This is not our official forum.  Post at your own risk.

This user has gone rogue, and is doing this out of spite.

** Warning:  User bible_pay gone rogue **

Butt hurt much?

There is no "official" in a decentralized project. And Togo is one of BiblePay's most loyal users.

Rob, don't spread FUD that it's "risky" to use this thread, when he posted all information correctly, all links go where they should, I checked. It's actually more "risky" to use your thread where you don't update it for months and a new user could go to an old link, see old information and generally get dizzy from the jumbled mess the post is.

Incorrect again Inblue, there always is an official thread on an organized project - and this isnt it.

You dont deserve a reply for the rest of the whiny comment - Ill go high while you stay low.

[sunk818]

** Warning:  Not official **

This is not our official forum.  Post at your own risk.

This user has gone rogue, and is doing this out of spite.

What happened to "I Love You Togo." ?



https://forum.biblepay.org/index.php?topic=273.msg4571#msg4571

[baoervsdier]

The www.qiex.com is fraud project! Website can't open! There is also my cryptocurrency inside!

[sogirl]

The www.qiex.com is fraud project! Website can't open! There is also my cryptocurrency inside!

I just asked QIEX customer service and said that they will open tomorrow.

[togoshigekata]

I created a 3rd ANN thread: https://bitcointalk.org/index.php?topic=5067231.0

Again a self-moderated thread? Even though your intentions are now good, nobody can know what could happen in the future, who will disagree with whom, who will be on which side etc.

The only way a thread is valid if it's not a self-moderated one. That way it doesn't matter who started it because they cannot censor the posts. The only posts which do need to be deleted are straight-up profanity, hard insults etc. And for that we already have the moderators of this forum, so there is not a single reason to have a self-moderated thread, unless the OP is scared of somebody sharing thoughts which don't align with their views.

The original ANN thread was Unmoderated, but sadly it had to be locked because of the spammers/trolls

There are Bitcointalk forum admins, but they have limited time/interest
and they have their own opinions/biases (their own rules basically say they can do what they want haha)

The Unmoderated thread got kind of crazy, and I believe most of it was not against the forum rules

I think there is a need for a Moderated thread, but who should be the Moderator? I dont know,
it would be great if it could be a community system vs a dictatorship

I offer an alternative to Robs thread since there currently is no alternative,
I also offer an alternative design

I doubt my thread will get used, Im not pushing for it, just opening it as an option

Rob has shown to be slow to update the ANN,
and for months he purposefully left out critical keywords from the title

Rob is a busy man, he has other priorities and work he is doing,
I believe we need more people to step up and do things

But anyways, I would support trying out a non-moderated thread again

If we stay self moderated though, I believe we need to discuss and make clear our forum rules

[togoshigekata]

I offer BiblePay users a 2nd Forum Option, Discourse:
https://discourse.biblepaycoin.org/

Understanding Discourse Trust Levels
https://blog.discourse.org/2018/06/understanding-discourse-trust-levels/

NOTE: Currently Ive set Trust Level "Member" the ability to post anonymously*

I have also setup the ability to login using Google, Facebook, Twitter and Github,
so users do not have to create another account, they can use one they already have!

=

Installation was pretty smooth, they use a docker image, can host it on a cheap cloud server $5/month
https://github.com/discourse/discourse/blob/master/docs/INSTALL-cloud.md

[bible_pay]

** Warning:  Not official **

This is not our official forum.  Post at your own risk.

This user has gone rogue, and is doing this out of spite.

What happened to "I Love You Togo." ?



https://forum.biblepay.org/index.php?topic=273.msg4571#msg4571

Love is possible in parallel, and replies for things done to me out of spite stir up new drama that requires yet more work for Christian brotherhood and the Holy Spirit to be grieved all over again.

But I wouldnt expect a less mean spirit post from you Sun.  You have a 90% track record of it, and although you have apologized and made up with me, you continue to antagonize and attempt to bring out the worst.  Maybe you came to BiblePay because you were seeking a friend, I'm not sure.

[bible_pay]

https://bitcointalk.org/index.php?topic=2388064.0

Why is the new thread opened?

Rob, Creator and Lead Developer controls the Original and 2nd ANN threads,

There have been issues with his moderation (and lack of moderation), but in particular his use of post deletions (censorship)

Im willing to put in the time to moderate and to figure out and set clear rules (with the help of the community)

I offer an alternative place for the community to talk out of reach of Rob's control

Incorrect Togo - you misunderstand the reason I deleted the posts I deleted.

When a degenerate posts something violating the community rules that is MODERATION.

Censorship is when the moderator deliberately tries to oppress the community by deleting posts that contain material information.

I only deleted posts that either derided, hurt investors, or tried to expose private information.  People mixed those things into some posts and on bitcointalk you only have one button - delete - so therefore it was misconstrued I was trying to hide the main thing they posted about which is not the case.

If people would break the post down or PM me they would have known.

To this day, the same policy exists and people are getting their points across on our main forum without censorship and we have more people filled with the Holy Spirit now than ever.

[coinsinspect]

Hi Togo,
I am here in this project because of your PR activity.
Glad you are with us and happy to see the dedication.

Keep your useful posts here, in the official thread and everywhere.

Good men, with so much dedication, are hard to find.

God bless you

[coinsinspect]

I will try to update important info here.

Please add here short and important quotes.

[coinsinspect]

BiblePay
1.4.4.3-Leisure Upgrade

- Enhance ABN/GSC tx creator to sort by coin-age first, then create the
tx (IE use lowest coin age possible).

[coinsinspect]

*** BIBLEPAY QUICK START GUIDE ***

Use this guide to get started with biblepay!   (Similar to unpacking a new lawnmower):

https://wiki.biblepay.org/Quick_Start

- I see we picked up a few new users over the last 24 hours!  We are now on our way towards the top 500!


Congratulations!

[togoshigekata]

Hi Togo,
I am here in this project because of your PR activity.
Glad you are with us and happy to see the dedication.

Keep your useful posts here, in the official thread and everywhere.

Good men, with so much dedication, are hard to find.

God bless you

Thank you for the kind words coinsinspect

[togoshigekata]

June Update:
https://medium.com/biblepay-news/biblepay-2019-june-updates-29d982a6f907

Togo's Open TODO List:
https://bitcointalk.org/index.php?topic=2388064.msg51884202#msg51884202
(Get Paid BBP Coins to help!)

[togoshigekata]

** DETERMINISTIC SANCS / GIN / PROD **


I promised to mention the status of Prod/dip3 and Deterministic sancs upgrade.

So our prod chain has voted in dip3 successfully, and we will soon be able to continue upgrading to deterministic sancs in prod.

But I would like to make one small change to the schedule.

Since it is so late into July, and our superblock is near, lets postpone the deterministic sancs upgrade until August (after our July superblock pays out).

I will modify the schedule now.

https://wiki.biblepay.org/Evolution_Upgrade

** Today's Goal **

- We are currently running 1.4.4.3. 
- We successfully support funded and non funded mining.  I think the ABN endeavor is turning out to be a success, as we are attracting new users, and this environment is satisfying both newbies who do not want to hold bbp and satisfying old-timers who want to provide the ABNs.
- The pool is still running in protocol v1.0.
- Some log spam exists related to ABN/funded mining activing, checkblock errors due to stale blocks from the pool, and some nodes seem to get banned occasionally.

Proposed Solution:
- Release pool mining protocol version 2.0.  This allows funded or non-funded mining in the pool without limitations, and provides more accurate health info.
- Remove log spam.
- Ensure blocks from the pool are not causing log spam issues.  Address any pool checkblockvaliditylite errors.  Ensure miners are not being d-dossed for bad block nBits or blockheaders.

I will notify when the new version is ready.  This is a leisure upgrade.

** Near Term Future **

- Update the roadmap goals for Q3.  Share the BiblePay goals (as related to Christian Spaces/HTML5) with the forum. 
- Make the users aware of a new project we will implement towards the end of the year and how they can help with this project.

BiblePay
1.4.4.4 - Leisure Upgrade

- Remove log spam
- Upgrade BiblePay Pool protocol to v2.0 (Upgrade busywait to mutex, add
two-way comm and handling of reply commands, add pool deadline support,
allow funded & non-funded mining at the same time per user)
- Handle bad nBits in pool mined blocks gracefully (and ddos
gracefully), and remove Pool log spam
- Disconnect nodes who spam us with bad block headers

** Pool Miners: please upgrade within 7 days **

[coinsinspect]

BiblePay
1.4.4.5-Mandatory Upgrade

- Ensure gobjects are propagated through entire network
- Add configurable key : changequantity=n (this allows you to specify
how many change outputs you wish to receive from GSC transmissions,
default is 10)


** Mac/Linux will not be ready for 3~ hours **

** This upgrade is for the entire network:  Users and Sanctuaries
Except:  Exchanges may run in litemode=1 if they wish to wait for the next mandatory **

** It is recommended that you delete banlist.dat **

[coinsinspect]

** UPGRADING YOUR SANCTUARIES TO DETERMINISTIC (DIP3) **


Recently we explained during our Evolution Upgrade guide steps that at height 135,300 we would start upgrading our sancs to deterministic (https://wiki.biblepay.org/Evolution_Upgrade).

The goal is to finish this process by the end of August (before our August superblock emits).  So we have 28 days to perform this.

This will allow us to emit a superblock entirely from dip3 based sancs (and set us in a position for the next step in September).

Here are two resources we can start with containing instructions to upgrade your sanc from legacy to deterministic:
How to upgrade a legacy Sanc to a deterministic Sanc using the BiblePay upgrade tool (built in the core wallet):
https://forum.biblepay.org/index.php?topic=391.msg5968#msg5968

How to create a deterministic sanc from scratch the Dash way:
https://docs.dash.org/en/stable/masternodes/setup.html#option-2-registering-from-dash-core-wallet

Very important info for you to know:
If you use the BiblePay upgradesanc tool, BiblePay will automatically create a file called deterministic.conf in your Data directory (this is where your masternode.conf file is).  We will automatically add a new row to this file every time you upgrade a sanctuary to deterministic.  This file will contain your sanctuary name, ip, port, collateral txid, pro-tx txid, blsprivkey, blspubkey, and all other pertinent tx info on one row.

Note that you should back up this file occasionally, in case you destroy your cold sanctuary (VMSs).  This will allow you to retrieve the masternodeblsprivkey, which is required to recreate a deterministic sanctuary!  So remember, back up your deterministic.conf along with backing up your wallet.dat.  If you create sancs using the Dash method above you will need to manually copy your masternodeblsprivkey over to notepad and create a backup system to back up your notes.

Summarizing the process:

1.  We assume you have a sanctuary named 'biblical1'.    This sanctuary exists in your masternode.conf file.
2.  Type 'exec upgradesanc biblical1 0' into the RPC.  If an error is thrown, post here and we will help.  Otherwise continue to step 3.
3.  Type 'exec upgradesanc biblical1 1' into the RPC.  This results in many lines of output with all the keys etc.
4.  Edit your remote hosted sanctuary biblepay.conf file (your cold sanc VMS's biblepay.conf file).
5.  Add an entry:  masternodeblsprivkey=nnnnnn  (replace the n's with the blsprivkey which is found in the output of the command.  Alternatively you can also get this value from viewing the deterministic.conf file we created in your datadir).
    **** VERY IMPORTANT:  You must ensure your masternodeblsprivkey is correct on the sanctuary itself, otherwise your sanctuary will get POSE banned in the future, and will utterly fail in the next mandatory version (our future branch of biblepay requires the masternodeblsprivkey to allow the sanc to participate in LLMQ quorums.) ****

6.  Reboot the remote sanctuary.  
7.  Verify the sanctuaries masternode status is ENABLED from the controller wallet sanctuary list.
8.  From the sanctuary, type 'masternode status' and verify the status is "Masternode successfully started".

How do I upgrade many sanctuaries at once:

If you own a massive number of sanctuaries, you can run the upgradesanc command on all of them first, then write a program to loop through your deterministic.conf file on the controller wallet, and for each entry, connect to the remote host (by IP found in the data row), edit the remote cold sanc masternode.conf file, adding the masternodeblsprivkey=nnnn entry in the file.  Then rebooting the remote sanc via script.

** Recommendation **

It is recommended that each of us upgrade one today and take a look at the network and verify everything looks fine, then continue with more.


** Step 1 **

I just upgraded my first sanc to deterministic successfully using the upgradesanc method.  

Let's test a few and please provide feedback here if anyone encounters a glitch.  

[coinsinspect]

** BiblePay 3rd Quarter Update **


- I will be temporarily passing my duties as Founder over to MIP for the next 60 days while I go on a programming sabbatical for BiblePay.  This is to help release our next major feature into testnet on time (the deadline is Sept. 30).  I'll be back on the Forum for our Cameroon One go-live and also when MIP is in the mountains.  Please contact MIP for day to day questions.
- We have our Cameroon-One Go-Live in Prod coming up at the end of August.  At this point, testing passed in testnet.  Cameroon-One hired a consultant to implement the BiblePay features.  We have a conference call Thursday to confirm things are on track.  We plan on doing a production test around Aug 15th.  If it passes, we plan on enabling the code at the end of the month.  (At this point, the last mandatory already contained the sanctuary code, so we don't anticipate a required upgrade).   

When Cameroon One goes live (with POOM), any BiblePay CPK will be able to sponsor a personal child at home, and be rewarded in GSC rewards for the child on a daily basis in BBP.  At today's rates, this means if you spend $40 per month in fiat with Cameroon-One, you will receive approx 3000 bbp per day in the GSC contract.

- MIP is working on mobile staking for the next version of BiblePay.
- I'm working on BIPFS (BiblePay IPFS).  I will release the wiki for this within 3 days to give everyone an idea of what this is for.
- Pastor Joshua in Kenya, who cares for 26 children being sponsored by us, is using Mobile BBP wallet to attempt to convert to local Shillings.  He will also be creating a proposal for future funding.
- Bhavani is working on the in-wallet Proposal Funding Level by Expense Type graph.
- Testnet testing for our .14 branch is going extremely well, now that we tested deterministic POSE successfully.  We regression tested our current branch (.13) in .14 successfully (we can mine and create and receive GSC rewards).  We are very close to testing ChainLocks.  Recently we successfully tested LLMQ, and the LLMQs have been resilient (this puts us on par with the very latest Dash releases and features). 
- We will be releasing a quick-sync feature very soon that will allow syncing from zero in a few minutes.

- One of the upcoming features coming up in our next BiblePay Sanctuary Release is called BMS (BiblePay middleware system).  The BMS allows the sanctuary to perform certain functions in a decentralized way.  One of the features being exposed to the users is the Christian Treasure Trove.  I want to take a minute to explain this to give the users a little homework in anticipation of the release.

I've received different confirmations from my various travels that some IT companies are starting to censor Christianity related content.  Some say results on search engines are being manipulated to give priority to a one world religion.  In my personal experience I noticed for example rapture videos that were uploaded recently are sometimes required to be 5 days old before I can see them - not to dwell on this, but let me make the assertion that there is a rising concern that Christian related content is being scrubbed from the web. 

This plus for example, I have seen certain documents available in search about certain theories about Popes, and the Vatican that were easily searchable at points in time and now appear to be lost (IE it is getting harder to find Vatican secret files and Pope related materials). 

So, the idea behind the Christian Treasure Trove is to have the Sanctuaries host critical Christian information, and this must be high caliber important information - forever.  Once uploaded into BIPFS, the info will be available as part of our exposed web presence (its a FQDN subdomain of biblepay.org with SEO) with our coming decentralized reverse DNS.

The way this affects You, our valuable User:
We would like you to download and keep any critical Christian information in a folder that you believe should be saved and available during the great tribulation, or during a time of scarcity of the Word of God.  It could be a testimony, a rapture dream, an end-times testimony (think things that are in BiblePay Pool external links), edifying things and/or things you believe are valuable.  And especially, documents that carry on the Word of God that could be sanitized from the internet. 

We will have a voting system where non-essential content gets voted down and eventually purged as good content gets voted up and automatically kept.  The future version will eventually estimate file sizes and fees associated with this, (and I understand the TT will be different than normal content so fees may not apply etc), but we will have a plan in place to ensure the Treasure Trove doesn't get overfilled with junk that can't be hosted without larger hard drives, etc.

So please remember to start looking for valuable Christian info that will keep the Word of God alive so you can share it.

[togoshigekata]

Mobile Wallet Updates (Android & iOS)

- Redeem paper wallet private keys using https://chainz.cryptoid.info/bbp/ UTXO explorer
- Update SPV protocol version numbers.

This latest update should fix the syncing issues users had in iOS lately.

Both versions are now available in Google Play/App Store.

Android - https://play.google.com/store/apps/details?id=com.biblepaywallet

iOS - https://apps.apple.com/us/app/biblepay-wallet/id1467714837

[coinsinspect]

** Cameroon Integration Testing this week **

Note:  Cameroon one is planning on releasing the code on their end to prod this week so we can go live soon with POOM.

POOM means you can sponsor an orphan at home personally with Cameroon using fiat or BBP for the monthly expense, referencing the BiblePay Orphan ID (in POOM).
This will then lock your orphan in providing you with rewards from the GSC Cameroon-One campaign (in BBP!)

Note:  I will need to set up a temporary campaign in Prod for integration testing only this week.  I will be setting up a very small version of Cameroon-One (with 1% of the normal rewards).  This is just to ensure things are working properly.  Please realize the rewards I receive for this test are actually based on real orphans that I sponsored with real money over 30 days ago (with Anna in Global Giving).

Starting later this month when we switch to the real Cameroon One campaign, we will start over with the voted in budget (50% of the GSC budget).

Wow, that sounds awesome! Will the FIAT sponsoring system be available worldwide or will there be any restrictions on countries/credit card companies etc.?
Also, will the orphan expenses get an anually "donation receipt" or something like that to declare at the tax office?

On the Fiat question "Will the FIAT sponsoring system be available worldwide or will there be any restrictions on countries/credit card companies etc.?
Also, will the orphan expenses get an anually "donation receipt" or something like that to declare at the tax office?":

1.  Yes, the donations can be made worldwide, with a couple restrictions.  A paper check can be mailed to Cameroon from anywhere as long as they can cash it (and it should have the POOM ID on the check or on the notes).  They also accept debit and credit cards from Global Giving.  They also accept Intl Paypal.  Meaning the payment can be made with a credit card internationally (or with paypal balances).  They believe for some reason paypal does not work in China though but it definitely works in Europe.

2.  The donation is tax deductible, and you will receive a receipt from Cameroon for your own personal taxes.

3.  They have something called "match" where a rich donor at global giving will match your donation, but I have been informed it wont work with POOM rewards, but, it will give you a free month of credit at Cameroon for the sake of the child - if you decide to want this Ill post more info on global givings match when we go live.  Global Giving accepts credit cards also.

4.  Cameroon recommends Paypal for setting up child payments, we have that info compiled in the wallet btw.  When you type 'sponsorchild' it will come up when you decide to sponsor one.

5.  So another benefit in POOM integration is it gives Fiat buyers an additional tax-deductible way to invest in BBP without going through an exchange; and it also decreases our monthly net sales pressure from coin emissions (as less rewards will be sold on the exchange for electricity/mining and instead be repaid for orphan expenses).  Its also good in the sense that it increases our real world utility.

[togoshigekata]

Apollon Network

 confirmed me that BBP is finally enabled in their MN hosting platform.

Website:
https://www.apollon.network/

Training Videos:
https://www.apollon.network/category/training-videos/

Who are Apollon Network?:
https://www.apollon.network/apollon-network-about-us/

[coinsinspect]

BiblePay
1.4.4.6 - Leisure Upgrade


- Fix reindex process (MIP)
- Show correct maturity icon for superblock transactions in transaction
list UI in QT
- Add exec register (this is to be explained in a future release) - for
BMS
- Add BIO URL for Cameroon One in listchildren
- Move 'sendgscc' to a dedicated RPC command.
Add ability to send a single GSC transmission (sendgscc campaign_name
donation_amt) - this sends a specific GSC transmission.
Add ability to send a customized foundation donation amount for POG
(sendgscc POG donation_amount).
- Modify BiblePay miner to only send an automatic tithe if it is
conceptually profitable.  (The GSC creator will check the ROI, and only
send the automatic tithe if the ROI > 0.01).  Note: You may still
forcefully send a tithe regardless of profitability with sendgscc.
- Fix bug in PDS where BiblePay will forget a PDS value after one year
(increased PDS storage duration to 7 years).

** This is our Windows release **
** MIP will notify when Linux/MAC is ready **

Footnotes:

1.  If you belong to multiple campaigns, now when you send a Healing diary entry from the UI from sendcoinsentry, POG will not be sent as a second transaction (only Healing will be sent).
2.  If you would like to manually send a POG transaction (with a tithe) for a specific tithe amount, you can now do this: 'sendgscc pog tithe_amount'.  The wallet will only send one transaction for the amount specified (therefore you don't need to change any keys).
3.  The wallet will no longer automatically tithe unless it believes it will be profitable.
4.  PDS means Persisted Data Cache.  This just means BiblePay will not forget your CPK nickname or prayers for 7 years (or other PDS settings).
5.  Press ctrl-f5 to refresh the biblepay.org web page before downloading.  If you ever receive the old version (1.4.4.5<) please clear your browser cache.

[togoshigekata]

*** Cameroon-One Go-Live ***


We are proud to announce our partnership with Cameroon-One and POOM (Proof of Orphan Mining) and this program will go live on September 5th, 2019.

In POOM you may sponsor a personal child directly with Cameroon-One (and this is a tax deductible contribution), and this personal sponsorship will reward you "points" daily in our GSC campaign for Cameroon-One, currently at a rate of 100%!

This means that you will receive $1.33 back per day in BBP rewards for sponsoring one child (at a rate of $40.00 per month currently).

Steps to sponsor a child:


1.  First ensure you already have a CPK (Christian public key).  If you do not have a CPK, type 'exec cpk your_desired_nickname' first.

2.  Type 'exec join cameroon-one' to join the campaign.

3.  From the core BBP wallet, type 'sponsorchild'.  After reading the warning, that BBP will charge a 50,000 BBP fee (this goes to our orphan sponsorship fund), then type 'sponsorchild authorize'.  (The 50K fee is a deterrent to keep people from sponsoring children they do not intend to pay for).

4.  You will receive a 6 character child ID.  Follow the instructions on the screen to know how to pay the monthly sponsorship fee (PayPal, Check, GlobalGiving Credit Card, or in BBP).  If you want to pay in BBP, you can send the BBP to Cameroons wallet at: BHRiFZYUpHj2r3gxw7pHyvByTUk1dGb8vz then e-mail Todd at: todd.justin@cameroonone.org with the child ID.  In our next release we will add this payment option to the wallet.

5.  To see the status of your child, type :  'listchildren'.  Please be patient, it can take up to 7 days for Cameroon to find a child for you.  In the mean time you can send a payment and pre pay for as many months as you desire (just remember to include the BBP Child-ID# with your payment).  While Cameroon is looking for a child, the wallet will say "Not Provisioned".  Once they find you a child, the balance will change to 0.  Once your payment is accepted by Cameroon, your balance will become a credit balance.  You will also receive a personal Bio URL for your child (it will appear in the listchildren output).

We currently cap our Cameroon-One emissions at the number of children sponsored * 1.33 per day (in USD).  You may sponsor more than one child.

! IMPORTANT !  It is extremely important that you either leave your miner running on one thread each day, or alternatively, type 'sendgscc cameroon-one' once per day.  This is necessary so that you are counted as a daily POOM participant.  If you miss a day you will miss out on the $1.33 reward for that day only.


Footnotes:

a.  Our POG campaign rewards have been reduced to 47.5% to make way for POOM rewards.  POOM rewards are currently 47.5% of the daily GSC budget.  The remaining 5% is still unchanged for Healing.

CameroonOne:
https://www.cameroonone.org/

Proof of Orphan Mining:
https://wiki.biblepay.org/POOM

Blog Post by Sunk818
https://whitewalr.us/2019/696.html

[coinsinspect]

** APOLLON Turnkey Sanctuary Hosting **


I have tested Apollon successfully and they work great!

To have your sanctuary hosted for only 99 cents per month (including hosting fees), navigate to:
https://www.apollon.network/

Click '+'.  Choose BiblePay.  Choose "Apollon Hosted Node".

[togoshigekata]

Any updates on Tokok?

They reached out to me last night, that they received the airdrop funds (1.35MM), and we decided to potentially go live on 9/17.

They still have to confirm this, the ticker pairs, the airdrop info, etc.  I will post go-live info as soon as I hear further confirmation back.

=

*** Orphan Partnership Update ***

I've been working with Pastor Joshua in Kenya at HFOC (Hope for Orphan Center) for 90 days.  Although we have gotten to the point close to compliance - where our partner creates a PDF package, bios, liquidates BBP->BTC, accepts letters, etc., unfortunately some elements of the partnership were not completed entirely (for example, creating a forum thread and answering investor questions directly from pastor Joshua to our users).  I wanted this for full transparency so no one outside of BiblePay could ever accuse us of spending even a penny that has not gone to the poor, and true account of each and every orphan.  (And to reiterate, all of our expenses have gone to help orphans with 0 overhead).   (During the interim months I have been manually paying out of my personal account to keep the relationship).

But now I feel the HFOC will need to be closed down, and instead, I feel it is in our best interests to scale up our 501c3 relationships to give our investors more of a warm and fuzzy feeling.

Therefore I have begun to close the relationship with HFOC today.

So please realize we will have some changes to our orphan records appearing in the pool.

Over the last 30 days, I have increased sponsorships with Kairos, as Pastor Andy Scribner has been phenomenal and located some children in desperate need in the Philipines in a very cost effective way - therefore I jumped on the opportunity for us to help them.  

So in summary, we will see a decrease of 26 kids from Kenya, but an increase of 11 kids from Kairos, and an increase of approx. 10 kids from Compassion.

Since we still have a credit at Compassion, I will also ensure we increase our compassion count by at least 5 kids, and then we can reassess our 6 month buffer with Compassion.

We now have 4 new kids coming this week thanks to POOM.  I will look into adding a POOM figure to our pool.biblepay home page also.

[coinsinspect]

BiblePay
1.4.4.7 - Leisure Upgrade
(Mandatory upgrade for Sanctuaries)

- 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.
- Disconnect nodes who ask for too much gov data
- Fix governance.dat bloated file size, on boot.  Reindex governance.dat
on boot if > 25 megs.
- Clean up GSC contract data after 1 day.  Sanctuary Quorums:  Vote to
delete duplicate contracts.
- Decrease memory consumption (by purging gobject cache)
- Limit network bandwidth (by removing unecessary and expired govobjs)

** Note:  The sync time and network utilization will improve *after* people start utilizing the new version **

[coinsinspect]

BiblePay
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 **

[coinsinspect]

*** 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 they won't have a problem matching up payments in BBP.

[coinsinspect]

BiblePay
1.4.4.9 - Leisure Upgrade

- Add CPK and height params to 'exec sentgsc cpk height' report.  This
allows you to audit a CPKs sent GSC/ABN transmissions per superblock
height.
- Add roi target_bbp_tithe to 'exec roi amount' report.  This shows the
ROI for a specific bbp tithe amount.
- Add 'exec cameroon_payments [xml/auto]'.  This report shows payments
sent to cameroon one for POOM - NOTE: This report only shows payments
sent via 'exec paycameroon'.
- Added block range result to 'leaderboard' rpc command.
- Added automatic change of up to 10 outputs for each created abn.
Note: We do not create change if the change will be less than the
minimum ABN amount.  You may set the key -changequantity=nnn to change
the default to up to 50 outputs.  (All this is for is to let ABN change
age in smaller distributed chunks - thereby utilizing coin-age more
efficiently for the next abn).
- Fix crash at startup in OSX (MIP)
- Add nonstandard port # to global health report.

** This is the windows release.  MIP will announce when linux/mac is ready. **

[coinsinspect]

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.

[coinsinspect]

*** 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.

[coinsinspect]

*** Christian Spaces / DSQL Thread ***

https://bitcointalk.org/index.php?topic=5188626.0

[coinsinspect]

BiblePay
1.4.5.0-Leisure Upgrade

- Add getblockforstratum rpc call to help support external cpu miner
(bbpminer.exe)
- Add exec pobh call for dev use (this allows us to test bible hashes
manually)
-  Fix instantsend GUI confirmation for signed/accepted IXs
- Add icon for decentralized network
- Increase IX timeout for locks and sigs
- Decrease memory consumption for votes and decrease network utilization
(Remove duplicate votes)


** This is the windows release; MIP will post when the rest of the binaries are ready **

** Now windows users, we can test mining with windows bbp-miner.exe against this windows build **

[coinsinspect]

*** External POBH (Heat/POW) miner being released now for testing in Prod or TestNet ***

Remember you will need to upgrade biblepay to 1.4.5.0+ first before you can use this miner (that release will be out shortly).  And, this release will only work in solo mining mode (so please comment out the pool entries).  And, you will need a self-funded abn, and the wallet unlocked for mining (so the internal core can create ABNs when needed).

1)  Repo for the new bbp-miner.exe:
https://github.com/biblepay/cpuminer

2) To build it yourself:
https://github.com/biblepay/cpuminer/blob/master/BuildingBBPMiner.txt

3) Binaries for Windows and for Linux (x86_64):
https://github.com/biblepay/cpuminer/tree/master/binaries

Windows Link:
https[Suspicious link removed]

Linux link:
https://github.com/biblepay/cpuminer/blob/master/binaries/bbpminer_linux

For more distros we will need to ask MIP to help us.

USAGE INSTRUCTIONS (SOLO MINING):

./bbpminer -o127.0.0.1:rpc_port_number -uYour_RPC_Username -pYour_RPC_Password --no-longpoll

BiblePay Configuration file (biblepay.conf):
server=1
rpcport=14000 (or your own number)
rpcallowip=127.0.0.1
rpcuser=your_rpc_username
rpcpassword=your_rpc_password


Please post if you have any trouble and we can all try to help.

[coinsinspect]

Biblepay CPU Miner
1.0.0.2-Leisure Upgrade

- Fix memory corruption error causing a crash
- Handle no work received

I cant say 100% the problem is resolved (as the valgrind trace was very vague), but this is the new version Im testing with tonight:
https://github.com/biblepay/cpuminer/tree/master/binaries

Feel free to upgrade and join me.

[coinsinspect]

I know the botnet is not back, because we have a 125K abn requirement.

One other nice hack the external miner relieves us of is the issue where we copy the wallet.dat out to many machines - with one bbp running node you can mine on multiple miners without copying wallet.dat.

Do you think a higher difficulty warrants high ABN? It sounded like you want to reduce ABN so the mining would not need much BBP to stake.

Can you explain a little more about not needing to copy the wallet.dat ?

We still need to run a node (biblepay-qt or biblepayd) but a blank wallet.dat is okay as long as one BiblePay wallet is running with the required ABN stake? That is news to me and sounds like a more secure way to mine. If mining is easier, I'm thinking it'll be easier for botnets to be set up too... if you set ABN to 5k, it wouldn't take much to mine continuously. Is there some way to keep botnets away without needing to stake BBP for ABN?

1) On the one biblepay node, multiple miners, like Nipar explained you can do that - the key is in the biblepay.conf on the single running node to do the :rpcallowip=ipv4 - one entry row per mining machine.  On the ABN question, yes that single node would need to have a high enough balance to cover all the ABN activity (IE 10 mining machines might need 1.25MM etc).  That particular wallet still needs unlocked, so that it can generate ABN's for the miners.  Its the same as required now, except concentrated against one node.  The nice thing about it though is we dont tell people to copy wallet.dat out to mining machines, and, its a little more efficient as you dont run multiple biblepays just to mine (I suppose thats better for our governance data and bandwidth consumption also).

2)
"
Do you think a higher difficulty warrants high ABN? It sounded like you want to reduce ABN so the mining would not need much BBP to stake.
"
->  Well, this is a definite conundrum.  On one hand, higher difficulty would dictate a higher ABN requirement if we go the "common sense route", but, the 'cryptocurrency economy model' is starting to explain to us that in order to attract many new users/miners, we have to lower the barrier.  This means we have to choose between these dimensions:  Less users/low diff/lower investor buying activity/more profit for a few - and risk of a collapse of the coin, or  b: more users/higher diff/higher buying activity/less profit per mined block/a more stable community.  So, I also realize, we are trying to protect our miners interests by blocking the botnet also - so it sounds as if a zero ABN is not good either.  Maybe we keep thinking about it - and ideas where we block the botnet - but increase user count.  All I have so far is the idea it might be good to lower the ABN req. to 10,000 or whatever, something that is a low barrier but would still afford some protection against a person who might install biblepay in a school system etc.  

[coinsinspect]

BiblePay - External CPU Miner
1.0.0.6-Mandatory upgrade for Miners

- Prevent crash during big blocks

Binaries:

https://github.com/biblepay/cpuminer/tree/master/binaries

[coinsinspect]

** BiblePay - New NOMP Pool - Opening in BETA mode for testing **



I am proud to announce our new NOMP pool is now opening in Beta mode.

You must use the BBP external miner to mine against our NOMP pool (as nomp requires stratum).

Note, that ABN's are going to be supported, however today all the shares temporarily pay the same amount (as ABN is not configured on the server side yet).

The goal today is to ensure the shares are being accepted in prod, the miners do not crash in stratum mode, the miners continually receive new work, and that we can actually solve blocks in prod.  Also, we need to ensure payouts work correctly from the NOMP side.

Regarding payouts:  NOMP pays every 15 minutes, but does require each solved block to be fully matured; here is an example of how your payout would work:
Miner A solves block 100,000.  NOMP records this miners shares and BBP address in the database (even if you stop mining, NOMP will remember your work).
At block 100,120, NOMP will see the block has matured.  Within 30 minutes, it will distribute all of the payouts (for every share that participated in that block).
So from a high level, you will be paid about 12 hours later for shares you solved.

WEB SITE URL:

http://nomp.biblepay.org

I have added some preliminary instructions on how to mine against NOMP on the home page.  Please see the wiki.

Basic configuration from our external miner:

https://wiki.biblepay.org/Nomp_mining
(See the Easy setup section)


As soon as ABN is configured on the server, I will post and explain how you can see your ABN status and ABN payout information, etc.

[coinsinspect]

BiblePay - External Miner
1.0.0.7-Leisure Upgrade

- Fix windows crash
- Fix issue where miner discards fresh work
- Deal with block size dynamically, to avoid memory problems.


https://github.com/biblepay/cpuminer/tree/master/binaries


** The updated server side NOMP code has just been released, so please, start testing over again and let's look at the ABN shares vs. worker shares as we solve them and verify these are incrementing correctly now.

Please upgrade to the new miner before NOMP mining as the prior version(s) had a work discard bug.

[coinsinspect]

Sorry guys but i have a really silly question.

do i use my worker name or my bbpaddress for the external miner?

Bit confused how it works.

Thanks

For Nomp, it only takes the BBP address currently.  For example here is my command line for windows:

bbpminer-x86.exe -ostratum+tcp://nomp.biblepay.org:3008 --user=BEsraanMpV3tzQ4dhJV1y9EkdEvf8MonF8

[coinsinspect]

BiblePay - Core Wallet
1.4.5.1-Leisure Upgrade

- Prevent wallet from crashing when using getblock to query a block with
missing element

** Release Ready **

[coinsinspect]

*** ABN (Anti-bot-net changes) - ABN is no longer required ***



All, we have been discussing potential future growth changes for BBP: https://forum.biblepay.org/index.php?topic=461.msg6381#msg6381
and following the suggestions from the DSS model, showing that we need a positive UPD (+1 or more new user per day), and also with the complexity of requiring people to unlock wallets and support ABNs in the pool(s) is probably not worth the benefit, since we are going to be moving to a new environment soon with stronger anti-bot-net possibilities (rewards for cancer mining/aids, limiting rewards to PODC, etc).

In light of this, I have disabled ABN (the sanctuary vote is largely pointing to this).  This is primarily being done now - so the devs can finish the NOMP pool now with simplicity in mind for the new users.

So, starting now, you no longer need an ABN to mine BBP.  The NOMP pool has been updated to pay equally. 

You may now move to the easy setup, and you no longer need to send single threaded abn's to pool.biblepay.org to mine.

The easy start guide has been modified for NOMP.

Pool.biblepay.org is being modified now to make payouts equal across the board.

(I am analyzing nomp's share rejects today, and will make a post ASAP about that).

[coinsinspect]

BiblePay - External CPU Miner
1.0.0.8-Leisure Upgrade

- Prevent submitting duplicate shares
- Handle time encoding correctly

** Ok guys, it appears the lions share of the problem with the pool was the time encoding and submission of duplicate shares.  Please upgrade the external miner, and try again with Nomp, lets see if the valid share percentages rise now. **

[coinsinspect]

External CPU Miner
1.0.0.9-Leisure Upgrade

- Ensure time is encoded properly for both stratum & non-stratum modes

** Ok everyone, the 1008 version is really not a working release.  I believe this version actually addresses the problem; please try now. **

[coinsinspect]

i went to pog so i browse how it worked ... and found this guide
https://wiki.biblepay.org/Getting_Started_with_Evolution
but exec sendgscc is not working anymore...
update is needed

btw how can i check if my wallet is already joined to pog? i'm not sure if i not leaved or so
sendgscc not thrown any error

1)  Its now : sendgscc instead of 'exec sendgscc', so you can type for example:  sendgscc pog 100, that would send a donation of 100 bbp to the foundation.
2)  If you leave the miner running on one thread with the wallet unlocked, it will send one sendgscc out every 12 hrs.
3)  You can try to type : exec join pog,  and it will throw an error if you already joined.

[coinsinspect]

1) can we have lower difficulty? Even 3 diff is kind of high for some computers. Could you offer difficulty of 1 or lower perhaps?

2) Wrote some new articles:

I downloaded the Biblepay wallet but it doesn’t sync, why?
https://whitewalr.us/2019/biblepay-wallet-sync-issue.html

How do I mine on the BiblePay NOMP pool?
https://whitewalr.us/2019/biblepay-nomp-pool-mining.html

3) I get disconnected from pool sometimes. I just communicated with it so I am not sure why this is happening.

stratum_recv_line failed
Stratum connection interrupted

I tried temporarily from different networks (usa, europe, asia, etc). it seems to happen regardless of where my miner traffic originates from.. i wonder if pool can handle all the workers?

is anyone else seeing the disconnect?

4) i let some miners run overnight and I think invalid shares is high again. out of 1050 submitted / only 1010 accepted. So, something like 96.1% accept rate. saturday day worked very good. but saturday night maybe more people joined pool, i don't know.

[coinsinspect]

BiblePay
1.4.5.2-Leisure Upgrade

- Fix exec paycameroon feature to use current bbp price
- Fix exec price to show current bbp price

** This is the windows release.  MIP will update when linux is ready **

[coinsinspect]

By the way, the DIP3 link is not working :
https://wiki.biblepay.org/Evolution_Upgrade

Here is a working link:
https://docs.dash.org/en/0.13.0/masternodes/dip3-upgrade.html

Are these the steps to upgrade masternode to deterministic?
https://bitcointalk.org/index.php?topic=2388064.msg51695886#msg51695886
https://www.reddit.com/r/BiblePay/comments/clyxyc/upgrading_masternodes_sanctuaries_to/
https://forum.biblepay.org/index.php?topic=391.msg5968#msg5968

EDIT:
This worked for me.
I noticed that you need to keep the old line, so the sanctuary will not exit:
masternodeprivkey=nnnn

[realdantreccia]

I can't get my wallet to sync pat 99.26% (10 days behind). I upgraded to the latest Windows 64-bit version from biblepay.org...

help?

[realdantreccia]

Here is what my debug says:

Code:

2019-11-04 14:34:04 init message: Loading addresses...
2019-11-04 14:34:04 Loaded 44315 addresses from peers.dat  116ms
2019-11-04 14:34:04 init message: Loading banlist...
2019-11-04 14:34:04 init message: Starting network threads...
2019-11-04 14:34:04 net thread start
2019-11-04 14:34:04 dnsseed thread start
2019-11-04 14:34:04 addcon thread start
2019-11-04 14:34:04 opencon thread start
2019-11-04 14:34:04 msghand thread start
2019-11-04 14:34:04 mncon thread start
2019-11-04 14:34:04 init message: Starting Miner...
2019-11-04 14:34:04 BibleMiner -- started thread 0.000000 
2019-11-04 14:34:04  ** Started 1.000000 BibleMiner threads. ** 

2019-11-04 14:34:04 init message: Done loading
2019-11-04 14:34:04 GUI: Platform customization: "windows"
2019-11-04 14:34:04 GUI: PaymentServer::LoadRootCAs: Loaded  68  root certificates
2019-11-04 14:34:15 Loading addresses from DNS seeds (could take a while)
2019-11-04 14:34:15 1 addresses found from DNS seeds
2019-11-04 14:34:15 dnsseed thread exit
2019-11-04 14:35:00 ERROR: AcceptBlockHeader: block 10d7b6ebc06d41a4c7b1059470af579a4cc24ff7ffefe8e10f135525fae39038 is marked invalid
2019-11-04 14:35:00 ERROR: invalid header received
2019-11-04 14:35:00 
ios_base_failure::mesg_fail::ProcessMessages(headers, 161031 bytes) FAILED peer=0
2019-11-04 14:35:00 Misbehaving: 134.209.2.19:40000 peer=0 (0 -> 1)

[coinsinspect]

Try asking in the main thread:
https://bitcointalk.org/index.php?topic=2388064.new#new

Rob, the main developer, is very helpful.

[coinsinspect]

I am using under Windows 10:

Code:

bbpminer-x86 -o stratum+tcp://nomp.biblepay.org:3032 -u MINING_WALLET -p x

Or:

Code:

bbpminer-x86 -o stratum+tcp://5.135.183.202:3032 -u MINING_WALLET -p x

Both returns rightaway:

Code:

KJV Loaded
Using bbpminer version 1009

solo mining 0
[2019-11-10 08:57:12] Starting Stratum on stratum+tcp://5.135.183.202
[2019-11-10 08:57:12] 4 miner threads started, using 'pobh' algorithm.
[2019-11-10 08:57:12] Binding thread 3 to cpu 3
[2019-11-10 08:57:31] stratum_recv_line failed
[2019-11-10 08:57:31] ...retry after 30 seconds

Last two lines in a loop (new line every 30 seconds).
Perhaps my hashrate is slow as I've been disconnected since 4th of November. But I cannot mine with the wallet client as well since then. The biblepay.conf file:

Code:

gen=1
genproclimit=3
minersleep=0
pool=tcp://5.135.183.202:3032
workerid=zupernovato1
workeridfunded=zupernovato2

But with getmining info:

Code:

...
"poolinfo3": "POOL DOWN-REVERTING TO SOLO MINING; POOL DOWN-REVERTING TO SOLO MINING; ",
"poolmining": false
...

Do I need to register workerids on the new pools hosts?

Do I need to turn onh WCG-BOINC once again in team BiblePay? (I've read something about it in the recent pages of this thread).

1) I've tested your bbpminer-x86 external miner config and it seems OK, it works for me.  I dont think you need the "-p x" at the end, but it should not be a concern.
2) I don't think its your hashrate; it doesn't sound like you ever get to the point where the miner is showing the hashmeter.  After a couple minutes you should see 'thread 1: nn KH/S'.  You can try adding "-t1" to mine on a single core (this would put more availability to one thread) and see if anything happens, but imo I dont think its the hashrate.
3) You can take out the workerid, workeridfunded, and pool settings in the biblepay.conf as currently pool.biblepay.org is out of play in favor of nomp.  Basically the internal miner in the core wallet is not being used for mining, but we are using the external miner now.  (I do have a side project to fix that, so they are equal, but for now lets all use the external miner to be equal in speed).
4) You do not need to register any workerid now, you can just use a valid BBP receive address.  Please do verify the receive address you use is valid (you get it from the core client Receiving address, or, from 'getnewaddress' . <- I would look at this as this could be the problem, nomp may be hanging up on you if its a bad address.
5) You don't need to have boinc on *yet*, but, we are going to require users to be on team BBP for WCG very soon - IE within 30 days - to earn PODC2.0 credits.  See this thread if you want to help us:  https://forum.biblepay.org/index.php?topic=465.msg6515#msg6515

6)  If none of this helps, please try the external miner on another machine and see if it works with the same settings.  If it does, you might have a bad binary on win10, just re-download it.
7) You can also try this:  telnet nomp.biblepay.org 3032
Verify the screen clears.  This shows you have a connection to the stratum port.  There is a remote chance you have a blocked firewall in win10?

[coinsinspect]

https://i.imgur.com/27JnOUk.png

i like big blocks and i can not lie

download the miner here:
https://github.com/biblepay/cpuminer/tree/master/binaries

join the pool and earn BBP rewards here:
bbpminer-x86.exe -o stratum+tcp://5.135.183.202:3032 -u BEXTU6iVeBdoqgwbP8rmzYNoKhQgwz5BGs -p PraiseJesus

-u is your bbp address
-p password can be anything

other pools:

nomp.biblepay.org
leopool.biblepay.org

[coinsinspect]

** BiblePay Prod Quick Sync **


I'm working on a quick sync script for prod to be released during our PODC 2.0 release - so Windows quick-sync is not ready yet, but in the mean time if anyone wants to test this the linux version is ready:

For biblepayd or biblepay-qt do the following for quick-sync (this is syncing fast from block 0, an alternative to -erasechain=1):

Do this part once:
cd ~/.biblepayevolution  (Be sure to cd to where your Biblepay data directory is first)
wget biblepay.org/syncblocks_prod.sh
chmod 777 syncblocks_prod.sh

Whenever you want to sync from 0:
cd ~/.biblepayevolution
./syncblocks_prod.sh


The script automatically gracefully stops biblepay first.  We do sync the prayers, blocks, llmq & chainlocks, and governance data, so theoretically the node should be stable after this.
You do have to start biblepay manually after this is done.

[coinsinspect]

** CAMEROON-ONE WALLET ADDRESS CHANGE **


Cameroon is migrating to a new wallet (and the old key is no longer available).

Please do not use the 'paycameroon' command until the next update, and please do not send any funds to the address in 'sponsorchild'.

We will be making this an adjustable spork in the next version (our testnet version) but for now we will release a leisure upgrade to fix this in the next day or so.

The new address is:
BF6qmwBMmnmb4FbSmRGTeWQL1m3rwh5n7b

[coinsinspect]

BiblePay
1.4.5.3-Leisure Upgrade

- Update Cameroon One receiving address

Please verify the 'exec paycameroon' works by sending a small amount to cameroon-one.

[coinsinspect]

Hi,
I deleted all files except wallet.dat and biblepay.conf  in my Sanctuary and wallet
on both stations I am at block 0 for ~12 hours.

From my Sanctuary  debug.log

Code:

2019-12-05 17:40:11 AcceptConnection -- masternode is not synced yet, skipping inbound connection attempt
2019-12-05 17:41:19 AcceptConnection -- masternode is not synced yet, skipping inbound connection attempt
2019-12-05 17:43:30 AcceptConnection -- masternode is not synced yet, skipping inbound connection attempt
2019-12-05 17:44:37 AcceptConnection -- masternode is not synced yet, skipping inbound connection attempt
2019-12-05 17:46:00 AcceptConnection -- masternode is not synced yet, skipping inbound connection attempt
2019-12-05 17:47:33 CActiveLegacyMasternodeManager::ManageState -- SYNC_IN_PROCESS: Sync in progress. Must wait until sync is complete to start Masternode
2019-12-05 17:52:38 AcceptConnection -- masternode is not synced yet, skipping inbound connection attempt
2019-12-05 17:55:53 AcceptConnection -- masternode is not synced yet, skipping inbound connection attempt
2019-12-05 17:57:33 CActiveLegacyMasternodeManager::ManageState -- SYNC_IN_PROCESS: Sync in progress. Must wait until sync is complete to start Masternode
2019-12-05 18:01:12 AcceptConnection -- masternode is not synced yet, skipping inbound connection attempt
2019-12-05 18:02:53 AcceptConnection -- masternode is not synced yet, skipping inbound connection attempt
2019-12-05 18:02:59 AcceptConnection -- masternode is not synced yet, skipping inbound connection attempt
2019-12-05 18:04:16 AcceptConnection -- masternode is not synced yet, skipping inbound connection attempt

Please try :

- Verify system time and time zone are correct
- Remove banlist.dat
- Start with "-erasechain=1"

The log above is normal (that means it wont share data until its synced).

EDIT:
Here is an extra addnode Im connected to now:
107.150.33.90
178.170.72.139

Thanks Togo!

I did the same and add to biblepay.conf:
addnode = 107.150.33.90
addnode = 178.170.72.139

Now I am getting blocks.

[coinsinspect]

Hope this helps, for the Iquidus explorer, I have a crontab that tries to run the biblepay daemon every 5 minutes:

crontab -e

Code:

*/5 * * * * /home/biblepay-evolution/src/biblepayd > /dev/null 2>&1

Gave this to Rogue a little earlier tonight. You could use this also

#!/bin/bash
# checkprocess.sh

PROCESS=<insert the name of what process you are kicking off>

check_running_process()
{
sudo ps -ef | grep -v grep | grep $PROCESS > /dev/null
result=$?
#echo "exit code: ${result}"

if [ "${result}" -eq "0" ] ; then
    echo "Process is Running"
    return 1
else
    echo "Process is Stopped"
    return 0
fi

}

echo Current Date and Time is: date +"%Y-%m-%d %T"
if (check_running_process); then
#Want to make sure it is not already being started
   sleep 10
   if (check_running_process); then
      echo "Restarting Process now"
      #syntax to restart the process
      #insert your command to restart the process that is not running <-- Here is the command you would put in to start the process if it has died
   fi
fi

here is my change if you are running several MN on same Linux :

Code:

./checkprocess.bash "biblepayd" "/sbin/runuser -l bbp -c './mn/biblepayd'"

Code:

root@station:~# cat checkprocess.bash
#!/bin/bash
# checkprocess.sh

echo process to check = $1
echo running command = $2

PROCESS=$1

check_running_process()
{
    sudo ps -ef | grep -v grep | grep -v checkprocess | grep $PROCESS > /dev/null
    result=$?
    #echo "exit code: ${result}"

    if [ "${result}" -eq "0" ] ; then
        echo "Process is Running"
        return 1
    else
        echo "Process is Stopped"
        return 0
    fi

}

if (check_running_process); then
#Want to make sure it is not already being started
   sleep 10
   if (check_running_process); then
      echo "Restarting Process now"
      #syntax to restart the process
      #insert your command to restart the process that is not running <-- Here is the command you would put in to start the process if it has died
      $2
   fi
fi

In crontab -e

Code:

*/5 * * * * /root/checkprocess.bash "biblepayd" "/sbin/runuser -l bbp -c './mn/biblepayd'" > /dev/null 2>&1

[coinsinspect]

BiblePay - MainNet
1.4.8.4 - Mandatory Christmas 2019 Upgrade @ 166075



- Merge in all Dash Prod 0.14 branch code and fixes up to Nov 2019
- Merge in PODC 2.0 and DWS and ExternalPurse and DSQL and Decentralized
Web surfing and Kairos Childrens Fund (POOM) and ChainLocks and
Deterministic Sancs and IX autolocks and IX fixes
- Merge in improved POBH internal solo miner (brings solo mining to 90%+
compared to external miner)
- Go live height is 166075 (approx 12/26/2019)

** Binaries ready **

** Exchanges have been notified **

** Explorers have been notified **

[coinsinspect]

BiblePay
1.4.8.4-Leisure Upgrade

- Add 'dashpay' and 'trackdashpay' RPC commands.
- Add 'poom_payments' RPC command.

** Binaries have been deployed **

To test the new alpha feature : dashpay, please see this guide:
https://wiki.biblepay.org/DashPay_RPC

[coinsinspect]

So in the spirit of a smooth PODC 2.0 rollout, and a smooth Kairos rollout, Im going through and verifying our team settings, etc, and getting ready to add a researcher.

First ensure you are upgraded to 1.4.8.4, then:

For those of you who want to sponsor a Kairos child, please type this:QQ
exec join kairos

To be on the safe side, if you already sponsor a cameroon-one child type this also:
exec join cameroon-one

For those of you who have CPIDs, type this:
exec join wcg
exec associate username wcg_verification_code true

To find your username in WCG:
Log into your WCG account at 'worldcommunitygrid.org' with your WCG E-mail address and WCG password.",
  "Step 2": "Click Settings | My Profile.  Record your 'Username' and 'Verification Code' and your 'CPID' (Cross-Project-ID).",
  "Step 3": "Click Settings | Data Sharing.  Ensure the 'Display my Data' radio button is selected.  Click Save. ",
  "Step 4": "Click My Contribution | My Team.  If you are not part of Team 'BiblePay' click Join Team | Search | BiblePay | Select BiblePay | Click Join Team | Save.",
  "Step 5": "NOTE: After choosing your team, and starting your research, please give WCG 24 hours for the CPID to propagate into BBP.  In the mean time you can start Boinc research - and ensure the computer is performing WCG tasks. ",
  "Step 6": "From our RPC console, type, exec associate your_username your_verification_code true",
  "Step 7": "Wait for 5 blocks to pass.  Then type 'exec rac' again, and see if you are linked!  ",
  "Step 8": "Once you are linked you will receive daily rewards.  Please read about our minimum stake requirements per RAC here: wiki.biblepay.org/PODC"

For researchers in PODC:
After all this is successful, you can send a GSC transmission (this contains your PODC daily stake), but you only have to do this once - today - just to test it:
sendgscc wcg

If you leave the wallet on, it will automatically send the WCG stake once per day (at the height shown in 'exec rac').

[coinsinspect]

ORBIS ako funguje to sponzorstvo deti?  da sa to aj dodatocne spustit?

@sunk  any idea how working sponsoring of children? thx

You want to sponsor child? There are many steps, but if you are interested, I can chat with you one-on-one and give you the steps.

I wrote instructions, but they are wrong after we upgraded to 1.4.8.4, so I have to re-write the instructions and re-do the screenshots:

https[Suspicious link removed]c_paycameroon

Remember, it costs you 50k BBP to authorize one sponsorship, then you pay for one month every month on the 1st.
Either you $40 USD CameroonONE or $25 USD Kairos.
Currently, you will get back about 33% to 50% back in BBP.

[coinsinspect]

** PODC 2.0 FAUCET RELEASED **


https://web.biblepay.org/BMS/AppServer?seo=1&b64=cG9zdD17Im5hbWUiOiIiLCJhY3Rpb24iOiJmb3JtbG9hZCIsImJvZHkiOiJwb3N0PUZyYW1lTmF2IiwiY2xhc3NuYW1lIjoiQk1TLkhvbWUiLCJldmVudG5hbWUiOiJmb3JtZXZlbnQiLCJtZXRob2RuYW1lIjoiTm9uQmlibGVQYXlGYXVjZXQiLCJkaXZuYW1lIjoiMSIsImd1aWQiOiJhYjY1MzExMS0wMzdjLTRmMTEtOTZkOS05YjA0NmEyYmYzNzQiLCJhbHRndWlkIjoiYWI2NTMxMTEtMDM3Yy00ZjExLTk2ZDktOWIwNDZhMmJmMzc0Iiwib3JkZXJieSI6IiIsImNoYWluIjoidGVzdCIsImNwayI6bnVsbCwidGltZXN0YW1wIjoiMTU3NzQ2NTM0NyIsInNpZ25hdHVyZSI6IiIsInNpZ25hdHVyZV92ZXJpZmllZCI6ZmFsc2V9


Alt link:

https://web.biblepay.org

Click Faucet

[coinsinspect]

Ive been updating Documentation:
https://www.reddit.com/r/BiblePay/comments/efeeg3/documentation_step_by_step_guides_need_help/

=

Proof of Distributed Computing (Science Research)
https://wiki.biblepay.org/PODC_Setup

=

Proof of BibleHash (Heat Mining)
https://wiki.biblepay.org/POBH_Setup

=

Masternode
http://wiki.biblepay.org/Create_Sanctuary_2
- added deterministic upgrading steps
- updated creating proposals and voting on proposals

=

Dynamic Whale Staking
https://wiki.biblepay.org/DWS_Setup

I just staked 1 million BBP for 30 days to test it out

=

Please review my guides and give feedback!

=

Healing Campaign
https://wiki.biblepay.org/BiblePay_Healing_Campaign

I tested this and it works, I think its a great guide,
Minor bug, I did crash my wallet trying to send a diary entry before my "exec join healing" transaction reached enough confirmations

I noticed in Suns guide there are config settings:
https://whitewalr.us/2019/biblepay-gsc-healing.html

Are there rewards to tithing more than 1 BBP?
Are there rewards for coin-age? Is this sort of a smaller version of POG?

[coinsinspect]

Android mobile wallet version 1.4.8.5

- added new tithe feature screen

iOS version will come in a few days

[coinsinspect]

BiblePay
1.4.8.5 - Leisure Upgrade

- Fix glitch where exec rac occasionaly comes unlinked
- Allow researchers with insufficient collateral to receive commensurate
RAC (NOTE: This does not go into effect until the next Mandatory
Sanctuary Upgrade is announced on the forum!)
- Added cancelsponsorship rpc command (cancelsponsorship charityname
childid authorize) to allow cancellation of a POOM child
- Removed ability to pay for POOM sponsorship via BBP.  An updated wiki
page will be announced on the forum with the updated payment info.
https://wiki.biblepay.org/Paying_For_a_POOM_Sponsored_Child
- Fixed error message in exec associate for non-bbp researchers. Allow
cpid to be associated if RAC > 256 for non-bbp researcher.
- Added unlock wallet verbiage to vote failure in Voting UI page.

[coinsinspect]

I've trying to map out what it means for a new user to set up PoDC 2.0 based on https://wiki.biblepay.org/PODC_Setup 

I created a knowledge article with a visual map: https://whitewalr.us/kb/podc-setup-mm

Feel free to leave any feedback or comment. Thanks!

https://i.imgur.com/DBlFKwx.jpg

[coinsinspect]

Question:
In Leader Board, assuming WCG, what is the meaning of :
1) points
2) owed
3) prominence

1= Your researcher RAC for the Day
2= The amount in BBP you earned for that days research
3= Your magnitude.  This is your % of contribution to the team in research.

[coinsinspect]

Question:
In PODC, if "exec rac" is OK, should I ran "exec sentgsc <CPK>" twice a day or automatic system working fine ?

Automatic works fine.

[coinsinspect]

BiblePay
1.4.8.6-Mandatory Upgrade for Entire Network @ 170830

- Increase sanctuary protoversion to 70751 (Enable new consensus rules
for PODC - fix low payment bug)
- Adjust deflation rate to match target in GetBlockSubsidy
- Add anti-gpu measures to POBH (reject high-nonce blocks)
- Mandatory height: 170830
- Adjust DWS creation and validation for DWS 2.0
- Add upgradesanc warning when no \r\n exists (Togo)
- Add addl warnings to exec rac, and ensure exec rac does not crash the
node
- Remove dead code from miner; modify miner to handle anti-gpu nonce
rules

** Note: We also have a mandatory upgrade for the external miner, please find the binaries here:
https://github.com/biblepay/cpuminer/tree/master/binaries

** Sanctuaries, please upgrade also

** The new POBH 2.0 rules do not start until 170830, so in the mean time, the pool will reject most of the shares.  As soon as this height passes the pool should start working correctly.  The pool is coming back online now.

POOLS:  Please upgrade.  The software has been updated here:
https://github.com/biblepay/node-stratum-pool/commits/master
To upgrade please follow the upgrade instructions in this document:
https://github.com/biblepay/node-open-mining-portal/blob/master/Deploy%20a%20Nomp%20BiblePay%20Pool.txt

[coinsinspect]

New wallet is crashing. Installed on previous version.
Error was 2020-01-20 16:06:52 ERROR: ReadBlockFromDisk: Deserialize or I/O error - ReadCompactSize(): size too large: iostream error at CBlockDiskPos(nFile=0, nPos=11296509)
I deleted my blocks directory to force rescan, now is crashing with no error in log.

Have you tried restarting with the "-erasechain=1" switch?

[coinsinspect]

MIP whats cmd for upgrade linux, forgot it, thanks...... good to add on main web in tutorials, missing it there

Using the masternode script
./masternode-install.sh -u -n

Manually
wget https://biblepay.org/biblepayd-evo-x86_64-pc-linux-gnu.tar.gz
tar -xzf biblepayd-evo-x86_64-pc-linux-gnu.tar.gz
#stop daemon, move/copy binaries to replace older, restart daemon

thanks.... appreciate it....thx to orbis with help how to setup this MIPs packages

I use this:

Code:

biblepay-cli stop
sleep 30
cd /usr/local/bin
sleep 5
rm biblepayd-evo-x86_64-pc-linux-gnu.tar.gz
sleep 3
wget https://biblepay.org/biblepayd-evo-x86_64-pc-linux-gnu.tar.gz
sleep 3
tar xvf biblepayd-evo-x86_64-pc-linux-gnu.tar.gz
sleep 3
rm biblepayd-evo-x86_64-pc-linux-gnu.tar.gz
sleep 3


biblepayd --version
sleep 3
biblepayd --daemon
sleep 3
cd ~
sleep 1
cd .biblepayevolution
sleep 1
tail -f debug.log

For biblepay miner:

Code:

cd .biblepayevolution
pkill bbpminer_linux
rm bbpminer_linux
rm bbpminer_linux
wget https://github.com/biblepay/cpuminer/raw/master/binaries/bbpminer_linux
chmod 755 bbpminer_linux

[coinsinspect]

DWS (Dynamic Whale Staking)

https://i.imgur.com/OCz1Q7E.png

Potentially gain 40% interest on your coins right now by staking them for one year

With mining, I have to make sure the miners stay updated and are running 24/7, I have to pay for electricity

Similar with a masternode, it has to stay updated and run 24/7, and I have to pay for a server

Staking, you just burn it!

https://wiki.biblepay.org/DWS_Setup

[coinsinspect]

Quick question about the CPK.  As I get more funds into my BBP wallet, do I have to occasionally send more funds to my CPK for them to be counted towards my coin age?  Thanks!

Coin-age is required only if you are doing PoDC (Boinc). I assume you are doing that; so you are correct, only funds in the CPK address count towards PoDC coin-age.

Having said that, there is no reason to keep increasing your coins in the CPK address unless you are running short on collateral for PoDC (i.e., increasing RAC).

[coinsinspect]

Hey everyone, here is my research for a BiblePay 2020 Q1 (Jan, Feb, March) Update Newsletter article
If anything is missing please post, and if you have any ideas on how to express, present, or organize these things also please post!

=

RANDOMX HISTORY

Voting for BiblePay's Future CPU Only Hashing Algorithm
https://www.reddit.com/r/BiblePay/comments/eud6o8/vote_for_biblepays_future_cpu_only_hash_algorithm/
REF: https://bitcointalk.org/index.php?topic=2388064.msg53736183#msg53736183
PIC: https://bitcointalk.org/index.php?topic=2388064.msg53710764#msg53710764

RandomX Tesnet Testing
https://www.reddit.com/r/BiblePay/comments/f0yueb/testnet_testing_monero_randomx_cpu_only_dual/

=

PODC VIDEO TUTORIAL & GIVEAWAY

Video Tutorials - How to Setup BiblePay Wallet and Contribute to Cancer Research!
https://www.publish0x.com/what-is-volunteer-computing-and-why-do-it/how-to-setup-up-a-biblepay-wallet-and-podc-20-xlnpxq

1 Million BiblePay PODC Giveaway!
Get rewarded coins every day for contributing to real science research!
https://www.reddit.com/r/BiblePay/comments/ekctku/1_million_biblepay_podc_giveaway/
PIC: https://twitter.com/BiblePay/status/1215097478418178049

=

DWS TUTORIAL, GAIN INTEREST

Dynamic Whale Staking
https://wiki.biblepay.org/DWS_Setup
https://bitcointalk.org/index.php?topic=2388064.msg53710394#msg53710394
PIC: https://twitter.com/BiblePay/status/1224368755725275136

=

USE CASES

Dimensions
https://wiki.biblepay.org/Dimensions
"we need to dedicate ourselves to finding the 'solid use case' for BiblePay"
https://bitcointalk.org/index.php?topic=2388064.msg53404151#msg53404151

Use Case Idea List
https://docs.google.com/spreadsheets/d/1VCjQoJ63F9cuttKdqn4iHxTUOB0DePXcXzS9GnRVU0w/edit#gid=1386834576

Decentralized Video List, 14,000 Videos added!
https://web.biblepay.org
https://bitcointalk.org/index.php?topic=2388064.msg53396602#msg53396602

Global Charity Agent
https://forum.biblepay.org/index.php?topic=486.msg6887#msg6887
https://bitcointalk.org/index.php?topic=2388064.msg53745506#msg53745506
https://bitcointalk.org/index.php?topic=2388064.msg53844605#msg53844605

Buy Gift Cards Instantly with BiblePay! (using Dash, InstantSend and Bitrefill)
https://www.reddit.com/r/BiblePay/comments/ef3yyw/new_alpha_development_feature_dashpay_buy_gift/
https://bitcointalk.org/index.php?topic=2388064.msg54008342#msg54008342
https://bitcointalk.org/index.php?topic=2388064.msg53956491#msg53956491
PIC: https://twitter.com/BiblePay/status/1209663588132163588

=

TRADING

BiblePay now trades to 9 decimal places of Bitcoin on our #1 exchange SouthXchange!
https://www.southxchange.com/Market/Book/BBP/BTC
Proof: https://twitter.com/southxchange/status/1211341592310812672

Sell Pressure Mitigation
https://bitcointalk.org/index.php?topic=2388064.msg53494820#msg53494820

=

ROADMAP, REBRAND, CORE

Roadmap Updated
https://wiki.biblepay.org/Roadmap

Vote on Rebranding
https://forum.biblepay.org/index.php?topic=499.0

What is BiblePay? What makes BiblePay unique?
https://www.reddit.com/r/BiblePay/comments/eff1cq/what_is_biblepay_what_makes_biblepay_unique/

=

CHARITY

CameroonONE @ONETrackInt Christmas party! Donations were organized by @sunk818
https://whitewalr.us/2019/cameroonone-kairos-children-gifts.html
PICS: https://twitter.com/BiblePay/status/1210376146765963265

Kairos Children's Fund Christmas party
https://twitter.com/AndrewScribner/status/1207273608407441408

"ONETrack International was awarded the 2019 Global Giving Staff Favorite badge!
OTI was selected as their favorite nonprofit of 2019!"
https://twitter.com/ONETrackInt/status/1225056933167628290

ONETrack International lists BiblePay donation address
http://onetrackinternational.org/cryptocurrency/

CoronaVirus Appeal
http://onetrackinternational.org/coronavirus/

Compassion Update
https://bitcointalk.org/index.php?topic=2388064.msg53657307#msg53657307

=

ACCOUNTABILITY

"We have received over 2,742 pages of inbound letters, written by our sponsored children to BIBLEPAY
https://bitcointalk.org/index.php?topic=2388064.msg53414454#msg53414454

New Accountability Website Coming
https://bitcointalk.org/index.php?topic=2388064.msg53844701#msg53844701

=

DASH

Dash Crypto Turns 6 Years Old! with Amanda B Johnson
https://www.youtube.com/watch?v=6Aa6OO37f6s

11 Ways Dash Is Building The Most Complete Cryptocurrency Experience
https://www.youtube.com/watch?v=FBWt0AVu-nI

Dash Celebrates Sixth Anniversary Full of Industry-Defining Innovations
https://dashnews.org/dash-celebrates-sixth-anniversary-full-of-industry-defining-innovations/

Dash Dapps
https://bitcointalk.org/index.php?board=159.0

=

MASTERNODE HOSTING

Apollon Network Shuts Down
https://bitcointalk.org/index.php?topic=3058895.msg53733889#msg53733889

=

PRAYER

Healing Campaign
https://bitcointalk.org/index.php?topic=2388064.msg53781131#msg53781131

Coronavirus Prayer
https://bitcointalk.org/index.php?topic=2388064.msg53817793#msg53817793

=

BOUNTY

2000 BBP Bounty Task: Retweet & Like Two GitHub repositories
https://www.reddit.com/r/BiblePay/comments/fa738m/2000_bbp_bounty_task_retweet_like_two_github/

=

NEWSLETTER

Previous Newsletter
https://medium.com/biblepay-news/biblepay-q4-updates-2019-october-november-december-ef80085d4b27

Sign up for Future Newsletters
https://www.biblepay.org/newsletter/

[coinsinspect]

BiblePay - 1.5.0.7
Mandatory Upgrade for Entire Network @184675 (March 24th, 2020)

- Add RandomX Mining to biblepaycore
- Add corporate whitebranding (for the future - this is dormant)
- Add DAC images and logos
- Merge Dash Mainnet changes up to Jan 2020 into Prod mandatory release
- RandomX starts at 184675
- Merge in changes to block database
- Move datastore to ~/.biblepay

** Note: This upgrade also requires new mining software after block 184675, with the switch to RandomX
** Note:  The wallet and data directory have been moved back to our original location (~/.biblepay) to cut down on confusion.  
** Our github location has been moved back to the original location (https://github.com/biblepay/biblepay)
** The new RandomX pool will come on-line approx. 1 day before our go live.  The address will be:  rx.biblepay.org
** Binaries have been released, and names and sha hash names have changed on biblepay.org.  Note, I believe we will not be able to release binaries for Rasberry pi or Arch.  You may be able to self compile those.  We are also limited to initially releasing 64 bit binaries for Windows and Linux.  (NOTE:  This is not because we are lazy or don't care about 32 bit, it's because both MIP and I receive errors in the randomx compile process for the 32bit processors.  We believe RX may not work on 32bit, therefore we must delay 32bit until we do more research.)  Please provide feedback to us if you find a binary is missing or does not work.

Please see this document for upgrade instructions:
https://wiki.biblepay.org/Upgrade_to_RandomX

[coinsinspect]

BiblePay Q1 2020 Updates

https://medium.com/biblepay-news/biblepay-q1-2020-dual-mining-randomx-960720c0fa06

[coinsinspect]

BiblePay in the City - Promo Video 1:
https://san.biblepay.org/Media/BiblePay_City_Promo.mp4

BiblePay - Plane - Promo #2:
https://san.biblepay.org/Media/Biblepay_Plane.mp4

Helicopter - Promo #3:
https://san.biblepay.org/Media/Biblepay_Helicopter.mp4

https://san.biblepay.org/Media/BiblePay_2020_Commercial.mp4

Additional 1st Quarter commercial for BBP - RandomX (short version):
https://san.biblepay.org/Media/BiblePay_Commercial_March_2020.mov

[coinsinspect]

*** NEW RANDOMX GIVEAWAY FOR NEW RANDOMX USERS ***
https://forum.biblepay.org/index.php?topic=503.msg7138#msg7138
Feel free to promote.  I believe we can do this for the first 150 new RX miners.

https://wiki.biblepay.org/Upgrade_to_RandomX

from:
https://forum.biblepay.org/index.php?topic=490.msg7143#msg7143

** Solution if your miner crashes when mining randomX **
Create a batch file on windows with the following
Code: [Select]
:miningloop
xmrig.exe -o rx.biblepay.org:3001 -u bbpaddress -p moneroaddress --threads=8
goto miningloop

[coinsinspect]

Where do people download the bbp xmrig software again?

https://github.com/biblepay/xmrig/tree/master/binaries

Is this the best location?

[coinsinspect]

Where do people download the bbp xmrig software again?

https://github.com/biblepay/xmrig/tree/master/binaries

Is this the best location?

Yeah normally i just download directly from github, all about your taste i guess. Directly from pool page also a option.

I am using port 3001 on rx.biblepay.org - the block height says 2062258

Height should be 184675. Am I mining on the correct chain? That block height looks awfully high, like it is testnet chain or something...

I haven't tried xmrig in a long time, so I could be mistaken too.

https://i.imgur.com/tDIR32B.jpg

As we covered in testnet we display the randomX height there and when you solve BBP shares then we pass through BBP height and bbp diff.

So that part is A-OK.

[coinsinspect]

https://docs.google.com/spreadsheets/d/1ep5G9rG-M460OZYLOd4NHv5sWFDwe_Ow_wop-Fi_SQU/edit#gid=35272442

[coinsinspect]

** BBPRIG (XMRIG) 5.10.0 - LEISURE UPGRADE **

- Merge in XMRig changes from Jan 2020 through March 2020 (MIP)
- https://github.com/biblepay/xmrig/commit/d47569b2b35802dd63f71b597af996816ca51c9a

Binaries:

https://wiki.biblepay.org/Upgrade_to_RandomX


Please test and let us know if its safe for everyone else to upgrade.  (I've unit tested it and it appears to be 1% faster).
Please also let us know if this resolves the machine language crashes for some people.

[coinsinspect]

** Sanctuary and Chainlocks Bulletin for block 187,000 **


Now that RandomX is stable and our difficulty has surpassed 1.0, we are planning to enable Chain Locks.  This is an exciting moment for Biblepay.

Realize that we are one of the few coins that exist that have chainlocks in Production (Other than Dash, who created it).

And, I believe we are the first Bitcoin based coin to have RandomX.  

In preparation for this, anyone who has a sanctuary, could you please ensure it is up and running?  As, once we enable Chain Locks, we move into strict mode meaning the Sanctuaries will be POSE banned and not paid if they do not respond to quorum requests.  Obviously we want to have a smooth cutover.

Lets shoot for block 187,000.


Update:

We have enabled Spork 17 (Deterministic sanctuary quorums) at block 187,000.

All Sancs seem to be up and none have PoSE score.

I wonder if there is some way to spread these great adoptions (Chainlocks and RandomX) from the PR point of view, to improve Biblepay's project exposure. I don't think there are many coins out there with this level of innovation.

Also, it would be a good hit if our exchanges know about us enabling chainlocks and reduce the number of deposit confirmations. Many investors in exchanges score coins better if they see lower confirmation numbers.

[coinsinspect]

All,

This thread is being moved to:
https://forum.biblepay.org/index.php?topic=517.msg7221#msg7221

Please update your bookmarks.

If you have any questions you can contact Rob who started this thread at rob@biblepay.org.

https://forum.biblepay.org/index.php?topic=517.new#new