MediaWiki API result

This is the HTML representation of the JSON format. HTML is good for debugging, but is unsuitable for application use.

Specify the format parameter to change the output format. To see the non-HTML representation of the JSON format, set format=json.

See the complete documentation, or the API help for more information.

{
    "batchcomplete": "",
    "query": {
        "pages": {
            "3523": {
                "pageid": 3523,
                "ns": 0,
                "title": "API",
                "revisions": [
                    {
                        "user": "Admin",
                        "timestamp": "2022-12-02T12:29:23Z",
                        "comment": "",
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "</p><p><br />\nWe are a blockchain with real world use cases.\n</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?\n</p><p><br />\n\nLive Service #1:\n</p><p><br />\n<b> BiblePay S3 File Hosting (S3aas) </b>\n</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).\n</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.\n</p><p><b> S3 Endpoint for Curl (Linux, Mac, others) </b>\n</p><p>Simply post your file from the command or through code as below, along with your biblepay private key in the Header field:\n</p><p>Example:\n</p>\n<pre>curl -X POST \n    -H \"key: YOUR_BIBLEPAY_PRIVATE_KEY\" \n    -H \"url: Your_preferred_filename\"\n    -F \"[email protected]\" \n    https://unchained.biblepay.org/api/web/bbpingress\n</pre>\nExample:\n<pre>curl -X POST \n    -H \"key: U1234567890\" \n    -H \"url: myfile.mp4\"\n    -F \"[email protected]\" \n    https://unchained.biblepay.org/api/web/bbpingress\n</pre>\n\n<p><br />\nResponse:\n</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.\nIf 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.\n</p><p><br />\n<b> S3 Endpoint for C# </b>\n</p><p>You can also post your file programatically in any language.  For C#, please see this example below:\n</p>\n<pre>public async static void UploadBiblePayFile()\n{\n      string sURL = \"https://unchained.biblepay.org/api/web/bbpingress\";\n      string sFilePath = \"s:\\\\yourfolder\\\\filename.mp4\";\n      HttpContent bytesContent = new ByteArrayContent(System.IO.File.ReadAllBytes(sFilePath));\n      using (var httpClient = new System.Net.Http.HttpClient())\n      {\n        using (var request = new HttpRequestMessage(new HttpMethod(\"POST\"), sURL))\n        {\n            httpClient.Timeout = new System.TimeSpan(0, 60, 00);\n            httpClient.DefaultRequestHeaders.Accept.Add(new MediaTypeWithQualityHeaderValue(\"application/json\"));\n            httpClient.DefaultRequestHeaders.TryAddWithoutValidation(\"key\", \"your_bbp_private_key\");\n            httpClient.DefaultRequestHeaders.TryAddWithoutValidation(\"url\", \"your_filename\");\n            var multipartContent = new MultipartFormDataContent();\n            multipartContent.Add(bytesContent, \"file\", System.IO.Path.GetFileName(sFilePath));\n            request.Content = multipartContent;\n            var oInitialResponse = await httpClient.PostAsync(sURL, multipartContent);\n            string sJsonResponse = await oInitialResponse.Content.ReadAsStringAsync();\n        }\n    }\n}\n</pre>\n<p><br />\n</p><p>Sample Response:\n</p>\n<pre>{\"error\":\"\",\"URL\":\"https://unchained.biblepay.org/BBSWt5B13GuM5xJQHYM468bLC5qxmRmQ7Y/9.mp4\",\"result\":200}\n</pre>\n<p><br />\n</p><p><br />\n</p><p><br />\n</p><p><br />\n\n\n<h3>Live Service #2 - Database</h3>\n<br>\n<br>\nYou can use biblepay to set and retrieve database values for your personal use. \nFrom the BiblePay Core RPC client, you can set or retrieve a value.\n\n'''Set Database Value'''\n\n setdatabasevalue my_bbp_privkey table key value\n\nBiblePay will respond with either an error or success.\n\n\n''' Retrieve database value '''\n\n getdatabasevalue my_bbp_privkey table key\n\nBiblePay will respond with the value of the key.\n\n\n''' How do I generate a storage keypair? '''\n\n generatestoragetoken\n\n''' How do I retrieve my current monthly billing assessment? '''\n\n getstoragebalance bbp_pub_key\n\n\n\n\n\n</p><p><b>FAQ</b>\n</p><p><br />\nQ: Where are my files stored and what is the durability?\n</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.\n</p><p><br />\nQ: What is a CDN?\n</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.\n</p><p><br />\nQ: How does billing work?\n</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.\n</p><p><br />\n</p><p>Q: Why shouldn't I go directly to STORJ or Amazon?\n</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.\n</p><p><br />\nQ: What if I want my data private and not public, like a backup file?\n</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.\n</p><p><br />\n</p><p><br />\n</p>\n<hr />\n<p><br />\n</p><p><br />"
                    }
                ]
            },
            "1": {
                "pageid": 1,
                "ns": 0,
                "title": "Main Page",
                "revisions": [
                    {
                        "user": "Sntjo2847",
                        "timestamp": "2021-06-28T17:29:32Z",
                        "comment": "Updated last 3 paragraphs of description to present tense from future",
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "{| class=\"wikitable\" style=\"text-align:center; margin-left:2em\"\n|| BIBLEPAY || 10% Charity, Masternodes (Sanctuaries), ASIC-Resistant, CPU-Mining\n|-\n|| Mint || Decentralized Proof Of Work\n|-\n|| Launch Date || July 23rd, 2017\n|-\n|| Developed by || Robert Andrews\n|-\n|| Ticker || BBP\n|-\n|| Plural || Biblepays\n|-\n|| Subunit || mBBP =0.001\n|-\n|| Lowest Unit || 0.00000001 = 1 BBP\n|-\n|| Operating System || Windows, Linux, macOS\n|-\n|| Algorithm || RandomX (merge mining)\n|-\n|| Current Version || Client v1.6.2.5 mandatory\n|-\n|| Blocktime || avg 7 Minutes\n|-\n|| Reward || 20,000 Decreasing by 1.5% per month (Approx 19% per year)\n|}\n\n==='''DETAILS'''===\n<p>'''NAME:''' BIBLEPAY</p>\n<p>'''TICKER:''' BBP</p>\n\n<p>'''LAUNCH DATE:'''  JULY 23, 2017 at 17:00:00 CST</p>\n\n<p>'''PREMINE:''' NONE</p>\n<p>'''ICO:''' NONE</p>\n\n<p>'''CIRCULATION CHARACTERISTIC:''' DEFLATIONARY</p>\n<p>'''CIRCULATION RATE:''' DECREASE BY 10% PER YEAR</p>\n<p>'''TOTAL CIRCULATION:''' 5.2 BILLION BY 2050, DECREASING BY 18% PER YEAR</p>\n\n<p>'''BLOCK TARGET RATE:''' 7 MINUTES</p>\n\n<p>'''ALGORITHM:''' RandomX (merge mining)</p>\n<p>'''TRANSACTION SPEED:''' SUPPORTS INSTANTSEND</p>\n\n<p>First coin with the KJV Bible compiled in the source, and utilizing the Bible in the hashing algorithm, while spreading the gospel throughout the IT community.  The blocks also hash to chained bible verses.</p>\n\n==='''BLOCK REWARD'''===\n    5.0% Monthly Budget  \n   \n            Exchange Fund Payoff  \n            IT (Software Development)  \n            MISC\n   \n   50.0% GSC (Generic Smart Contracts)\n   \n            Portfolio Builder Rewards\n   \n   25.0% RandomX (CPU Mining)\n   \n   20.0% Sanctuaries (Masternodes)\n\n==='''LINKS'''===\n<p>'''Bitcointalk Forum:''' [https://bitcointalk.org/index.php?topic=2388064.0 bitcointalk.org/index.php?topic=2388064.0]</p>\n<p>'''BiblePay Forum:''' [http://forum.biblepay.org/ forum.biblepay.org]</p>\n\n<p>'''BLOCK EXPLORER:''' [https://chainz.cryptoid.info/bbp/ chainz.cryptoid.info/bbp]</p>\n\n<p>'''SOURCE CODE:''' [https://github.com/biblepay/biblepay github.com/biblepay/biblepay]</p>\n\n<p>'''WEB SITE:''' [http://biblepay.org biblepay.org]</p>\n\n==='''EXCHANGES'''===\n<p>'''[https://www.southxchange.com/Market/Book/BBP/BTC SouthXchange]'''</p>\n\n==='''DESCRIPTION'''===\n<p>A secure blockchain benefiting those in distress - 10% of the emission goes to sponsoring Orphans, with provable contributions, expenses contributed to [https://www.cameroonone.org/ https://www.cameroonone.org/] - and future charities that are more than 75% efficient.  ** NOTE: THE COIN HAS RPC COMMANDS THAT PROVE 100% OF CONTRIBUTIONS ARE SPENT THE WAY INTENDED **</p> \n\n<p>Proof Of Biblehash (POBh) has been replaced with RandomX(merge mining) - an algorithm that combines mining BBP and XMR(Monero), while preventing GPUs and ASIC, along with chained bible verses. This means biblepay subsidizes full nodes that stay online.</p>\n\n<p>Seven minute block targets minimize the blockchain file size, yet BiblePay does support Dash's instantsend for speedy transactions. MasterNodes (called Sanctuaries) allow all expenses to be voted on and approved.</p>\n<p>Expense receipts, to prove the sponshorship of new orphans, will be accessible from inside the wallet and we will even provide phone numbers for auditors to prove </p>\n100% charity expenditures.  (From the rpc, type &#39;run contribution&#39; to see the tithes into the foundation for a time period, and to see the outgoing sponsorship click the wallets &#39;Accounting&#39; button to see a list of orphans, expenses, sponsorship dates, amounts, and the txid).\n \n<p>For the first 6 months, 10% of each block will be allocated to the foundation, for sponsoring orphans at 100%.  Once per month, we will cash in anything over $40 available on an exchange, and sponsor orphans on our volunteer time. After the sanctuaries go live, the 10% tithe will be diverted to an ongoing budget with DAO governance, voting, allowing the coin to function as a dectralized autonomous charity; at that point the lead dev and volunteers will become a normal part of the community allowing the coin to run by itself.</p>\n\n<p>The network will be high efficiency with low total energy consumption, and the charities sponsored must also be high efficiency (over 75%).\nNext, we are deflationary, meaning that we start by issuing a larger amount of coins per block, and each year we tighten the supply by 18%.</p>\n\nThe schedule is here: (205 blocks per day, 7 minute block targets)\n\nEMISSION SCHEDULE PROJECTION: http://wiki.biblepay.org/Emission_Schedule\n\n<p>The block reward breakdown is as follows</p>\n\nECONOMICS: http://wiki.biblepay.org/Economics\n\n<p>We allocate 10% of each block subsidy to our governance committee (a DAO), automatically, with 100% of that being spent on charity.  \n\nOur sanctuaries are a charity governance committee, allowing our community to control the day to day operations of the charity: voting on what money is spent on, and how much is spent. This way, we will not be centralized.</p>\n\n<p>We only partner with charities over 75% efficient, meaning over 75% reaches the end-user.</p>\n\n==='''NO PREMINE'''===\n<p>the lead dev starts with zero, the orphan foundation fund starts with zero, the distribution is entirely fair.  NO ICO.  The distribution curve is evenly declining with no hidden bumps early.\nThe self-governance committee and masternode payments are deliberately delayed until Christmas, to allow people to prepare and save up the initial requirement.  Running a sanctuary is open to anyone.\nThe lead dev will sponsor the first 10 orphans out of his own pocket.</p>\n\n===<p>'''ACCOUNTABILITY'''</p>===\n<p>The wallet will have a reconciliation page built in at go live, to show all charitable income and expenses.</p>\n<p>The expenses will be auditable - to prove the money actually was spent on orphans.</p>\n<p>This will be accomplished through the use of : an RPC audit command that tallies the orphan income from the blockchain, and secondly, an API connection to a database that stores the Compassion expenses (until sanctuaries go live), with auditable backing contact info for each expense. We will also provide a web page with pictures of the sponsored orphans clicable from the wallet to show our investors what good we are doing. And finally- we will maintain a copy of receipts in order to maintain 100% accountability.</p>\n<p>Future Feature: Pay to Preach, in wallet ineractive prayer rooms.</p>\n\n==='''ROADMAP'''===\n\n[https://wiki.biblepay.org/Roadmap wiki.biblepay.org/Roadmap]\n\n==='''DISTINCT FEATURES'''===\n\n<p>Proof of Bible Hash algorithm (POBh), getblockinfo shows the chained bible verses required to solve the block, sending money exposes a Tithe checkbox - allowing 10% to be gifted to the orphan foundation, wallet has an in-wallet prayer system, allowing a user to send out a prayer request to the network or store prayers in the chain for the community to pray for from the overview page, Transactions support in-chain messages, Instant Send, Voting, Decentralized Automated Charity Governance Committee, Repentance of Sins, Contributing to the orphan foundation checkbox, and reading the sin list and various staple prayers in wallet.</p>\n\n==='''ALL PAGES'''===\nAll Wiki Pages: [[Special:AllPages]]"
                    }
                ]
            }
        }
    }
}