Topic: BiblePay (BBP) | 10% Charity | POW/POS | CPU Only | Masternode | No Premine (Read 2358 times)

** BBP-Xmrig 5.10.1 - Mandatory Upgrade for Miners **

---

- Remove automatic tithing from the miner

* Note:  The old version of the miner tithes 10%.  Please start using the new version, as the pool now holds back the 10% orphan-tithe automatically.

Binaries:
https://wiki.biblepay.org/Upgrade_to_RandomX

** Mac is still building, MIP will notify

btw: some tipps for xmrig:

• use the number of physical threads your System has, which is 12 (2x6), not 24
• for slightly better performance enable "hugepages" in your system or start the miner as root (xmrig can configure RAM itself)
• for even better performance you could enable "1GB-hugepages" (just google xmrig 1gb-hugepages ubuntu), but this would require a lot more RAM than you currently have (at least 40 GB)

Fractional sancs are now ready to test at foundation.biblepay.org.

Note that I plan on making a cool dashboard that shows a gauge of the ROI (kind of like GIN had), and the current daily ROI and stuff, but have not gotten a chance to do it yet.
But the basics should work now - and the rewards are live.  (We have one sanctuary in the farm - that I am lending to the foundation for this project, and of course we support unlimited scalability as we grow).

So here is how you test it:
- Log In
- Ensure you have a credit balance
- Navigate to Fractional Sancs
- Populate the amount you want to invest, and click Add fractional sanc.
- Wait 24 hours
- Then you should see a daily reward appear in the list, and your Foundation balance should increase.

So the main point of this is to not only let the small investor buy a fraction of a sanc and earn rewards, but also for someone on southexchange to easily create an account and a position in 5 minutes and hold it in biblepay to get the 40% ROI, etc.

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 [email protected].

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.

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

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.

Where do people download the bbp xmrig software again?

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

Is this the best location?

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

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

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

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

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

I use this:


For biblepay miner:

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

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

Automatic works fine.

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.

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

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.

Android mobile wallet version 1.4.8.5

- added new tithe feature screen

iOS version will come in a few days

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?

** PODC 2.0 FAUCET RELEASED **


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


Alt link:

https://web.biblepay.org

Click Faucet

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.

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').

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

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

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

#!/bin/bash
# checkprocess.sh

PROCESS=

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

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.

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.

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

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

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

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://bitcointalksearch.org/topic/m.51695886
https://www.reddit.com/r/BiblePay/comments/clyxyc/upgrading_masternodes_sanctuaries_to/
https://forum.biblepay.org/index.php?topic=391.msg5968#msg5968

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

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.

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.

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

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

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

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

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

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.

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

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

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.

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

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

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

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.

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

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

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

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

Apollon Network

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

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.

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

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

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

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

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

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

What happened to "I Love You Togo." ?



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

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

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

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

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

https://bitcointalksearch.org/topic/biblepay-10-to-orphan-charity-randomx-mining-sanctuaries-masternodes-2388064

Why is the new thread opened?