http -> https (#117)

README.md

@@ -1,11 +1,11 @@
 # About Bcoin.io
-This is the GitHub Pages hosted [website for Bcoin](http://bcoin.io).
+This is the GitHub Pages hosted [website for Bcoin](https://bcoin.io).
 
 Bcoin is the first fullnode Bitcoin implementation built specifically for production systems at scale. Originally created to be used as backend infrastructure for [Purse.io](https://purse.io), Bcoin enables companies to spin up consumer-grade bitcoin applications/wallet systems without the long-term concern of scalability, and security. Engineered from the ground-up in Nodejs to create scalable, flexible, and efficient production-ready systems. Bcoin can be integrated into almost any desktop or browser application to enable native payments, using bitcoin’s trusted and robust global network.
 
 # Guide Contribution Guidelines
 ## Submitting Ideas and Claiming Bounties
-Have an idea for a guide you'd like to contribute to [our collection of Bitcoin tutorials](http://bcoin.io/guides.html)? Want to collect a bounty for a submitted guide? First head on over to the [GitHub issues](https://github.com/bcoin-org/bcoin-org.github.io/issues) and see if your idea is already posted. Bounties will be placed on issues via [bountysource](https://bountysource.com) and tagged with the "guide" label.
+Have an idea for a guide you'd like to contribute to [our collection of Bitcoin tutorials](https://bcoin.io/guides.html)? Want to collect a bounty for a submitted guide? First head on over to the [GitHub issues](https://github.com/bcoin-org/bcoin-org.github.io/issues) and see if your idea is already posted. Bounties will be placed on issues via [bountysource](https://bountysource.com) and tagged with the "guide" label.
 
 ## Adding a New Guide
 To add a new guide, just a submit a Pull Request with a markdown file added to the `/guides-markdown` directory in this repo (take a look at [some of the other guides already there](https://github.com/bcoin-org/bcoin-org.github.io/tree/staging/guides-markdown)). Make sure to include a title using a top level header (with a single `#` hashtag in the markdown) and then a `post-author` and `post-description` at the top using code-snippet blocks labeled accordingly. If your PR is accepted, it will automatically be converted to html, added to the website and any bounty associated with the GitHub issue will be yours!
@@ -18,4 +18,4 @@ To add a new guide, just a submit a Pull Request with a markdown file added to t
 - If possible, links to repo with full working code implementation
 
 ## Updating API Docs
-Our [API Documentation](http://bcoin.io/api-docs/index.html) runs on the Open Source [Slate Framework](https://github.com/lord/slate). To make an update, fork the repo and make the changes to the appropriate Markdown in the file directory: bcoin-org.github.io/api-docs-slate/source/includes/. When your PR is merged in to staging, the new docs will be built and deployed to the live docs page http://bcoin.io/api-docs/index.html.
+Our [API Documentation](https://bcoin.io/api-docs/index.html) runs on the Open Source [Slate Framework](https://github.com/lord/slate). To make an update, fork the repo and make the changes to the appropriate Markdown in the file directory: bcoin-org.github.io/api-docs-slate/source/includes/. When your PR is merged in to staging, the new docs will be built and deployed to the live docs page https://bcoin.io/api-docs/index.html.

api-docs-slate/source/includes/_wallet_events.md

@@ -17,7 +17,7 @@ throughout the bcoin ecosystem including
 [`bclient`](https://github.com/bcoin-org/bclient) and [`bpanel`](https://github.com/bpanel-org/bpanel).
 
 For a deeper dive into events and sockets in bcoin, including a tutorial
-on using `bsock` and `bclient`, see the [bcoin.io Events and Sockets Guide.](http://bcoin.io/guides/events.html)
+on using `bsock` and `bclient`, see the [bcoin.io Events and Sockets Guide.](https://bcoin.io/guides/events.html)
 
 ```
 # Authentication

api-docs-slate/source/index.html.md

@@ -1,18 +1,18 @@
 ---
 title: Bcoin API Reference
 
-home_link: http://bcoin.io
+home_link: https://bcoin.io
 
 language_tabs: # must be one of https://git.io/vQNgJ
   - shell--curl: cURL
   - shell--cli: CLI
   - javascript
 
 toc_footers:
-  - <a href='http://bcoin.io/slack-signup.html'>Join us on Slack</a>
+  - <a href='https://bcoin.io/slack-signup.html'>Join us on Slack</a>
   - <a href='https://github.com/bcoin-org/bcoin'>See the code on GitHub</a>
-  - <a href='http://bcoin.io/guides.html'>Browse the guides</a>
-  - <a href='http://bcoin.io/docs/index.html'>Full API Documentation</a>
+  - <a href='https://bcoin.io/guides.html'>Browse the guides</a>
+  - <a href='https://bcoin.io/docs/index.html'>Full API Documentation</a>
   - <a href='https://github.com/tripit/slate'>Documentation Powered by Slate</a>
 
 includes:

api-docs/index.html

@@ -209,7 +209,7 @@
       </span>
     </a>
     <div class="toc-wrapper">
-        <a href="http://bcoin.io">
+        <a href="https://bcoin.io">
       <img src="images/logo.png" class="logo" alt="Logo" />
         </a>
         <div class="lang-selector">
@@ -711,10 +711,10 @@
           </li>
       </div>
         <ul class="toc-footer">
-            <li><a href='http://bcoin.io/slack-signup.html'>Join us on Slack</a></li>
+            <li><a href='https://bcoin.io/slack-signup.html'>Join us on Slack</a></li>
             <li><a href='https://github.com/bcoin-org/bcoin'>See the code on GitHub</a></li>
-            <li><a href='http://bcoin.io/guides.html'>Browse the guides</a></li>
-            <li><a href='http://bcoin.io/docs/index.html'>Full API Documentation</a></li>
+            <li><a href='https://bcoin.io/guides.html'>Browse the guides</a></li>
+            <li><a href='https://bcoin.io/docs/index.html'>Full API Documentation</a></li>
             <li><a href='https://github.com/tripit/slate'>Documentation Powered by Slate</a></li>
         </ul>
     </div>

browser.html

@@ -41,10 +41,10 @@ <h1>A bitcoin full node in the browser</h1>
   blocks all ports except bitcoin ports. If it is abused, I will be forced to
   require a proof of work for socket creation, making it slower for
   everyone.</small>
-  <p><a href="http://browser.bcoin.io/?network=main&prune=true">
+  <p><a href="https://browser.bcoin.io/?network=main&prune=true">
     Click here to start a full node on main (pruned).
   </a></p>
-  <p><a href="http://browser.bcoin.io/?network=testnet&prune=true">
+  <p><a href="https://browser.bcoin.io/?network=testnet&prune=true">
     Click here to start a full node on testnet (pruned).
   </a></p>
 </div>

docs/index.html

@@ -60,14 +60,14 @@ <h2>Uses</h2><ul>
 <li>Layer 2 Backend (lightning)</li>
 <li>General Purpose Bitcoin Library</li>
 </ul>
-<p>Try it in the browser: http://bcoin.io/browser.html</p>
+<p>Try it in the browser: https://bcoin.io/browser.html</p>
 <h2>Install</h2><pre class="prettyprint source"><code>$ git clone git://github.com/bcoin-org/bcoin.git
 $ cd bcoin
 $ npm install
 $ ./bin/bcoin</code></pre><p>See the <a href="https://github.com/bcoin-org/bcoin/blob/master/docs/Beginner's-Guide.md">Beginner's Guide</a> for more in-depth installation instructions.</p>
 <h2>Documentation</h2><ul>
-<li>API Docs: http://bcoin.io/docs/</li>
-<li>REST Docs: http://bcoin.io/api-docs/index.html</li>
+<li>API Docs: https://bcoin.io/docs/</li>
+<li>REST Docs: https://bcoin.io/api-docs/index.html</li>
 <li>Docs: <a href="docs/README.md">docs/</a></li>
 </ul>
 <h2>Support</h2><p>Join us on <a href="https://freenode.net/">freenode</a> in the <a href="irc://irc.freenode.net/bcoin">#bcoin</a> channel.</p>

guides-markdown/bcoin-clock.md

@@ -180,7 +180,7 @@ bcoin-cli info
 
 After a few minutes of loading, your output should resemble the printout below.
 You can repeat the `info` command to watch bcoin sync with the network, until `progress` reaches `1`. This won't take as much time as a full node would need but it could be a while.
-You can learn more about the command-line API clients `bcoin-cli` and `bwallet-cli` at [http://bcoin.io/api-docs.](http://bcoin.io/api-docs/?shell--cli#introduction)
+You can learn more about the command-line API clients `bcoin-cli` and `bwallet-cli` at [https://bcoin.io/api-docs.](https://bcoin.io/api-docs/?shell--cli#introduction)
 
 ```bash
 {
@@ -714,8 +714,8 @@ When `curses` catches a user pressing either `-` or `+`, the `WINDOW` parameter
 
 What else can we do with this structure?
 What else can you add on your own? Since we are receiving transactions, maybe there should be some kind of send function,
-[using the node API and another cURL request from Python.](http://bcoin.io/api-docs/?shell--curl#send-a-transaction)
-You could also use the same QR code functionality to [display the private key for an address you have deposited to](http://bcoin.io/api-docs/?shell--curl#get-private-key-by-address),
+[using the node API and another cURL request from Python.](https://bcoin.io/api-docs/?shell--curl#send-a-transaction)
+You could also use the same QR code functionality to [display the private key for an address you have deposited to](https://bcoin.io/api-docs/?shell--curl#get-private-key-by-address),
 allowing the user to sweep that key with a mobile phone wallet.
 
 Notice when a wallet-related transaction gets confirmed in a block, the details we get for that block include a [Merkle Proof](https://en.bitcoin.it/wiki/Protocol_documentation#Merkle_Trees).

guides-markdown/cltv.md

@@ -26,7 +26,7 @@ and, then satisfying some locking condition on that previous output.
 "Scripts" are conditions that need to be satisfied on an output to
 prove ownership. You can have a Bitcoin script that is locked with the
 math problem "What is 2 + 5", and anyone that knows to answer "7" can "prove"
-ownership over that output (Check out this guide, [Intro To Scripting](http://bcoin.io/guides/scripting.html)
+ownership over that output (Check out this guide, [Intro To Scripting](https://bcoin.io/guides/scripting.html)
 to see how to write and redeem this simple script in bcoin, and [this section](https://github.com/bitcoinbook/bitcoinbook/blob/develop/ch06.asciidoc#a-simple-script) in Mastering Bitcoin for a helpful walkthrough).
 
 In the vast majority of Bitcoin and other cryptocurrency transactions,

guides-markdown/crowdfund-tx.md

@@ -18,9 +18,9 @@ Here's how it's explained in *Mastering Bitcoin*:
 This construction can be used to make a "crowdfunding”-style transaction. Someone attempting to raise funds can construct a transaction with a single output. The single output pays the "goal" amount to the fundraiser. Such a transaction is obviously not valid, as it has no inputs. However, others can now amend it by adding an input of their own, as a donation. They sign their own input with ALL|ANYONECANPAY. Unless enough inputs are gathered to reach the value of the output, the transaction is invalid. Each donation is a "pledge," which cannot be collected by the fundraiser until the entire goal amount is raised.
 
 ## The Code
-We'll walk through the steps of creating the transaction first without any wallet database or node running. Then we'll do the same thing using bcoin's walletdb to manage the keys to see how it would work in a more realistic application (skip to [Version 2](#version-2-using-the-bcoin-wallet-system)) further in the guide to check it out). At the end, we'll put out some ideas of how these can be built upon for a more robust, production ready application. (If this is something you'd be interested in building, [get in touch](http://bcoin.io/slack-signup.html)!). If you want to see the code, checkout the [repo on github](https://github.com/Bucko13/bitcoin-fundraise).
+We'll walk through the steps of creating the transaction first without any wallet database or node running. Then we'll do the same thing using bcoin's walletdb to manage the keys to see how it would work in a more realistic application (skip to [Version 2](#version-2-using-the-bcoin-wallet-system)) further in the guide to check it out). At the end, we'll put out some ideas of how these can be built upon for a more robust, production ready application. (If this is something you'd be interested in building, [get in touch](https://bcoin.io/slack-signup.html)!). If you want to see the code, checkout the [repo on github](https://github.com/Bucko13/bitcoin-fundraise).
 
-If you're not comfortable with key management, coin selection, and how transactions are constructed, checkout the tutorial on [working with transactions](http://bcoin.io/guides/working-with-txs.html) first.
+If you're not comfortable with key management, coin selection, and how transactions are constructed, checkout the tutorial on [working with transactions](https://bcoin.io/guides/working-with-txs.html) first.
 
 ### Version 1 - Manual Key Management
 #### Step 1: Setup

guides-markdown/events.md

@@ -121,7 +121,7 @@ Luckily the bcoin developers have developed [bsock](https://github.com/bcoin-org
 a minimal websocket-only implementation of the socket.io protocol. By default, bsock listens on
 `localhost`, and you only need to pass it a port number to connect to one of the bcoin servers.
 The example below illustrates how to establish the socket connection, authenticate with your
-user-defined [API key](http://bcoin.io/api-docs/#authentication) and then send and receive events!
+user-defined [API key](https://bcoin.io/api-docs/#authentication) and then send and receive events!
 [See the tables below for a complete list of calls and events available in bcoin.](#socket-events-directory)
 
 ```javascript

guides-markdown/multisig-tx.md

@@ -428,7 +428,7 @@ You will notice that we grab the `.account.accountKey`, first key is the xpubkey
 and both will be using xpubkey key derivation to come up with new addresses.
 You won't need to share any other public keys, they will derive them for you.
 Depth of the account is the only thing you'll need to keep in mind.
-[addSharedKey](http://bcoin.io/api-docs/index.html#add-xpubkey-multisig) in
+[addSharedKey](https://bcoin.io/api-docs/index.html#add-xpubkey-multisig) in
 wallet/account is used for adding cosigner xpubkeys keys.
 
 ### Step 2: Generate Transaction
@@ -500,7 +500,7 @@ send remaining funds (minus fee) to change address and sign it.
 `wallet2.sign` will take raw transaction and sign it with according key.
 After that we can just broadcast the transaction to the network.
 
-[API-DOCS]: http://bcoin.io/api-docs/index.html
+[API-DOCS]: https://bcoin.io/api-docs/index.html
 
 
 ## Final Notes

guides-markdown/segwit.md

@@ -438,7 +438,7 @@ You can check [BIP List][BIPS] for other related proposals.
 [tx-malleability]: https://en.bitcoin.it/wiki/Transaction_Malleability
 [BIP62]: https://github.com/bitcoin/bips/blob/master/bip-0062.mediawiki#motivation
 [guide-repo]: https://github.com/nodar-chkuaselidze/bcoin-segwit-guide
-[multisig-guide]: http://bcoin.io/guides/multisig-tx.html
+[multisig-guide]: https://bcoin.io/guides/multisig-tx.html
 
 [create-p2wpkh.js]: https://github.com/nodar-chkuaselidze/bcoin-segwit-guide/blob/master/create-p2wpkh.js
 [create-p2wsh.js]: https://github.com/nodar-chkuaselidze/bcoin-segwit-guide/blob/master/create-p2wsh.js

guides-markdown/vps-setup.md

@@ -303,7 +303,7 @@ $ bclient info --api-key=hunter2
 
 ```
 
-For a complete list of CLI commands, check the [API documentation](http://bcoin.io/api-docs/index.html). The CLI supports node, wallet and has full RPC functionality.
+For a complete list of CLI commands, check the [API documentation](https://bcoin.io/api-docs/index.html). The CLI supports node, wallet and has full RPC functionality.
 
 ### Using Bcoin as a library
 

guides-markdown/wallets.md

@@ -66,7 +66,7 @@ Zo2k6EXtfczvbWyv7FdjMhppvJ"}'
 
 ### API Authentication
 
-Bcoin can run as a server and allow you to interact with your wallets via a [REST API](http://bcoin.io/api-docs/index.html?shell--curl#wallet). It also allows you protect wallets from unauthenticated requests by running the server with the `wallet-auth` option. Each wallet you create has a `token` value that must be passed in with each request. Tokens, like accounts and keys, can also be deterministically generated using your HD seed. This means you can change the token on a wallet as often as you'd like.
+Bcoin can run as a server and allow you to interact with your wallets via a [REST API](https://bcoin.io/api-docs/index.html?shell--curl#wallet). It also allows you protect wallets from unauthenticated requests by running the server with the `wallet-auth` option. Each wallet you create has a `token` value that must be passed in with each request. Tokens, like accounts and keys, can also be deterministically generated using your HD seed. This means you can change the token on a wallet as often as you'd like.
 
 ### Recovery
 

guides.html

@@ -32,7 +32,7 @@
   <meta name="theme-color" content="#ffffff">
 
   <!-- Web Fonts -->
-  <link href='http://fonts.googleapis.com/css?family=Open+Sans:300,400italic,400,600,700' rel='stylesheet'>
+  <link href='https://fonts.googleapis.com/css?family=Open+Sans:300,400italic,400,600,700' rel='stylesheet'>
   <link href='https://fonts.googleapis.com/css?family=Montserrat:700' rel='stylesheet' type='text/css'>
 
   <!-- Bootstrap core CSS -->
@@ -199,7 +199,7 @@
             <!-- END API -->
 
             <!-- FULL DOCS - older, full reference
-            <li><a href="http://bcoin.io/docs/index.html">Docs</a></li>-->
+            <li><a href="https://bcoin.io/docs/index.html">Docs</a></li>-->
             <!-- END DOCS -->
 
             <!-- DIVIDER
@@ -273,7 +273,7 @@ <h6 class="montserrat text-uppercase bottom-line">Guides</h6>
   <!-- TEXT WIDGET -->
   <div class="widget">
     <h6 class="montserrat text-uppercase bottom-line">Looking for Docs?</h6>
-    <p>Checkout our <a href="../api-docs/index.html">API Docs</a> or the <a href="http://bcoin.io/docs/index.html">Full Documentation</a></p>
+    <p>Checkout our <a href="../api-docs/index.html">API Docs</a> or the <a href="https://bcoin.io/docs/index.html">Full Documentation</a></p>
   </div>
   <!-- END TEXT WIDGET -->
 
@@ -615,7 +615,7 @@ <h2 class="montserrat text-uppercase m-b-30">Ready to start building? Read the d
   <!-- JAVASCRIPT FILES -->
 
   <script src="assets/js/jquery-2.2.3.min.js"></script>
-  <script src="http://maps.googleapis.com/maps/api/js?v=3"></script>
+  <script src="https://maps.googleapis.com/maps/api/js?v=3"></script>
   <script src="assets/bootstrap/js/bootstrap.min.js"></script>
   <script src="assets/js/plugins.min.js"></script>
   <script src="assets/js/stickyfill.min.js"></script>