GITBOOK-58: Add FAQ page

Author: kenrogers

.gitbook/assets/error-1.jpg

@@ -19,8 +19,10 @@
 * [Testnets](nakamoto-upgrade/testnets/README.md)
   * [Pre-Launch Testnet](nakamoto-upgrade/testnets/pre-launch.md)
   * [Nakamoto Testnet](nakamoto-upgrade/testnets/nakamoto.md)
-* [How to Run a Signer](nakamoto-upgrade/running-a-signer.md)
-* [How to Stack](nakamoto-upgrade/stacking-flow.md)
+* [Signing and Stacking](nakamoto-upgrade/signing-and-stacking/README.md)
+  * [How to Run a Signer](nakamoto-upgrade/signing-and-stacking/running-a-signer.md)
+  * [How to Stack](nakamoto-upgrade/signing-and-stacking/stacking-flow.md)
+  * [FAQ](nakamoto-upgrade/signing-and-stacking/faq.md)
 
 ## 🎓 Stacks 101 (Pre-Nakamoto) <a href="#stacks-101" id="stacks-101"></a>
 

.gitbook/assets/telegram-cloud-photo-size-4-6046167312920330449-y.jpg

@@ -0,0 +1,5 @@
+# Signing and Stacking
+
+Signing and stacking are critical roles in Nakamoto.
+
+The pages in this section will guide you in setting up a signer and the different ways you can go about stacking in Nakamoto.

.gitbook/assets/telegram-cloud-photo-size-5-6334823135647481068-y (1).jpg

@@ -0,0 +1,129 @@
+# FAQ
+
+### Signer Setup
+
+<details>
+
+<summary>My signer says it is uninitialized</summary>
+
+If you get a message like the following saying your signer is uninitialized, that means that it has not registered for the current or upcoming reward cycle (or the burnchain block height is not yet at the second block in the prepare phase) for the signer to know if it is registered.
+
+`Signer spawned successfully. Waiting for messages to process... INFO [1711088054.872542] [stacks-signer/src/runloop.rs:278] [signer_runloop] Running one pass for signer ID# 0. Current state: Uninitialized`
+
+At this point if you want your signer to do something you need someone to either delegate to you or you need to stack on your own for an upcoming reward cycle.
+
+For more on this, be sure to check out the [How to Stack ](stacking-flow.md)doc.
+
+</details>
+
+<details>
+
+<summary>I am trying to run my signer using Docker and it is not working correctly</summary>
+
+Currently, for PRs, we only build for glibc x64 images. If you want to test on another architecture, you'll need to build the Docker image locally or build the binary from source as described in the [How to Run a Signer](running-a-signer.md) doc.
+
+</details>
+
+<details>
+
+<summary>I'm getting an error about a missing variable</summary>
+
+There aren't yet properly tagged releases for Nakamoto, so you'll need to make sure that you are building from the `next` branch of building from source or using the `next` tag if using the Docker image.
+
+</details>
+
+### Stacks Nodes
+
+<details>
+
+<summary>Do I need to run a Stacks node alongside a signer?</summary>
+
+Yes, you'll need to run both a Stacks node and a signer. Set up the signer first and then set up your Stacks node following the instructions in the [How to Run a SIgner](running-a-signer.md) doc. Specifically, you'll want to run a testnet follower node.
+
+If the instructions in the above linked guide for setting up a Stacks node are not suitable, you can follow one of the guides found in the [Nodes and Miners](../../stacks-in-depth/nodes-and-miners/) section.
+
+</details>
+
+<details>
+
+<summary>When trying to run the node I am getting a connection error</summary>
+
+First, be sure that you have the proper entry point specified in your `node-config.toml` file as specified in the [How to Run a Signer](running-a-signer.md) doc.
+
+If you are getting an error like the following:
+
+![](../../.gitbook/assets/telegram-cloud-photo-size-4-6046167312920330449-y.jpg)
+
+And you are inside a Docker container with default bridging mode, then localhost is not available, and you'll need to point to the Docker host.
+
+</details>
+
+### Stacking
+
+<details>
+
+<summary>What is stacking?</summary>
+
+Stacking is the act of locking your STX tokens in order to help secure the network. In Nakamoto, stackers take on the additional responsibility of validating new Stacks blocks as miners propose them.
+
+If you aren't familiar with stacking as a concept you can take a look at the [Stacking](../../stacks-101/stacking.md) doc.
+
+</details>
+
+<details>
+
+<summary>As a signer, what exactly do I need to do in regards to stacking?</summary>
+
+Because stackers also function as signers in Nakamoto, signers must either solo stack or delegate their STX tokens to a delegate.
+
+These options and the processes for doing so are outlined in the [How to Stack](stacking-flow.md) doc, but you must do one of the two in order to operate as a signer.
+
+</details>
+
+<details>
+
+<summary>How can I delegate my STX as a signer?</summary>
+
+In order to delegate your STX tokens, you'll need to call the `delegate-stack-stx` function in the `pox-4` contract. The process for doing this can be found in the [How to Stack](stacking-flow.md) doc.
+
+</details>
+
+<details>
+
+<summary>Signer public keys need to be provided when calling delegate and solo stacking functions, does this correspond to the same public key used when generating the signer signature?</summary>
+
+Yes, the signer pubkey field always corresponds with the signer signature.
+
+</details>
+
+<details>
+
+<summary>What is the .stackers boot contract?</summary>
+
+This tracks the signers that are registered in a given reward-cycle.
+
+</details>
+
+<details>
+
+<summary>Are there any changes to the overall stacking flow minus the inclusion of the signer pubkey?</summary>
+
+No, the latest changes revolved around the signature, then about including a max-amount & auth-id with the signature.
+
+</details>
+
+<details>
+
+<summary>Is there a list of 3rd party signers available?</summary>
+
+&#x20;We have publicly announced many signers joining the network including: Blockdaemon, Figment, Kiln, Chorus One, Luganodes and[ more](https://stacks.org/new-signers-join-stacks).
+
+</details>
+
+<details>
+
+<summary>Signers change every reward cycle, so do we need a way to get the new signers at each reward cycle?</summary>
+
+That's correct, the PoX contract does a DKG event every cycle (every \~2 weeks). This is detailed in the [Nakamoto SIP](https://github.com/stacksgov/sips/blob/feat/sip-021-nakamoto/sips/sip-021/sip-021-nakamoto.md#stacker-turnover) where signers must register their keys.
+
+</details>

.gitbook/assets/telegram-cloud-photo-size-5-6334823135647481068-y (2).jpg

@@ -21,8 +21,8 @@ It will also walk through how to set up the config files to get the signer and S
 ### Knowledge Prerequisites
 
 * Docker and basic knowledge of pulling and running images
-* Basic knowledge of [Stacks accounts](../stacks-101/accounts.md)
-* Basic knowledge of [stacking](../stacks-101/stacking.md) and the [Nakamoto stacking flow](stacking-flow.md)
+* Basic knowledge of [Stacks accounts](../../stacks-101/accounts.md)
+* Basic knowledge of [stacking](../../stacks-101/stacking.md) and the [Nakamoto stacking flow](stacking-flow.md)
 
 <details>
 

.gitbook/assets/telegram-cloud-photo-size-5-6334823135647481068-y (3).jpg

@@ -5,14 +5,14 @@ This document intends to lay out all the steps required to stack STX tokens on t
 {% endhint %}
 
 {% hint style="info" %}
-This doc assumes you are familiar with stacking at a conceptual level. If not, you may want to read the [Stacking](../stacks-101/stacking.md) section of Stacks 101.
+This doc assumes you are familiar with stacking at a conceptual level. If not, you may want to read the [Stacking](../../stacks-101/stacking.md) section of Stacks 101.
 {% endhint %}
 
 In Nakamoto, stacking flows have significant changes in comparison to previous versions of Stacks. Because Nakamoto requires stackers to run a signer, which validates blocks produced by Stacks miners, stackers need to provide new information when making Stacking transactions.
 
 These changes affect both solo Stacking and delegated Stacking. This document outlines the new flows for both cases.
 
-If you aren't familiar with the general block production process under Nakamoto and what role signers and stackers play, you may want to read [Nakamoto in 10 Minutes](nakamoto-in-10-minutes.md) to get up to speed.
+If you aren't familiar with the general block production process under Nakamoto and what role signers and stackers play, you may want to read [Nakamoto in 10 Minutes](../nakamoto-in-10-minutes.md) to get up to speed.
 
 ### Definitions
 
@@ -243,7 +243,7 @@ The exact tooling that will be available for both solo and delegated stacking is
 
 This section describes the various transactions that signers need to make in order to be registered as a signer for a certain reward cycle. The order of operations between the automated signer and the stacking transactions that need to be done “manually” is important for ensuring that a signer is fully set up for a certain reward cycle.
 
-<figure><img src="../.gitbook/assets/Untitled design (1).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../.gitbook/assets/Untitled design (1).png" alt=""><figcaption></figcaption></figure>
 
 #### Prerequisite: ensure the signer is hosted and running