Bitcoin Development Mailing List

Hey Jeremy, While this is certainly an interesting alternative mitigation against some attacks, the

Hi spartacusrex, thanks for raising this point. The current published version of SHRINCS (described

Hi Everyone, I would like to propose a new informational BIP to formally document the Low-R signature

> Including replies from Murch ...where he dipped out after accusing you of being a bot. Your

Hi aj, I want to push back on this framing: > Trying to prevent other people from making different

On Fri, Jun 05, 2026 at 05:54:50PM +1000, Anthony Towns wrote: > On Thu, Jun 04, 2026 at 11:01:

Hi AJ, Thanks for the detailed feedback! Pol and I have coordinated on the main points below and I

Hi Antoine, Conduition, Pieter, and list, I want to share my proposal for EC public key recovery in

Hey guys, > Those not motivated by funds could publish a zero knowledge proof instead of moving

You missed the point. The 2-transaction design is intentional — it's the only approach that

On Mon, Jun 01, 2026 at 02:24:04PM -0700, Murch wrote: > I get the concern that in the case of the

On Fri, Jun 05, 2026 at 07:35:27PM +1000, Anthony Towns wrote: > compared with current mainnet

Rootstock uses SPV proofs to power its Bitcoin SPV node that runs in consensus inside the Bridge

Hello list, This post is a general announcement of 2 updates to BIP127 Simple Proof-of-Reserves

Gosh, what a ton of words have been spilled on this. xD Address re-use has serious privacy

So you'd essentially be computing: e = H(R || hybrid_pk || m) P = e^{-1} * (s*G - R) ie the same

> Can you remind me in what way Ark would benefit from sibling commitments? In all honesty,

> 3's Company HE-SD (High-Entropy Seed Distillation) algorithm Never heard of that. Google

Hello Murch, Thanks for the feedback. I will remove the mediawiki syntax and keep it simple ...

Laolu's OP benchmarks which you cite used a design which was hard to arithmetize, so the proofs

Hey everyone, After directly contacting the BIP52 authors failed, I'm forwarding the following

To make a counter argument to mine, and assuming Bitcoin soft forks are not impossible, FlyClient has

On Wed, May 20, 2026, 9:02 AM Pieter Wuille <bitco...@wuille.net> wrote: Hi Jason, See my

Thanks for the pushback. A few points worth challenging though: The chainwork argument doesn't

Hi Eric, Fair enough. The BIP rationale should discuss explicitly your point that it introduces a

Hi, > Two, Alice and Caroll can always collude to have Bob never getting the HTLC > secret and

Hi AJ, Sorry for the late answer here. > Sending a bunch of FEATURE messages that are immediately

Oopsie, I just saw Laolu's footnote #4 about ignoring isogeny crypto. Guess I should learn to

Hi, This is an interesting class of bug. Escalating a use-after-free into a userspace remote code

Hi waxwing, thank you for your comments. > I'm probably against Recirculation as an idea. If