diff --git a/hush-v3.tex b/hush-v3.tex
index 0c94d75..3366cf7 100644
--- a/hush-v3.tex
+++ b/hush-v3.tex
@@ -448,7 +448,7 @@ zk-SNARKs, HushList, cryptoconditions, smart contracts, 51\% attack, double spen
     latest version of \Hush migrates to a new codebase based on Komodo and Zcash
     2.0.x with a new genesis block mined on April 14th 2019, while keeping the
     emission schedule as close as possible to the original intentions. Latest
-    details can be found at https://myhush.org .
+    details can be found at https://hush.is .
 
 \begin{quote}
 A beginning is the time for taking the most delicate care that the balances are correct.
@@ -590,7 +590,7 @@ of the RPC interface.
 
 \HUSH v3 is a source code fork of the jl777/komodo git repository and lives at
 
-    https://github.com/MyHush/hush3
+    https://git.hush.is/hush/hush3
 
 As of Block 500,000, the legacy Hush network and codebase is unsupported.  The
 network is not being forcibly turned off, those that want are free to use it,
@@ -811,11 +811,11 @@ block height while still able to answer RPC requests.
 
 Full data is available here:
 
-https://github.com/MyHush/hush3/blob/duke/contrib/snapshot/snapshot\_500000.json
+https://git.hush.is/hush/hush3/src/branch/master/contrib/snapshot/snapshot\_500000.json
 
 The actual script used to disperse funds can be found here:
 
-https://github.com/MyHush/hush3/blob/duke/contrib/snapshot/airdrop\_hush3.sh
+https://git.hush.is/hush/hush3/src/branch/master/contrib/snapshot/airdrop\_hush3.sh
 
 71326 \HUSH was locked into old Sprout addresses and are stuck on the legacy Hush
 chain, no longer in circulating supply.  Due to this fact the new \HUSH v3 was
@@ -850,7 +850,7 @@ such as exchanges that only support transparent addresses.
 
 The HushList protocol whitepaper
 
-https://github.com/leto/hushlist/blob/master/whitepaper/protocol.pdf
+https://git.hush.is/hush/hushlist/src/branch/master/whitepaper/protocol.pdf
 
 describes a protcol which sits on top of the Zcash Protocol, utilizing the memo
 field as 512 bytes of encrypted storage in every transaction. At the time, only