diff --git a/doc/README.md b/doc/README.md
index 9415a44ab..d2dd2ba37 100644
--- a/doc/README.md
+++ b/doc/README.md
@@ -8,7 +8,7 @@ Dogecoin 1.7.2 ALPHA
 
 Setup
 ---------------------
-[Dogecoin Core](http://dogecoin.com/en/download) is the original Dogecoin client and it builds the backbone of the network. However, it downloads and stores the entire history of Dogecoin transactions (which is currently several GBs); depending on the speed of your computer and network connection, the synchronization process can take anywhere from a few hours to a day or more. Thankfully you only have to do this once.
+[Dogecoin Core](http://dogecoin.com/en/download) is the original Dogecoin client and it builds the backbone of the network. However, it downloads and stores the entire history of Dogecoin transactions (which is currently several GBs); depending on the speed of your computer and network connection, the synchronization process can take anywhere from a few hours to a day or more. Thankfully you only have to do this once. If you would like the process to go faster you can [download the blockchain directly](bootstrap.md)
 
 Running
 ---------------------
diff --git a/doc/bootstrap.md b/doc/bootstrap.md
new file mode 100644
index 000000000..d66903188
--- /dev/null
+++ b/doc/bootstrap.md
@@ -0,0 +1,58 @@
+### Bootstrap the Blockchain Synchronization
+
+Normally the Dogecoin Core client will download the transaction and network information, called the blockchain, from network by syncing with the other clients. This can be a process that can take multiple days as the Dogecoin block chain has grown to more than 3 gigabytes, and is growing almost half a gigabyte every month. Luckily there is a safe and fast way to speed up this process. We’ll show you how to bootstrap your blockchain to bring your client up to speed in just a few simple steps.
+
+You only need to do this when first syncing Dogecoin Core; after that, updates are relatively small and shouldn't take too long.
+
+### Requirements
+
+- A fresh install of the Dogecoin Core client software.
+
+### Download the block chain
+Be sure to only use the official repositories listed below.
+
+#### US Mirror
+
+*Updated once per day, hosted by SoChain*
+
+Click [here](https://bootstrap.chain.so/bootstrap.dat) to download, or use the URL below.
+
+    https://bootstrap.chain.so/bootstrap.dat 
+
+#### EU Mirror
+
+*Updated once per month, hosted by Moolah*
+
+Click [here](http://bootstrap.moolah.io/dogecoin/bootstrap.dat) to download, or use the URL below.
+
+    http://bootstrap.moolah.io/dogecoin/bootstrap.dat
+
+### Importing the blockchain
+Launch the Dogecoin Core client once before continuing the process and then exit the Dogecoin Core software. Be sure not to have an actively used wallet in use. Now we are going to copy the download of the blockchain to the Dogecoin Core data directory. You should run the client software at least once so it can generate the data directory. Copy the downloaded bootstrap.dat file into the Dogecoin data folder.
+
+**For Windows users:**
+Open explorer, and type into the address bar:
+
+    %APPDATA%\Roaming\DogeCoin
+
+This will open up the data folder. It should look like the image below. Copy over the bootstrap.dat from your download folder to this directory.
+![Fig4](img/dogestrap1.png)
+
+**For OSX users:**
+Open Finder by pressing Press [shift] + [cmd] + [g] and enter:
+
+    ~/Library/Application Support/DogeCoin/
+
+**For Linux users:**
+The directory is hidden in your User folder. Go to:
+
+    ~/.dogecoin/
+
+### Importing the blockchain
+Now start the Dogecoin Core client software. It should show "Importing blocks from disk" like the image below. 
+![Fig5](img/dogestrap2.png)
+Wait until the import finishes. The client will download the last days not covered by the import. Congratulations you have successfully imported the blockchain!
+
+### Is this safe?
+
+Yes, the above method is safe. The download contains only raw block chain data and the client verifies this on import. Do not download the blockchain from unofficial sources, especially if they provide `*.rev` and `*.sst` files. These files are not verified and can contain malicious edits.
diff --git a/doc/img/dogestrap1.png b/doc/img/dogestrap1.png
new file mode 100644
index 000000000..9b05d946f
Binary files /dev/null and b/doc/img/dogestrap1.png differ
diff --git a/doc/img/dogestrap2.png b/doc/img/dogestrap2.png
new file mode 100644
index 000000000..21cc230f6
Binary files /dev/null and b/doc/img/dogestrap2.png differ