Skip to content

Commit 586eddd

Browse files
jonatackbitschmidty
authored andcommitted
News119: Bitcoin Core review club signet feature
1 parent c1281dd commit 586eddd

File tree

2 files changed

+63
-5
lines changed

2 files changed

+63
-5
lines changed

_posts/en/newsletters/2020-10-14-newsletter.md

Lines changed: 60 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -123,12 +123,62 @@ changes to popular Bitcoin infrastructure software.
123123
meeting, highlighting some of the important questions and answers. Click on a
124124
question below to see a summary of the answer from the meeting.*
125125

126-
FIXME:jnewbery or jonatack
126+
[BIP-325: Signet][review club #18267] is a PR ([#18267][Bitcoin Core #18267]) by
127+
Kalle Alm that implements a new kind of Bitcoin test network. The PR has since
128+
been merged (see [Newsletter #117][news117 signet]), and the upcoming v0.21
129+
release will support [signet][topic signet].
130+
131+
The review club discussion covered general concepts before diving into the
132+
deeper technical aspects. Participants with good answers were rewarded with
133+
signet coins. Here is a mini-quiz on general signet concepts:
127134

128135
{% include functions/details-list.md
129-
q0="FIXME"
130-
a0="FIXME"
131-
a0link="https://bitcoincore.reviews/19339#l-FIXME"
136+
q0="What is signet?"
137+
a0="Signet is defined by [BIP325][bip325] and is a mechanism to build
138+
stable, centralized, and custom proof-of-work networks. It's also
139+
the name of a specific global testnet."
140+
a0link="https://bitcoincore.reviews/18267#l-94"
141+
142+
q1="Is signet intended to replace existing Bitcoin testing networks like
143+
testnet or regtest?"
144+
a1="They are complementary. Signet was conceived as a centralized, stable
145+
improvement for cases where the current testnet isn't ideal."
146+
147+
q2="What problems do we have with the current testnet?"
148+
a2="Testnet is unreliable due to disruptive reorgs, highly variable
149+
block production, and a skewed incentive model: testnet coins don't have
150+
value, but testnet mining is not free and the difficulty fluctuates."
151+
a2link="https://bitcoincore.reviews/18267#l-149"
152+
153+
q3="What is the difference between signet and regtest (Bitcoin Core's
154+
regression test framework)?"
155+
a3="Regtest is a sandboxed environment with entirely manual network topology
156+
and block generation that is suitable for local testing, but its
157+
permissionless nature that allows anyone to mine means that regtest
158+
cannot be used publicly with third-party peers in a stable fashion. Signet
159+
is an actual network with public nodes, suitable for testing network
160+
effects like finding peers, transaction selection, and transaction and
161+
block propagation."
162+
163+
q4="What is the default signet challenge script in the PR?"
164+
a4="Multisig 1-of-2 addresses. This may be modified with the `-signetchallenge`
165+
configuration option."
166+
a4link="https://bitcoincore.reviews/18267#l-252"
167+
168+
q5="In the `CreateGenesisBlock()` method, which parameter determines the
169+
difficulty?"
170+
a5="Difficulty is set by the [nBits][] parameter, a custom compressed
171+
representation of the proof of work target whose human-readable representation is
172+
difficulty."
173+
a5link="https://bitcoincore.reviews/18267#l-474"
174+
175+
q6="Is the difficulty for the signet genesis block lower than the difficulty
176+
for the mainnet genesis block?"
177+
a6="Yes, signet has a higher default `nBits` and therefore a lower difficulty target:
178+
[mainnet 1d00ffff, signet 1e0377ae][compare difficulty].
179+
However, it's just a minimum target; the signer
180+
[may set it to be higher][signet difficulty]."
181+
a6link="https://bitcoincore.reviews/18267#l-481"
132182
%}
133183

134184
## Releases and release candidates
@@ -164,7 +214,7 @@ release candidates.*
164214
enough (e.g. when consolidating and rebalancing channels).
165215

166216
{% include references.md %}
167-
{% include linkers/issues.md issues="19954,1537" %}
217+
{% include linkers/issues.md issues="19954,1537,18267" %}
168218
[hwi 1.2.0]: https://github.com/bitcoin-core/HWI/releases/tag/1.2.0
169219
[eclair 0.4.2]: https://github.com/ACINQ/eclair/releases/tag/v0.4.2
170220
[lnd warning]: https://lists.linuxfoundation.org/pipermail/lightning-dev/2020-October/002819.html
@@ -182,3 +232,8 @@ release candidates.*
182232
[news113 witasym]: /en/newsletters/2020/09/02/#witness-asymmetric-payment-channels
183233
[fournier v2]: https://github.com/LLFourn/witness-asymmetric-channel
184234
[wuille new bech32]: https://gist.github.com/sipa/a9845b37c1b298a7301c33a04090b2eb#improving-detection-of-insertion-errors
235+
[bip325]: https://github.com/bitcoin/bips/blob/master/bip-0325.mediawiki
236+
[compare difficulty]: https://bitcoincore.reviews/18267#l-478
237+
[signet difficulty]: https://bitcoincore.reviews/18267#l-485
238+
[news117 signet]: /en/newsletters/2020/09/30/#bitcoin-core-18267
239+
[nbits]: https://btcinformation.org/en/developer-reference#target-nbits

_topics/en/signet.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -85,6 +85,9 @@ optech_mentions:
8585
- title: "C-Lightning #4068 and #4078 update C-Lightning’s signet implementation"
8686
url: /en/newsletters/2020/09/30/#c-lightning-4068
8787

88+
- title: Summary of Bitcoin Core PR Review Meeting on adding signet support
89+
url: /en/newsletters/2020/10/14/#bitcoin-core-pr-review-club
90+
8891
## Optional. Same format as "primary_sources" above
8992
see_also:
9093
- title: "Bitcoin Core #16411: signet support"

0 commit comments

Comments
 (0)