@@ -136,7 +136,43 @@ answers posted since our last update.*
136136{% comment %}<!-- https://bitcoin.stackexchange.com/search?tab=votes&q=created%3a1m..%20is%3aanswer -->{% endcomment %}
137137{% assign bse = "https://bitcoin.stackexchange.com/a/" %}
138138
139- FIXME:bitschmidty
139+ - [Why is witness data downloaded during IBD in prune mode?]({{bse}}117057)
140+ Pieter Wuille notes that for nodes running in [prune mode], "the witness data
141+ that is both (a) before the assumevalid point and (b) sufficiently buried to
142+ be past the prune point, there is indeed little to gain from having it". There
143+ is currently a [draft PR][Bitcoin Core #27050] open to address this and [a PR
144+ Review Club][pr review 27050] covering the proposed change.
145+
146+ - [Can Bitcoin's P2P network relay compressed data?]({{bse}}116999)
147+ Pieter Wuille links to two mailing list discussions about compression (one about
148+ [specialized compression for headers sync][] and one about [general LZO-based
149+ compression][]) and points out that Blockstream Satellite uses a custom
150+ transaction compression scheme.
151+
152+ - [How does one become a DNS seed for Bitcoin Core?]({{bse}}116931)
153+ User Paro explains the requirements for someone wanting to become a [DNS
154+ seed][news66 dns seed] to provide new nodes with initial peers.
155+
156+ - [Where can I learn about open research topics in Bitcoin?]({{bse}}116898)
157+ Michael Folkson provides a variety of resources including [Chaincode Labs
158+ Research][] and [Bitcoin Problems][], among others.
159+
160+ - [What is the maximum size transaction that will be relayed by bitcoin nodes using the default configuration?]({{bse}}117277)
161+ Pieter Wuille points out Bitcoin Core's 400,000 [weight unit][] standardness
162+ policy rule, notes that it is not currently configurable, and explains the
163+ intended benefits of that limit including DoS protections.
164+
165+ - [Understanding how ordinals work with in Bitcoin. What is exactly stored on the blockchain?]({{bse}}117018)
166+ Vojtěch Strnad clarifies that Ordinals Inscriptions do not use `OP_RETURN`,
167+ but instead embed data into an unexecuted script branch using the
168+ `OP_PUSHDATAx` opcodes similar to:
169+
170+ ```
171+ OP_0
172+ OP_IF
173+ <data pushes>
174+ OP_ENDIF
175+ ```
140176
141177## Releases and release candidates
142178
@@ -210,7 +246,7 @@ Proposals (BIPs)][bips repo], and [Lightning BOLTs][bolts repo].*
210246 having to construct a candidate transaction.
211247
212248{% include references.md %}
213- {% include linkers/issues.md v=2 issues="24149,25344,2596,2595,2479,5988,1636" %}
249+ {% include linkers/issues.md v=2 issues="24149,25344,2596,2595,2479,5988,1636,27050 " %}
214250[core lightning 23.02rc3]: https://github.com/ElementsProject/lightning/releases/tag/v23.02rc3
215251[news226 jam]: /en/newsletters/2022/11/16/#paper-about-channel-jamming-attacks
216252[news86 boomerang]: /en/newsletters/2020/02/26/#boomerang-redundancy-improves-latency-and-throughput-in-payment-channel-networks
@@ -230,3 +266,11 @@ Proposals (BIPs)][bips repo], and [Lightning BOLTs][bolts repo].*
230266[op codex32]: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2023-February/021469.html
231267[RUSTSEC-2022-0090]: https://rustsec.org/advisories/RUSTSEC-2022-0090
232268[bdk 0.27.1]: https://github.com/bitcoindevkit/bdk/releases/tag/v0.27.1
269+ [prune mode]: https://bitcoin.org/en/full-node#reduce-storage
270+ [pr review 27050]: https://bitcoincore.reviews/27050
271+ [specialized compression for headers sync]: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2018-March/015851.html
272+ [general LZO-based compression]: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-November/011837.html
273+ [news66 dns seed]: /en/newsletters/2019/10/02/#bitcoin-core-15558
274+ [Chaincode Labs Research]: https://research.chaincode.com/research-intro/
275+ [Bitcoin Problems]: https://bitcoinproblems.org/
276+ [weight unit]: https://en.bitcoin.it/wiki/Weight_units
0 commit comments