BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

*** Foundation.biblepay.org has moved ***


Our foundation web site and randomx pool has moved; the site is now running on our sanctuaries.
We have 40 miners mining:
https://foundation.biblepay.org/bbp/poolabout

If anyone has any questions, please feel free to ask.

Note that our site is now web3 based meaning that you may login with metamask in order to set your nickname or portfolio builder settings.

** Portfolio Builder has upgraded - Action Required **


Unchained.biblepay.org has been migrated to our sanctuaries.  The login technology has been upgraded to use web3 (metamask) in contrast to login credentials.

Because of this, your portfolio builder settings need to be re-entered (otherwise your position(s) will not be showing on the Portfolio Builder Leaderboard in MAINNET).

Please verify that you are on this report if you have a PB position:
https://unchained.biblepay.org/bbp/portfoliobuilderleaderboard


Thanks!

I see confusion in BBP Social medias, or FUD, from users who dual mine (no staking), with regards to the email "Foundation.biblepay.org is moving - Action required".  Glad I'm not the only one 

I see confusion in BBP Social medias, or FUD, from users who dual mine (no staking), with regards to the email "Foundation.biblepay.org is moving - Action required".  Glad I'm not the only one 

That email was strictly to instruct people to withdraw their funds from the old foundation.biblepay.org pool, because our new pool is no longer custodial.

** BiblePay Core Wallet - Mandatory Upgrade by height 346,500 **

BiblePay 0.17.2.5

https://github.com/biblepay/biblepay/releases/tag/0.17.2.5

- Transition to POVS (proof of video streaming)

Press Release:
https://social.biblepay.org/foundation/Images/Press/PressRelease01725.htm

Sanctuary Streaming Example:
https://wiki.biblepay.org/Sanctuary_Streaming

Q:  Can we upgrade early?
A:  Yes

That email was strictly to instruct people to withdraw their funds from the old foundation.biblepay.org pool, because our new pool is no longer custodial.

Thank you for taking the time and patience with me, Rob. I'm either getting older or recent markets have me confused these days. Please disregard or remove that post.

** BiblePay Core Wallet - Mandatory Upgrade by height 346,500 **

BiblePay 0.17.2.5

https://github.com/biblepay/biblepay/releases/tag/0.17.2.5

- Transition to POVS (proof of video streaming)

Press Release:
https://social.biblepay.org/foundation/Images/Press/PressRelease01725.htm

Sanctuary Streaming Example:
https://wiki.biblepay.org/Sanctuary_Streaming

Q:  Can we upgrade early?
A:  Yes

Great work Rob! And thank you to the beta testers!

Is there a guide to setup a POVS sanctuary?

Great work Rob! And thank you to the beta testers!

Is there a guide to setup a POVS sanctuary?

Thanks.

To set up a POVS sanc first create a regular sanc in prod and ensure its Enabled:
https://wiki.biblepay.org/Create_Sanctuary

Then install BMS:
https://wiki.biblepay.org/Install_BMS

At that point you can check the status of the sanc by looking at its status page:
https://your_sanc_IP/BMS/Status


** Important **
The new node must have at least a 400gb hard drive (free space) and 6 core cpu (otherwise it does not meet the minimum spec and will not be paid).

Thanks.

To set up a POVS sanc first create a regular sanc in prod and ensure its Enabled:
https://wiki.biblepay.org/Create_Sanctuary

Then install BMS:
https://wiki.biblepay.org/Install_BMS

At that point you can check the status of the sanc by looking at its status page:
https://your_sanc_IP/BMS/Status


** Important **
The new node must have at least a 400gb hard drive (free space) and 6 core cpu (otherwise it does not meet the minimum spec and will not be paid).

Thanks, that seems fairly straightforward. 

I noticed the setup specifies ubuntu 20.04 LTS. Is there a reason not to use the latest version of ubuntu LTS (long term support)? Meaning ubuntu 22.04 LTS.

** Cameroon one has created Orphan NFTs **

https://foundation.biblepay.org/bbp/nftlistorphans

Thanks, that seems fairly straightforward. 

I noticed the setup specifies ubuntu 20.04 LTS. Is there a reason not to use the latest version of ubuntu LTS (long term support)? Meaning ubuntu 22.04 LTS.

Just that its not tested.  If it works we can adjust the instructions.

** CoinGecko has added BBP Supply Metrics **

https://www.coingecko.com/en/coins/biblepay

** We now have two superblocks per day for Portfolio Builder **


First, to find out what the ROI is for portfolio builder, please see this page:
https://unchained.biblepay.org/bbp/portfoliobuilder

Notice that we now accept "portfolio builder donations".  This allows users who feel charitable to donate to our portfolio builder kitty (any amount they want) and this raises the ROI for all the other participants for 30 days (the donation is split among participants for 30 days).  See the "PB Donations" page for more info.

So realize that you will receive two rewards per day:
One for the base reward matching the PB Leaderboard
One for the excess ROI sourced from donations


May God be pleased with BiblePay.

Dear Rob,

The Hash of biblepay-lin64.zip (linux wallet) does not appear to match the published hash on the website

Published hash                        = 70e0c55f4af8c93f2387e8e91aa56f27972d969b2c633472e1f46bedb53a4214
Newly Downloaded file hash = ac764d5e04e05d7ae1c13a555f01b98bdf35786eb6137261281ff518d32ee03d
Hashes do not match...

Thanks,
oncoapop

Thanks.

To set up a POVS sanc first create a regular sanc in prod and ensure its Enabled:
https://wiki.biblepay.org/Create_Sanctuary

Then install BMS:
https://wiki.biblepay.org/Install_BMS

At that point you can check the status of the sanc by looking at its status page:
https://your_sanc_IP/BMS/Status


** Important **
The new node must have at least a 400gb hard drive (free space) and 6 core cpu (otherwise it does not meet the minimum spec and will not be paid).

Dear Rob,

The Hash of biblepay-lin64.zip (linux wallet) does not appear to match the published hash on the website

Published hash                        = 70e0c55f4af8c93f2387e8e91aa56f27972d969b2c633472e1f46bedb53a4214
Newly Downloaded file hash = ac764d5e04e05d7ae1c13a555f01b98bdf35786eb6137261281ff518d32ee03d
Hashes do not match...

Thanks,
oncoapop

Thanks for pointing that out.

The problem was not any security issue, but that the deploy script somehow lost the permissions to write the hash to the web site.
I fixed the deploy process and redeployed.

The Win64.hash.htm is now c2ba*.
The Lin64.hash.htm is now 648c*.