@@ -89,7 +89,55 @@ answers posted since our last update.*
89
89
{% comment %}<!-- https://bitcoin.stackexchange.com/search?tab=votes&q=created%3a1m..%20is%3aanswer --> {% endcomment %}
90
90
{% assign bse = "https://bitcoin.stackexchange.com/a/ " %}
91
91
92
- FIXME: bitschmidty
92
+ - [ How does ColliderScript improve Bitcoin and what features does it enable?] ( {{bse}}124690 )
93
+ Victor Kolobov lists potential uses for ColliderScript (see [ Newsletter
94
+ #330 ] [ news330 cs ] and [ Podcast #330 ] [ pod330 cs ] ) including [ covenants] [ topic
95
+ covenants] , [ vaults] [ topic vaults ] , emulation of [ CSFS] [ topic
96
+ op_checksigfromstack] , and validity rollups (see [ Newsletter #222 ] [ news222
97
+ validity rollups] ) while noting the high computational costs of such transactions.
98
+
99
+ - [ Why do standardness rules limit transaction weight?] ( {{bse}}124636 )
100
+ Murch provides arguments for and against Bitcoin Core's standardness weight
101
+ limits and outlines how economic demand for larger transactions could erode
102
+ the effectiveness of the [ policy] [ policy series ] .
103
+
104
+ - [ Is the scriptSig spending an PayToAnchor output expected to always be empty?] ( {{bse}}124615 )
105
+ Pieter Wuille points out that because of how [ pay-to-anchor (P2A)] [ topic ephemeral
106
+ anchors] outputs are [ constructed] [ news326 p2a ] , they must adhere to segwit spending
107
+ conditions, including an empty scriptSig.
108
+
109
+ - [ What happens to the unused P2A outputs?] ( {{bse}}124617 )
110
+ Instagibbs notes that unused P2A outputs will eventually be swept when the block
111
+ inclusion feerate drops low enough to make a sweep worth it, removing them from
112
+ the UTXO set. He goes on to reference
113
+ the recently-merged [ ephemeral dust] [ news330 ed ] PR that allows a single
114
+ below-dust-threshold output in a zero-fee transaction provided a [ child
115
+ transaction] [ topic cpfp ] immediately spends it.
116
+
117
+ - [ Why doesn't Bitcoin's PoW algorithm use a chain of lower-difficulty hashes?] ( {{bse}}124777 )
118
+ Pieter Wuille and Vojtěch Strnad describe the mining centralization pressure
119
+ that would happen if the progress-free property of Bitcoin's mining was
120
+ violated with such an approach.
121
+
122
+ - [ Clarification on false value in Script] ( {{bse}}124673 )
123
+ Pieter Wuille specifies the three values that evaluate to false in Bitcoin
124
+ Script: an empty array, an array of 0x00 bytes, and an array of 0x00 bytes with a
125
+ 0x80 at the end. He notes that all other values are evaluated as true.
126
+
127
+ - [ What is this strange microtransaction in my wallet?] ( {{bse}}124744 )
128
+ Vojtěch Strnad explains the mechanics of an address poisoning attack and ways
129
+ to mitigate such attacks.
130
+
131
+ - [ Are there any UTXOs that can not be spent?] ( {{bse}}124865 )
132
+ Pieter Wuille provides two examples of outputs that are unspendable regardless
133
+ of the breaking of cryptographic assumptions: ` OP_RETURN ` outputs and outputs
134
+ with a scriptPubKey longer than 10,000 bytes.
135
+
136
+ - [ Why was BIP34 not implemented via the coinbase tx's locktime or nSequence?] ( {{bse}}75987 )
137
+ Antoine Poinsot follows up to this older question to point out that the
138
+ coinbase transaction's ` nLockTime ` value cannot be set to the current block
139
+ height because the [ locktime] [ topic timelocks ] represents the last block at
140
+ which a transaction is * invalid* .
93
141
94
142
## Releases and release candidates
95
143
@@ -188,3 +236,9 @@ repo], and [BINANAs][binana repo]._
188
236
[ ldk 0.18.4-beta.rc1 ] : https://github.com/lightningnetwork/lnd/releases/tag/v0.18.4-beta.rc1
189
237
[ news316 askrene ] : /en/newsletters/2024/08/16/#core-lightning-7517
190
238
[ news263 renepay ] : /en/newsletters/2023/08/09/#core-lightning-6376
239
+ [ news330 cs ] : /en/newsletters/2024/11/22/#covenants-based-on-grinding-rather-than-consensus-changes
240
+ [ pod330 cs ] : /en/podcast/2024/11/26/#covenants-based-on-grinding-rather-than-consensus-changes
241
+ [ news222 validity rollups ] : /en/newsletters/2022/10/19/#validity-rollups-research
242
+ [ policy series ] : /en/blog/waiting-for-confirmation/
243
+ [ news326 p2a ] : /en/newsletters/2024/10/25/#how-was-the-structure-of-pay-to-anchor-decided
244
+ [ news330 ed ] : /en/newsletters/2024/11/22/#bitcoin-core-30239
0 commit comments