-
Notifications
You must be signed in to change notification settings - Fork 5
/
Copy pathhomepage.json
316 lines (316 loc) · 19.9 KB
/
homepage.json
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
{
"header_summary": "Peter Todd's update on the integration of taproot annex support into Libre Relay, as referenced by a GitHub commit, highlights the adoption of criteria for standard transactions containing taproot annexes, inspired by Joost Jager's pull request on the Bitcoin repository. This specification ensures the differentiation of these annexes from future consensus-relevant ones, potentially safeguarding against soft-fork conflicts, while addressing multi-party protocol vulnerabilities like transaction pinning attacks ([source](https://github.com/petertodd/bitcoin/commit/04c8e449a34e74e048bf5751d13592a22763ff7e)).\n\nMurch's communication regarding the progress of BIP3, now in its draft phase and pending final comments before moving to proposed status, signifies a pivotal moment in its adoption within the Bitcoin protocol. The lack of feedback suggests a broad consensus among stakeholders, marking a step forward in the proposal's lifecycle and inviting further community involvement for its refinement ([source](https://github.com/bitcoin/bips/pull/1794)).\n\nErik Aronesty raises concerns about security vulnerabilities in Bitcoin transactions, particularly the risk of attackers deducing private keys from public ones in specific transaction scenarios. This discussion opens up considerations for network protocol changes, such as hard forks, to address these vulnerabilities and the implications of QR-based transactions for the ecosystem's security ([source](https://gnusha.org/pi/bitcoindev/CALkkCJZ3TBEfRYBHVv_NON18mqbsQixgUEtgGThau4D=W6gdGg@mail.gmail.com/T/#mceac77c133dddc2c08b815b63deea2a517cd9503)).\n\nStevenroose's analysis of the Arkoor model introduces a nuanced approach to managing liquidity costs in VTXO refreshes, balancing trustlessness with fee savings. The model's interactivity requirement, crucial for its operation, is highlighted alongside the challenges it faces, such as vulnerability to DoS attacks, underscoring the broader complexities of systems requiring cooperative participant behavior ([source](https://delvingbitcoin.org/t/the-ark-case-for-ctv/1528/5)).",
"recent_posts": [
{
"id": "md34f3d5ad6bb83526df6817364ac8843b43dd8bb",
"title": "Standard Unstructured Annex",
"link": "https://gnusha.org/pi/bitcoindev/[email protected]/T/#u#md34f3d5ad6bb83526df6817364ac8843b43dd8bb",
"authors": [
"Peter Todd"
],
"published_at": "2025-03-20T00:27:00+00:00",
"summary": "- Libre Relay integrates taproot annex support; influenced by Joost Jager's Bitcoin pull request.\n- Transactions must initiate non-empty annexes with byte 0x00 to be standard, preventing future soft-fork conflicts.\n- Initiative is part of Bitcoin Development Mailing List discussions, with further details on Peter Todd's website.",
"n_threads": 0,
"dev_name": "bitcoin-dev",
"contributors": [],
"file_path": "static/bitcoin-dev/March_2025/md34f3d5ad6bb83526df6817364ac8843b43dd8bb_Standard-Unstructured-Annex.xml",
"combined_summ_file_path": ""
},
{
"id": "m5ed327e544e9ee793b0babfb23bd7a8e30fee217",
"title": "Finished planned work on BIP 3: Updated BIP Process",
"link": "https://gnusha.org/pi/bitcoindev/[email protected]/T/#m5ed327e544e9ee793b0babfb23bd7a8e30fee217",
"authors": [
"Murch"
],
"published_at": "2025-03-19T02:38:00+00:00",
"summary": "- BIP3 progressed to Draft on February 20th, with a minor update following.\n- Lack of feedback suggests a consensus for BIP3's readiness and broader adoption.\n- Stakeholders are encouraged to share thoughts for its advancement to Proposed status.",
"n_threads": 1,
"dev_name": "bitcoin-dev",
"contributors": [],
"file_path": "static/bitcoin-dev/March_2025/m5ed327e544e9ee793b0babfb23bd7a8e30fee217_Finished-planned-work-on-BIP-3-Updated-BIP-Process.xml",
"combined_summ_file_path": "static/bitcoin-dev/March_2025/combined_Finished-planned-work-on-BIP-3-Updated-BIP-Process.xml"
},
{
"id": "mceac77c133dddc2c08b815b63deea2a517cd9503",
"title": "Hashed keys are actually fully quantum secure",
"link": "https://gnusha.org/pi/bitcoindev/CALkkCJZ3TBEfRYBHVv_NON18mqbsQixgUEtgGThau4D=W6gdGg@mail.gmail.com/T/#mceac77c133dddc2c08b815b63deea2a517cd9503",
"authors": [
"Erik Aronesty"
],
"published_at": "2025-03-18T16:48:00+00:00",
"summary": "- The email details security risks in Bitcoin transactions, including QR output exploitation.\n- It suggests a hard fork might be needed to secure QR-based transactions, changing the protocol significantly.\n- Limited evidence exists on QR transactions' prominence in Bitcoin, per the Bitcoin Development Mailing List discussion.",
"n_threads": 6,
"dev_name": "bitcoin-dev",
"contributors": [
"Martin Habov\u0161tiak",
"Agustin Cruz",
"Lloyd Fournier"
],
"file_path": "static/bitcoin-dev/March_2025/mceac77c133dddc2c08b815b63deea2a517cd9503_Hashed-keys-are-actually-fully-quantum-secure.xml",
"combined_summ_file_path": "static/bitcoin-dev/March_2025/combined_Hashed-keys-are-actually-fully-quantum-secure.xml"
},
{
"id": "4590",
"title": "The Ark case for CTV",
"link": "https://delvingbitcoin.org/t/the-ark-case-for-ctv/1528/5",
"authors": [
"stevenroose"
],
"published_at": "2025-03-22T19:12:19.635000+00:00",
"summary": "- The Arkoor model balances liquidity cost and trustless ownership for managing VTXOs.\n- It strategizes against DoS attacks by banning non-cooperative users and penalizing offenders.\n- Challenges include interactivity and the inability to directly penalize non-contributing receivers.",
"n_threads": 4,
"dev_name": "delvingbitcoin",
"contributors": [
"instagibbs",
"neha"
],
"file_path": "static/delvingbitcoin/March_2025/4590_The-Ark-case-for-CTV.xml",
"combined_summ_file_path": "static/delvingbitcoin/March_2025/combined_The-Ark-case-for-CTV.xml"
},
{
"id": "4587",
"title": "Disclosure: LND Excessive Failback Exploit",
"link": "https://delvingbitcoin.org/t/disclosure-lnd-excessive-failback-exploit/1493/6",
"authors": [
"ariard"
],
"published_at": "2025-03-22T00:51:53.089000+00:00",
"summary": "- The analysis reviews fee management in Lightning Network's BOLT3 and risks from manipulated transactions.\n- It details how malicious actors can inflate fees by withholding messages, affecting honest nodes.\n- Changes to BOLT5 may encourage fee exploitation, exposing nodes to significant financial losses.",
"n_threads": 5,
"dev_name": "delvingbitcoin",
"contributors": [
"morehouse"
],
"file_path": "static/delvingbitcoin/March_2025/4587_Disclosure-LND-Excessive-Failback-Exploit.xml",
"combined_summ_file_path": "static/delvingbitcoin/March_2025/combined_Disclosure-LND-Excessive-Failback-Exploit.xml"
},
{
"id": "4586",
"title": "Fee-Based Spam Prevention For Lightning",
"link": "https://delvingbitcoin.org/t/fee-based-spam-prevention-for-lightning/1524/3",
"authors": [
"JohnLaw"
],
"published_at": "2025-03-21T21:08:20.002000+00:00",
"summary": "- A two-step update process for HTLCs in blockchain aims to address handling of Hold Fees.\n- The suggested protocol modification includes a stage for including increased burn funds before HTLC output.\n- Enabling race-free, asynchronous updates could improve protocol efficiency and fee theft prevention.",
"n_threads": 2,
"dev_name": "delvingbitcoin",
"contributors": [
"harding"
],
"file_path": "static/delvingbitcoin/March_2025/4586_Fee-Based-Spam-Prevention-For-Lightning.xml",
"combined_summ_file_path": "static/delvingbitcoin/March_2025/combined_Fee-Based-Spam-Prevention-For-Lightning.xml"
}
],
"active_posts": [
{
"id": "m4979b674dd06ff3cbff550fd152a931de75cec6b",
"title": "\"Recursive covenant\" with CTV and CSFS",
"link": "https://gnusha.org/pi/bitcoindev/[email protected]/T/#u#m4979b674dd06ff3cbff550fd152a931de75cec6b",
"authors": [
"Anthony Towns"
],
"published_at": "2025-03-05T00:01:00+00:00",
"summary": "- Twitter discussions have brought attention to Bitcoin proposals CTV and CSFS.\n- Critics question the effectiveness of CTV's approach to preventing recursive covenants.\n- Alternatives like bllsh offer different methods for enhancing Bitcoin's script capabilities.",
"n_threads": 19,
"dev_name": "bitcoin-dev",
"contributors": [
"Antoine Riard",
"Nadav Ivgi",
"moonsettler",
"Antoine Poinsot",
"Greg Sanders",
"James OBeirne",
"Olaoluwa Osuntokun"
],
"file_path": "static/bitcoin-dev/March_2025/m4979b674dd06ff3cbff550fd152a931de75cec6b_-Recursive-covenant-with-CTV-and-CSFS.xml",
"combined_summ_file_path": "static/bitcoin-dev/March_2025/combined_-Recursive-covenant-with-CTV-and-CSFS.xml"
},
{
"id": "maa28d9da6af644d2c597d7bc4b8f33893b8d14d1",
"title": "Against Allowing Quantum Recovery of Bitcoin",
"link": "https://gnusha.org/pi/bitcoindev/CAL1wk_XDnZop2PxxCiAvgeiOgQBcRV3cN4=+1JcKf43TrKV0TA@mail.gmail.com/T/#maa28d9da6af644d2c597d7bc4b8f33893b8d14d1",
"authors": [
"Jameson Lopp"
],
"published_at": "2025-03-16T14:15:00+00:00",
"summary": "- Quantum computing poses potential threats to Bitcoin's cryptographic security, sparking varied responses.\n- Debates focus on handling Bitcoin funds vulnerable to quantum attacks, balancing security with foundational principles.\n- Ethical, technical, and philosophical complexities frame the quantum computing threat to Bitcoin, emphasizing the need for a balanced approach.",
"n_threads": 7,
"dev_name": "bitcoin-dev",
"contributors": [
"IdeA",
"Matt Corallo",
"Sjors Provoost"
],
"file_path": "static/bitcoin-dev/March_2025/maa28d9da6af644d2c597d7bc4b8f33893b8d14d1_Against-Allowing-Quantum-Recovery-of-Bitcoin.xml",
"combined_summ_file_path": "static/bitcoin-dev/March_2025/combined_Against-Allowing-Quantum-Recovery-of-Bitcoin.xml"
},
{
"id": "m08b97860799484a7f1a388892f86649065c11503",
"title": "Unbreaking testnet4",
"link": "https://gnusha.org/pi/bitcoindev/hU75DurC5XToqizyA-vOKmVtmzd3uZGDKOyXuE_ogE6eQ8tPCrvX__S08fG_nrW5CjH6IUx7EPrq8KwM5KFy9ltbFBJZQCHR2ThoimRbMqU=@protonmail.com/T/#u#m08b97860799484a7f1a388892f86649065c11503",
"authors": [
"Antoine Poinsot"
],
"published_at": "2025-03-18T14:29:00+00:00",
"summary": "- Testnet4's difficulty reset rule continues to hinder its goal of emulating the Bitcoin mainnet.\n- A hard fork in 2026 is proposed to remove this rule, aiming for a smoother development process.\n- The change seeks to balance realistic test conditions with easy access for developers.",
"n_threads": 7,
"dev_name": "bitcoin-dev",
"contributors": [
"Melvin Carvalho",
"Sjors Provoost",
"Garlo Nicon",
"bitcoin-dev-ml.void867"
],
"file_path": "static/bitcoin-dev/March_2025/m08b97860799484a7f1a388892f86649065c11503_Unbreaking-testnet4.xml",
"combined_summ_file_path": "static/bitcoin-dev/March_2025/combined_Unbreaking-testnet4.xml"
},
{
"id": "1996",
"title": "Great Consensus Cleanup Revival",
"link": "https://delvingbitcoin.org/t/great-consensus-cleanup-revival/710",
"authors": [
"AntoineP"
],
"published_at": "2024-03-24T17:29:42.691000+00:00",
"summary": "- The analysis suggests improvements to Bitcoin's protocol, focusing on security and efficiency.\n- Significant issues like the timewarp vulnerability and transaction validation delays are addressed.\n- Controversial topics include block size reduction and standardization of technical elements.",
"n_threads": 80,
"dev_name": "delvingbitcoin",
"contributors": [
"ajtowns",
"evoskuil",
"harding",
"sjors",
"zawy",
"Chris_Stewart_5",
"MattCorallo",
"recent798",
"1440000bytes",
"ariard",
"benthecarman",
"garlonicon",
"instagibbs",
"kcalvinalvin",
"plebhash",
"sipa"
],
"file_path": "static/delvingbitcoin/March_2024/1996_Great-Consensus-Cleanup-Revival.xml",
"combined_summ_file_path": "static/delvingbitcoin/March_2024/combined_Great-Consensus-Cleanup-Revival.xml"
},
{
"id": "4462",
"title": "CTV+CSFS: Can we reach consensus on a first step towards covenants?",
"link": "https://delvingbitcoin.org/t/ctv-csfs-can-we-reach-consensus-on-a-first-step-towards-covenants/1509/2",
"authors": [
"1440000bytes"
],
"published_at": "2025-03-10T22:58:38.433000+00:00",
"summary": "- Covenants in Bitcoin allow setting conditions on how funds can be spent, enhancing security.\n- They enable the development of complex applications like trustless escrow and DeFi.\n- A dedicated wiki page offers comprehensive insights into Bitcoin covenants for interested individuals.",
"n_threads": 53,
"dev_name": "delvingbitcoin",
"contributors": [
"instagibbs",
"jamesob",
"stevenroose",
"ariard",
"AntoineP",
"ajtowns",
"reardencode",
"moneyball",
"moonsettler",
"Rob1Ham",
"harding",
"sanket1729"
],
"file_path": "static/delvingbitcoin/March_2025/4462_CTV-CSFS-Can-we-reach-consensus-on-a-first-step-towards-covenants-.xml",
"combined_summ_file_path": "static/delvingbitcoin/March_2025/combined_CTV-CSFS-Can-we-reach-consensus-on-a-first-step-towards-covenants-.xml"
},
{
"id": "4497",
"title": "Question about OP_CTV and Non-Recursive Covenants",
"link": "https://delvingbitcoin.org/t/question-about-op-ctv-and-non-recursive-covenants/1517",
"authors": [
"josh"
],
"published_at": "2025-03-12T23:02:27.468000+00:00",
"summary": "- The OP_CTV proposal enhances Bitcoin by preventing recursive covenant creation.\n- It explores committing to transaction output locations without making recursive covenants possible.\n- The initiative might boost Bitcoin's utility, including the potential for native stock issuances.",
"n_threads": 10,
"dev_name": "delvingbitcoin",
"contributors": [
"JeremyRubin",
"ariard",
"ajtowns"
],
"file_path": "static/delvingbitcoin/March_2025/4497_Question-about-OP-CTV-and-Non-Recursive-Covenants.xml",
"combined_summ_file_path": "static/delvingbitcoin/March_2025/combined_Question-about-OP-CTV-and-Non-Recursive-Covenants.xml"
}
],
"today_in_history_posts": [
{
"id": "018732",
"title": "Proposal: Bitcoin Secure Multisig Setup",
"link": "https://gnusha.org/url/https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-April/018732.html",
"authors": [
"Hugo Nguyen"
],
"published_at": "2021-04-05T07:02:45+00:00",
"summary": "- The BSMS BIP proposes a secure, standardized setup for multisig wallets across vendors.\n- It outlines a process involving multiple signers, encryption, and a two-round communication protocol.\n- Encryption options include NO_ENCRYPTION, STANDARD, and EXTENDED, utilizing AES-256-CTR encryption.",
"n_threads": 36,
"dev_name": "bitcoin-dev",
"contributors": [
"Dmitry Petukhov",
"Christopher Allen",
"Craig Raw",
"Robert Spigler",
"Sjors Provoost",
"Erik Aronesty",
"Michael.flaxman",
"Pavol Rusnak",
"Peter D. Gray",
"Salv"
],
"file_path": "static/bitcoin-dev/April_2021/018732_Proposal-Bitcoin-Secure-Multisig-Setup.xml",
"combined_summ_file_path": "static/bitcoin-dev/April_2021/combined_Proposal-Bitcoin-Secure-Multisig-Setup.xml"
},
{
"id": "003005",
"title": "Increase channel-jamming capital requirements by not counting dust HTLCs",
"link": "https://gnusha.org/url/https://lists.linuxfoundation.org/pipermail/lightning-dev/2021-April/003005.html",
"authors": [
"Eugene Siegel"
],
"published_at": "2021-04-23T15:58:18+00:00",
"summary": "- Eugene from Crypt-iQ suggests raising capital requirements to deter channel-jamming attacks.\n- He proposes trimming dust HTLC outputs in commitment transactions to prevent easy jams.\n- This approach allows 483 non-dust HTLCs per side, aiming to limit low-capital attackers.",
"n_threads": 7,
"dev_name": "lightning-dev",
"contributors": [
"Bastien Teinturier",
"M"
],
"file_path": "static/lightning-dev/April_2021/003005_Increase-channel-jamming-capital-requirements-by-not-counting-dust-HTLCs.xml",
"combined_summ_file_path": "static/lightning-dev/April_2021/combined_Increase-channel-jamming-capital-requirements-by-not-counting-dust-HTLCs.xml"
},
{
"id": "62",
"title": "Thoughts on scaling and consensus changes (2023)",
"link": "https://delvingbitcoin.org/t/thoughts-on-scaling-and-consensus-changes-2023/32",
"authors": [
"jamesob"
],
"published_at": "2023-08-16T14:53:52.896000+00:00",
"summary": "- Bitcoin aims for 1 billion weekly users via 50,000 off-chain \"bitcoin banks.\" - Increasing block size is dismissed, focusing on distributed banks and Utreexo for scalability.\n- Layer 2 protocols and tools like OP_VAULT are critical for security and efficiency.",
"n_threads": 5,
"dev_name": "delvingbitcoin",
"contributors": [
"Ajian",
"CubicEarth",
"EthnTuttle",
"jungly",
"melvincarvalho"
],
"file_path": "static/delvingbitcoin/Aug_2023/62_Thoughts-on-scaling-and-consensus-changes-2023-.xml",
"combined_summ_file_path": "static/delvingbitcoin/Aug_2023/combined_Thoughts-on-scaling-and-consensus-changes-2023-.xml"
}
]
}