https://wiki.biblepay.org/api.php?action=feedcontributions&user=Admin&feedformat=atomBiblePay Wiki - User contributions [en]2024-03-29T15:07:10ZUser contributionsMediaWiki 1.31.12https://wiki.biblepay.org/index.php?title=BBP_Intrinsic_Value&diff=6951BBP Intrinsic Value2024-03-24T14:49:39Z<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/index.php?title=BBP_Intrinsic_Value&diff=6950BBP Intrinsic Value2024-03-24T14:49:19Z<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 use 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/index.php?title=BBP_Intrinsic_Value&diff=6949BBP Intrinsic Value2024-03-24T14:47:52Z<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 have dual sourced SEO.<br />
<br />
* INSTANT GLOBAL SETTLEMENT ON EVERY EXCHANGE: With our atomic trade, you can send any amount to any metamask use 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/index.php?title=BBP_Intrinsic_Value&diff=6948BBP Intrinsic Value2024-03-24T14:44:37Z<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 />
* 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/index.php?title=BBP_Intrinsic_Value&diff=6947BBP Intrinsic Value2024-03-23T14:30:25Z<p>Admin: </p>
<hr />
<div><br />
'''The Naysers'''<br />
<br />
<br />
Naysayers argue that small blockchains, like BBP are worthless because the world already has Bitcoin. Why create another blockchain when Bitcoin is available that allows you to transact large values efficiently on thousands of exchanges.<br />
<br />
<br />
''' The Argument for BBP '''<br />
<br />
However, there are certain elements in the BBP ecosystem that are novel and useful. Remember the original deflation argument that when a currency is emitting coins at a decreasing rate, versus the behavior of central banks that are printing money at an alarming rate? The argument is that the safer place is in a deflationary environment. There is no central bank that can change the emission characteristics of BBP. We have set our chain parameters in the genesis block that dictate that we will have 5.2B coins circulating in total, at a decreasing emission rate of 20% per year. We have emitted 3.6B of those 5.2B coins (starting at blocks that were 18,000 BBP and now we have blocks that are 2,000 BBP). <br />
<br />
<br />
Bitcoin has experienced 50% of its all time sensationalism. Bitcoin is awesome, as they wrote the whitepaper and established a foundation for us. There is a place for bitcoin. However investors need to place a portion of their hard earned money in chains that have large growth potential. We know with the new ETFs and halving, Bitcoin could absolutely double again. But smaller tokens like Shiba Inu and BiblePay still have 4 zeroes in front of their price, therefore have more leverage. The difference is chasing a 2* potential increase vs a 100* potential increase. But this also has to be done prudently and only in chains you believe have potential.<br />
<br />
<br />
<br />
<br />
'''Points:'''<br />
<br />
<br />
* We tithe 10% to orphan charity and have since inception. This of course is our cornerstone and makes it very easy for any crypto user to get exposure to sponsoring orphans or doing good things like building water wells. A crypto user can: Buy ARB or Doge anywhere, cross chain swap that to BBP, sponsor an orphan NFT, or simply hold BBP in a sanctuary which helps our network and pays a reward to the sanctuary.<br />
<br />
* Real world use cases: Our sidechain allows you to store large files (mp4s, image links, ticket attachments, social media attachments) and while paying small storage fees in BBP, you can use those links to mint NFTs or make social media posts. We have a feature in Unchained that displays gospel videos for channels. We provide Christian theological material in Unchained as well.<br />
<br />
* Phone system: A true long distance phone embedded in your unchained wallet that is charged to your BBP private key, with a real US phone number.<br />
<br />
* Making things easier for the user: Our features wrap the technology in a way that makes it easy for the end user. You dont need to know about the technical details to interact with smart contracts.<br />
<br />
<br />
''' Future '''<br />
<br />
* Our best technological feature, the sidechain v3.0 is soon to be released. This provides an ERP system that is bound to our L1 chain, with grantable deterministic permissions. The chain will drive the ERP views. This solidifies BiblePay's total value in the crypto space.</div>Adminhttps://wiki.biblepay.org/index.php?title=BBP_Intrinsic_Value&diff=6946BBP Intrinsic Value2024-03-23T14:29:55Z<p>Admin: </p>
<hr />
<div><br />
'''The Naysers'''<br />
<br />
<br />
Naysayers argue that small blockchains, like BBP are worthless because the world already has Bitcoin. Why create another blockchain when Bitcoin is available that allows you to transact large values efficiently on thousands of exchanges.<br />
<br />
<br />
''' The Argument for BBP '''<br />
<br />
However, there are certain elements in the BBP ecosystem that are novel and useful. Remember the original deflation argument that when a currency is emitting coins at a decreasing rate, versus the behavior of central banks that are printing money at an alarming rate? The argument is that the safer place is in a deflationary environment. There is no central bank that can change the emission characteristics of BBP. We have set our chain parameters in the genesis block that dictate that we will have 5.2B coins circulating in total, at a decreasing emission rate of 20% per year. We have emitted 3.6B of those 5.2B coins (starting at blocks that were 18,000 BBP and now we have blocks that are 2,000 BBP). <br />
<br />
<br />
Bitcoin has experienced 50% of its all time sensationalism. Bitcoin is awesome, as they wrote the whitepaper and established a foundation for us. There is a place for bitcoin. However investors need to place a portion of their hard earned money in chains that have large growth potential. We know with the new ETFs and halving, Bitcoin could absolutely double again. But smaller tokens like Shiba Inu and BiblePay still have 4 zeroes in front of their price, therefore have more leverage. The difference is chasing a 2* potential increase vs a 100* potential increase. But this also has to be done prudently and only in chains you believe have potential.<br />
<br />
<br />
<br />
<br />
'''Points:'''<br />
<br />
<br />
* We tithe 10% to orphan charity and have since inception. This of course is our cornerstone and makes it very easy for any crypto user to get exposure to sponsoring orphans or doing good things like building water wells. A crypto user can: Buy ARB or Doge anywhere, cross chain swap that to BBP, sponsor an orphan NFT, or simply hold BBP in a sanctuary which helps our network and pays a reward to the sanctuary.<br />
<br />
* Real world use cases: Our sidechain allows you to store large files (mp4s, image links, ticket attachments, social media attachments) and while paying small storage fees in BBP, you can use those links to mint NFTs or make social media posts. We have a feature in Unchained that displays gospel videos for channels. We provide Christian theological material in Unchained as well.<br />
<br />
* Phone system: A true long distance phone embedded in your unchained wallet that is charged to your BBP private key, with a real US phone number.<br />
<br />
* Making things easier for the user: Our features wrap the technology in a way that makes it easy for the end user. You dont need to know about the technical details of interactive with smart contracts.<br />
<br />
<br />
''' Future '''<br />
<br />
* Our best technological feature, the sidechain v3.0 is soon to be released. This provides an ERP system that is bound to our L1 chain, with grantable deterministic permissions. The chain will drive the ERP views. This solidifies BiblePay's total value in the crypto space.</div>Adminhttps://wiki.biblepay.org/index.php?title=BBP_Intrinsic_Value&diff=6945BBP Intrinsic Value2024-03-23T14:27:19Z<p>Admin: </p>
<hr />
<div><br />
'''The Naysers'''<br />
<br />
<br />
Naysayers argue that small blockchains, like BBP are worthless because the world already has Bitcoin. Why create another blockchain when Bitcoin is available that allows you to transact large values efficiently on thousands of exchanges.<br />
<br />
<br />
''' The Argument for BBP '''<br />
<br />
However, there are certain elements in the BBP ecosystem that are novel and useful. Remember the original deflation argument that when a currency is emitting coins at a decreasing rate, versus the behavior of central banks that are printing money at an alarming rate? The argument is that the safer place is in a deflationary environment. There is no central bank that can change the emission characteristics of BBP. We have set our chain parameters in the genesis block that dictate that we will have 5.2B coins circulating in total, at a decreasing emission rate of 20% per year. We have emitted 3.6B of those 5.2B coins (starting at blocks that were 18,000 BBP and now we have blocks that are 2,000 BBP). <br />
<br />
<br />
Bitcoin has experienced 50% of its all time sensationalism. Bitcoin is awesome, as they wrote the whitepaper and established a foundation for us. There is a place for bitcoin. However investors need to place a portion of their hard earned money in chains that have large growth potential. We know with the new ETFs and halving, Bitcoin could absolutely double again. But smaller tokens like Shiba Inu and BiblePay still have 4 zeroes in front of their price, therefore have more leverage. The difference is chasing a 2* potential increase vs a 100* potential increase. But this also has to be done prudently and only in chains you believe have potential.<br />
<br />
<br />
<br />
<br />
'''Points:'''<br />
<br />
<br />
* We tithe 10% to orphan charity and have since inception. This of course is our cornerstone and makes it very easy for any crypto user to get exposure to sponsoring orphans or doing good things like building water wells. A crypto user can: Buy ARB or Doge anywhere, cross chain swap that to BBP, sponsor an orphan NFT, or simply hold BBP in a sanctuary which helps our network and pays a reward to the sanctuary.<br />
<br />
* Real world use cases: Our sidechain allows you to store large files (mp4s, image links, ticket attachments, social media attachments) and while paying small storage fees in BBP, you can use those links to mint NFTs or make social media posts. We have a connection to Rumble that displays gospel videos. We provide gospel media in Unchained.<br />
<br />
* Phone system: A true long distance phone embedded in your unchained wallet that is charged to your BBP private key, with a real US phone number.<br />
<br />
* Making things easier for the user: Our features wrap the technology in a way that makes it easy for the end user. You dont need to know about the technical details of interactive with smart contracts.<br />
<br />
<br />
''' Future '''<br />
<br />
* Our best technological feature, the sidechain v3.0 is soon to be released. This provides an ERP system that is bound to our L1 chain, with grantable deterministic permissions. The chain will drive the ERP views. This solidifies BiblePay's total value in the crypto space.</div>Adminhttps://wiki.biblepay.org/index.php?title=BBP_Intrinsic_Value&diff=6944BBP Intrinsic Value2024-03-23T14:26:30Z<p>Admin: Created page with " '''The Naysers''' Naysayers argue that small blockchains, like BBP are worthless because the world already has Bitcoin. Why create another blockchain when Bitcoin is availa..."</p>
<hr />
<div><br />
'''The Naysers'''<br />
<br />
Naysayers argue that small blockchains, like BBP are worthless because the world already has Bitcoin. Why create another blockchain when Bitcoin is available that allows you to transact large values efficiently on thousands of exchanges.<br />
<br />
''' The Argument for BBP '''<br />
<br />
However, there are certain things in the BBP ecosystem that is novel and useful. Remember the original deflation argument that when a currency is emitting coins at a decreasing rate, versus the behavior of central banks that are printing money at an alarming rate? The argument is that the safer place is in a deflationary environment. There is no central bank that can change the emission characteristics of BBP. We have set our chain parameters in the genesis block that dictate that we will have 5.2B coins circulating in total, at a decreasing emission rate of 20% per year. We have emitted 3.6B of those 5.2B coins (starting at blocks that were 18,000 BBP and now we have blocks that are 2,000 BBP). <br />
<br />
<br />
Bitcoin has experienced 50% of its all time sensationalism. Bitcoin is awesome, as they wrote the whitepaper and established a foundation for us. There is a place for bitcoin. However investors need to place a portion of their hard earned money in chains that have large growth potential. We know with the new ETFs and halving, Bitcoin could absolutely double again. But smaller tokens like Shiba Inu and BiblePay still have 4 zeroes in front of their price, therefore have more leverage. The difference is chasing a 2* potential increase vs a 100* potential increase. But this also has to be done prudently and only in chains you believe have potential.<br />
<br />
<br />
<br />
<br />
'''Points:'''<br />
<br />
<br />
* We tithe 10% to orphan charity and have since inception. This of course is our cornerstone and makes it very easy for any crypto user to get exposure to sponsoring orphans or doing good things like building water wells. A crypto user can: Buy ARB or Doge anywhere, cross chain swap that to BBP, sponsor an orphan NFT, or simply hold BBP in a sanctuary which helps our network and pays a reward to the sanctuary.<br />
<br />
* Real world use cases: Our sidechain allows you to store large files (mp4s, image links, ticket attachments, social media attachments) and while paying small storage fees in BBP, you can use those links to mint NFTs or make social media posts. We have a connection to Rumble that displays gospel videos. We provide gospel media in Unchained.<br />
<br />
* Phone system: A true long distance phone embedded in your unchained wallet that is charged to your BBP private key, with a real US phone number.<br />
<br />
* Making things easier for the user: Our features wrap the technology in a way that makes it easy for the end user. You dont need to know about the technical details of interactive with smart contracts.<br />
<br />
<br />
''' Future '''<br />
<br />
* Our best technological feature, the sidechain v3.0 is soon to be released. This provides an ERP system that is bound to our L1 chain, with grantable deterministic permissions. The chain will drive the ERP views. This solidifies BiblePay's total value in the crypto space.</div>Adminhttps://wiki.biblepay.org/index.php?title=ERC721b&diff=6943ERC721b2024-03-17T12:00:00Z<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/index.php?title=ERC721b&diff=6942ERC721b2024-03-17T11:58:57Z<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. Maybe its something they are holding on to and deciding on.<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/index.php?title=ERC721b&diff=6941ERC721b2024-03-17T11:51:59Z<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 provide 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. Maybe its something they are holding on to and deciding on.<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/index.php?title=ERC721b&diff=6940ERC721b2024-03-17T11:39:24Z<p>Admin: Created page with "'''Improving the ERC-721 Spec (ERC-721b) ''' '''Reason: ''' Enhancing the functionality, security, and convenience of NFTs for use on the BiblePay blockchain. '''Current..."</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 provide 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. Maybe its something they are holding on to and deciding on.<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, <br />
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.<br />
It is discouraged to list a single NFT in multiple places, however if the NFT is sold in one marketplace it will dissapear from ownership in another since it ties back to the same NFT object on the chain.</div>Adminhttps://wiki.biblepay.org/index.php?title=ERP&diff=6939ERP2024-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/index.php?title=Free_Phone_Calls_for_New_Users&diff=6938Free Phone Calls for New Users2023-07-09T17:35:14Z<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/index.php?title=Building_A_Temple&diff=6937Building A Temple2023-07-08T19:12:55Z<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/index.php?title=Building_A_Temple&diff=6936Building A Temple2023-07-08T19:10:49Z<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 />
biblepay1.conf, biblepay2.conf ... biblepay10.conf<br />
(IE type:<br />
cp biblepay1.conf biblepay2.conf<br />
cp biblepay1.conf biblepay3.conf<br />
... <br />
)<br />
<br />
Edit each file by using nano, and set the following values:<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 />
For biblepay10.conf, ensure the port=10010 and the rpcport=20010<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 />
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/index.php?title=Building_A_Temple&diff=6935Building A Temple2023-07-08T19:08:12Z<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 />
biblepay1.conf, biblepay2.conf ... biblepay10.conf<br />
(IE type:<br />
cp biblepay1.conf biblepay2.conf<br />
cp biblepay1.conf biblepay3.conf<br />
... <br />
)<br />
<br />
Edit each file by using nano, and set the following values:<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 />
For biblepay10.conf, ensure the port=10010 and the rpcport=20010<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 />
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 />
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 />
ctrl-X, Shift-Y <enter><br />
chmod 777 startbiblepayd.sh<br />
<br />
<br />
''' Check if BiblePay is synced '''<br />
<br />
cd /biblepay/biblepay/src<br />
biblepay-cli -conf=/configs/biblepay1.conf getblockchaininfo<br />
<br />
This should respond with the synced number of blocks<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/index.php?title=Building_A_Temple&diff=6934Building A Temple2023-07-08T19:05:30Z<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 />
biblepay1.conf, biblepay2.conf ... biblepay10.conf<br />
(IE type:<br />
cp biblepay1.conf biblepay2.conf<br />
cp biblepay1.conf biblepay3.conf<br />
... <br />
)<br />
<br />
Edit each file by using nano, and set the following values:<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 />
For biblepay10.conf, ensure the port=10010 and the rpcport=20010<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-10010<br />
sudo ufw allow 40000<br />
<br />
<br />
''' Start the Nodes and verify each one syncs and acts as a Sanctuary '''<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 />
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 />
ctrl-X, Shift-Y <enter><br />
chmod 777 startbiblepayd.sh<br />
<br />
<br />
''' Check if BiblePay is synced '''<br />
<br />
cd /biblepay/biblepay/src<br />
biblepay-cli -conf=/configs/biblepay1.conf getblockchaininfo<br />
<br />
This should respond with the synced number of blocks<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/index.php?title=Building_A_Temple&diff=6933Building A Temple2023-07-08T18:52:32Z<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 />
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 />
biblepay1.conf, biblepay2.conf ... biblepay10.conf<br />
(IE type:<br />
cp biblepay1.conf biblepay2.conf<br />
cp biblepay1.conf biblepay3.conf<br />
... <br />
)<br />
<br />
Edit each file by using nano, and set the following values:<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 />
For biblepay10.conf, ensure the port=10010 and the rpcport=20010<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-10010<br />
sudo ufw allow 40000</div>Adminhttps://wiki.biblepay.org/index.php?title=Building_A_Temple&diff=6932Building A Temple2023-07-08T18:48:38Z<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 a configs directory:<br />
cd /<br />
mkdir /configs<br />
mkdir /data<br />
cd /configs<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 />
Save the file (ctrl-x, shift-Y, enter)<br />
<br />
Copy this file 10 times to:<br />
biblepay1.conf, biblepay2.conf ... biblepay10.conf<br />
Edit each file and set the following values:<br />
For biblepay1.conf, ensure the port=40000 and the rpcport=20001<br />
For biblepay2.conf, ensure the port=10002 and the rpcport=20002<br />
...<br />
For biblepay10.conf, ensure the port=10010 and the rpcport=20010<br />
Edit the your_bls_privkey with the privkey of the sanctuary that you set up in "EasySanc".<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), but, each successive sanc from sanc2-sanc10 must have a port of 10002-10010 (as other sancs whitelist this port, ports outside of the 100NN range are POSE banned. )<br />
The rule for "rpcport" is they should be unique, starting with 20001 and working up to 20010 (there is no rule for RPCport except that it must be unique, otherwise the node will not start).<br />
<br />
Firewall Changes:<br />
In this section simply expose <br />
sudo ufw allow 10002-10010<br />
sudo ufw allow 40000</div>Adminhttps://wiki.biblepay.org/index.php?title=Building_A_Temple&diff=6931Building A Temple2023-07-08T18:48:09Z<p>Admin: Created page with "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. When you run a temp..."</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 <br />
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 a configs directory:<br />
cd /<br />
mkdir /configs<br />
mkdir /data<br />
cd /configs<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 />
Save the file (ctrl-x, shift-Y, enter)<br />
<br />
Copy this file 10 times to:<br />
biblepay1.conf, biblepay2.conf ... biblepay10.conf<br />
Edit each file and set the following values:<br />
For biblepay1.conf, ensure the port=40000 and the rpcport=20001<br />
For biblepay2.conf, ensure the port=10002 and the rpcport=20002<br />
...<br />
For biblepay10.conf, ensure the port=10010 and the rpcport=20010<br />
Edit the your_bls_privkey with the privkey of the sanctuary that you set up in "EasySanc".<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), but, each successive sanc from sanc2-sanc10 must have a port of 10002-10010 (as other sancs whitelist this port, ports outside of the 100NN range are POSE banned. )<br />
The rule for "rpcport" is they should be unique, starting with 20001 and working up to 20010 (there is no rule for RPCport except that it must be unique, otherwise the node will not start).<br />
<br />
Firewall Changes:<br />
In this section simply expose <br />
sudo ufw allow 10002-10010<br />
sudo ufw allow 40000</div>Adminhttps://wiki.biblepay.org/index.php?title=Free_Phone_Calls_for_New_Users&diff=6930Free Phone Calls for New Users2023-07-04T15:12:29Z<p>Admin: Created page with " BiblePay is giving away 50,000 BBP for free phone calls to our new users! Simply follow these directions: 1. Download the BiblePay Desktop Wallet from here: https://biblepa..."</p>
<hr />
<div><br />
BiblePay is giving away 50,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/index.php?title=Activate_Hardware_Phone&diff=6929Activate 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/index.php?title=BiblePay_Email&diff=6928BiblePay Email2023-06-11T16:47:35Z<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/index.php?title=BiblePay_Email&diff=6927BiblePay Email2023-06-11T16:17:43Z<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 />
<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/index.php?title=BiblePay_Email&diff=6926BiblePay Email2023-06-11T15:39:16Z<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 />
<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></div>Adminhttps://wiki.biblepay.org/index.php?title=BiblePay_Email&diff=6925BiblePay Email2023-06-11T15:36:59Z<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 />
<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 />
Https://seven.biblepay.org/img/Thunderbird/Thunder1.png<br />
<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 />
Https://seven.biblepay.org/img/Thunderbird/Thunder2.png<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 />
Https://seven.biblepay.org/img/Thunderbird/Thunder3.png</div>Adminhttps://wiki.biblepay.org/index.php?title=BiblePay_Email&diff=6924BiblePay Email2023-06-11T15:36:11Z<p>Admin: Created page with "''' How to Create a BiblePay E-Mail Account ''' From Unchained desktop, navigate to E-Mail | E-Mail Maintenance. Specify the E-Mail username you would like to use, without t..."</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 />
<br />
<br />
<br />
<br />
''' How to Set Up BiblePay E-Mail with Thunderbird '''<br />
<br />
From Thunderbird, click on Tools | Account Settings.<br />
Populate the Account Name and the "Your Name" to be your preferred human readable account names.<br />
Populate E-Mail address to be your new UserName + @biblepay.org.<br />
<br />
Https://seven.biblepay.org/img/Thunderbird/Thunder1.png<br />
<br />
<br />
<br />
<br />
Click Server Settings - Here is where you populate the IMAP settings:<br />
<br />
Populate Server Type = IMAP<br />
Server Name = seven.biblepay.org<br />
User Name = Your BBP username @biblepay.org<br />
Port = 993<br />
Security = SSL/TLS<br />
Auth Method = Normal<br />
<br />
<br />
Https://seven.biblepay.org/img/Thunderbird/Thunder2.png<br />
<br />
Click Outgoing Server - this is where you set the SMTP settings:<br />
<br />
Click Add<br />
Server Name = seven.biblepay.org<br />
User Name = Your BBP username @biblepay.org<br />
Port = 465<br />
Security = SSL/TLS<br />
Auth Method = Normal<br />
<br />
<br />
Https://seven.biblepay.org/img/Thunderbird/Thunder3.png</div>Adminhttps://wiki.biblepay.org/index.php?title=Red_Sea_User_Guide&diff=6923Red Sea User Guide2023-06-04T17:45:19Z<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>Adminhttps://wiki.biblepay.org/index.php?title=Red_Sea_User_Guide&diff=6922Red Sea User Guide2023-05-20T17:45:16Z<p>Admin: Created page with " '''Introduction''' 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, ho..."</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.</div>Adminhttps://wiki.biblepay.org/index.php?title=Red_Sea_Release&diff=6921Red Sea Release2023-05-13T13:41:39Z<p>Admin: </p>
<hr />
<div>All Glory to God.<br />
<br />
God is responsible for the Architecture of BiblePay, and all Good things come down from our Heavenly Father: the great I AM (Yahweh).<br />
<br />
<br />
Red Sea plans for a strong foundation:<br />
<br />
- The Core Wallet (C++ BiblePayd and C++/QT Wallet) stays pristine so that we can integrate upstream commits and keep the wallet pure, clean, and secure.<br />
* Security means you can always count on the core wallet to provide a secure place (your keys, your balance) for your biblepay.<br />
* Security means our web site code will never maniuplate or read your wallet keys (except one key that we designate as your BBP-Unchained Key).<br />
* Pristine means that we will not pollute the core wallet with UI pages that will break in the future when upstream commits refactor the wallet.<br />
<br />
- Unchained will move to the desktop.<br />
* This means that the cool features that we always wanted to put in the wallet (like the prayer room, BBP chat, Deliverance videoconference rooms, Social Media Timeline) will now be possible<br />
as they will live in our new Desktop Web Pages.<br />
* This opens up the exciting possibility for devs to contribute to make new UI pages without interfering with the c++ core wallet code<br />
* This means security will be improved in unchained because signing will occur on the desktop<br />
* This opens up the possibility for BBP to offer new collaboration apps (IE competition for Basecamp/Zoho)<br />
<br />
<br />
- Unchained Web will lose some features:<br />
* Turnkey Sancs will be retired in favor of Decentralized Offline Sancs<br />
a. If you fund a new sanc and keep it offline you will earn a 50% reward (this replaces portfolio builder and turnkey sancs)<br />
b. If you fund a sanc and keep it online (along with BMS), you receive a 100% reward<br />
* Portfolio Builder will be retired in favor of decentralized Offline Sancs<br />
<br />
- RandomX Mining to be retired:<br />
* RandomX pool mining is going to be retired in favor of Sanctuary Mining<br />
* Sanctuaries mine in a non competetive, deterministic way in the background (consuming low resources)<br />
* This increases the sanctuary reward<br />
* The sanctuary reward goes to both offline sancs and online sancs so we may reward both types of investors (offline sancs get half)<br />
<br />
<br />
- Extra Large Sancs (Temple) <br />
* If you own 10 or more sancs, your node will automatically run an instance of Cockroach DB (A decentralized database).<br />
* This database is used to store our orphan collage, our expenses and our revenue<br />
* In this way we fully dencetralize biblepay 100% so that no party is responsible for any back-end database<br />
* This database also stores the metadata for bio images, the forum, timeline posts, etc.<br />
<br />
<br />
- Decentralized Governance Voting improvements<br />
* It will be possible to vote on configuration changes (IE permission delegation)<br />
* This allows a responsible party to enter a historical accounting record or perform clerical duties<br />
<br />
- BiblePay will have a nice API:<br />
<br />
* The core wallet will have a button on the menu that launches Desktop Unchained<br />
* Desktop Unchained will contain all of the Extra BBP UI<br />
* A back end Biblepay.DLL will be included in our releases which give developers the capability to interface with BBP<br />
(IE upload videos, download files, send money, receive money, etc)<br />
* Our biblepay DLL will eventually become a DLL on NuGet, opening up BBP to thousands of c# developers (Scheduled for Q4 2023)<br />
<br />
- BiblePay moves away from Metamask/ERC-20 Signing Keys:<br />
<br />
* To make Unchained more accessible, we move away from Metamask so that we no longer require the plug-in<br />
* Unchained authenticates by using one Core wallet key (the Unchained Key)<br />
* You can fund your Unchained key by sending BBP to it<br />
* You can spend funds from your Unchained Key by spending it in the Desktop App (Desktop Features will be revealed during the Red Sea Release)<br />
* Because of this, all funds should be withdrawn from unchained.biblepay.org (Remove web wallet funds and remove Turnkey Sanctuaries). You can leave Portfolio Builder balances as those live in the Core Wallet.<br />
<br />
- True decentralized bandwidth is coming to the desktop:<br />
<br />
* Our video player pulls files in parallel from STORJ's 4000+ hard drives and does not use DNS. Since it works in parallel it cannot be ddossed, and it uses IP rather than DNS for the addresses.<br />
If the individual Storj miners are up, our videos are up. We no longer rely on cloudflare for DDOS/CDN.<br />
* Our video uploader will also upload in parallel directly to the STORJ network, and cannot be taken down from conventional DDOS. If StorJ miners are up, we are up.<br />
* Our file attachments also work this way<br />
* Our decentralized balances work across our sancs, not against one public web host.<br />
* Our cockroach decentralized database is up even when some BBP sancs fail. (Storage density is always 3* or more).<br />
* Our web server is truly decentralized. Every BBP user will run their own server.<br />
* Our web pages will be PRIVATE. Meaning that when you sign a transaction it will be done on your machine and not on the web hosts server!<br />
* Now we can offer the ability to write software that competes with Zoho (public collaboration software). This could be a sustainable source of revenue for BBP in the future.<br />
Our software being decentralized will run each instance on the BBP desktop.</div>Adminhttps://wiki.biblepay.org/index.php?title=Red_Sea_Release&diff=6920Red Sea Release2023-05-13T13:41:10Z<p>Admin: </p>
<hr />
<div>All Glory to God.<br />
<br />
God is responsible for the Architecture of BiblePay, and all Good things come down from our Heavenly Father: the great I AM (Yahweh).<br />
<br />
Praise be to Jesus, the Ruach Hakodesh and Yahweh.<br />
<br />
<br />
<br />
Red Sea plans for a strong foundation:<br />
<br />
- The Core Wallet (C++ BiblePayd and C++/QT Wallet) stays pristine so that we can integrate upstream commits and keep the wallet pure, clean, and secure.<br />
* Security means you can always count on the core wallet to provide a secure place (your keys, your balance) for your biblepay.<br />
* Security means our web site code will never maniuplate or read your wallet keys (except one key that we designate as your BBP-Unchained Key).<br />
* Pristine means that we will not pollute the core wallet with UI pages that will break in the future when upstream commits refactor the wallet.<br />
<br />
- Unchained will move to the desktop.<br />
* This means that the cool features that we always wanted to put in the wallet (like the prayer room, BBP chat, Deliverance videoconference rooms, Social Media Timeline) will now be possible<br />
as they will live in our new Desktop Web Pages.<br />
* This opens up the exciting possibility for devs to contribute to make new UI pages without interfering with the c++ core wallet code<br />
* This means security will be improved in unchained because signing will occur on the desktop<br />
* This opens up the possibility for BBP to offer new collaboration apps (IE competition for Basecamp/Zoho)<br />
<br />
<br />
- Unchained Web will lose some features:<br />
* Turnkey Sancs will be retired in favor of Decentralized Offline Sancs<br />
a. If you fund a new sanc and keep it offline you will earn a 50% reward (this replaces portfolio builder and turnkey sancs)<br />
b. If you fund a sanc and keep it online (along with BMS), you receive a 100% reward<br />
* Portfolio Builder will be retired in favor of decentralized Offline Sancs<br />
<br />
- RandomX Mining to be retired:<br />
* RandomX pool mining is going to be retired in favor of Sanctuary Mining<br />
* Sanctuaries mine in a non competetive, deterministic way in the background (consuming low resources)<br />
* This increases the sanctuary reward<br />
* The sanctuary reward goes to both offline sancs and online sancs so we may reward both types of investors (offline sancs get half)<br />
<br />
<br />
- Extra Large Sancs (Temple) <br />
* If you own 10 or more sancs, your node will automatically run an instance of Cockroach DB (A decentralized database).<br />
* This database is used to store our orphan collage, our expenses and our revenue<br />
* In this way we fully dencetralize biblepay 100% so that no party is responsible for any back-end database<br />
* This database also stores the metadata for bio images, the forum, timeline posts, etc.<br />
<br />
<br />
- Decentralized Governance Voting improvements<br />
* It will be possible to vote on configuration changes (IE permission delegation)<br />
* This allows a responsible party to enter a historical accounting record or perform clerical duties<br />
<br />
- BiblePay will have a nice API:<br />
<br />
* The core wallet will have a button on the menu that launches Desktop Unchained<br />
* Desktop Unchained will contain all of the Extra BBP UI<br />
* A back end Biblepay.DLL will be included in our releases which give developers the capability to interface with BBP<br />
(IE upload videos, download files, send money, receive money, etc)<br />
* Our biblepay DLL will eventually become a DLL on NuGet, opening up BBP to thousands of c# developers (Scheduled for Q4 2023)<br />
<br />
- BiblePay moves away from Metamask/ERC-20 Signing Keys:<br />
<br />
* To make Unchained more accessible, we move away from Metamask so that we no longer require the plug-in<br />
* Unchained authenticates by using one Core wallet key (the Unchained Key)<br />
* You can fund your Unchained key by sending BBP to it<br />
* You can spend funds from your Unchained Key by spending it in the Desktop App (Desktop Features will be revealed during the Red Sea Release)<br />
* Because of this, all funds should be withdrawn from unchained.biblepay.org (Remove web wallet funds and remove Turnkey Sanctuaries). You can leave Portfolio Builder balances as those live in the Core Wallet.<br />
<br />
- True decentralized bandwidth is coming to the desktop:<br />
<br />
* Our video player pulls files in parallel from STORJ's 4000+ hard drives and does not use DNS. Since it works in parallel it cannot be ddossed, and it uses IP rather than DNS for the addresses.<br />
If the individual Storj miners are up, our videos are up. We no longer rely on cloudflare for DDOS/CDN.<br />
* Our video uploader will also upload in parallel directly to the STORJ network, and cannot be taken down from conventional DDOS. If StorJ miners are up, we are up.<br />
* Our file attachments also work this way<br />
* Our decentralized balances work across our sancs, not against one public web host.<br />
* Our cockroach decentralized database is up even when some BBP sancs fail. (Storage density is always 3* or more).<br />
* Our web server is truly decentralized. Every BBP user will run their own server.<br />
* Our web pages will be PRIVATE. Meaning that when you sign a transaction it will be done on your machine and not on the web hosts server!<br />
* Now we can offer the ability to write software that competes with Zoho (public collaboration software). This could be a sustainable source of revenue for BBP in the future.<br />
Our software being decentralized will run each instance on the BBP desktop.</div>Adminhttps://wiki.biblepay.org/index.php?title=Red_Sea_Release&diff=6919Red Sea Release2023-04-02T21:03:00Z<p>Admin: </p>
<hr />
<div>All Glory to God.<br />
<br />
God is responsible for the Architecture of BiblePay, and all Good things come down from our Heavenly Father: the great I AM (Yahweh).<br />
<br />
Praise be to Jesus, the Ruach Hakodesh and Yahweh.<br />
<br />
Our goal for the Red Sea Release is to organize BiblePay into it's proper and clear and logical demarcation points so that we can maintain it and build on a strong decentralized foundation.<br />
<br />
As you know things have shifted around while we "feel out" what is best, but only truth stands, and that comes from God.<br />
<br />
Red Sea plans for a strong foundation:<br />
<br />
- The Core Wallet (C++ BiblePayd and C++/QT Wallet) stays pristine so that we can integrate upstream commits and keep the wallet pure, clean, and secure.<br />
* Security means you can always count on the core wallet to provide a secure place (your keys, your balance) for your biblepay.<br />
* Security means our web site code will never maniuplate or read your wallet keys (except one key that we designate as your BBP-Unchained Key).<br />
* Pristine means that we will not pollute the core wallet with UI pages that will break in the future when upstream commits refactor the wallet.<br />
<br />
- Unchained will move to the desktop.<br />
* This means that the cool features that we always wanted to put in the wallet (like the prayer room, BBP chat, Deliverance videoconference rooms, Social Media Timeline) will now be possible<br />
as they will live in our new Desktop Web Pages.<br />
* This opens up the exciting possibility for devs to contribute to make new UI pages without interfering with the c++ core wallet code<br />
* This means security will be improved in unchained because signing will occur on the desktop<br />
* This opens up the possibility for BBP to offer new collaboration apps (IE competition for Basecamp/Zoho)<br />
<br />
- Unchained Web will lose some features:<br />
* Turnkey Sancs will be retired in favor of Decentralized Offline Sancs<br />
a. If you fund a new sanc and keep it offline you will earn a 50% reward (this replaces portfolio builder and turnkey sancs)<br />
b. If you fund a sanc and keep it online (along with BMS), you receive a 100% reward<br />
* Portfolio Builder will be retired in favor of decentralized Offline Sancs<br />
<br />
- RandomX Mining to be retired:<br />
* RandomX pool mining is going to be retired in favor of Sanctuary Mining<br />
* Sanctuaries mine in a non competetive, deterministic way in the background (consuming low resources)<br />
* This increases the sanctuary reward<br />
* The sanctuary reward goes to both offline sancs and online sancs so we may reward both types of investors (offline sancs get half)<br />
<br />
<br />
- Extra Large Sancs (Temple) <br />
* If you own 10 or more sancs, your node will automatically run an instance of Cockroach DB (A decentralized database).<br />
* This database is used to store our orphan collage, our expenses and our revenue<br />
* In this way we fully dencetralize biblepay 100% so that no party is responsible for any back-end database<br />
* This database also stores the metadata for bio images, the forum, timeline posts, etc.<br />
<br />
- Decentralized Governance Voting improvements<br />
* It will be possible to vote on configuration changes (IE permission delegation)<br />
* This allows a responsible party to enter a historical accounting record or perform clerical duties<br />
<br />
- BiblePay will have a nice API:<br />
<br />
* The core wallet will have a button on the menu that launches Desktop Unchained<br />
* Desktop Unchained will contain all of the Extra BBP UI<br />
* A back end Biblepay.DLL will be included in our releases which give developers the capability to interface with BBP<br />
(IE upload videos, download files, send money, receive money, etc)<br />
* Our biblepay DLL will eventually become a DLL on NuGet, opening up BBP to thousands of c# developers (Scheduled for Q4 2023)<br />
<br />
- BiblePay moves away from Metamask/ERC-20 Signing Keys:<br />
<br />
* To make Unchained more accessible, we move away from Metamask so that we no longer require the plug-in<br />
* Unchained authenticates by using one Core wallet key (the Unchained Key)<br />
* You can fund your Unchained key by sending BBP to it<br />
* You can spend funds from your Unchained Key by spending it in the Desktop App (Desktop Features will be revealed during the Red Sea Release)<br />
* Because of this, all funds should be withdrawn from unchained.biblepay.org (Remove web wallet funds and remove Turnkey Sanctuaries). You can leave Portfolio Builder balances as those live in the Core Wallet.<br />
<br />
- True decentralized bandwidth is coming to the desktop:<br />
<br />
* Our video player pulls files in parallel from STORJ's 4000+ hard drives and does not use DNS. Since it works in parallel it cannot be ddossed, and it uses IP rather than DNS for the addresses.<br />
If the individual Storj miners are up, our videos are up. We no longer rely on cloudflare for DDOS/CDN.<br />
* Our video uploader will also upload in parallel directly to the STORJ network, and cannot be taken down from conventional DDOS. If StorJ miners are up, we are up.<br />
* Our file attachments also work this way!<br />
* Our decentralized balances work across our sancs, not against one public web host.<br />
* Our cockroach decentralized database is up even when some BBP sancs fail. (Storage density is always 3* or more).<br />
* Our web server is truly decentralized. Every BBP user will run their own server.<br />
* Our web pages will be PRIVATE. Meaning that when you sign a transaction it will be done on your machine and not on the web hosts server!<br />
* Now we can offer the ability to write software that competes with Zoho (public collaboration software). This could be a sustainable source of revenue for BBP in the future.<br />
Our software being decentralized will run each instance on the BBP desktop.</div>Adminhttps://wiki.biblepay.org/index.php?title=Red_Sea_Release&diff=6918Red Sea Release2023-04-02T20:47:14Z<p>Admin: </p>
<hr />
<div>All Glory to God.<br />
<br />
God is responsible for the Architecture of BiblePay, and all Good things come down from our Heavenly Father: the great I AM (Yahweh).<br />
<br />
Praise be to Jesus, the Ruach Hakodesh and Yahweh.<br />
<br />
Our goal for the Red Sea Release is to organize BiblePay into it's proper and clear and logical demarcation points so that we can maintain it and build on a strong decentralized foundation.<br />
<br />
As you know things have shifted around while we "feel out" what is best, but only truth stands, and that comes from God.<br />
<br />
Red Sea plans for a strong foundation:<br />
<br />
- The Core Wallet (C++ BiblePayd and C++/QT Wallet) stays pristine so that we can integrate upstream commits and keep the wallet pure, clean, and secure.<br />
* Security means you can always count on the core wallet to provide a secure place (your keys, your balance) for your biblepay.<br />
* Security means our web site code will never maniuplate or read your wallet keys (except one key that we designate as your BBP-Unchained Key).<br />
* Pristine means that we will not pollute the core wallet with UI pages that will break in the future when upstream commits refactor the wallet.<br />
<br />
- Unchained will move to the desktop.<br />
* This means that the cool features that we always wanted to put in the wallet (like the prayer room, BBP chat, Deliverance videoconference rooms, Social Media Timeline) will now be possible<br />
as they will live in our new Desktop Web Pages.<br />
* This opens up the exciting possibility for devs to contribute to make new UI pages without interfering with the c++ core wallet code<br />
* This means security will be improved in unchained because signing will occur on the desktop<br />
* This opens up the possibility for BBP to offer new collaboration apps (IE competition for Basecamp/Zoho)<br />
<br />
- Unchained Web will lose some features:<br />
* Turnkey Sancs will be retired in favor of Decentralized Offline Sancs<br />
a. If you fund a new sanc and keep it offline you will earn a 50% reward (this replaces portfolio builder and turnkey sancs)<br />
b. If you fund a sanc and keep it online (along with BMS), you receive a 100% reward<br />
* Portfolio Builder will be retired in favor of decentralized Offline Sancs<br />
<br />
- RandomX Mining to be retired:<br />
* RandomX pool mining is going to be retired in favor of Sanctuary Mining<br />
* Sanctuaries mine in a non competetive, deterministic way in the background (consuming low resources)<br />
* This increases the sanctuary reward<br />
* The sanctuary reward goes to both offline sancs and online sancs so we may reward both types of investors (offline sancs get half)<br />
<br />
<br />
- Extra Large Sancs (Temple) <br />
* If you own 10 or more sancs, your node will automatically run an instance of Cockroach DB (A decentralized database).<br />
* This database is used to store our orphan collage, our expenses and our revenue<br />
* In this way we fully dencetralize biblepay 100% so that no party is responsible for any back-end database<br />
* This database also stores the metadata for bio images, the forum, timeline posts, etc.<br />
<br />
- Decentralized Governance Voting improvements<br />
* It will be possible to vote on configuration changes (IE permission delegation)<br />
* This allows a responsible party to enter a historical accounting record or perform clerical duties<br />
<br />
- BiblePay will have a nice API:<br />
<br />
* The core wallet will have a button on the menu that launches Desktop Unchained<br />
* Desktop Unchained will contain all of the Extra BBP UI<br />
* A back end Biblepay.DLL will be included in our releases which give developers the capability to interface with BBP<br />
(IE upload videos, download files, send money, receive money, etc)<br />
* Our biblepay DLL will eventually become a DLL on NuGet, opening up BBP to thousands of c# developers (Scheduled for Q4 2023)<br />
<br />
- BiblePay moves away from Metamask/ERC-20 Signing Keys:<br />
<br />
* To make Unchained more accessible, we move away from Metamask so that we no longer require the plug-in<br />
* Unchained authenticates by using one Core wallet key (the Unchained Key)<br />
* You can fund your Unchained key by sending BBP to it<br />
* You can spend funds from your Unchained Key by spending it in the Desktop App (Desktop Features will be revealed during the Red Sea Release)<br />
* Because of this, all funds should be withdrawn from unchained.biblepay.org (Remove web wallet funds and remove Turnkey Sanctuaries). You can leave Portfolio Builder balances as those live in the Core Wallet.</div>Adminhttps://wiki.biblepay.org/index.php?title=Red_Sea_Release&diff=6917Red Sea Release2023-04-02T20:07:14Z<p>Admin: </p>
<hr />
<div>All Glory to God.<br />
<br />
God is responsible for the Architecture of BiblePay, and all Good things come down from our Heavenly Father: the great I AM (Yahweh).<br />
<br />
Praise be to Jesus, the Ruach Hakodesh and Yahweh.<br />
<br />
Our goal for the Red Sea Release is to organize BiblePay into it's proper and clear and logical demarcation points so that we can maintain it and build on a strong decentralized foundation.<br />
<br />
As you know things have shifted around while we "feel out" what is best, but only truth stands, and that comes from God.<br />
<br />
Red Sea plans for a strong foundation:<br />
<br />
- The Core Wallet (C++ BiblePayd and C++/QT Wallet) stays pristine so that we can integrate upstream commits and keep the wallet pure, clean, and secure.<br />
* Security means you can always count on the core wallet to provide a secure place (your keys, your balance) for your biblepay.<br />
* Security means our web site code will never maniuplate or read your wallet keys (except one key that we designate as your BBP-Unchained Key).<br />
* Pristine means that we will not pollute the core wallet with UI pages that will break in the future when upstream commits refactor the wallet.<br />
<br />
- Unchained will move to the desktop.<br />
* This means that the cool features that we always wanted to put in the wallet (like the prayer room, BBP chat, Deliverance videoconference rooms, Social Media Timeline) will now be possible<br />
as they will live in our new Desktop Web Pages.<br />
* This opens up the exciting possibility for devs to contribute to make new UI pages without interfering with the c++ core wallet code<br />
* This means security will be improved in unchained because signing will occur on the desktop<br />
* This opens up the possibility for BBP to offer new collaboration apps (IE competition for Basecamp/Zoho)<br />
<br />
- Unchained Web will lose some features:<br />
* Turnkey Sancs will be retired in favor of Decentralized Offline Sancs<br />
a. If you fund a new sanc and keep it offline you will earn a 50% reward (this replaces portfolio builder and turnkey sancs)<br />
b. If you fund a sanc and keep it online (along with BMS), you receive a 100% reward<br />
* Portfolio Builder will be retired in favor of decentralized Offline Sancs<br />
<br />
- RandomX Mining to be retired:<br />
* RandomX pool mining is going to be retired in favor of Sanctuary Mining<br />
* Sanctuaries mine in a non competetive, deterministic way in the background (consuming low resources)<br />
* This increases the sanctuary reward<br />
* The sanctuary reward goes to both offline sancs and online sancs so we may reward both types of investors (offline sancs get half)<br />
<br />
<br />
- Extra Large Sancs (Temple) <br />
* If you own 10 or more sancs, your node will automatically run an instance of Cockroach DB (A decentralized database).<br />
* This database is used to store our orphan collage, our expenses and our revenue<br />
* In this way we fully dencetralize biblepay 100% so that no party is responsible for any back-end database<br />
* This database also stores the metadata for bio images, the forum, timeline posts, etc.<br />
<br />
- Decentralized Governance Voting improvements<br />
* It will be possible to vote on configuration changes (IE permission delegation)<br />
* This allows a responsible party to enter a historical accounting record or perform clerical duties<br />
<br />
- BiblePay will have a nice API:<br />
<br />
* The core wallet will have a button on the menu that launches Desktop Unchained<br />
* Desktop Unchained will contain all of the Extra BBP UI<br />
* A back end Biblepay.DLL will be included in our releases which give developers the capability to interface with BBP<br />
(IE upload videos, download files, send money, receive money, etc)<br />
* Our biblepay DLL will eventually become a DLL on NuGet, opening up BBP to thousands of c# developers (Scheduled for Q4 2023)</div>Adminhttps://wiki.biblepay.org/index.php?title=Red_Sea_Release&diff=6916Red Sea Release2023-04-02T19:59:42Z<p>Admin: Created page with "All Glory to God. God is responsible for the Architecture of BiblePay, and all Good things come down from our Heavenly Father: the great I AM (Yahweh). Praise be to Jesus,..."</p>
<hr />
<div>All Glory to God.<br />
<br />
God is responsible for the Architecture of BiblePay, and all Good things come down from our Heavenly Father: the great I AM (Yahweh).<br />
<br />
Praise be to Jesus, the Ruach Hakodesh and Yahweh.<br />
<br />
Our goal for the Red Sea Release is to organize BiblePay into it's proper and clear and logical demarcation points so that we can maintain it and build on a strong decentralized foundation.<br />
<br />
As you know things have shifted around while we "feel out" what is best, but only truth stands, and that comes from God.<br />
<br />
Red Sea plans for a strong foundation:<br />
<br />
- The Core Wallet (C++ BiblePayd and C++/QT Wallet) stays pristine so that we can integrate upstream commits and keep the wallet pure, clean, and secure.<br />
* Security means you can always count on the core wallet to provide a secure place (your keys, your balance) for your biblepay.<br />
* Security means our web site code will never maniuplate or read your wallet keys (except one key that you designate as your BBP-Unchained Key).<br />
* Pristine means that we will not pollute the core wallet with UI pages that will break in the future when upstream commits refactor the wallet.<br />
<br />
- Unchained will move to the desktop.<br />
* This means that the cool features that we always wanted to put in the wallet (like the prayer room, BBP chat, Deliverance videoconference rooms, Social Media Timeline) will now be possible<br />
as they will live in our new Desktop Web Pages.<br />
* This opens up the exciting possibility for devs to contribute to make new UI pages without interfering with the c++ core wallet code<br />
* This means security will be improved in unchained because signing will occur on the desktop<br />
* This opens up the possibility for BBP to offer new collaboration apps (IE competition for Basecamp/Zoho)<br />
<br />
- Unchained Web will lose some features:<br />
* Turnkey Sancs will be retired in favor of Decentralized Offline Sancs<br />
a. If you fund a new sanc and keep it offline you will earn a 50% reward (this replaces portfolio builder and turnkey sancs)<br />
b. If you fund a sanc and keep it online (along with BMS), you receive a 100% reward<br />
* Portfolio Builder will be retired in favor of decentralized Offline Sancs<br />
<br />
- RandomX Mining to be retired:<br />
* RandomX pool mining is going to be retired in favor of Sanctuary Mining<br />
* Sanctuaries mine in a non competetive, deterministic way in the background (consuming low resources)<br />
* This increases the sanctuary reward<br />
* The sanctuary reward goes to both offline sancs and online sancs so we may reward both types of investors (offline sancs get half)<br />
<br />
<br />
- Extra Large Sancs (Temple) <br />
* If you own 10 or more sancs, your node will automatically run an instance of Cockroach DB (A decentralized database).<br />
* This database is used to store our orphan collage, our expenses and our revenue<br />
* In this way we fully dencetralize biblepay 100% so that no party is responsible for any back-end database<br />
* This database also stores the metadata for bio images, the forum, timeline posts, etc.<br />
<br />
- Decentralized Governance Voting improvements<br />
* It will be possible to vote on configuration changes (IE permission delegation)<br />
* This allows a responsible party to enter a historical accounting record or perform clerical duties<br />
<br />
- BiblePay will have a nice API:<br />
<br />
* The core wallet will have a button on the menu that launches Desktop Unchained<br />
* Desktop Unchained will contain all of the Extra BBP UI<br />
* A back end Biblepay.DLL will be included in our releases which give developers the capability to interface with BBP<br />
(IE upload videos, download files, send money, receive money, etc)<br />
* Our biblepay DLL will eventually become a DLL on NuGet, opening up BBP to thousands of c# developers (Scheduled for Q4 2023)</div>Adminhttps://wiki.biblepay.org/index.php?title=Install_BMS&diff=6915Install BMS2023-01-22T19:27:11Z<p>Admin: </p>
<hr />
<div>''' Install BMS on Ubuntu 20.04 '''<br />
<br />
<pre><br />
cd /<br />
<br />
mkdir bms<br />
<br />
cd bms<br />
<br />
#Install dotnet 20.04:<br />
wget https://packages.microsoft.com/config/ubuntu/20.04/packages-microsoft-prod.deb -O packages-microsoft-prod.deb <br />
<br />
sudo dpkg -i packages-microsoft-prod.deb<br />
<br />
sudo apt-get install -y apt-transport-https<br />
<br />
sudo apt-get update <br />
<br />
sudo apt-get install -y dotnet-sdk-3.1<br />
<br />
#optional: To see if its OK type "dotnet --info"<br />
<br />
dotnet dev-certs https<br />
<br />
#It may say "certificate already present", but still necessary.<br />
<br />
#retrieve the node software<br />
<br />
rm bms.zip #will say no such file, thats OK<br />
<br />
wget https://social.biblepay.org/bms/bms.zip<br />
<br />
unzip bms.zip<br />
<br />
#prime the node<br />
dotnet BiblePay.BMSD.dll<br />
<br />
#You will see: ERROR: missing bms.conf file: This is OK<br />
<br />
#Now we need to create BMS config file, we do this by executing:<br />
<br />
nano /inetpub/wwwroot/bms/bms.conf<br />
<br />
bindurl=https://your.sanc.ip:8443<br />
<br />
</pre><br />
<br />
''' PHASE II: Additional Items added to BMS.conf as of of May 29th, 2022 to lock in the sidechain with the sanc'''<br />
<pre><br />
nano /inetpub/wwwroot/bms/bms.conf<br />
<br />
#Add these items:<br />
testnetrpchost=localhost:20001<br />
testnetrpcuser=your_testnet_rpc_user<br />
tesnetrpcpassword=your_testnet_rpc_password<br />
rpchost=localhost:20000<br />
rpcuser=your_mainnet_rpc_user<br />
rpcpassword=your_mainnet_rpc_password<br />
<br />
<br />
<br />
#Additionally, Phase II changes requires us to add more settings to our testnet biblepaycore SANCTUARY biblepay.conf file (you can find this at ~/biblepay/biblepaytest.conf):<br />
<br />
testnet=1<br />
masternodeblsprivkey=your_bls_priv_key #this is already set since you set up your testnet sanc<br />
[test]<br />
rpcuser=your_testnet_rpc_username<br />
rpcpassword=your_testnet_rpc_password<br />
server=1<br />
listen=1<br />
daemon=1<br />
rpcbind=0.0.0.0<br />
rpcallowip=127.0.0.1<br />
rpcallowip=your_home_ip<br />
rpcport=20001<br />
<br />
#Additionally, Phase II changes requires us to add more settings to our MAINNET biblepaycore SANCTUARY config settings to the BiblePay.conf Mainnet file: You can find this at ~/.biblepay/biblepay.conf:<br />
<br />
masternodeblsprivkey=your_mainnet_bls_priv_key #(already set)<br />
rpcuser=your_mainnet_rpc_username<br />
rpcpassword=your_mainnet_rpc_password<br />
server=1<br />
listen=1<br />
daemon=1<br />
rpcbind=0.0.0.0<br />
rpcallowip=127.0.0.1<br />
rpcallowip=your_home_ip<br />
rpcport=20000<br />
<br />
</pre><br />
'''END OF Phase II changes for May 29th, 2022'''<br />
<br />
<pre><br />
<br />
<br />
<br />
sudo ufw allow 8443/tcp<br />
sudo ufw allow 40000/tcp<br />
sudo ufw allow 40001/tcp<br />
sudo ufw enable<br />
sudo ufw allow from your_home_ip<br />
#If you plan to run a randomx pool on ports 3001 (mainnet) and 3002 (testnet):<br />
sudo ufw allow 3001/tcp<br />
sudo ufw allow 3002/tcp<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
#now start the node<br />
dotnet BiblePay.BMSD.dll<br />
<br />
#The node should respond with a top level menu and continue running.<br />
<br />
<br />
To test the node, point a web browser at:<br />
<br />
https://your_sanc_ip:8443/BMS/Status<br />
#You will see WARNING: SSL Certificate invalid. Just click Details, Proceed anyway (this is OK for the local machine). In mainnet, the node will use our wildcard SSL cert.<br />
<br />
</pre><br />
<br />
<br />
<br />
<br />
''' How to Manually Upgrade BMS '''<br />
<br />
<pre><br />
<br />
#Click ctrl-c a few times to close the old copy of BMS and this gives you the command prompt again.<br />
<br />
cd /bms<br />
rm bms.zip<br />
wget https://social.biblepay.org/bms/bms.zip<br />
unzip bms.zip<br />
#When it asks should we overwrite files, answer [A] for ALL and press enter.<br />
#At this point the old files are overwritten.<br />
#Now you can start the node again:<br />
dotnet BiblePay.BMSD.dll<br />
#The node should start<br />
<br />
<br />
</pre></div>Adminhttps://wiki.biblepay.org/index.php?title=API&diff=6914API2022-12-02T12:29:23Z<p>Admin: </p>
<hr />
<div></p><p><br /><br />
We are a blockchain with real world use cases.<br />
</p><p>We are offering an alternative to big tech, big media, and we are fighting for freedom. Just as God wants freedom for us, we want freedom for you. We do not believe in censoring free speech but the principles of the founding fathers. Additionally, when you use our services, you are paying for orphan sponsorships. What better relationship could there be?<br />
</p><p><br /><br />
<br />
Live Service #1:<br />
</p><p><br /><br />
<b> BiblePay S3 File Hosting (S3aas) </b><br />
</p><p>This API allows you to store files, accessible by public URL (via CDN). You may store small files all the way up to very large files (1 byte to 1Gigabyte per file).<br />
</p><p>Use cases: Upload your mp4 videos, your audio tracks, your encrypted backup files, your web site files, your images/css/assets for web hosting, share files etc.<br />
</p><p><b> S3 Endpoint for Curl (Linux, Mac, others) </b><br />
</p><p>Simply post your file from the command or through code as below, along with your biblepay private key in the Header field:<br />
</p><p>Example:<br />
</p><br />
<pre>curl -X POST <br />
-H "key: YOUR_BIBLEPAY_PRIVATE_KEY" <br />
-H "url: Your_preferred_filename"<br />
-F "file=@myfile.mp4" <br />
https://unchained.biblepay.org/api/web/bbpingress<br />
</pre><br />
Example:<br />
<pre>curl -X POST <br />
-H "key: U1234567890" <br />
-H "url: myfile.mp4"<br />
-F "file=@myfile.mp4" <br />
https://unchained.biblepay.org/api/web/bbpingress<br />
</pre><br />
<br />
<p><br /><br />
Response:<br />
</p><p>If successful, Biblepay will respond with an http-200 response, with JSON containing an empty error field, a result code with a value of 200, and the URL which you can use immediately.<br />
If unsuccessful, BiblePay will respond with an http-200 response, with JSON containing an error field with a populated reason, and a result code below zero.<br />
</p><p><br /><br />
<b> S3 Endpoint for C# </b><br />
</p><p>You can also post your file programatically in any language. For C#, please see this example below:<br />
</p><br />
<pre>public async static void UploadBiblePayFile()<br />
{<br />
string sURL = "https://unchained.biblepay.org/api/web/bbpingress";<br />
string sFilePath = "s:\\yourfolder\\filename.mp4";<br />
HttpContent bytesContent = new ByteArrayContent(System.IO.File.ReadAllBytes(sFilePath));<br />
using (var httpClient = new System.Net.Http.HttpClient())<br />
{<br />
using (var request = new HttpRequestMessage(new HttpMethod("POST"), sURL))<br />
{<br />
httpClient.Timeout = new System.TimeSpan(0, 60, 00);<br />
httpClient.DefaultRequestHeaders.Accept.Add(new MediaTypeWithQualityHeaderValue("application/json"));<br />
httpClient.DefaultRequestHeaders.TryAddWithoutValidation("key", "your_bbp_private_key");<br />
httpClient.DefaultRequestHeaders.TryAddWithoutValidation("url", "your_filename");<br />
var multipartContent = new MultipartFormDataContent();<br />
multipartContent.Add(bytesContent, "file", System.IO.Path.GetFileName(sFilePath));<br />
request.Content = multipartContent;<br />
var oInitialResponse = await httpClient.PostAsync(sURL, multipartContent);<br />
string sJsonResponse = await oInitialResponse.Content.ReadAsStringAsync();<br />
}<br />
}<br />
}<br />
</pre><br />
<p><br /><br />
</p><p>Sample Response:<br />
</p><br />
<pre>{"error":"","URL":"https://unchained.biblepay.org/BBSWt5B13GuM5xJQHYM468bLC5qxmRmQ7Y/9.mp4","result":200}<br />
</pre><br />
<p><br /><br />
</p><p><br /><br />
</p><p><br /><br />
</p><p><br /><br />
<br />
<br />
<h3>Live Service #2 - Database</h3><br />
<br><br />
<br><br />
You can use biblepay to set and retrieve database values for your personal use. <br />
From the BiblePay Core RPC client, you can set or retrieve a value.<br />
<br />
'''Set Database Value'''<br />
<br />
setdatabasevalue my_bbp_privkey table key value<br />
<br />
BiblePay will respond with either an error or success.<br />
<br />
<br />
''' Retrieve database value '''<br />
<br />
getdatabasevalue my_bbp_privkey table key<br />
<br />
BiblePay will respond with the value of the key.<br />
<br />
<br />
''' How do I generate a storage keypair? '''<br />
<br />
generatestoragetoken<br />
<br />
''' How do I retrieve my current monthly billing assessment? '''<br />
<br />
getstoragebalance bbp_pub_key<br />
<br />
<br />
<br />
<br />
<br />
</p><p><b>FAQ</b><br />
</p><p><br /><br />
Q: Where are my files stored and what is the durability?<br />
</p><p>A: The network is comprised of three partners: BiblePay (for metadata), BiblePay Sanctuaries, IPFS, and CDN (for retrieval). The durability is set higher than normal so that the files will never be deleted unless you fail to pay the BBP hosting fee.<br />
</p><p><br /><br />
Q: What is a CDN?<br />
</p><p>A: A content data network copies your file to hundreds of global POPs (Points of Presence) so that the file can be downloaded faster to your user. This also provides resilience, in case the file is attempted to be taken down due to censorship, your file will still be available. Also if a fiber optic line is cut in a certain area, your file will still be available to the rest of the world. The CDN also provides anti-ddos, meaning that the CDN network is larger than any potential ddos threat. A good use case for a CDN is a news article. If you host it on biblepay, even if the article is attacked by thousands of malicious botnet actors, our CDN will keep supplying that news article to your readers. News orgs already use CDNs for their articles.<br />
</p><p><br /><br />
Q: How does billing work?<br />
</p><p>A: Once per month, we bill your private key for the sum in size of the bytes hosted for that key to the key itself so please ensure your key has enough to cover future hosting. We create an invoice that may be viewed in My Invoices. If your key does not have enough funds to cover the fees, after the grace period elapses (+14 days), then the files that cannot be paid for will be deleted. Other files in good standing will stay hosted.<br />
</p><p><br /><br />
</p><p>Q: Why shouldn't I go directly to STORJ or Amazon?<br />
</p><p>A: For STORJ, you will find that you need to setup a lot of technical items such as your download gateway and you will need to deal with the command line to send and receive files while we offer a programmatic solution above. We also do all the technical work for you to make it easier for you. Additionally, you dont get a free CDN. With Amazon, you are dealing with big tech, who will definitely charge you for all public bandwidth consumption which could cost you more than BiblePay. For example if your file is abused (repeatedly downloaded millions of times you could end up with a very high S3 invoice). With BiblePay, we only charge for the storage. Finally, with BiblePay you are helping ORPHANS. It's easy to decide when you want to make the world a better place.<br />
</p><p><br /><br />
Q: What if I want my data private and not public, like a backup file?<br />
</p><p>A: Reach out to us on social.biblepay.org and ask for the feature and if the demand is there, we will add an encryption option for you so that your data at rest file in cloud is encrypted with your key.<br />
</p><p><br /><br />
</p><p><br /><br />
</p><br />
<hr /><br />
<p><br /><br />
</p><p><br /></div>Adminhttps://wiki.biblepay.org/index.php?title=API&diff=6913API2022-11-29T12:14:23Z<p>Admin: </p>
<hr />
<div></p><p><br /><br />
We are a blockchain with real world use cases.<br />
</p><p>We are offering an alternative to big tech, big media, and we are fighting for freedom. Just as God wants freedom for us, we want freedom for you. We do not believe in censoring free speech but the principles of the founding fathers. Additionally, when you use our services, you are paying for orphan sponsorships. What better relationship could there be?<br />
</p><p><br /><br />
Live Service #1:<br />
</p><p><br /><br />
<b> BiblePay S3 File Hosting (S3aas) </b><br />
</p><p>This API allows you to store files, accessible by public URL (via CDN). You may store small files all the way up to very large files (1 byte to 1Gigabyte per file).<br />
</p><p>Use cases: Upload your mp4 videos, your audio tracks, your encrypted backup files, your web site files, your images/css/assets for web hosting, share files etc.<br />
</p><p><b> S3 Endpoint for Curl (Linux, Mac, others) </b><br />
</p><p>Simply post your file from the command or through code as below, along with your biblepay private key in the Header field:<br />
</p><p>Example:<br />
</p><br />
<pre>curl -X POST <br />
-H "key: YOUR_BIBLEPAY_PRIVATE_KEY" <br />
-H "url: Your_preferred_filename"<br />
-F "file=@myfile.mp4" <br />
https://unchained.biblepay.org/api/web/bbpingress<br />
</pre><br />
Example:<br />
<pre>curl -X POST <br />
-H "key: U1234567890" <br />
-H "url: myfile.mp4"<br />
-F "file=@myfile.mp4" <br />
https://unchained.biblepay.org/api/web/bbpingress<br />
</pre><br />
<br />
<p><br /><br />
Response:<br />
</p><p>If successful, Biblepay will respond with an http-200 response, with JSON containing an empty error field, a result code with a value of 200, and the URL which you can use immediately.<br />
If unsuccessful, BiblePay will respond with an http-200 response, with JSON containing an error field with a populated reason, and a result code below zero.<br />
</p><p><br /><br />
<b> S3 Endpoint for C# </b><br />
</p><p>You can also post your file programatically in any language. For C#, please see this example below:<br />
</p><br />
<pre>public async static void UploadBiblePayFile()<br />
{<br />
string sURL = "https://unchained.biblepay.org/api/web/bbpingress";<br />
string sFilePath = "s:\\yourfolder\\filename.mp4";<br />
HttpContent bytesContent = new ByteArrayContent(System.IO.File.ReadAllBytes(sFilePath));<br />
using (var httpClient = new System.Net.Http.HttpClient())<br />
{<br />
using (var request = new HttpRequestMessage(new HttpMethod("POST"), sURL))<br />
{<br />
httpClient.Timeout = new System.TimeSpan(0, 60, 00);<br />
httpClient.DefaultRequestHeaders.Accept.Add(new MediaTypeWithQualityHeaderValue("application/json"));<br />
httpClient.DefaultRequestHeaders.TryAddWithoutValidation("key", "your_bbp_private_key");<br />
httpClient.DefaultRequestHeaders.TryAddWithoutValidation("url", "your_filename");<br />
var multipartContent = new MultipartFormDataContent();<br />
multipartContent.Add(bytesContent, "file", System.IO.Path.GetFileName(sFilePath));<br />
request.Content = multipartContent;<br />
var oInitialResponse = await httpClient.PostAsync(sURL, multipartContent);<br />
string sJsonResponse = await oInitialResponse.Content.ReadAsStringAsync();<br />
}<br />
}<br />
}<br />
</pre><br />
<p><br /><br />
</p><p>Sample Response:<br />
</p><br />
<pre>{"error":"","URL":"https://unchained.biblepay.org/BBSWt5B13GuM5xJQHYM468bLC5qxmRmQ7Y/9.mp4","result":200}<br />
</pre><br />
<p><br /><br />
</p><p><br /><br />
</p><p><br /><br />
</p><p><br /><br />
</p><p><b>FAQ</b><br />
</p><p><br /><br />
Q: Where are my files stored and what is the durability?<br />
</p><p>A: The network is comprised of three partners: BiblePay (for metadata), BiblePay Sanctuaries, IPFS, and CDN (for retrieval). The durability is set higher than normal so that the files will never be deleted unless you fail to pay the BBP hosting fee.<br />
</p><p><br /><br />
Q: What is a CDN?<br />
</p><p>A: A content data network copies your file to hundreds of global POPs (Points of Presence) so that the file can be downloaded faster to your user. This also provides resilience, in case the file is attempted to be taken down due to censorship, your file will still be available. Also if a fiber optic line is cut in a certain area, your file will still be available to the rest of the world. The CDN also provides anti-ddos, meaning that the CDN network is larger than any potential ddos threat. A good use case for a CDN is a news article. If you host it on biblepay, even if the article is attacked by thousands of malicious botnet actors, our CDN will keep supplying that news article to your readers. News orgs already use CDNs for their articles.<br />
</p><p><br /><br />
Q: How does billing work?<br />
</p><p>A: Once per month, we bill your private key for the sum in size of the bytes hosted for that key to the key itself so please ensure your key has enough to cover future hosting. We create an invoice that may be viewed in My Invoices. If your key does not have enough funds to cover the fees, after the grace period elapses (+14 days), then the files that cannot be paid for will be deleted. Other files in good standing will stay hosted.<br />
</p><p><br /><br />
</p><p>Q: Why shouldn't I go directly to STORJ or Amazon?<br />
</p><p>A: For STORJ, you will find that you need to setup a lot of technical items such as your download gateway and you will need to deal with the command line to send and receive files while we offer a programmatic solution above. We also do all the technical work for you to make it easier for you. Additionally, you dont get a free CDN. With Amazon, you are dealing with big tech, who will definitely charge you for all public bandwidth consumption which could cost you more than BiblePay. For example if your file is abused (repeatedly downloaded millions of times you could end up with a very high S3 invoice). With BiblePay, we only charge for the storage. Finally, with BiblePay you are helping ORPHANS. It's easy to decide when you want to make the world a better place.<br />
</p><p><br /><br />
Q: What if I want my data private and not public, like a backup file?<br />
</p><p>A: Reach out to us on social.biblepay.org and ask for the feature and if the demand is there, we will add an encryption option for you so that your data at rest file in cloud is encrypted with your key.<br />
</p><p><br /><br />
</p><p><br /><br />
</p><br />
<hr /><br />
<p><br /><br />
</p><p><br /></div>Adminhttps://wiki.biblepay.org/index.php?title=API&diff=6912API2022-11-29T12:13:42Z<p>Admin: </p>
<hr />
<div></p><p><br /><br />
We are a blockchain with real world use cases.<br />
</p><p>We are offering an alternative to big tech, big media, and we are fighting for freedom. Just as God wants freedom for us, we want freedom for you. We do not believe in censoring free speech but the principles of the founding fathers. Additionally, when you use our services, you are paying for orphan sponsorships. What better relationship could there be?<br />
</p><p><br /><br />
Live Service #1:<br />
</p><p><br /><br />
<b> BiblePay S3 File Hosting (S3aas) </b><br />
</p><p>This API allows you to store files, accessible by public URL (via CDN). You may store small files all the way up to very large files (1 byte to 1Gigabyte per file).<br />
</p><p>Use cases: Upload your mp4 videos, your audio tracks, your encrypted backup files, your web site files, your images/css/assets for web hosting, share files etc.<br />
</p><p><b> S3 Endpoint for Curl (Linux, Mac, others) </b><br />
</p><p>Simply post your file from the command or through code as below, along with your biblepay private key in the Header field:<br />
</p><p>Example:<br />
</p><br />
<pre>curl -X POST <br />
-H "key: YOUR_BIBLEPAY_PRIVATE_KEY" <br />
-H "url: Your_preferred_filename"<br />
-F "file=@myfile.mp4" <br />
https://unchained.biblepay.org/api/web/bbpingress<br />
</pre><br />
Example:<br />
<pre>curl -X POST <br />
-H "key: U1234567890" <br />
-H "url: myfile.mp4"<br />
-F "file=@myfile.mp4" <br />
https://unchained.biblepay.org/api/web/bbpingress<br />
</pre><br />
<br />
<p><br /><br />
Response:<br />
</p><p>If successful, Biblepay will respond with an http-200 response, with JSON containing an empty error field, a result code with a value of 200, and the URL which you can use immediately.<br />
If unsuccessful, BiblePay will respond with an http-200 response, with JSON containing an error field with a populated reason, and a result code below zero.<br />
</p><p><br /><br />
<b> S3 Endpoint for C# </b><br />
</p><p>You can also post your file programatically in any language. For C#, please see this example below:<br />
</p><br />
<pre>public async static void UploadBiblePayFile()<br />
{<br />
string sURL = "https://unchained.biblepay.org/api/web/bbpingress";<br />
string sFilePath = "s:\\yourfolder\\filename.mp4";<br />
HttpContent bytesContent = new ByteArrayContent(System.IO.File.ReadAllBytes(sFilePath));<br />
using (var httpClient = new System.Net.Http.HttpClient())<br />
{<br />
using (var request = new HttpRequestMessage(new HttpMethod("POST"), sURL))<br />
{<br />
httpClient.Timeout = new System.TimeSpan(0, 60, 00);<br />
httpClient.DefaultRequestHeaders.Accept.Add(new MediaTypeWithQualityHeaderValue("application/json"));<br />
httpClient.DefaultRequestHeaders.TryAddWithoutValidation("Key", "your_bbp_private_key");<br />
httpClient.DefaultRequestHeaders.TryAddWithoutValidation("url", "your_filename");<br />
var multipartContent = new MultipartFormDataContent();<br />
multipartContent.Add(bytesContent, "file", System.IO.Path.GetFileName(sFilePath));<br />
request.Content = multipartContent;<br />
var oInitialResponse = await httpClient.PostAsync(sURL, multipartContent);<br />
string sJsonResponse = await oInitialResponse.Content.ReadAsStringAsync();<br />
}<br />
}<br />
}<br />
</pre><br />
<p><br /><br />
</p><p>Sample Response:<br />
</p><br />
<pre>{"error":"","URL":"https://unchained.biblepay.org/BBSWt5B13GuM5xJQHYM468bLC5qxmRmQ7Y/9.mp4","result":200}<br />
</pre><br />
<p><br /><br />
</p><p><br /><br />
</p><p><br /><br />
</p><p><br /><br />
</p><p><b>FAQ</b><br />
</p><p><br /><br />
Q: Where are my files stored and what is the durability?<br />
</p><p>A: The network is comprised of three partners: BiblePay (for metadata), BiblePay Sanctuaries, IPFS, and CDN (for retrieval). The durability is set higher than normal so that the files will never be deleted unless you fail to pay the BBP hosting fee.<br />
</p><p><br /><br />
Q: What is a CDN?<br />
</p><p>A: A content data network copies your file to hundreds of global POPs (Points of Presence) so that the file can be downloaded faster to your user. This also provides resilience, in case the file is attempted to be taken down due to censorship, your file will still be available. Also if a fiber optic line is cut in a certain area, your file will still be available to the rest of the world. The CDN also provides anti-ddos, meaning that the CDN network is larger than any potential ddos threat. A good use case for a CDN is a news article. If you host it on biblepay, even if the article is attacked by thousands of malicious botnet actors, our CDN will keep supplying that news article to your readers. News orgs already use CDNs for their articles.<br />
</p><p><br /><br />
Q: How does billing work?<br />
</p><p>A: Once per month, we bill your private key for the sum in size of the bytes hosted for that key to the key itself so please ensure your key has enough to cover future hosting. We create an invoice that may be viewed in My Invoices. If your key does not have enough funds to cover the fees, after the grace period elapses (+14 days), then the files that cannot be paid for will be deleted. Other files in good standing will stay hosted.<br />
</p><p><br /><br />
</p><p>Q: Why shouldn't I go directly to STORJ or Amazon?<br />
</p><p>A: For STORJ, you will find that you need to setup a lot of technical items such as your download gateway and you will need to deal with the command line to send and receive files while we offer a programmatic solution above. We also do all the technical work for you to make it easier for you. Additionally, you dont get a free CDN. With Amazon, you are dealing with big tech, who will definitely charge you for all public bandwidth consumption which could cost you more than BiblePay. For example if your file is abused (repeatedly downloaded millions of times you could end up with a very high S3 invoice). With BiblePay, we only charge for the storage. Finally, with BiblePay you are helping ORPHANS. It's easy to decide when you want to make the world a better place.<br />
</p><p><br /><br />
Q: What if I want my data private and not public, like a backup file?<br />
</p><p>A: Reach out to us on social.biblepay.org and ask for the feature and if the demand is there, we will add an encryption option for you so that your data at rest file in cloud is encrypted with your key.<br />
</p><p><br /><br />
</p><p><br /><br />
</p><br />
<hr /><br />
<p><br /><br />
</p><p><br /></div>Adminhttps://wiki.biblepay.org/index.php?title=API&diff=6911API2022-11-28T01:58:32Z<p>Admin: </p>
<hr />
<div></p><p><br /><br />
We are a blockchain with real world use cases.<br />
</p><p>We are offering an alternative to big tech, big media, and we are fighting for freedom. Just as God wants freedom for us, we want freedom for you. We do not believe in censoring free speech but the principles of the founding fathers. Additionally, when you use our services, you are paying for orphan sponsorships. What better relationship could there be?<br />
</p><p><br /><br />
Live Service #1:<br />
</p><p><br /><br />
<b> BiblePay S3 File Hosting (S3aas) </b><br />
</p><p>This API allows you to store files, accessible by public URL (via CDN). You may store small files all the way up to very large files (1 byte to 1Gigabyte per file).<br />
</p><p>Use cases: Upload your mp4 videos, your audio tracks, your encrypted backup files, your web site files, your images/css/assets for web hosting, share files etc.<br />
</p><p><b> S3 Endpoint for Curl (Linux, Mac, others) </b><br />
</p><p>Simply post your file from the command or through code as below, along with your biblepay private key in the Header field:<br />
</p><p>Example:<br />
</p><br />
<pre>curl -X POST <br />
-H "key: YOUR_BIBLEPAY_PRIVATE_KEY" <br />
-H "url: Your_preferred_filename"<br />
-F "file=@myfile.mp4" <br />
https://unchained.biblepay.org/api/web/bbpingress<br />
</pre><br />
<p><br /><br />
Response:<br />
</p><p>If successful, Biblepay will respond with an http-200 response, with JSON containing an empty error field, a result code with a value of 200, and the URL which you can use immediately.<br />
If unsuccessful, BiblePay will respond with an http-200 response, with JSON containing an error field with a populated reason, and a result code below zero.<br />
</p><p><br /><br />
<b> S3 Endpoint for C# </b><br />
</p><p>You can also post your file programatically in any language. For C#, please see this example below:<br />
</p><br />
<pre>public async static void UploadBiblePayFile()<br />
{<br />
string sURL = "https://unchained.biblepay.org/api/web/bbpingress";<br />
string sFilePath = "s:\\yourfolder\\filename.mp4";<br />
HttpContent bytesContent = new ByteArrayContent(System.IO.File.ReadAllBytes(sFilePath));<br />
using (var httpClient = new System.Net.Http.HttpClient())<br />
{<br />
using (var request = new HttpRequestMessage(new HttpMethod("POST"), sURL))<br />
{<br />
httpClient.Timeout = new System.TimeSpan(0, 60, 00);<br />
httpClient.DefaultRequestHeaders.Accept.Add(new MediaTypeWithQualityHeaderValue("application/json"));<br />
httpClient.DefaultRequestHeaders.TryAddWithoutValidation("Key", "your_bbp_private_key");<br />
httpClient.DefaultRequestHeaders.TryAddWithoutValidation("url", "your_filename");<br />
var multipartContent = new MultipartFormDataContent();<br />
multipartContent.Add(bytesContent, "file", System.IO.Path.GetFileName(sFilePath));<br />
request.Content = multipartContent;<br />
var oInitialResponse = await httpClient.PostAsync(sURL, multipartContent);<br />
string sJsonResponse = await oInitialResponse.Content.ReadAsStringAsync();<br />
}<br />
}<br />
}<br />
</pre><br />
<p><br /><br />
</p><p>Sample Response:<br />
</p><br />
<pre>{"error":"","URL":"https://unchained.biblepay.org/BBSWt5B13GuM5xJQHYM468bLC5qxmRmQ7Y/9.mp4","result":200}<br />
</pre><br />
<p><br /><br />
</p><p><br /><br />
</p><p><br /><br />
</p><p><br /><br />
</p><p><b>FAQ</b><br />
</p><p><br /><br />
Q: Where are my files stored and what is the durability?<br />
</p><p>A: The network is comprised of three partners: BiblePay (for metadata), BiblePay Sanctuaries, IPFS, and CDN (for retrieval). The durability is set higher than normal so that the files will never be deleted unless you fail to pay the BBP hosting fee.<br />
</p><p><br /><br />
Q: What is a CDN?<br />
</p><p>A: A content data network copies your file to hundreds of global POPs (Points of Presence) so that the file can be downloaded faster to your user. This also provides resilience, in case the file is attempted to be taken down due to censorship, your file will still be available. Also if a fiber optic line is cut in a certain area, your file will still be available to the rest of the world. The CDN also provides anti-ddos, meaning that the CDN network is larger than any potential ddos threat. A good use case for a CDN is a news article. If you host it on biblepay, even if the article is attacked by thousands of malicious botnet actors, our CDN will keep supplying that news article to your readers. News orgs already use CDNs for their articles.<br />
</p><p><br /><br />
Q: How does billing work?<br />
</p><p>A: Once per month, we bill your private key for the sum in size of the bytes hosted for that key to the key itself so please ensure your key has enough to cover future hosting. We create an invoice that may be viewed in My Invoices. If your key does not have enough funds to cover the fees, after the grace period elapses (+14 days), then the files that cannot be paid for will be deleted. Other files in good standing will stay hosted.<br />
</p><p><br /><br />
</p><p>Q: Why shouldn't I go directly to STORJ or Amazon?<br />
</p><p>A: For STORJ, you will find that you need to setup a lot of technical items such as your download gateway and you will need to deal with the command line to send and receive files while we offer a programmatic solution above. We also do all the technical work for you to make it easier for you. Additionally, you dont get a free CDN. With Amazon, you are dealing with big tech, who will definitely charge you for all public bandwidth consumption which could cost you more than BiblePay. For example if your file is abused (repeatedly downloaded millions of times you could end up with a very high S3 invoice). With BiblePay, we only charge for the storage. Finally, with BiblePay you are helping ORPHANS. It's easy to decide when you want to make the world a better place.<br />
</p><p><br /><br />
Q: What if I want my data private and not public, like a backup file?<br />
</p><p>A: Reach out to us on social.biblepay.org and ask for the feature and if the demand is there, we will add an encryption option for you so that your data at rest file in cloud is encrypted with your key.<br />
</p><p><br /><br />
</p><p><br /><br />
</p><br />
<hr /><br />
<p><br /><br />
</p><p><br /></div>Adminhttps://wiki.biblepay.org/index.php?title=API&diff=6910API2022-11-28T01:58:02Z<p>Admin: </p>
<hr />
<div></p><p><br /><br />
We are a blockchain with real world use cases.<br />
</p><p>We are offering an alternative to big tech, big media, and we are fighting for freedom. Just as God wants freedom for us, we want freedom for you. We do not believe in censoring free speech but the principles of the founding fathers. Additionally, when you use our services, you are paying for orphan sponsorships. What better relationship could there be?<br />
</p><p><br /><br />
Live Service #1:<br />
</p><p><br /><br />
<b> BiblePay S3 File Hosting (S3aas) </b><br />
</p><p>This API allows you to store files, accessible by public URL (via CDN). You may store small files all the way up to very large files (1 byte to 1Gigabyte per file).<br />
</p><p>Use cases: Upload your mp4 videos, your audio tracks, your encrypted backup files, your web site files, your images/css/assets for web hosting, share files etc.<br />
</p><p><b> S3 Endpoint for Curl (Linux, Mac, others) </b><br />
</p><p>Simply post your file from the command or through code as below, along with your biblepay private key in the Header field:<br />
</p><p>Example:<br />
</p><br />
<pre>curl -X POST <br />
-H "key: YOUR_BIBLEPAY_PRIVATE_KEY" <br />
-H "url: Your_preferred_filename"<br />
-F "file=@myfile.mp4" <br />
https://unchained.biblepay.org/api/web/bbpingress<br />
</pre><br />
<p><br /><br />
Response:<br />
</p><p>If successful, Biblepay will respond with an http-200 response, with JSON containing an empty error field, a result code with a value of 200, and the URL which you can use immediately.<br />
If unsuccessful, BiblePay will respond with an http-200 response, with JSON containing an error field with a populated reason, and a result code below zero.<br />
</p><p><br /><br />
<b> S3 Endpoint for C# </b><br />
</p><p>You can also post your file programatically in any language. For C#, please see this example below:<br />
</p><br />
<pre>public async static void UploadBiblePayFile()<br />
{<br />
string sURL = "https://unchained.biblepay.org/api/web/bbpingress";<br />
string sFilePath = "s:\\yourfolder\\filename.mp4";<br />
HttpContent bytesContent = new ByteArrayContent(System.IO.File.ReadAllBytes(sFilePath));<br />
using (var httpClient = new System.Net.Http.HttpClient())<br />
{<br />
using (var request = new HttpRequestMessage(new HttpMethod("POST"), sURL))<br />
{<br />
httpClient.Timeout = new System.TimeSpan(0, 60, 00);<br />
httpClient.DefaultRequestHeaders.Accept.Add(new MediaTypeWithQualityHeaderValue("application/json"));<br />
httpClient.DefaultRequestHeaders.TryAddWithoutValidation("Key", "your_bbp_private_key");<br />
httpClient.DefaultRequestHeaders.TryAddWithoutValidation("url", "your_filename");<br />
var multipartContent = new MultipartFormDataContent();<br />
multipartContent.Add(bytesContent, "file", System.IO.Path.GetFileName(sFilePath));<br />
request.Content = multipartContent;<br />
var oInitialResponse = await httpClient.PostAsync(sURL, multipartContent);<br />
string sJsonResponse = await oInitialResponse.Content.ReadAsStringAsync();<br />
}<br />
}<br />
}<br />
</pre><br />
<p><br /><br />
</p><p>Sample Response:<br />
</p><br />
<pre>{"error":"","URL":"https://bbp.s3.filebase.com/BBSWt5B13GuM5xJQHYM468bLC5qxmRmQ7Y/9.mp4","result":200}<br />
</pre><br />
<p><br /><br />
</p><p><br /><br />
</p><p><br /><br />
</p><p><br /><br />
</p><p><b>FAQ</b><br />
</p><p><br /><br />
Q: Where are my files stored and what is the durability?<br />
</p><p>A: The network is comprised of three partners: BiblePay (for metadata), BiblePay Sanctuaries, IPFS, and CDN (for retrieval). The durability is set higher than normal so that the files will never be deleted unless you fail to pay the BBP hosting fee.<br />
</p><p><br /><br />
Q: What is a CDN?<br />
</p><p>A: A content data network copies your file to hundreds of global POPs (Points of Presence) so that the file can be downloaded faster to your user. This also provides resilience, in case the file is attempted to be taken down due to censorship, your file will still be available. Also if a fiber optic line is cut in a certain area, your file will still be available to the rest of the world. The CDN also provides anti-ddos, meaning that the CDN network is larger than any potential ddos threat. A good use case for a CDN is a news article. If you host it on biblepay, even if the article is attacked by thousands of malicious botnet actors, our CDN will keep supplying that news article to your readers. News orgs already use CDNs for their articles.<br />
</p><p><br /><br />
Q: How does billing work?<br />
</p><p>A: Once per month, we bill your private key for the sum in size of the bytes hosted for that key to the key itself so please ensure your key has enough to cover future hosting. We create an invoice that may be viewed in My Invoices. If your key does not have enough funds to cover the fees, after the grace period elapses (+14 days), then the files that cannot be paid for will be deleted. Other files in good standing will stay hosted.<br />
</p><p><br /><br />
</p><p>Q: Why shouldn't I go directly to STORJ or Amazon?<br />
</p><p>A: For STORJ, you will find that you need to setup a lot of technical items such as your download gateway and you will need to deal with the command line to send and receive files while we offer a programmatic solution above. We also do all the technical work for you to make it easier for you. Additionally, you dont get a free CDN. With Amazon, you are dealing with big tech, who will definitely charge you for all public bandwidth consumption which could cost you more than BiblePay. For example if your file is abused (repeatedly downloaded millions of times you could end up with a very high S3 invoice). With BiblePay, we only charge for the storage. Finally, with BiblePay you are helping ORPHANS. It's easy to decide when you want to make the world a better place.<br />
</p><p><br /><br />
Q: What if I want my data private and not public, like a backup file?<br />
</p><p>A: Reach out to us on social.biblepay.org and ask for the feature and if the demand is there, we will add an encryption option for you so that your data at rest file in cloud is encrypted with your key.<br />
</p><p><br /><br />
</p><p><br /><br />
</p><br />
<hr /><br />
<p><br /><br />
</p><p><br /></div>Adminhttps://wiki.biblepay.org/index.php?title=API&diff=6909API2022-11-27T21:13:41Z<p>Admin: </p>
<hr />
<div></p><p><br /><br />
We are a blockchain with real world use cases.<br />
</p><p>We are offering an alternative to big tech, big media, and we are fighting for freedom. Just as God wants freedom for us, we want freedom for you. We do not believe in censoring free speech but the principles of the founding fathers. Additionally, when you use our services, you are paying for orphan sponsorships. What better relationship could there be?<br />
</p><p><br /><br />
Live Service #1:<br />
</p><p><br /><br />
<b> BiblePay S3 File Hosting (S3aas) </b><br />
</p><p>This API allows you to store files, accessible by public URL (via CDN). You may store small files all the way up to very large files (1 byte to 1Gigabyte per file).<br />
</p><p>Use cases: Upload your mp4 videos, your audio tracks, your encrypted backup files, your web site files, your images/css/assets for web hosting, share files etc.<br />
</p><p><b> S3 Endpoint for Curl (Linux, Mac, others) </b><br />
</p><p>Simply post your file from the command or through code as below, along with your biblepay private key in the Header field:<br />
</p><p>Example:<br />
</p><br />
<pre>curl -X POST <br />
-H "key: YOUR_BIBLEPAY_PRIVATE_KEY" <br />
-F "file=@myfile.mp4" <br />
https://unchained.biblepay.org/api/web/bbpingress<br />
</pre><br />
<p><br /><br />
Response:<br />
</p><p>If successful, Biblepay will respond with an http-200 response, with JSON containing an empty error field, a result code with a value of 200, and the URL which you can use immediately.<br />
If unsuccessful, BiblePay will respond with an http-200 response, with JSON containing an error field with a populated reason, and a result code below zero.<br />
</p><p><br /><br />
<b> S3 Endpoint for C# </b><br />
</p><p>You can also post your file programatically in any language. For C#, please see this example below:<br />
</p><br />
<pre>public async static void UploadBiblePayFile()<br />
{<br />
string sURL = "https://unchained.biblepay.org/api/web/bbpingress";<br />
string sFilePath = "s:\\san\\rapture2\\9.mp4";<br />
HttpContent bytesContent = new ByteArrayContent(System.IO.File.ReadAllBytes(sFilePath));<br />
using (var httpClient = new System.Net.Http.HttpClient())<br />
{<br />
using (var request = new HttpRequestMessage(new HttpMethod("POST"), sURL))<br />
{<br />
httpClient.Timeout = new System.TimeSpan(0, 60, 00);<br />
httpClient.DefaultRequestHeaders.Accept.Add(new MediaTypeWithQualityHeaderValue("application/json"));<br />
httpClient.DefaultRequestHeaders.TryAddWithoutValidation("Key", "your_bbp_private_key");<br />
var multipartContent = new MultipartFormDataContent();<br />
multipartContent.Add(bytesContent, "file", System.IO.Path.GetFileName(sFilePath));<br />
request.Content = multipartContent;<br />
var oInitialResponse = await httpClient.PostAsync(sURL, multipartContent);<br />
string sJsonResponse = await oInitialResponse.Content.ReadAsStringAsync();<br />
}<br />
}<br />
}<br />
</pre><br />
<p><br /><br />
</p><p>Sample Response:<br />
</p><br />
<pre>{"error":"","URL":"https://bbp.s3.filebase.com/BBSWt5B13GuM5xJQHYM468bLC5qxmRmQ7Y/9.mp4","result":200}<br />
</pre><br />
<p><br /><br />
</p><p><br /><br />
</p><p><b> BIPFS - BiblePay Immutable Public File System (BIPFSaas) </b><br />
</p><p>This API allows you to store provably immutable files, accessible by public URL (via CDN). You may store small files all the way up to very large files (1 byte to 1Gigabyte per file).<br />
</p><p>The storage is extremely cost effective, priced at&#160;: 1 bbp per 100 megabytes per month.<br />
The files are available worldwide through our anti-ddos CDN which is located in all major cities and countries.<br />
</p><p>Bandwidth costs: Zero.<br />
</p><p>Use cases: NFT metadata files, contract data, special social media posts, provable timestamped videos, or any file that needs immutability.<br />
</p><p>How it is immutable: <br />
First, we hash the file with a standard sha256 hash.<br />
We require the sha256 hash to become the filename. The filename extension is preserved. <br />
Once the file is stored, we create an immutable biblepay transaction pointing to the file which contains the sha256 hash (this permanently preserves the timestamp and the record).<br />
The file contents can never be changed (because it can always be proven the hash matches) except in the case of non-payment.<br />
In the case of nonpayment, the contents of the file will be served as "UNPAID" and the blockchain record of the file will remain intact.<br />
</p><p><b> S3 Endpoint for Curl (Linux, Mac, others) </b><br />
</p><p>Simply post your file from the command or through code as below, along with your biblepay private key in the Header field:<br />
</p><p>Example:<br />
</p><br />
<pre>curl -X POST <br />
-H "key: YOUR_BIBLEPAY_PRIVATE_KEY" <br />
-H "immutable: 1" <br />
-F "file.mp4" <br />
https://unchained.biblepay.org/api/web/bbpingress<br />
</pre><br />
<p><br /><br />
Response:<br />
</p><p>If successful, Biblepay will respond with an http-200 response, with JSON containing an empty error field, a result code with a value of 200, and the URL which you can use immediately.<br />
If unsuccessful, BiblePay will respond with an http-200 response, with JSON containing an error field with a populated reason, and a result code below zero.<br />
</p><p><br /><br />
</p><p><br /><br />
</p><p><br /><br />
</p><p><b>FAQ</b><br />
</p><p><br /><br />
Q: Where are my files stored and what is the durability?<br />
</p><p>A: The network is comprised of three partners: BiblePay (for metadata), BiblePay Sanctuaries, IPFS, and CDN (for retrieval). The durability is set higher than normal so that the files will never be deleted unless you fail to pay the BBP hosting fee.<br />
</p><p><br /><br />
Q: What is a CDN?<br />
</p><p>A: A content data network copies your file to hundreds of global POPs (Points of Presence) so that the file can be downloaded faster to your user. This also provides resilience, in case the file is attempted to be taken down due to censorship, your file will still be available. Also if a fiber optic line is cut in a certain area, your file will still be available to the rest of the world. The CDN also provides anti-ddos, meaning that the CDN network is larger than any potential ddos threat. A good use case for a CDN is a news article. If you host it on biblepay, even if the article is attacked by thousands of malicious botnet actors, our CDN will keep supplying that news article to your readers. News orgs already use CDNs for their articles.<br />
</p><p><br /><br />
Q: How does billing work?<br />
</p><p>A: Once per month, we bill your private key for the sum in size of the bytes hosted for that key to the key itself so please ensure your key has enough to cover future hosting. We create an invoice that may be viewed in My Invoices. If your key does not have enough funds to cover the fees, after the grace period elapses (+14 days), then the files that cannot be paid for will be deleted. Other files in good standing will stay hosted.<br />
</p><p><br /><br />
</p><p>Q: Why shouldn't I go directly to STORJ or Amazon?<br />
</p><p>A: For STORJ, you will find that you need to setup a lot of technical items such as your download gateway and you will need to deal with the command line to send and receive files while we offer a programmatic solution above. We also do all the technical work for you to make it easier for you. Additionally, you dont get a free CDN. With Amazon, you are dealing with big tech, who will definitely charge you for all public bandwidth consumption which could cost you more than BiblePay. For example if your file is abused (repeatedly downloaded millions of times you could end up with a very high S3 invoice). With BiblePay, we only charge for the storage. Finally, with BiblePay you are helping ORPHANS. It's easy to decide when you want to make the world a better place.<br />
</p><p><br /><br />
Q: What if I want my data private and not public, like a backup file?<br />
</p><p>A: Reach out to us on social.biblepay.org and ask for the feature and if the demand is there, we will add an encryption option for you so that your data at rest file in cloud is encrypted with your key.<br />
</p><p><br /><br />
</p><p><br /><br />
</p><br />
<hr /><br />
<p><br /><br />
</p><p><br /></div>Adminhttps://wiki.biblepay.org/index.php?title=API&diff=6908API2022-11-27T20:55:39Z<p>Admin: </p>
<hr />
<div></p><p><br /><br />
We are a blockchain with real world use cases.<br />
</p><p>We are offering an alternative to big tech, big media, and we are fighting for freedom. Just as God wants freedom for us, we want freedom for you. We do not believe in censoring free speech but the principles of the founding fathers. Additionally, when you use our services, you are paying for orphan sponsorships. What better relationship could there be?<br />
</p><p><br /><br />
Live Service #1:<br />
</p><p><br /><br />
<b> BiblePay S3 File Hosting (S3aas) </b><br />
</p><p>This API allows you to store files, accessible by public URL (via CDN). You may store small files all the way up to very large files (1 byte to 1Gigabyte per file).<br />
</p><p>The storage is extremely cost effective, priced at&#160;: 1 bbp per 100 megabytes per month.<br />
The files are available worldwide through our anti-ddos CDN which is located in all major cities and countries.<br />
</p><p>Bandwidth costs: Zero.<br />
</p><p>Use cases: Upload your mp4 videos, your audio tracks, your encrypted backup files, your web site files, your images/css/assets for web hosting, share files etc.<br />
</p><p><b> S3 Endpoint for Curl (Linux, Mac, others) </b><br />
</p><p>Simply post your file from the command or through code as below, along with your biblepay private key in the Header field:<br />
</p><p>Example:<br />
</p><br />
<pre>curl -X POST <br />
-H "key: YOUR_BIBLEPAY_PRIVATE_KEY" <br />
-F "file=@myfile.mp4" <br />
https://unchained.biblepay.org/api/web/bbpingress<br />
</pre><br />
<p><br /><br />
Response:<br />
</p><p>If successful, Biblepay will respond with an http-200 response, with JSON containing an empty error field, a result code with a value of 200, and the URL which you can use immediately.<br />
If unsuccessful, BiblePay will respond with an http-200 response, with JSON containing an error field with a populated reason, and a result code below zero.<br />
</p><p><br /><br />
<b> S3 Endpoint for C# </b><br />
</p><p>You can also post your file programatically in any language. For C#, please see this example below:<br />
</p><br />
<pre>public async static void UploadBiblePayFile()<br />
{<br />
string sURL = "https://unchained.biblepay.org/api/web/bbpingress";<br />
string sFilePath = "s:\\san\\rapture2\\9.mp4";<br />
HttpContent bytesContent = new ByteArrayContent(System.IO.File.ReadAllBytes(sFilePath));<br />
using (var httpClient = new System.Net.Http.HttpClient())<br />
{<br />
using (var request = new HttpRequestMessage(new HttpMethod("POST"), sURL))<br />
{<br />
httpClient.Timeout = new System.TimeSpan(0, 60, 00);<br />
httpClient.DefaultRequestHeaders.Accept.Add(new MediaTypeWithQualityHeaderValue("application/json"));<br />
httpClient.DefaultRequestHeaders.TryAddWithoutValidation("Key", "your_bbp_private_key");<br />
var multipartContent = new MultipartFormDataContent();<br />
multipartContent.Add(bytesContent, "file", System.IO.Path.GetFileName(sFilePath));<br />
request.Content = multipartContent;<br />
var oInitialResponse = await httpClient.PostAsync(sURL, multipartContent);<br />
string sJsonResponse = await oInitialResponse.Content.ReadAsStringAsync();<br />
}<br />
}<br />
}<br />
</pre><br />
<p><br /><br />
</p><p>Sample Response:<br />
</p><br />
<pre>{"error":"","URL":"https://bbp.s3.filebase.com/BBSWt5B13GuM5xJQHYM468bLC5qxmRmQ7Y/9.mp4","result":200}<br />
</pre><br />
<p><br /><br />
</p><p><br /><br />
</p><p><b> BIPFS - BiblePay Immutable Public File System (BIPFSaas) </b><br />
</p><p>This API allows you to store provably immutable files, accessible by public URL (via CDN). You may store small files all the way up to very large files (1 byte to 1Gigabyte per file).<br />
</p><p>The storage is extremely cost effective, priced at&#160;: 1 bbp per 100 megabytes per month.<br />
The files are available worldwide through our anti-ddos CDN which is located in all major cities and countries.<br />
</p><p>Bandwidth costs: Zero.<br />
</p><p>Use cases: NFT metadata files, contract data, special social media posts, provable timestamped videos, or any file that needs immutability.<br />
</p><p>How it is immutable: <br />
First, we hash the file with a standard sha256 hash.<br />
We require the sha256 hash to become the filename. The filename extension is preserved. <br />
Once the file is stored, we create an immutable biblepay transaction pointing to the file which contains the sha256 hash (this permanently preserves the timestamp and the record).<br />
The file contents can never be changed (because it can always be proven the hash matches) except in the case of non-payment.<br />
In the case of nonpayment, the contents of the file will be served as "UNPAID" and the blockchain record of the file will remain intact.<br />
</p><p><b> S3 Endpoint for Curl (Linux, Mac, others) </b><br />
</p><p>Simply post your file from the command or through code as below, along with your biblepay private key in the Header field:<br />
</p><p>Example:<br />
</p><br />
<pre>curl -X POST <br />
-H "key: YOUR_BIBLEPAY_PRIVATE_KEY" <br />
-H "immutable: 1" <br />
-F "file.mp4" <br />
https://unchained.biblepay.org/api/web/bbpingress<br />
</pre><br />
<p><br /><br />
Response:<br />
</p><p>If successful, Biblepay will respond with an http-200 response, with JSON containing an empty error field, a result code with a value of 200, and the URL which you can use immediately.<br />
If unsuccessful, BiblePay will respond with an http-200 response, with JSON containing an error field with a populated reason, and a result code below zero.<br />
</p><p><br /><br />
</p><p><br /><br />
</p><p><br /><br />
</p><p><b>FAQ</b><br />
</p><p><br /><br />
Q: Where are my files stored and what is the durability?<br />
</p><p>A: The network is comprised of three partners: BiblePay (for metadata), BiblePay Sanctuaries, IPFS, and CDN (for retrieval). The durability is set higher than normal so that the files will never be deleted unless you fail to pay the BBP hosting fee.<br />
</p><p><br /><br />
Q: What is a CDN?<br />
</p><p>A: A content data network copies your file to hundreds of global POPs (Points of Presence) so that the file can be downloaded faster to your user. This also provides resilience, in case the file is attempted to be taken down due to censorship, your file will still be available. Also if a fiber optic line is cut in a certain area, your file will still be available to the rest of the world. The CDN also provides anti-ddos, meaning that the CDN network is larger than any potential ddos threat. A good use case for a CDN is a news article. If you host it on biblepay, even if the article is attacked by thousands of malicious botnet actors, our CDN will keep supplying that news article to your readers. News orgs already use CDNs for their articles.<br />
</p><p><br /><br />
Q: How does billing work?<br />
</p><p>A: Once per month, we bill your private key for the sum in size of the bytes hosted for that key to the key itself so please ensure your key has enough to cover future hosting. We create an invoice that may be viewed in My Invoices. If your key does not have enough funds to cover the fees, after the grace period elapses (+14 days), then the files that cannot be paid for will be deleted. Other files in good standing will stay hosted.<br />
</p><p><br /><br />
</p><p>Q: Why shouldn't I go directly to STORJ or Amazon?<br />
</p><p>A: For STORJ, you will find that you need to setup a lot of technical items such as your download gateway and you will need to deal with the command line to send and receive files while we offer a programmatic solution above. We also do all the technical work for you to make it easier for you. Additionally, you dont get a free CDN. With Amazon, you are dealing with big tech, who will definitely charge you for all public bandwidth consumption which could cost you more than BiblePay. For example if your file is abused (repeatedly downloaded millions of times you could end up with a very high S3 invoice). With BiblePay, we only charge for the storage. Finally, with BiblePay you are helping ORPHANS. It's easy to decide when you want to make the world a better place.<br />
</p><p><br /><br />
Q: What if I want my data private and not public, like a backup file?<br />
</p><p>A: Reach out to us on social.biblepay.org and ask for the feature and if the demand is there, we will add an encryption option for you so that your data at rest file in cloud is encrypted with your key.<br />
</p><p><br /><br />
</p><p><br /><br />
</p><br />
<hr /><br />
<p><br /><br />
</p><p><br /></div>Adminhttps://wiki.biblepay.org/index.php?title=API&diff=6907API2022-11-27T16:34:04Z<p>Admin: </p>
<hr />
<div></p><p><br /><br />
We are a blockchain with real world use cases.<br />
</p><p>We are offering an alternative to big tech, big media, and we are fighting for freedom. Just as God wants freedom for us, we want freedom for you. We do not believe in censoring free speech but the principles of the founding fathers. Additionally, when you use our services, you are paying for orphan sponsorships. What better relationship could there be?<br />
</p><p><br /><br />
Live Service #1:<br />
</p><p><br /><br />
<b> BiblePay S3 File Hosting (S3aas) </b><br />
</p><p>This API allows you to store files, accessible by public URL (via CDN). You may store small files all the way up to very large files (1 byte to 1Gigabyte per file).<br />
</p><p>The storage is extremely cost effective, priced at&#160;: 1 bbp per 100 megabytes per month.<br />
The files are available worldwide through our anti-ddos CDN which is located in all major cities and countries.<br />
</p><p>Bandwidth costs: Zero.<br />
</p><p>Use cases: Upload your mp4 videos, your audio tracks, your encrypted backup files, your web site files, your images/css/assets for web hosting, share files etc.<br />
</p><p><b> S3 Endpoint for Curl (Linux, Mac, others) </b><br />
</p><p>Simply post your file from the command or through code as below, along with your biblepay private key in the Header field:<br />
</p><p>Example:<br />
</p><br />
<pre>curl -X POST <br />
-H "key: YOUR_BIBLEPAY_PRIVATE_KEY" <br />
-F "myfile.mp4" <br />
https://unchained.biblepay.org/api/web/bbpingress<br />
</pre><br />
<p><br /><br />
Response:<br />
</p><p>If successful, Biblepay will respond with an http-200 response, with JSON containing an empty error field, a result code with a value of 200, and the URL which you can use immediately.<br />
If unsuccessful, BiblePay will respond with an http-200 response, with JSON containing an error field with a populated reason, and a result code below zero.<br />
</p><p><br /><br />
<b> S3 Endpoint for C# </b><br />
</p><p>You can also post your file programatically in any language. For C#, please see this example below:<br />
</p><br />
<pre>public async static void UploadBiblePayFile()<br />
{<br />
string sURL = "https://unchained.biblepay.org/api/web/bbpingress";<br />
string sFilePath = "s:\\san\\rapture2\\9.mp4";<br />
HttpContent bytesContent = new ByteArrayContent(System.IO.File.ReadAllBytes(sFilePath));<br />
using (var httpClient = new System.Net.Http.HttpClient())<br />
{<br />
using (var request = new HttpRequestMessage(new HttpMethod("POST"), sURL))<br />
{<br />
httpClient.Timeout = new System.TimeSpan(0, 60, 00);<br />
httpClient.DefaultRequestHeaders.Accept.Add(new MediaTypeWithQualityHeaderValue("application/json"));<br />
httpClient.DefaultRequestHeaders.TryAddWithoutValidation("Key", "your_bbp_private_key");<br />
var multipartContent = new MultipartFormDataContent();<br />
multipartContent.Add(bytesContent, "file", System.IO.Path.GetFileName(sFilePath));<br />
request.Content = multipartContent;<br />
var oInitialResponse = await httpClient.PostAsync(sURL, multipartContent);<br />
string sJsonResponse = await oInitialResponse.Content.ReadAsStringAsync();<br />
}<br />
}<br />
}<br />
</pre><br />
<p><br /><br />
</p><p>Sample Response:<br />
</p><br />
<pre>{"error":"","URL":"https://bbp.s3.filebase.com/BBSWt5B13GuM5xJQHYM468bLC5qxmRmQ7Y/9.mp4","result":200}<br />
</pre><br />
<p><br /><br />
</p><p><br /><br />
</p><p><b> BIPFS - BiblePay Immutable Public File System (BIPFSaas) </b><br />
</p><p>This API allows you to store provably immutable files, accessible by public URL (via CDN). You may store small files all the way up to very large files (1 byte to 1Gigabyte per file).<br />
</p><p>The storage is extremely cost effective, priced at&#160;: 1 bbp per 100 megabytes per month.<br />
The files are available worldwide through our anti-ddos CDN which is located in all major cities and countries.<br />
</p><p>Bandwidth costs: Zero.<br />
</p><p>Use cases: NFT metadata files, contract data, special social media posts, provable timestamped videos, or any file that needs immutability.<br />
</p><p>How it is immutable: <br />
First, we hash the file with a standard sha256 hash.<br />
We require the sha256 hash to become the filename. The filename extension is preserved. <br />
Once the file is stored, we create an immutable biblepay transaction pointing to the file which contains the sha256 hash (this permanently preserves the timestamp and the record).<br />
The file contents can never be changed (because it can always be proven the hash matches) except in the case of non-payment.<br />
In the case of nonpayment, the contents of the file will be served as "UNPAID" and the blockchain record of the file will remain intact.<br />
</p><p><b> S3 Endpoint for Curl (Linux, Mac, others) </b><br />
</p><p>Simply post your file from the command or through code as below, along with your biblepay private key in the Header field:<br />
</p><p>Example:<br />
</p><br />
<pre>curl -X POST <br />
-H "key: YOUR_BIBLEPAY_PRIVATE_KEY" <br />
-H "immutable: 1" <br />
-F "file.mp4" <br />
https://unchained.biblepay.org/api/web/bbpingress<br />
</pre><br />
<p><br /><br />
Response:<br />
</p><p>If successful, Biblepay will respond with an http-200 response, with JSON containing an empty error field, a result code with a value of 200, and the URL which you can use immediately.<br />
If unsuccessful, BiblePay will respond with an http-200 response, with JSON containing an error field with a populated reason, and a result code below zero.<br />
</p><p><br /><br />
</p><p><br /><br />
</p><p><br /><br />
</p><p><b>FAQ</b><br />
</p><p><br /><br />
Q: Where are my files stored and what is the durability?<br />
</p><p>A: The network is comprised of three partners: BiblePay (for metadata), BiblePay Sanctuaries, IPFS, and CDN (for retrieval). The durability is set higher than normal so that the files will never be deleted unless you fail to pay the BBP hosting fee.<br />
</p><p><br /><br />
Q: What is a CDN?<br />
</p><p>A: A content data network copies your file to hundreds of global POPs (Points of Presence) so that the file can be downloaded faster to your user. This also provides resilience, in case the file is attempted to be taken down due to censorship, your file will still be available. Also if a fiber optic line is cut in a certain area, your file will still be available to the rest of the world. The CDN also provides anti-ddos, meaning that the CDN network is larger than any potential ddos threat. A good use case for a CDN is a news article. If you host it on biblepay, even if the article is attacked by thousands of malicious botnet actors, our CDN will keep supplying that news article to your readers. News orgs already use CDNs for their articles.<br />
</p><p><br /><br />
Q: How does billing work?<br />
</p><p>A: Once per month, we bill your private key for the sum in size of the bytes hosted for that key to the key itself so please ensure your key has enough to cover future hosting. We create an invoice that may be viewed in My Invoices. If your key does not have enough funds to cover the fees, after the grace period elapses (+14 days), then the files that cannot be paid for will be deleted. Other files in good standing will stay hosted.<br />
</p><p><br /><br />
</p><p>Q: Why shouldn't I go directly to STORJ or Amazon?<br />
</p><p>A: For STORJ, you will find that you need to setup a lot of technical items such as your download gateway and you will need to deal with the command line to send and receive files while we offer a programmatic solution above. We also do all the technical work for you to make it easier for you. Additionally, you dont get a free CDN. With Amazon, you are dealing with big tech, who will definitely charge you for all public bandwidth consumption which could cost you more than BiblePay. For example if your file is abused (repeatedly downloaded millions of times you could end up with a very high S3 invoice). With BiblePay, we only charge for the storage. Finally, with BiblePay you are helping ORPHANS. It's easy to decide when you want to make the world a better place.<br />
</p><p><br /><br />
Q: What if I want my data private and not public, like a backup file?<br />
</p><p>A: Reach out to us on social.biblepay.org and ask for the feature and if the demand is there, we will add an encryption option for you so that your data at rest file in cloud is encrypted with your key.<br />
</p><p><br /><br />
</p><p><br /><br />
</p><br />
<hr /><br />
<p><br /><br />
</p><p><br /></div>Adminhttps://wiki.biblepay.org/index.php?title=API&diff=6906API2022-11-27T16:33:20Z<p>Admin: </p>
<hr />
<div></p><p><br /><br />
We are a blockchain with real world use cases.<br />
</p><p>We are offering an alternative to big tech, big media, and we are fighting for freedom. Just as God wants freedom for us, we want freedom for you. We do not believe in censoring free speech but the principles of the founding fathers. Additionally, when you use our services, you are paying for orphan sponsorships. What better relationship could there be?<br />
</p><p><br /><br />
Live Service #1:<br />
</p><p><br /><br />
<b> BiblePay S3 File Hosting (S3aas) </b><br />
</p><p>This API allows you to store files, accessible by public URL (via CDN). You may store small files all the way up to very large files (1 byte to 1Gigabyte per file).<br />
</p><p>The storage is extremely cost effective, priced at&#160;: 1 bbp per 100 megabytes per month.<br />
The files are available worldwide through our anti-ddos CDN which is located in all major cities and countries.<br />
</p><p>Bandwidth costs: Zero.<br />
</p><p>Use cases: Upload your mp4 videos, your audio tracks, your encrypted backup files, your web site files, your images/css/assets for web hosting, share files etc.<br />
</p><p><b> S3 Endpoint for Curl (Linux, Mac, others) </b><br />
</p><p>Simply post your file from the command or through code as below, along with your biblepay private key in the Header field:<br />
</p><p>Example:<br />
</p><br />
<pre>curl -X POST <br />
-H "key: YOUR_BIBLEPAY_PRIVATE_KEY" <br />
-F "myfile.mp4" <br />
https://unchained.biblepay.org/api/web/bbpingress<br />
</pre><br />
<p><br /><br />
Response:<br />
</p><p>If successful, Biblepay will respond with an http-200 response, with JSON containing an empty error field, a result code with a value of 200, and the URL which you can use immediately.<br />
If unsuccessful, BiblePay will respond with an http-200 response, with JSON containing an error field with a populated reason, and a result code below zero.<br />
</p><p><br /><br />
<b> S3 Endpoint for C# </b><br />
</p><p>You can also post your file programatically in any language. For C#, please see this example below:<br />
</p><br />
<pre>public async static void UploadBiblePayFile()<br />
{<br />
string sURL = "https://unchained.biblepay.org/api/web/bbpingress";<br />
string sFilePath = "s:\\san\\rapture2\\9.mp4";<br />
HttpContent bytesContent = new ByteArrayContent(System.IO.File.ReadAllBytes(sFilePath));<br />
using (var httpClient = new System.Net.Http.HttpClient())<br />
{<br />
using (var request = new HttpRequestMessage(new HttpMethod("POST"), sURL))<br />
{<br />
httpClient.Timeout = new System.TimeSpan(0, 60, 00);<br />
httpClient.DefaultRequestHeaders.Accept.Add(new MediaTypeWithQualityHeaderValue("application/json"));<br />
httpClient.DefaultRequestHeaders.TryAddWithoutValidation("Key", "your_bbp_private_key");<br />
var multipartContent = new MultipartFormDataContent();<br />
multipartContent.Add(bytesContent, "file", System.IO.Path.GetFileName(sFilePath));<br />
request.Content = multipartContent;<br />
var oInitialResponse = await httpClient.PostAsync(sURL, multipartContent);<br />
string sJsonResponse = await oInitialResponse.Content.ReadAsStringAsync();<br />
}<br />
}<br />
}<br />
</pre><br />
<p><br /><br />
</p><p>Sample Response:<br />
</p><br />
<pre>{"error":"","URL":"https://bbp.s3.filebase.com/BBSWt5B13GuM5xJQHYM468bLC5qxmRmQ7Y/9.mp4","result":200}<br />
</pre><br />
<p><br /><br />
</p><p><br /><br />
</p><p><b> BIPFS - BiblePay Immutable Public File System (BIPFSaas) </b><br />
</p><p>This API allows you to store provably immutable files, accessible by public URL (via CDN). You may store small files all the way up to very large files (1 byte to 1Gigabyte per file).<br />
</p><p>The storage is extremely cost effective, priced at&#160;: 1 bbp per 100 megabytes per month.<br />
The files are available worldwide through our anti-ddos CDN which is located in all major cities and countries.<br />
</p><p>Bandwidth costs: Zero.<br />
</p><p>Use cases: NFT metadata files, contract data, special social media posts, provable timestamped videos, or any file that needs immutability.<br />
</p><p>How it is immutable: <br />
First, we hash the file with a standard sha256 hash.<br />
We require the sha256 hash to become the filename. The filename extension is preserved. <br />
Once the file is stored, we create an immutable biblepay transaction pointing to the file which contains the sha256 hash (this permanently preserves the timestamp and the record).<br />
The file contents can never be changed (because it can always be proven the hash matches) except in the case of non-payment.<br />
In the case of nonpayment, the contents of the file will be served as "UNPAID" and the blockchain record of the file will remain intact.<br />
</p><p><b> S3 Endpoint for Curl (Linux, Mac, others) </b><br />
</p><p>Simply post your file from the command or through code as below, along with your biblepay private key in the Header field:<br />
</p><p>Example:<br />
</p><br />
<pre>curl -X POST <br />
-H "key: YOUR_BIBLEPAY_PRIVATE_KEY" <br />
-H "immutable: 1" <br />
-F "file.mp4" <br />
https://unchained.biblepay.org/api/web/bbpingress<br />
</pre><br />
<p><br /><br />
Response:<br />
</p><p>If successful, Biblepay will respond with an http-200 response, with JSON containing an empty error field, a result code with a value of 200, and the URL which you can use immediately.<br />
If unsuccessful, BiblePay will respond with an http-200 response, with JSON containing an error field with a populated reason, and a result code below zero.<br />
</p><p><br /><br />
</p><p><br /><br />
</p><p><br /><br />
</p><p><b>FAQ</b><br />
</p><p><br /><br />
Q: Where are my files stored and what is the durability?<br />
</p><p>A: The network is comprised of three partners: BiblePay (for metadata), BiblePay Sanctuaries, IPFS, and CDN (for retrieval). The durability is set higher than normal so that the files will never be deleted unless you fail to pay the BBP hosting fee.<br />
</p><p><br /><br />
Q: What is a CDN?<br />
</p><p>A: A content data network copies your file to hundreds of global POPs (Points of Presence) so that the file can be downloaded faster to your user. This also provides resilience, in case the file is attempted to be taken down due to censorship, your file will still be available. Also if a fiber optic line is cut in a certain area, your file will still be available to the rest of the world. The CDN also provides anti-ddos, meaning that the CDN network is larger than any potential ddos threat. A good use case for a CDN is a news article. If you host it on biblepay, even if the article is attacked by thousands of malicious botnet actors, our CDN will keep supplying that news article to your readers. News orgs already use CDNs for their articles.<br />
</p><p><br /><br />
Q: How does billing work?<br />
</p><p>A: Once per month, we bill your private key for the sum in size of the bytes hosted for that key to the key itself so please ensure your key has enough to cover future hosting. We create an invoice that may be viewed in My Invoices. If your key does not have enough funds to cover the fees, after the grace period elapses (+14 days), then the files that cannot be paid for will be deleted. Other files in good standing will stay hosted.<br />
</p><p><br /><br />
</p><p>Q: Why shouldn't I go directly to STORJ or Amazon?<br />
</p><p>A: For STORJ, you will find that you need to setup a lot of technical items such as your download gateway and you will need to deal with the command line to send and receive files while we offer a programmatic solution above. We also do all the technical work for you to make it easier for you. Additionally, you dont get a free CDN. With Amazon, you are dealing with big tech, who will definitely charge you for all public bandwidth consumption which could cost you more than BiblePay. For example if your file is abused (repeatedly downloaded millions of times you could end up with a very high S3 invoice). With BiblePay, we only charge for the storage. Finally, with BiblePay you are helping ORPHANS. It's easy to decide when you want to make the world a better place.<br />
</p><p><br /><br />
Q: What if I want my data private and not public, like a backup file?<br />
</p><p>A: Reach out to us on social.biblepay.org and ask for the feature and if the demand is there, we will add an encryption option for you so that your data at rest file in cloud is encrypted with your key.<br />
</p><p><br /><br />
</p><p><br /><br />
</p><br />
<hr /><br />
<p><br /><br />
</p><p><br /><br />
<b>DbAAS - Database As a Service</b><br />
</p><p><br /><br />
Database As a Service provides you with a personal instance of a MYSQL database that runs on our cluster. Our cluster runs across a set of our sanctuaries and is self healing giving you 99.9% uptime.<br />
When one of our nodes go down in our cluster, you will not notice. We also have a built in load balancer, meaning that if one of our back-end nodes go down, the cluster as a whole will not go down.<br />
You can reach our cluster with one primary DNS address, disclosed when you subscribe. (Our DNS members are also self healing).<br />
</p><p>To subscribe to DbAAS, simply log into social.biblepay.org, click BBP from the left menu, then click DbAAS. Fill in the form and create Submit.<br />
There is a minimum amount of BBP required to be in escrow on the page.<br />
</p><p>FAQ:<br />
</p><p>Q: Are there any special requirements for my tables?<br />
</p><p>A: All tables must have a primary key. Otherwise you will receive an error when you insert data.<br />
</p><p>Q: What can I do with this?<br />
</p><p>A: You can run a website, a personal program or development environment, an instance of social.biblepay, a wordpress site, etc., against your mysql instance.<br />
</p></div>Adminhttps://wiki.biblepay.org/index.php?title=Decentralized_Autonomous_Charity&diff=6905Decentralized Autonomous Charity2022-11-27T15:06:15Z<p>Admin: </p>
<hr />
<div>'''Decentralized Autonomous Charity'''<br />
<br />
A DAC is a flavor of a Decentralized Autonomous Organization (DAO). The significant difference is that our operations revolve around charity. And the difference between a Corporation and a DAO is that a DAO is a self sustaining non government related entity that is not incorporated, and has no formal legal structure (such as 501c3 or for-profit corporation).<br />
<br />
<br />
''' How to donate to the DAC '''<br />
<br />
From our core wallet, click Send Money and check Donate To Foundation.<br />
<br />
<br />
''' Our current charities '''<br />
<br />
As of December 2022, we sponsor 60 children over 3 charities: 35 from Cameroon-One, 15 from Kairos Childrens Fund, and 5 from Compassion.com. <br />
<br />
The primary reasons that we still sponsor with these partners include: We have existing relationships with these organizations, the monthly costs are low ($25-$40 per month each), we see the majority reaches the beneficiary, the children are truly in desperate need (these are not children living at home -- they are mostly homeless), these orgs provide limited schooling and health care and food, these orgs are Jesus based, they accept BIBLEPAY as a source of payment, and we have a propensity to continue with children we already started until we cannot afford the child or the organization is found to be questionable.</div>Adminhttps://wiki.biblepay.org/index.php?title=Economics&diff=6904Economics2022-11-27T14:52:55Z<p>Admin: </p>
<hr />
<div>== BiblePay Economics: ==<br />
<br />
== Gross Block Breakdown: ==<br />
<br />
* Block Emission Level: Starting at 20,000 BBP at inception and decreasing by 19.5% per year.<br />
* 15% is escrowed for governance for expenses paid via our sanctuary voted budget - emitted as one monthly superblock (10% for charity, 5% IT)<br />
* 85% is rewarded to our Sanctuaries for Services and block security<br />
<br />
<br />
== Gross breakdown of Governance Budget: ==<br />
<br />
* Charity and Recurring Orphanage expenses (compassion.com, Cameroon One, Kairos, etc): 66%<br />
* IT Expenses and Payroll: 33%<br />
<br />
== Gross breakdown of Sanctuary Service reward: ==<br />
<br />
* 99% is given for POVS (Proof of video storage)<br />
* 1% is given to the sanctuary for Block Security (POW mining)<br />
<br />
== Deflation: ==<br />
<br />
The deflation rate of our emission is 1.5% Per Month, or 19.5% per year compounded.<br />
<br />
See [[Emission Schedule|BiblePay Emission Schedule]] for more details.<br />
<br />
[[Category:BiblePay Economics]]</div>Adminhttps://wiki.biblepay.org/index.php?title=BiblePay_Is_Not_Centralized&diff=6903BiblePay Is Not Centralized2022-11-27T14:47:49Z<p>Admin: </p>
<hr />
<div><br />
<br />
FAQ:<br />
<br />
I am an investor and I'm concerned that your community might be too centralized. Could you explain more about your structure and what would happen if the Founder dies tomorrow?<br />
<br />
<br />
<br />
'''The aftermath of BiblePay in a Post Founder World'''<br />
<br />
<br />
<br />
Sanctuaries: <br />
<br />
We have 36 sanctuaries that sponsor orphans. If the founder leaves the project, it would actually create a very active investment opportunity (simply because the Founder's sanctuaries would not get paid, and financially would be very lucrative for new ones to come in). Think of 200% ROI, this ROI would quickly fill the void. Also, Cameroon-One makes enough revenue to weather a transition through biblepay orphans to new biblepay orphans. This aspect is POSITIVE if the founder dies.<br />
<br />
<br />
Exchange Price:<br />
<br />
If the founder dies, there would be coins locked in his wallet that cannot be spent; this is positive for the price.<br />
<br />
<br />
Sporks:<br />
<br />
The rest of the development team would take over.<br />
<br />
<br />
Github Releases:<br />
<br />
Other key devs may still create github releases. <br />
<br />
<br />
Block Explorer:<br />
<br />
Our block explorer is run by chainz. No changes necessary.<br />
<br />
<br />
Locked up funds:<br />
<br />
The Founder only controls a tiny fraction of BBP in the Foundation wallet which cycles between zero and small amount due to charity donations. All contributions from the core wallet to orphan charity actually go directly to a transparent community funded project. <br />
<br />
<br />
NFTs:<br />
<br />
Our NFTs are bought and sold in the BMS marketplace. The owner of an NFT actually owns the NFT.<br />
<br />
<br />
Forums:<br />
<br />
The founder controls forum.biblepay.org, and that could possibly go down. But BiblePay Community is also on bitcointalk, telegram, and discord, giving us complete continuity in this area.<br />
<br />
<br />
Mobile Wallet:<br />
<br />
MIP holds the keys to deploy the mobile wallet. If either of us dies, another user can branch the repository. <br />
<br />
<br />
Orphan Sponsorship through Cameroon-One:<br />
<br />
Cameroon-One is not associated with our founder. We as a community choose our orphanages through sanctuary voting. We have been staying Cameroon because they said Yes to technical integrations, such as querying orphan balances and POOS, and we have open sponsorships with 35 children currently.<br />
<br />
<br />
Security:<br />
<br />
<br />
Our emission schedule is location here:<br />
https://wiki.biblepay.org/Emission_Schedule_2020<br />
<br />
We did not have a premine, we did not have an ICO. All blockchain emissions from inception have been earned through Mining, Hosting a Sanctuary, or buying on an exchange. <br />
<br />
We will never change the schedule, or the block time parameters. <br />
<br />
We are committed to providing a high quality Christian blockchain service with integrity. <br />
<br />
BiblePay has never stolen, or failed to pay orphan expenses or misrepresented any expense in our accounting records. <br />
<br />
The code has been hardened over time to eliminate any known attack vectors. Our chain has not been compromised, has not been hacked, or materially stolen from (other than a pool that had a break-in incident), but those have been recovered and have nothing to do with our block security). The security is based on: POW Mining (RandomX), and Chainlocks.<br />
<br />
<br />
NOTE: It is not possible for any sanctuary, or spork or the founder to cause emissions to change.<br />
<br />
<br />
Know that Rob A. is God Fearing, and we are held by the integrity that Jesus guides us in within this community.<br />
<br />
<br />
''' SUMMARY '''<br />
<br />
Based on these facts, my assessment is nothing bad would happen during a transition of power. The exchange would keep trading. Our dev team would find another developer to decentralize github releases and regain status quo. Less coins would be available, therefore the price might rise. The development efforts might increase or slow down depending on the replacement dev(s). <br />
<br />
Our Sanctuaries would continue voting on new charities. They might bring back compassion.com, or increase their expenditures with cameroon-one.<br />
<br />
The forum may change hands.<br />
<br />
The block explorers would still work. The blocks would still mine through Fun, and our community would look to open more pools. Besides, our wallet has solo mining which would keep the chain moving.<br />
<br />
If the sanctuaries fail to vote on the daily contract, the RX mining would still continue, meaning the chain would not go down.<br />
<br />
<br />
God bless you!</div>Adminhttps://wiki.biblepay.org/index.php?title=BiblePay_Services&diff=6902BiblePay Services2022-11-27T14:35:18Z<p>Admin: </p>
<hr />
<div>BiblePay differentiates itself from other cryptocurrencies by providing real world use cases through useful services.<br />
<br />
<br />
''' Services '''<br />
<br />
* Host files (large or small) such as documents and videos. You may upload your file either programatically with c#, or through our social media website. <br />
* Store Database data: Our decentralized sidechain can store your data relieving you of the nuisances of hosting your own database. We specialize in NoSQL storage of JSON documents. Generally, you will store your transactional records or metadata in our database, and this can point to or reference the files you have hosted with us.<br />
* Instant sidechain cryptocurrency transfer: You can send and receive funds without the core wallet.<br />
* BiblePay University: Take free college courses and earn your Bachelors of Theology.<br />
* NFTs: Market custom made NFTs in our marketplace. Sponsor orphan NFTs.</div>Admin