diff --git a/whitepaper/protocol.pdf b/whitepaper/protocol.pdf
index 5b75d17..ae12acf 100644
Binary files a/whitepaper/protocol.pdf and b/whitepaper/protocol.pdf differ
diff --git a/whitepaper/protocol.tex b/whitepaper/protocol.tex
index 7919882..02b2171 100644
--- a/whitepaper/protocol.tex
+++ b/whitepaper/protocol.tex
@@ -944,8 +944,7 @@ A user may choose to send a \HushList memo via multiple coins as long as there i
 address for each Hush Contact on for each coin. For example, if you have addresses for three of your friends on each of the \HUSH, \KMD and \ZEC chains, then you may choose to redundantly send a memo on all of the chains. This provides a backup of the data on the other chains should one of them be blocked (such as dropping any packets for certain peer-to-peer ports), filtered or temporarily inaccessible.
 
 Additionally a user may choose to send day-to-day memos on a inexpensive chain such as \HUSH
-which has lower network difficulty and for things that need to have \Bitcoin-level security, an archive copy to \KMD can be sent. \KMD uses the delayed-Proof-Of-Work algorithm ensuring that once the information is engraved on the Bitcoin blockchain, it would be required both blockchains in question to be compromised to prevent accessing the data.
-
+which has lower network difficulty and for things that need to have \Bitcoin-level security, an archive copy to \KMD can be sent. \KMD uses the delayed-Proof-Of-Work \cite{dPOW} algorithm ensuring that once the information is engraved on the Bitcoin blockchain, it would be required both blockchains in question to be compromised to prevent accessing the data.
 
 \nsubsection{Public \HushLists}