@@ -97,6 +97,48 @@ you pay to access all of segwit's benefits.*
97
97
98
98
{% include specials/bech32/24-conclusion.md %}
99
99
100
+ ## Selected Q&A from Bitcoin StackExchange
101
+
102
+ * [ Bitcoin StackExchange] [ bitcoin.se ] is one of the first places Optech
103
+ contributors look for answers to their questions---or when we have a
104
+ few spare moments of time to help curious or confused users. In
105
+ this monthly feature, we highlight some of the top-voted questions and
106
+ answers made since our last update.*
107
+
108
+ {% comment %}<!-- https://bitcoin.stackexchange.com/search?tab=votes&q=created%3a1m..%20is%3aanswer --> {%
109
+ endcomment %}
110
+ {% assign bse = "https://bitcoin.stackexchange.com/a/ " %}
111
+
112
+ - [ What are the key differences between regtest and the proposed
113
+ signet?] ( {{bse}}89640 ) Pieter Wuille and Andrew Chow explain that while
114
+ regtest is good for local automated integration tests, signet is more akin to
115
+ testnet in that it allows testing of things like peer finding, propagation,
116
+ and transaction selection. Signet allows for more control over block
117
+ production timing than testnet and more than one signet can exist for testing
118
+ different scenarios.
119
+
120
+ - [ Can hardware wallets actually display the amount of funds leaving your
121
+ control?] ( {{bse}}89508 ) Andrew Chow explains that since a hardware wallet is
122
+ not a full node, it needs to get its transaction amount information elsewhere.
123
+ In the case of non-segwit inputs, often the amount is provided to the hardware
124
+ signing device via the host computer or other wallet by sending the previous
125
+ transaction to the device. In the case of segwit inputs, the amount for the
126
+ input being signed must always be provided because it is a required part of
127
+ the data that is signed and verified.
128
+
129
+ - [ How does one prove that they sent bitcoins to an unspendable
130
+ wallet?] ( {{bse}}89554 ) JBaczuk explains that you can prove coins
131
+ unspendable by sending the coins to an OP_RETURN output
132
+ or another script that always returns false, or by sending coins to an
133
+ address derived from a contrived, non-random script hash.
134
+
135
+ - [ Why is proof-of-work required in Bitcoin?] ( {{bse}}89972 ) Pieter Wuille
136
+ explains that PoW does not create trust, but instead creates incentive for
137
+ miners to cooperate with other miners by building on their blocks. PoW is also
138
+ used to regulate block times (and thus protect against denial of service)
139
+ since the difficulty adjustment makes it expensive to reliably produce blocks
140
+ more often than every 10 minutes on average.
141
+
100
142
## Notable code and documentation changes
101
143
102
144
* Notable changes this week in [ Bitcoin Core] [ bitcoin core repo ] ,
0 commit comments