https://wiki.biblepay.org/index.php?title=Special:NewPages&feed=atom&hideredirs=1&limit=50&offset=&namespace=0&username=&tagfilter=BiblePay Wiki - New pages [en]2024-03-28T17:52:40ZFrom BiblePay WikiMediaWiki 1.31.12https://wiki.biblepay.org/BBP_Intrinsic_ValueBBP Intrinsic Value2024-03-23T14:26:30Z<p>Admin: </p>
<hr />
<div><br />
<br />
<br />
''' What makes BIBLEPAY stand out from the other cryptocurrencies? '''<br />
<br />
<br />
* DEFLATIONARY. We decrease our emissions by 20% per year with a total cap of 5.2B, and a circulating supply of 3.6B. Block emission has decreased from 20K to 2K since inception.<br />
<br />
* HIGHER INVESTMENT LEVERAGE. BiblePay still has 4 zeroes before its BBP-USDT trading price (.0000225 as of March 2024). <br />
<br />
* TITHE 10% to ORPHAN CHARITY. This is our cornerstone and makes it easy for any crypto user to get exposure to sponsoring orphans and doing good things like building water wells. Sponsor an orphan with a BBP NFT, or hold BBP and help orphans.<br />
<br />
* SIDECHAIN. We are an L1 chain with an L2 sidechain allowing you to store files (mp4s, image links, ticket attachments, social media attachments). Display gospel videos and provide theological material.<br />
<br />
* SOCIAL MEDIA. Our site at https://unchained.biblepay.org is being enhanced every month, with more and more web3 features.<br />
<br />
* ADVANCED NFTs (v2): We have NFTs with treasure chests, autonomous settlement, orphan NFTs (soulbound), and our NFTs are versatile enough to be marketed in more than one marketplace.<br />
<br />
* INSTANT GLOBAL SETTLEMENT ON EVERY EXCHANGE: With our atomic trade, you can send any amount to any metamask user globally and have it settled in a block in a few seconds. <br />
<br />
* PHONE SYSTEM: We provide you with a real US phone number and a true long distance phone system with charges to your BBP private key.<br />
<br />
* EASY ACCESS TO WEB3: We make things easier for the user by wrapping high technology smart contracts and providing a UI for access to our ERP features.<br />
<br />
<br />
''' Future '''<br />
<br />
* Our next sidechain (v3.0) is soon to be released. This marries the blockchain with our ERP that provides grantable deterministic permissions and ERP views. <br />
<br />
* This solidifies BiblePay's total value in the crypto space.</div>Adminhttps://wiki.biblepay.org/ERC721bERC721b2024-03-17T11:39:24Z<p>Admin: </p>
<hr />
<div>'''Improving the ERC-721 Spec (ERC-721b)<br />
'''<br />
<br />
'''Reason: '''<br />
<br />
Enhancing the functionality, security, and convenience of NFTs for use on the BiblePay blockchain.<br />
<br />
<br />
'''Current limitations with ERC-721:'''<br />
<br />
<br />
<br />
* Normal NFTs do not support Orphans because they can be re-sold to successive owners (bad in the sense of having a risk of deceiving or cheating the successive user out of the original relationship, and bad morally in the sense that you are reselling a sponsored orphan that you originally committed to). The solution is a Soul Bound NFT; an NFT that cannot be resold, and has a special designation on it allowing us to characterize the NFT as an orphan in showrooms.<br />
<br />
* NFTs cannot be deleted, they live forever. This is a positive trait, however for NFTs that are botched, they will just take more and more precious space in showrooms. The ERC solution is to transfer the NFT to the 0x0DEAD address, thereby filtering it out of active results. <br />
<br />
* NFTs do not protect valuable content. The original ERC721 spec allows anyone with view access to read the json payload and therefore download the contents of every file in the json. Yes, the intrinsic value of the NFT is based on the rarity, but it would be an improvement to be able to encrypt or hide a Treasure Chest that is only revealed to the Owner (IE the purchaser receives this ability after buying). This could be used for license activations, high resolution images, longer videos, crypto rewards, keys etc that are not revealed in the promotional NFT.<br />
<br />
* NFTs require a very high level of trust to the marketplace operator. The normal flow in buying an nft goes like this: You sign the rights off of your entire collection to OpenSea when you list *any* of your NFTs in that collection; the listing price is enforced at their UI level. There is no deterministic custodial account in the ERC721 NFT that holds the funds that proves that a user paid. Instead funds flow from the buyer to OpenSea (IE custodian), then you receive an email asking you to approve the transaction, and then the funds flow from OpenSea to your ERC wallet. This is on the minor end of our problems, but begs for an alternative deterministic solution.<br />
<br />
* The ERC721 spec does not allow for a minimum buy it now price to be set and for autonomous transactions to occur (goes hand in hand with point 4).<br />
<br />
* The ERC721 spec does not allow for a switch that would make the art "marketable" vs "non marketable". This is just a nice to have that would allow the owner to take something off the market temporarily, or hide an NFT without sending it to the dead address. <br />
<br />
<br />
<br />
<br />
<br />
'''Solution (Enhancing the ERC-721 spec to ERC-721b):'''<br />
<br />
<br />
* Modify the ERC721 spec (the OpenZeppelin Solidity contract ERC721.sol) with new enhancements, naming it ERC721b. Derive a BiblePay class for BBP use of the contract, and release the contract opensource when it goes to prod.<br />
<br />
<br />
* Add a public object to the solidity contract that tracks the following objects in maps, on the chain:<br />
<br />
UserBalances<br />
TreasureChest<br />
IsDeleted<br />
IsMarketable<br />
IsSoulBound<br />
BuyItNowAmount<br />
<br />
* Make it so the owner of an NFT, or the authorized NFT operator (permission given by owner in a marketplace) can update an NFTs IsDeleted, IsMarketable, IsSoulBound, and BuyItNow status just by interacting with the contract and paying gas.<br />
<br />
* Make it so the minting platform can set the TreasureChest URL that points to the TreasureChest JSON contents in a secure way, that can only be retrieved by the Owner of the NFT.<br />
The GetTreasureChest method will be protected by the _IsApprovedOrOwner() permission of the NFT, effectively making it impossible for a non-owner to call for the contents until they become the owner.<br />
The contents of the TreasureChest will be created upon minting, obfuscated to a uint256 private URL json file, stored in the BBP sidechain as a link, and set as a private property on the NFT at mint.<br />
<br />
* Make it so that users can deposit offers into the NFT contract securely, and if they decide to not purchase, they can withdraw from the NFT thereby their native currency is safe (minus gas fees).<br />
<br />
* Make it so that if a user has deposited more than the buy it now amount and an NFT is "marketable" and the user decides to BuyItNow, the NFT contract will automatically send the BuyItNow amount to the <br />
last owner, reduce the balance of the purchaser by the buy it now amount, and transfer the NFT to the new owner in a deterministic fashion so the steps cannot fail or leave the NFT and payment in an unknown state.<br />
The new owner will have access to the TreasureChest function, and ability to Edit the BBP fields if they decide to make the nft marketable again. <br />
<br />
* Soul Bound NFTs however, cannot be made marketable again. The SoulBound designation will allow the front end to display Orphans in a friendly way (different captions and sponsor process).<br />
<br />
* If IsDeleted is set to true, the NFT will be hidden (but still exists on the blockchain).<br />
<br />
* If a random user deposits ARB to an ERC721b contract, that balance will be credited to the sending address. The balance will be withdrawable by the original sender, if they call the "Withdraw" function on the contract.<br />
This is the same facility that will allow us to deterministically offer autonomous sales in the marketplace.<br />
<br />
* The ERC721b spec is backwards compatible with ERC721, meaning these same minted NFTs can be set up for sale on OpenSea or other marketplaces.<br />
However, OpenSea will not honor the Deleted flag, or the BuyItNowAmount, or the SoulBound, it will be up to the user to set up the sale in the classic manner. This is an important consideration however, as in the SEO discussion we find it important to maintain both a native NFT showroom and a public (external marketplace) for maximum traffic. <br />
<br />
<br />
<br />
<br />
'''SEO Strategy'''<br />
<br />
<br />
* The initial strategy for release is to create 3 new NFT contracts that capture our broad categories: Christian (God focused NFTs), General (Any other NFT or product or item), Orphan (An orphan to be sponsored for an amount of time as an NFT).<br />
<br />
* The categories derived by each contract drive a 'collection', and therefore the showroom caption (Orphan,Christian, General).<br />
<br />
* The collections can be viewed on OpenSea for external traffic. Those collections can be purchased with ETH inside the opensea marketplace.<br />
<br />
* The collections can be rendered by the BiblePay gallery engine for external HTML static content that leads to Unchained, but cannot be purchased unless the user logs in to unchained.<br />
<br />
* The collections can be rendered by BiblePay gallery as a logged in user, allowing actual BuyItNow with BBP or ARB.<br />
<br />
* In summary, this gives us (2) external SEO sources that we do not have now (OpenSea and our 'marketing' domain that is not released yet that hosts static content that leads to unchained. It also provides (2) ways to purchase an NFT: OpenSea with credit card/ethereum, Or BBP with BBP/ARB.<br />
<br />
* When buying an NFT through OpenSea, the deterministic BuyItNow function will not be called, but instead they will act as custodian and complete the sale.<br />
<br />
* When buying an NFT through BBP, the deterministic BuyItNow will be called, and the NFT will transfer autonomously.</div>Adminhttps://wiki.biblepay.org/ERPERP2024-01-12T00:41:32Z<p>Admin: Created page with "'''Enterprise Resource Planning System''' An ERP system is tightly integrated with a companies back end processes allowing management of core operations. These activities in..."</p>
<hr />
<div>'''Enterprise Resource Planning System'''<br />
<br />
An ERP system is tightly integrated with a companies back end processes allowing management of core operations. These activities include data maintenance pages, accounting, project management, utilities, supply chain processes, reports, compliance etc.<br />
<br />
Some of the common boilerplate functionality that needs to exist in an ERP includes: authentication, permissions to data, permissions to functions, data maintenance pages, field captions, internationalization etc.<br />
<br />
Some of the common features that enterprises demand include video teleconferncing, meetings, phone service, source code management, e-mail hosting, ticket management and collaboration features.<br />
<br />
One place where BBP proposes to enter this space is in the area of custom designed front end business system (ERP) pages.<br />
<br />
Breaking this down into succinct technical features that BBP provides:<br />
- Synchronized Sidechain hosted on our decentralized database (ChainDB)<br />
- Synchronized View per organization-table (ChainDB views)<br />
- Field captions (ChainDB field captions)<br />
- ChainDb hosted ERP pages<br />
- ERP pages hosted from Sanctuaries<br />
<br />
Use Cases:<br />
NFT 2.0 will be hosted on ChainDB. Benefits: Immutable NFTs.<br />
BBP Phone History stored on ChainDB.</div>Adminhttps://wiki.biblepay.org/Building_A_TempleBuilding A Temple2023-07-08T18:48:09Z<p>Admin: </p>
<hr />
<div>A Temple is a collection of 10 Sanctuaries. The first 12 Temples that we Christen will be named after a Tribe of Israel and will receive a special Seal.<br />
<br />
<br />
When you run a temple you are not only helping the BiblePay network by providing a cluster of Ten Sanctuaries (helping the users sync blocks and conduct instant send transactions), but you also act as a CockroachDB database node within the BiblePay Cockroach Cluster. Your node is entrusted to hold our active Orphan Sponsorship list, orphan expenses, orphan revenue records, Gospel Articles and Content, Gospel Wiki Content, Images hosted on our web site (Unchained.biblepay.org), our Wells project, the active Proposals and Voting records, Phone call transactions, and other database transactions. <br />
<br />
<br />
Note that Temples are rewarded at the same rate as other sanctuaries so the Temple operator is not earning more rewards than the average sanctuary owner, it is more of a community service position.<br />
<br />
<br />
<br />
''' Step 1 - Build a Single BiblePay Node '''<br />
<br />
For clarity, please build your temple as the root user, and build the temple in the folder "/biblepay".<br />
<br />
Rent an Unbuntu 20 VMS from your favorite VMS provider with a minimum of 6 cores, 600gb hard drive and 16gb of ram (these requirements ensure that the temple will not slow down the cockroachdb cluster and will<br />
be able to service the ten sanctuary instances, and most importantly will allow the temple to handle future Video traffic and cache storage for our gospel videos feature and upcoming social media features such as Deliverance Rooms ) .<br />
<br />
Follow these instructions to build biblebay:<br />
https://github.com/biblepay/biblepay/blob/master/BuildBiblePay.txt<br />
<br />
If you built biblepay in the /biblepay directory, you should find your biblepayd dameon here:<br />
/biblepay/biblepay/src/biblepayd<br />
If not, you can download the binary from the biblepay web site and copy it here, this way the rest of this guide will match.<br />
<br />
''' Step 2 - Set up 10 Sanctuaries to become a Potential Temple '''<br />
<br />
To be a temple, you will need to override the biblepayd settings with special values that will allow it to write to custom data folders and read custom configuration settings.<br />
For easy maintenance, in this guide I put all of your biblepay block data in /data and all of your biblepay configurations in /configs.<br />
First create configs directories:<br />
<br />
cd /<br />
mkdir /configs<br />
mkdir /data<br />
mkdir /data/biblepay1<br />
mkdir /data/biblepay2<br />
mkdir /data/biblepay3<br />
mkdir /data/biblepay4<br />
mkdir /data/biblepay5<br />
mkdir /data/biblepay6<br />
mkdir /data/biblepay7<br />
mkdir /data/biblepay8<br />
mkdir /data/biblepay9<br />
mkdir /data/biblepay10<br />
cd /configs<br />
<br />
<br />
nano biblepay1.conf<br />
shrinkdebugfile=1<br />
datadir=/data/biblepay1<br />
masternodeblsprivkey=your_bls_privkey<br />
port=40000<br />
rpcport=20000<br />
<br />
<br />
Save the file (ctrl-x, shift-Y, enter)<br />
<br />
<br />
Copy this biblepay1.conf file 10 times to:<br />
<br />
<br />
biblepay1.conf, biblepay2.conf, biblepay3.conf ... biblepay10.conf<br />
<br />
<br />
(IE type: )<br />
<br />
cp biblepay1.conf biblepay2.conf<br />
<br />
cp biblepay1.conf biblepay3.conf<br />
<br />
cp biblepay1.conf biblepay4.conf<br />
... <br />
Stopping with<br />
cp biblepay1.conf biblepay10.conf<br />
<br />
<br />
<br />
Next, edit each file by using nano, and set the following values:<br />
<br />
<br />
For biblepay1.conf, ensure the port=40000 and the rpcport=20001<br />
<br />
For biblepay2.conf, ensure the port=10002 and the rpcport=20002<br />
<br />
... (Continue this pattern for files 3 through 9).<br />
<br />
<br />
For biblepay10.conf, ensure the port=10010 and the rpcport=20010.<br />
<br />
<br />
<br />
<br />
Edit the your_bls_privkey with the privkey of the sanctuary that you set up in "EasySanc".<br />
<br />
The general rule for the "port" is your first sanc (biblepay1) must have a port of 40000 (this allows outside nodes to find you), <br />
but, each successive sanc from sanc2-sanc10 must have a port of 10002-10010 (as other sancs will pose ban you otherwise. )<br />
<br />
The rule for "rpcport" is they should be unique, starting with 20001 and working up to 20010 (they must be unique, otherwise the node will not start).<br />
<br />
<br />
Firewall Changes:<br />
<br />
In this section simply expose :<br />
<br />
sudo ufw allow 10002<br />
sudo ufw allow 10003<br />
sudo ufw allow 10004<br />
sudo ufw allow 10005<br />
sudo ufw allow 10006<br />
sudo ufw allow 10007<br />
sudo ufw allow 10008<br />
sudo ufw allow 10009<br />
sudo ufw allow 10010<br />
sudo ufw allow 40000<br />
<br />
<br />
''' Start the Nodes and verify each one syncs and acts as a Sanctuary '''<br />
<br />
<br />
Write a script to launch your nodes so you dont need to manually launch each node in the case of a reboot etc:<br />
<br />
cd /configs<br />
<br />
nano startbiblepayd.sh<br />
<br />
/biblepay/biblepay/src/biblepayd -conf=/configs/biblepay1.conf<br />
/biblepay/biblepay/src/biblepayd -conf=/configs/biblepay2.conf<br />
/biblepay/biblepay/src/biblepayd -conf=/configs/biblepay3.conf<br />
/biblepay/biblepay/src/biblepayd -conf=/configs/biblepay4.conf<br />
/biblepay/biblepay/src/biblepayd -conf=/configs/biblepay5.conf<br />
/biblepay/biblepay/src/biblepayd -conf=/configs/biblepay6.conf<br />
/biblepay/biblepay/src/biblepayd -conf=/configs/biblepay7.conf<br />
/biblepay/biblepay/src/biblepayd -conf=/configs/biblepay8.conf<br />
/biblepay/biblepay/src/biblepayd -conf=/configs/biblepay9.conf<br />
/biblepay/biblepay/src/biblepayd -conf=/configs/biblepay10.conf<br />
<br />
<br />
ctrl-X, Shift-Y <enter> (to save the file)<br />
<br />
<br />
chmod 777 startbiblepayd.sh<br />
<br />
To start the nodes simply run the startbiblepayd.sh file by doing this:<br />
<br />
cd /configs<br />
./startbiblepayd.sh<br />
<br />
<br />
<br />
<br />
''' Check if BiblePay is synced '''<br />
<br />
cd /biblepay/biblepay/src<br />
<br />
biblepay-cli -conf=/configs/biblepay1.conf getblockchaininfo<br />
<br />
This command should respond with the synced number of blocks<br />
<br />
<br />
<br />
''' Check if each node is running as a sanctuary '''<br />
<br />
biblepay-cli -conf=/configs/biblepay1.conf masternode status<br />
<br />
This should respond with outpoint info if masternode is running.</div>Adminhttps://wiki.biblepay.org/Free_Phone_Calls_for_New_UsersFree Phone Calls for New Users2023-07-04T15:12:29Z<p>Admin: </p>
<hr />
<div><br />
BiblePay is giving away 125,000 BBP for free phone calls to our new users!<br />
<br />
Simply follow these directions:<br />
<br />
1. Download the BiblePay Desktop Wallet from here:<br />
https://biblepay.org/biblepay-win64.exe<br />
<br />
2. Install the Wallet<br />
<br />
3. Launch the wallet and sync the block chain<br />
<br />
4. Sync the wallet (allow the blocks to sync to height 431,000+)<br />
<br />
5. Click on the Unchained button from the left menu (this launches the Unchained Application)<br />
<br />
6. Click on Softphone (this is our built in BBP softphone that allows you to call anywhere in the world!)<br />
Copy your BBP address to the clipboard<br />
<br />
7. Email rob@biblepay.org with your address and he will send you your Free BBP so that you can make long distance phone calls for free.</div>Adminhttps://wiki.biblepay.org/Activate_Hardware_PhoneActivate Hardware Phone2023-06-24T18:19:16Z<p>Admin: Created page with "''' How do I get my new telephone (hardware)? ''' Our plan is to support multiple phone models. Our first entry level phone can be purchased on Amazon here: https://www.ama..."</p>
<hr />
<div>''' How do I get my new telephone (hardware)? '''<br />
<br />
Our plan is to support multiple phone models.<br />
<br />
Our first entry level phone can be purchased on Amazon here:<br />
<br />
https://www.amazon.com/Grandstream-Business-Single-account-GXP1610/dp/B01318HLCC/<br />
<br />
<br />
Once you have the phone, unpack it, plug a cat5 network cable from the phone to your LAN jack and turn it on.<br />
<br />
Verify it boots up and obtains an IP address. It will display its IP address on the screen.<br />
<br />
<br />
<br />
<br />
''' How do I provision the phone for the BBP network? '''<br />
<br />
<br />
Navigate a web browser from your home PC to the IP address on the phone.<br />
<br />
For example, if the IP is 192.168.1.2, then go to this web address:<br />
<br />
http://192.168.1.2<br />
<br />
Once there, it will ask you the username and password.<br />
Enter admin for the username<br />
Enter admin for the password<br />
<br />
<br />
To provision the phone, open the unchained application by clicking on Unchained from the BiblePay Core wallet.<br />
<br />
This will open the Unchained app. In that app, click Phone | Hardware Settings.<br />
<br />
You can now find the answers to each of the provision questions by filling in the values presented on the screen.<br />
<br />
You must have more than 10,000 BBP in your phone account to provision your phone (there is no cost associated with this).<br />
<br />
Once you populate the answers into the phone (by filling each of the grid value answers), your phone will move to Registered and display your name.<br />
<br />
Now you can make calls. You can also take your phone with you on vacation, and your phone number will stay with you and you can make calls from any internet jack.</div>Adminhttps://wiki.biblepay.org/BiblePay_EmailBiblePay Email2023-06-11T15:36:11Z<p>Admin: </p>
<hr />
<div>''' How to Create a BiblePay E-Mail Account '''<br />
<br />
From Unchained desktop, navigate to E-Mail | E-Mail Maintenance.<br />
<br />
Specify the E-Mail username you would like to use, without the @biblepay.org suffix.<br />
<br />
Click Submit.<br />
<br />
Note that you must have at least 1000 BBP in your unchained wallet.<br />
<br />
Once provisioned, you will immediately see the e-mail client settings that are used to set up the home e-mail client. Now you can set up your home e-mail client (IE Outlook, Mozilla Thunderbird) or your iPhone etc (See below).<br />
<br />
The password for your e-mail account is the private key of your Unchained wallet address (to get the password, type 'dumpprivkey unchained_pub_key' from the command line of the wallet).<br />
<br />
<br />
<br />
<br />
''' How to Set Up BiblePay E-Mail with Thunderbird '''<br />
<br />
From Thunderbird, click on Tools | Account Settings.<br />
<br />
Populate the Account Name and the "Your Name" to be your preferred human readable account names.<br />
<br />
Populate E-Mail address to be your new UserName + @biblepay.org.<br />
<br />
<html><br />
<img src='Https://seven.biblepay.org/img/Thunderbird/Thunder1.png' /><br />
</html><br />
<br />
<br />
<br />
Click Server Settings - Here is where you populate the IMAP settings:<br />
<br />
Populate Server Type = IMAP<br />
<br />
Server Name = seven.biblepay.org<br />
<br />
User Name = Your BBP username @biblepay.org<br />
<br />
Port = 993<br />
<br />
Security = SSL/TLS<br />
<br />
Auth Method = Normal<br />
<br />
<br />
<br />
<br />
<html><br />
<img src='Https://seven.biblepay.org/img/Thunderbird/Thunder2.png' /><br />
</html><br />
<br />
<br />
Click Outgoing Server - this is where you set the SMTP settings:<br />
<br />
Click Add<br />
<br />
Server Name = seven.biblepay.org<br />
<br />
User Name = Your BBP username @biblepay.org<br />
<br />
Port = 465<br />
<br />
Security = SSL/TLS<br />
<br />
Auth Method = Normal<br />
<br />
<br />
<br />
<html><br />
<img src='Https://seven.biblepay.org/img/Thunderbird/Thunder3.png' /><br />
</html><br />
<br />
<br />
<br />
<br />
''' How to Setup BiblePay E-Mail with Outlook '''<br />
<br />
<br />
<br />
<html><br />
<img src='Https://seven.biblepay.org/img/Thunderbird/Outlook1.png' /><br />
</html></div>Adminhttps://wiki.biblepay.org/Red_Sea_User_GuideRed Sea User Guide2023-05-20T17:45:16Z<p>Admin: </p>
<hr />
<div><br />
'''Introduction'''<br />
<br />
BiblePay has moved features away from the web and to the Unchained Desktop Application. The Unchained Desktop App is part of the BiblePay core wallet, however it lives in its own EXE (executable program). It is connected to the wallet through one core-wallet wallet keypair to Unchained Desktop: The key label 'Unchained'. This allows Unchained to provide features such as video tipping, NFT purchases, file storage charges, and the BiblePay Phone System.<br />
<br />
<br />
''' How to associate the Core Wallet with Unchained '''<br />
<br />
When you launch unchained for the first time, the core wallet will automatically provision the 'Unchained' key for you. You will need to send funds to that key in order to spend in Unchained.<br />
<br />
<br />
<br />
''' How To Launch Unchained '''<br />
<br />
Click the Unchained button from the left menu.<br />
<br />
<br />
''' BiblePay Phone System '''<br />
<br />
We are happy to announce the first Blockchain Phone Service. With the BiblePay Phone system, you get a real US phone number attached to your BBP keypair. Our softphone allows you to make and receive phone calls globally from real PSTN phone numbers and to real PSTN phone numbers at an extremely low rate per minute (1.9 cents per minute) for long distance. You can call any country in the world for this low rate. In version 1.0, the phone service works as a softphone where you wear your headset. In version 2.0 (coming soon) you can use a hardware phone as well.<br />
<br />
<br />
''' How do I provision my BiblePay Phone? '''<br />
<br />
1. Launch Unchained Desktop<br />
<br />
2. Verify your Balance is > 5000 BBP<br />
<br />
3. Click on Phone Service<br />
<br />
4. Choose a Phone Region and Area Code.<br />
<br />
5. BiblePay will provide a real phone number.<br />
<br />
6. Make a test call.<br />
<br />
7. Your assigned phone number will always be visible from the Phone Service page.<br />
<br />
<br />
<br />
''' Online Sancs (Active Hosted Sanctuaries/Techies) vs Offline Sancs (Investors) '''<br />
<br />
We have two modes. Online Sancs are designed for enthusiasts who want to host a sanctuary on a VM and earn the full 100% reward.<br />
These sanctuaries actively help the network by ensuring nodes are available to supply blocks, they perform Sanctuary Mining, and they take part in running our Cockroach Database and help host the phone system.<br />
<br />
Offline Sancs (Investor Sancs) are sanctuaries that are always offline. They do not participate in servicing the users, but they do help maintain our price by holding a stake in a sanctuary investment.<br />
<br />
Both types of sancs require the same collateral: 4,500,001 BBP.<br />
<br />
The Online sanc receives a 100% reward while the offline sanc receives a 50% reward.<br />
<br />
<br />
''' How to Create a Sanctuary '''<br />
<br />
Regardless whether you want an Investor sanc or an active sanc, you can follow these instructions to create a new sanc:<br />
<br />
https://wiki.biblepay.org/EasySanc<br />
<br />
Once the sanctuary is running, you will receive a full reward if it is hosted. If it falls into the INVESTOR state you will receive half of the reward.<br />
Note, investors will need to set a key in their biblepay.conf file: revivesanctuaries=1.<br />
This key will cause the biblepay wallet to revive your investor sancs once per day.<br />
You will need to leave the home controller wallet running so that biblepay can revive your sanctuaries. Also, your wallet needs to be unlocked so that BBP can send out a revival transaction.<br />
<br />
<br />
Thank you for Using BiblePay!</div>Admin