GITBOOK-119: Add supported BTC address types heading

stacks-network · Apr 23, 2024 · 80a6e84 · 80a6e84
1 parent 6d319f5
commit 80a6e84
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 2 deletions.
diff --git a/clarity/example-contracts/stacking.md b/clarity/example-contracts/stacking.md
@@ -1568,9 +1568,12 @@ First let's cover the needed parameters.
 * `auth-id` is a unique string to prevent re-use of this stacking transaction
 
 {% hint style="warning" %}
-It's important to make sure that these fields match what you pass in to the signer signature generation. If they don't, you will likely get error 35 (`ERR_INVALID_SIGNATURE_PUBKEY`) when trying to submit this transaction as the signer signature will not be valid.
+It's important to make sure that these fields match what you pass in to the signer signature generation. If they don't, you will likely get error 35 (`ERR_INVALID_SIGNATURE_PUBKEY`) \
+when trying to submit this transaction as the signer signature will not be valid.
 {% endhint %}
 
+#### Supported Reward Address Types
+
 {% hint style="info" %}
 For the `pox-addr` field, the `version` buffer must represent what kind of bitcoin address is being submitted. These are all the possible values you can pass here depending on your address type:
 

diff --git a/stacks-101/stacking.md b/stacks-101/stacking.md
@@ -88,7 +88,7 @@ Stacks (STX) token holders don't automatically receive stacking rewards. Instead
 * Commit to participation before a reward cycle begins
 * Commit the minimum amount of STX tokens to secure a reward slot, or pool with others to reach the minimum
 * Lock up STX tokens for a specified period
-* Provide a supported Bitcoin address to receive rewards (native segwit is not supported)
+* Provide a supported Bitcoin address to receive rewards
 * Maintain their signer software (if they are operating a signer)
 
 The following diagram describes how the minimum STX tokens per slot is determined.