GITBOOK-291: Add sbtc faq

stacks-network · Feb 18, 2025 · 34b5f9f · 34b5f9f
1 parent 1b0542d
commit 34b5f9f
Show file tree

Hide file tree

Showing 27 changed files with 254 additions and 13 deletions.
diff --git a/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png b/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png b/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1) (1).png b/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1).png b/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (1) (1) (1) (1) (1) (1).png b/.gitbook/assets/image (1) (1) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (1) (1) (1) (1) (1).png b/.gitbook/assets/image (1) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (1) (1) (1) (1).png b/.gitbook/assets/image (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (1) (1) (1).png b/.gitbook/assets/image (1) (1) (1).png
diff --git a/.gitbook/assets/image (1) (1).png b/.gitbook/assets/image (1) (1).png
diff --git a/.gitbook/assets/image (1).png b/.gitbook/assets/image (1).png
diff --git a/.gitbook/assets/image (2) (1) (1) (1) (1).png b/.gitbook/assets/image (2) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (2) (1) (1) (1).png b/.gitbook/assets/image (2) (1) (1) (1).png
diff --git a/.gitbook/assets/image (2) (1) (1).png b/.gitbook/assets/image (2) (1) (1).png
diff --git a/.gitbook/assets/image (2) (1).png b/.gitbook/assets/image (2) (1).png
diff --git a/.gitbook/assets/image (2).png b/.gitbook/assets/image (2).png
diff --git a/.gitbook/assets/image (24).png b/.gitbook/assets/image (24).png
diff --git a/.gitbook/assets/image.png b/.gitbook/assets/image.png
diff --git a/SUMMARY.md b/SUMMARY.md
@@ -63,6 +63,7 @@
   * [Walkthroughs](concepts/sbtc/walkthroughs/README.md)
     * [Signer Process Walkthrough](concepts/sbtc/walkthroughs/signer-process.md)
     * [sBTC Transaction Walkthrough](concepts/sbtc/walkthroughs/sbtc-transaction-lifecycle.md)
+  * [sBTC FAQ](concepts/sbtc/sbtc-faq.md)
 * [Gaia](concepts/gaia/README.md)
   * [Configuration](concepts/gaia/configuration.md)
   * [Deploy Gaia Hub](concepts/gaia/deploy-gaia-hub.md)

diff --git a/concepts/block-production/stacking.md b/concepts/block-production/stacking.md
@@ -30,7 +30,7 @@ Although stackers do fulfill a consensus critical role in Stacks by serving as s
 
 Rather, if stackers do not perform their duties as signers, they simply cannot unlock their STX tokens and will not receive their BTC rewards.
 
-<figure><img src="../../.gitbook/assets/image (2) (1) (1) (1).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../.gitbook/assets/image (2) (1) (1) (1) (1).png" alt=""><figcaption></figcaption></figure>
 
 Stacking is a built-in action, required by the "proof-of-transfer" (PoX) mechanism. The PoX mechanism is executed by every miner on the Stacks network.
 

diff --git a/concepts/sbtc/sbtc-faq.md b/concepts/sbtc/sbtc-faq.md
@@ -0,0 +1,241 @@
+# sBTC FAQ
+
+### sBTC Basics
+
+<details>
+
+<summary>What is sBTC?</summary>
+
+sBTC is a non-custodial 1:1 Bitcoin-backed asset on the Stacks Bitcoin Layer. Read more about Stacks [here](https://www.stacks.co) and sBTC [here](https://www.stacks.co/sbtc).
+
+</details>
+
+<details>
+
+<summary>How does sBTC work?</summary>
+
+1. sBTC is a SIP-010 token on the Stacks blockchain that represents Bitcoin (BTC) in a 1:1 ratio. sBTC is always backed 1:1 against BTC.
+2. The sBTC peg wallet is maintained and managed by a set of sBTC signers. This decentralized approach enhances security and reduces single points of failure. Read more about Stacker Signing [here](https://docs.stacks.co/concepts/block-production/stackers-and-signing).
+
+</details>
+
+<details>
+
+<summary>What is Bitcoin Finality, and why is it important?</summary>
+
+Stacks and sBTC state automatically fork with Bitcoin. As such, all transactions settle to Bitcoin with 100% Bitcoin Finality. This protects users against attacks to sBTC via a hard fork. This is a critical security measure that aligns sBTC security with Bitcoin. Read more in [the Stacks Documentation](https://docs.stacks.co/concepts/block-production/bitcoin-finality).
+
+</details>
+
+<details>
+
+<summary>How does the Stacks Signer network improve security?</summary>
+
+Signers are responsible for approving all sBTC deposit and withdrawal operations, ensuring the integrity of the system. With a requirement of 70% consensus for transaction approval, Signers maintain the protocol's liveness and security.
+
+To launch sBTC, the Stacks community approved [SIP-028](https://github.com/stacksgov/sips/blob/69d40a5f4f0ad98eb448ba44e7c31ca054820aa3/sips/sip-028-sbtc_peg.md), defining the criteria for selecting signers based on factors such as technical expertise, reliability, performance, and decentralization. An initial group of 15 institutional Signers has been chosen for Phase 1 to maintain simplicity and reduce operational risks. This group will expand over time as the protocol matures.
+
+The list of sBTC signers is public and listed [here](https://bitcoinl2labs.com/sbtc-rollout#sbtc-signers).
+
+</details>
+
+<details>
+
+<summary>What security measures have been put in place to ensure sBTC is safe?</summary>
+
+sBTC is always backed 1:1 against BTC, and it's verifiably secure through threshold cryptography. sBTC removes the need for 3rd party custodian or trusted setup. Instead, BTC is secured by a decentralized signer set.
+
+Partnerships with top-tier security experts have been established to ensure the protocol is fortified at every level:
+
+1. **Asymmetric Research:** [Asymmetric Research](https://www.asymmetric.re) is a core security contributor. Known for their rigorous research and protocol audits, Asymmetric brings security expertise to sBTC to identify and mitigate potential vulnerabilities.
+2. **ImmuneFi:** A robust bug bounty program incentivizes ethical hackers to uncover and address potential issues, adding an additional layer of defense.
+3. **3rd Party Audits:** Independent audit reports are in progress for additional security reviews, ensuring the protocol is thoroughly vetted by external experts.
+
+</details>
+
+<details>
+
+<summary>What sets sBTC apart?</summary>
+
+Here are the main differentiating characteristics of sBTC:
+
+* sBTC is a true Bitcoin native product
+* sBTC is backed by respected leaders in the Bitcoin community (signer network)
+* sBTC's security is provided by a decentralized network of validators/signers rather than a single custodian, removing the need to trust a single entity or exchange
+* sBTC leverages 100% Bitcoin finality
+* sBTC's technology offers optimal UX and DevEx for an L2
+* sBTC is a fully transparent project/product working in the open with public code
+
+</details>
+
+<details>
+
+<summary>Where can I learn more about the sBTC signers?</summary>
+
+Read the "[Selection of sBTC Signer Set](https://github.com/stacks-network/sbtc/discussions/624)" post for more information about each signer and their qualifications.
+
+</details>
+
+### sBTC Rewards Program
+
+<details>
+
+<summary>Where does the yield paid in BTC come from?</summary>
+
+The sBTC Rewards Program is powered by a group of Stackers "Stacking" STX to a designated reward address, contributing their BTC rewards to the program.
+
+When Stacking STX, Stackers receive BTC through Stack's [Proof-of-Transfer](https://docs.stacks.co/concepts/stacks-101/proof-of-transfer) (PoX) consensus mechanism. For example, over a given 2-week period, the Stacks protocol has historically [distributed around 10% APY to Stackers](https://www.stacking-tracker.com/), paid in BTC.
+
+To enable the sBTC Rewards Program, these stackers contribute the corresponding Proof of Transfer BTC rewards to the sBTC incentive pool. This BTC from the incentive pool is directly deposited into a smart contract that bridges the BTC to sBTC and distributes the rewards pro rata to sBTC holders.
+
+The program is designed to increase sBTC liquidity and drive early usage of the protocol.
+
+Here's a handy illustration to show the sBTC incentives design:
+
+![](<../../.gitbook/assets/image (1).png>)
+
+</details>
+
+<details>
+
+<summary>How are rewards distributed?</summary>
+
+sBTC is automatically distributed every two weeks to the STX address used to enroll in your non-custodial wallet.
+
+</details>
+
+<details>
+
+<summary>What do I have to do to be eligible for rewards?</summary>
+
+To be eligible, you must enroll in the rewards program at bitcoinismore.org.
+
+</details>
+
+<details>
+
+<summary>What level of rewards should I expect?</summary>
+
+The level of rewards users can expect will vary based on the amount of STX in the rewards pool, the PoX yield rate, and the amount of sBTC that has been minted.
+
+</details>
+
+<details>
+
+<summary>What is the difference between PoX Rewards and the sBTC Rewards Program?</summary>
+
+PoX Bitcoin rewards are earned by Stackers who lock up their STX tokens to secure the Stacks network, a process that has been ongoing since the launch of Stacks.
+
+The sBTC Rewards Program, on the other hand, offers additional BTC rewards specifically for early adopters who hold sBTC without requiring them to participate in network consensus or lock up any tokens.
+
+</details>
+
+### Using sBTC
+
+<details>
+
+<summary>When will sBTC be available?</summary>
+
+sBTC deposits first went live on December 16, 2024, quickly hitting the 1,000 BTC cap. The second cap will go live on February 25th, 2025, with withdrawals expected in March 2025.
+
+Full decentralization of the Signer set will follow in [a subsequent phase](https://bitcoinl2labs.com/sbtc-rollout), gradually expanding beyond the initial 15 community-elected signers.
+
+</details>
+
+<details>
+
+<summary>What wallets are supported for sBTC?</summary>
+
+[Xverse](https://www.xverse.app) and [Leather](https://leather.io) wallets are supported — two leading wallets with seamless integrations designed for Bitcoin and Stacks users.
+
+In addition, [Ledger](https://www.ledger.com/) and [Asigna](https://www.asigna.io/) support sBTC.
+
+We are actively working with institutional custodians, staking providers, and other 3rd party wallets to support sBTC. More will be announced.
+
+</details>
+
+<details>
+
+<summary>Why is there a .01 BTC minimum for BTC to sBTC deposits?</summary>
+
+A .01 BTC minimum is imposed for BTC to sBTC deposits to ensure the system does not get spammed by many smaller transactions. We are exploring reducing the deposit minimum for future phases.
+
+</details>
+
+<details>
+
+<summary>What are the steps to use the sBTC Bridge and earn rewards?</summary>
+
+In the Stacks Documentation, find a [video](https://www.youtube.com/watch?v=XZruuDgTo4k\&t=1s) and a [more detailed walkthrough](https://docs.stacks.co/guides-and-tutorials/sbtc/how-to-use-the-sbtc-bridge).
+
+1. Ensure BTC is accessible via one of the following non-custodial wallets: [Xverse](https://www.xverse.app), [Leather](https://leather.io), [Ledger](https://www.ledger.com/), or [Asigna](https://www.asigna.io/).
+2. To interact with the sBTC protocol and mint sBTC, head to [app.stacks.co](http://app.stacks.co) and connect your non-custodial wallet with BTC ready to deposit.
+3. Enter the BTC amount to convert to sBTC ([app.stacks.co](http://app.stacks.co) will guide you through this step).
+4. Enter your Stacks receiving address to initiate the transfer ([app.stacks.co](http://app.stacks.co) will guide you through this step).
+5. After your sBTC has been minted to your wallet, visit the rewards program site at [bitcoinismore.org](https://bitcoinismore.org/) and connect your wallet. Then click the 'Earn Rewards' button. Read more in [the Stacks Documentation](https://docs.stacks.co/guides-and-tutorials/sbtc/earn-sbtc-rewards).
+6. Seamlessly start earning sBTC rewards. sBTC is automatically paid every two weeks to the STX address used to enroll in your non-custodial wallet.
+
+**Note:** There is an initial lock-up period until withdrawals are activated in March. Following the lock-up period, sBTC can always be withdrawn.
+
+</details>
+
+<details>
+
+<summary>How long will it take for my BTC deposit to confirm?</summary>
+
+sBTC facilitates rapid movement between BTC and sBTC.
+
+1. BTC to sBTC conversion can be completed within 3 Bitcoin blocks (under an hour).
+2. sBTC to BTC conversion can be completed within 6 Bitcoin blocks (Approximately two hours)
+
+Read more in the [Stacks Documentation](https://docs.stacks.co/concepts/sbtc/operations/deposit-withdrawal-times).
+
+</details>
+
+<details>
+
+<summary>Why is the BTC locked until March?</summary>
+
+sBTC will be rolled out over two main phases. The first phase focuses on the peg-in functionality. Phase 2 will activate the withdrawal functionality, which is expected to activate in March.
+
+For security purposes, only the deposit/peg-in functionality will be activated in phase 1. The sBTC team is taking an iterative approach to ensure greater stability at launch. For more details on the sBTC launch plan, see [here](https://bitcoinl2labs.com/sbtc-rollout).
+
+</details>
+
+<details>
+
+<summary>Why is there a cap on the total BTC pegged in?</summary>
+
+A BTC cap will be implemented to ensure a smooth rollout process with a focus on security.
+
+In addition, the BTC cap will give developers the time to focus on the sBTC user experience and integration with DeFi applications across the Stacks ecosystem prior to opening sBTC for all users.
+
+</details>
+
+<details>
+
+<summary>Are there any associated fees with minting sBTC?</summary>
+
+There are two transaction fees required to mint your sBTC. The first is set by the user manually when they initiate the deposit transaction within their wallet.
+
+The second is a fee used to consolidate the deposit UTXOs into the single signer UTXO. This separate transaction fee happens automatically and is set to a max of 80k sats. This is automatically deducted from your minted sBTC. This is not a signer fee but a regular Bitcoin transaction fee.
+
+</details>
+
+<details>
+
+<summary>Are there multi-signature solutions for sBTC?</summary>
+
+Yes. [Asigna](https://www.asigna.io) provides a multi-signature solution for sBTC users.
+
+</details>
+
+<details>
+
+<summary>Are custodians available to support sBTC?</summary>
+
+At the moment, there is no custodian support for sBTC. However, we are actively working with institutional custodians to support sBTC.
+
+Copper and BitGo already support Stacks and Stacking; however, we are working to prioritize SIP-10 and sBTC integration.
+
+</details>
diff --git a/concepts/transactions/post-conditions.md b/concepts/transactions/post-conditions.md
@@ -28,7 +28,7 @@ When you use a Stacks wallet like the Hiro web wallet and initiate a transaction
 
 Here's what that looks like:
 
-<figure><img src="../../.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png" alt=""><figcaption></figcaption></figure>
 
 In this example, if the smart contract does not transfer one fabulous-frog NFT and and take 50 STX from the user, the transaction will abort.
 

diff --git a/guides-and-tutorials/running-a-signer/README.md b/guides-and-tutorials/running-a-signer/README.md
@@ -188,7 +188,7 @@ To make sure your signer is running successfully, run `docker ps` to list your r
 
 You should see something like this
 
-<figure><img src="../../.gitbook/assets/image (1) (1) (1) (1) (1).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../.gitbook/assets/image (1) (1) (1) (1) (1) (1).png" alt=""><figcaption></figcaption></figure>
 
 Now check the logs of that container by running:
 
@@ -303,7 +303,7 @@ If when running your node you get a connection refused error that looks like thi
 
 First, be sure that you have the proper entry point specified in your `node-config.toml` file.
 
-<figure><img src="../../.gitbook/assets/image (1) (1) (1).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../.gitbook/assets/image (1) (1) (1) (1).png" alt=""><figcaption></figcaption></figure>
 
 If 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.
 

diff --git a/guides-and-tutorials/sbtc/earn-sbtc-rewards.md b/guides-and-tutorials/sbtc/earn-sbtc-rewards.md
@@ -21,7 +21,7 @@ After your sBTC has been minted to your wallet, visit the rewards program site a
 {% hint style="info" %}
 You may need to enable the sBTC token listing display in your wallet before it is visible. In Leather, you can do this by clicking 'Manage Tokens' and toggling on sBTC.
 
-<img src="../../.gitbook/assets/image.png" alt="" data-size="original">
+<img src="../../.gitbook/assets/image (2).png" alt="" data-size="original">
 {% endhint %}
 
 <figure><img src="../../.gitbook/assets/image (20).png" alt=""><figcaption></figcaption></figure>

diff --git a/guides-and-tutorials/sbtc/how-to-use-the-sbtc-bridge.md b/guides-and-tutorials/sbtc/how-to-use-the-sbtc-bridge.md
@@ -32,7 +32,7 @@ There are 5 simple steps to convert your BTC to sBTC.
 
 First, you'll need to connect your wallet to the bridge UI. Currently Leather and Xverse are supported, with more on the way.
 
-<figure><img src="../../.gitbook/assets/image (1).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../.gitbook/assets/image (1) (1).png" alt=""><figcaption></figcaption></figure>
 {% endstep %}
 
 {% step %}
@@ -46,15 +46,15 @@ There are two transaction fees required to mint your sBTC. The first is set by t
 
 
 
-<figure><img src="../../.gitbook/assets/image (1) (1).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../.gitbook/assets/image (1) (1) (1).png" alt=""><figcaption></figcaption></figure>
 {% endstep %}
 
 {% step %}
 ### Choose the Stacks address to mint to
 
 Next, enter the Stacks address you would like your sBTC minted to.
 
-<figure><img src="../../.gitbook/assets/image (2).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../.gitbook/assets/image (2) (1).png" alt=""><figcaption></figcaption></figure>
 {% endstep %}
 
 {% step %}

diff --git a/guides-and-tutorials/stack-stx/operate-a-pool.md b/guides-and-tutorials/stack-stx/operate-a-pool.md
@@ -384,8 +384,6 @@ Even after the signer commits to a certain amount of STX in the previous step, t
 
 </details>
 
-
-
 ### Step by Step Stacking Guide
 
 Now that you are familiar with the overall stacking flow and the different roles played, let's dive into the step-by-step guide for actually conducting the stacking process as a pool operator.
@@ -511,7 +509,7 @@ To generate a signer key signature, it’s important that you’ve logged in Lea
 \
 Click the link “Signer key signature” at the bottom of the page. This will open the “generate a signer key signature” page.
 
-<figure><img src="../../.gitbook/assets/image (2) (1).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../.gitbook/assets/image (2) (1) (1).png" alt=""><figcaption></figcaption></figure>
 
 The fields are:
 

diff --git a/guides-and-tutorials/stack-stx/stacking-flow.md b/guides-and-tutorials/stack-stx/stacking-flow.md
@@ -369,6 +369,7 @@ You may want to review this contract to familiarize yourself with it.
 {% endhint %}
 
 Here is an overview of the fields you will need to pass. We'll cover how to get and pass these fields as we dive further into this doc:
+
 1. `signer-key`: the public key that corresponds to the `stacks_private_key` your signer is using
 2. `signer-signature`: a signature that demonstrates that you actually controls your `signer-key`. Because signer keys need to be unique, this is also a safety check to ensure that other Stackers can’t use someone else’s public key
 3. `max-amount`: The maximum amount of ustx (1 STX = 1,000,000 uSTX) that can be locked in the transaction that uses this signature. For example, if calling `stack-increase`, then this parameter dictates the maximum amount of uSTX that can be used to add more locked STX
@@ -450,7 +451,7 @@ To generate a signer key signature, it’s important that you’ve logged in Lea
 \
 Click the link “Signer key signature” at the bottom of the page. This will open the “generate a signer key signature” page.
 
-<figure><img src="../../.gitbook/assets/image (2) (1).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../.gitbook/assets/image (2) (1) (1).png" alt=""><figcaption></figcaption></figure>
 
 The fields are:
 

diff --git a/nakamoto-upgrade/nakamoto-in-10-minutes.md b/nakamoto-upgrade/nakamoto-in-10-minutes.md
@@ -44,7 +44,7 @@ This elegant design creates a cooperative relationship between miners and stacke
 
 Here is a diagram outlining miner and signer behavior.
 
-<figure><img src="../.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1) (1).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png" alt=""><figcaption></figcaption></figure>
 
 ### Bitcoin MEV Mitigation