diff --git a/whitepaper/protocol.pdf b/whitepaper/protocol.pdf
index ad16d92..5b75d17 100644
Binary files a/whitepaper/protocol.pdf and b/whitepaper/protocol.pdf differ
diff --git a/whitepaper/protocol.tex b/whitepaper/protocol.tex
index db7fe3b..7919882 100644
--- a/whitepaper/protocol.tex
+++ b/whitepaper/protocol.tex
@@ -898,7 +898,7 @@ Multipart sends and public HushLists are still in development.
 
 \nsection{Account Funding}
 
-On first run, \HushList creates a new shielded zaddress $z_F$ to fund transparent addresses for pseudonymous sending via the \zsendmany RPC method.
+On first run, \HushList creates a new shielded zaddress $z_F$ to fund transparent addresses for pseudonymous sending via the \zsendmany  RPC method.
 
 It may be funded by the user from any taddr or zaddr with no loss of privacy.
 
@@ -933,11 +933,22 @@ to ensure delivery and subvert censorship of a single chain.
 \nsection{\HushList Creation}
 
 \nsubsection{Private \HushLists}
+
 A private \HushList is simply a list of contacts stored locally and costs nothing. The
 \Zcash protocol itself has a max of 54 recipients in a \zsendmany RPC currently, so \HushList implementations
 should not allow lists with more than 54 recipients at this time.
 
+\nsubsection{Multi-Chain Private \HushLists}
+
+A user may choose to send a \HushList memo via multiple coins as long as there is a valid
+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.
+
+
 \nsubsection{Public \HushLists}
+
 A public \HushList means publishing the PRIVATE KEY of a taddr (or potentially a zaddr)
 such that this address is no longer owned by a single individual. By intentially
 publishing the PRIVATE KEY in a public place, the owner has put all FUNDS and more importantly, the metadata of all transactions to that address, in the public domain.
@@ -990,7 +1001,7 @@ is equivalent to
 
 One may send to a \HushList from a taddr (pen name, psuedonym) or zaddr
 (anonymous shielded address) which is implemented in the client via
-the \textbf{z\_sendmany} RPC method. Up to 54 recepients may be in a single shielded
+the \zsendmany  RPC method. Up to 54 recepients may be in a single shielded
 transaction. v1 of HushList only supports HushLists of this size, but v2
 may implement larger HushLists by breaking large recipient lists into multiple sends.