update keysets and proofs instructions

templates/keysets.html

@@ -13,18 +13,22 @@
     this server. Proofs should be generated with that keyset. They were generated from the utxo snapshot at the specified blockheight.
     As long as you had a taproot utxo at that specific blockheight for which you own the private key, you can generate the proof.
     <br><br>
-    <a href="./">Download mainnet keyset here</a>
+    <a href="./replacethis">Download mainnet keyset here</a>
     <br>
-    <a href="./">Download signet keyset here</a>
+    <a href="./replacethis">Download signet keyset here</a>
     <br><br>
+    <b> Only mainnet is currently working.
+        Note that the minimum amount of sats (500000) and the blockheight of the snapshot are in the file name.</b>
+    <br>
     Trusting the server to generate the keyset file for you is not great! It's just to make the proof
     of concept easier.
     While it doesn't violate the
     security of your private keys, it theoretically makes the anonymity of your key weaker, if the server
     is malicious.
     <br>
-    In future you can generate the keyset yourself, with your own bitcoin node. And you can do that today;
-    read <a href="./">here</a> for how to do that; note that it will take 30-40 minutes at minimum, but for
+    You can generate the keyset yourself, with your own bitcoin node.
+    Read <a href="https://github.com/AdamISZ/aut-ct/blob/master/docs/utxo-keysets.md">here</a> for how to do that;
+    note that it will take 30-40 minutes at minimum, but for
     the technically capable, it's not too hard, if you have the motivation.
 </div>
 {% endblock %}

templates/proofs.html

@@ -25,8 +25,9 @@
         Also, add a flag <code>-n mainnet|signet|regtest</code> if you need to; the default is mainnet.
     </li>
     <li> Copy the WIF into a file "privkey" (or any name) in the working directory.
-        Make its read permission user-only.</li>
-    <li><ul>If you are using Core (ignore if using Sparrow)</ul>. Do the following steps using the RPC:
+        Recommendation: make its read permission user-only.</li>
+    <li><ul>If you are using Core (<b>Ignore and go to the next step if using Sparrow</b>)</ul>.
+        Do the following sub-steps using the RPC:
         <br>
         <code>bitcoin-cli getdescriptorinfo "tr(WIF)"</code>
         <br>
@@ -39,12 +40,13 @@
         You can use e.g. <code>bitcoin-cli getaddressesbylabel anything</code>
         to sanity check that the address is present in the wallet.
     </li>
-    <li>Fund the address with any amount above 500K sats.</li>
-    <li>After some delay, find the keyset file from <a href="./keysets">here</a>. It will include your utxo,
+    <li>Fund the p2tr address from the first step with any amount above 500K sats.</li>
+    <li>After confirmation, download the keyset file from <a href="./keysets">here</a>. It will include your utxo,
         as long as your utxo was in the blockchain before the starting block of that file.</li>
-    <li>Generate the proof with the command: <code>target/release/autct -M prove -k hodlboard:name-of-keyset-file -i privkey -b 1024 --base64-proof true</code>.
-        , where the -i argument should match your private key file.
-    Note that the proving is slow; 30-150 seconds is typical.</li>
+    <li>Generate the proof with the command: <code>target/release/autct -M prove -k hodlboardmainnet:name-of-keyset-file -i privkey -b 1024 --base64-proof true</code>.
+        , where the -i argument should match your private key file, and "name-of-keyset-file" should be the (relative or absolute)
+        path to the file you downloaded in the previous step. <b>Don't change the name of the file</b>.
+    Note that the proving is slow; 30-150 seconds is typical currently, though it will be improved later.</li>
     <li> Take the base64 string printed out from the previous step and use it in the <a href="./signup">signup page</a> here.</li>
     <li>After you have successfully signed up, sweep the private key into a wallet, either <a href="https://sparrowwallet.com">Sparrow</a> (easier for most users),
        or <a href="https://bitcoincore.org">Bitcoin Core</a>. See a few notes on this below.</li>