Bitcoin Development Mailing List

Hey all, Thank you for your ardent review and discussion. I have read and processed all emails in

Hi y'all, Mike wrote: > But if we use different parameters sets don't we already loose the

Hi everyone, We will organize a meeting next week to discuss the activation parameters for BIP 119.

Hi waxwing/AdamISZ, On incentives: agreed that "good" only matters if it's an

Hello all, I would appreciate early peer review on two BIP drafts I have published: BUDS (Bitcoin

Hi list, Surfacing an old idea concerning the network-level and the current meddling of block, tx and

Hi Novo, Responses inline: > I'm not sure adding a block height does much to reduce scanning

Thanks Boris! > I just noticed that BIP360 doesn't appear to specify the exact hash function

Hi Erik, We can organize a meeting to discuss the activation parameters and build an activation

Hey Tadge, You're right that OP_CIV would discourage address reuse, but it'd also make life

Hi Russell, thanks for taking a look at the code. In interpreter.cpp the static function

> Clear disclosure of AI assistance as a process note, not a stigma. I agree with you, but I think

Hello everyone, I am thrilled to announce the public release of Penlock! The goal is achieved! If you

Dear bitcoin-dev, I am submitting a draft Bitcoin Improvement Proposal titled “Standardization of On-

I don't see any specific measure that would require specific support from Bitcoin Core, maybe you

Hello devs, Shared new code for bitcoin backbone available on the website (bitcoinbackbone.org).

Hi Erik, > Most nodes could operate on a rolling history validated by occasional, high-value

Presigned transactions are quite real and are used by people, eg for inheritance so you can allow

Hi Poinsot, Thanks for the precision. Yes my wonder is more if you put yourself in the shoes of an

As the original proposer of LNHANCE, let it be known that I still think it's a great direction

Hello Antoine, For a moment I did confuse you, but (at least part of) the response still applies ;)

> I already told you, when I said "known plaintext attack". If you want to put random

Hi Defenwycke, I think this is not a horrible idea, there might be future demand for a pruneable

čt 30. 10. 2025 v 20:35 odesílatel Martin Habovštiak <martin.h...@gmail.com> napsal:

Fine, I ended up looking into it. PR 5247 changed the semantics of STRICTENC policy in late 2014 so

A preemptive response to those who might say that a conservative "tiny_count" of 100 "

Hello everyone, I've been thinking extensively about how we could scale Bitcoin, particularly

when blocks aren't full, fees are negligible, miners aren't sufficiently rewarded, and we

Hi everyone, In accordance with our security disclosure policy, i am sharing today four advisories

Hi everyone, This is a disclosure of a low-severity vulnerability that exists in all bitcoin core