Bitcoin Development Mailing List

It seems you are right. However, this rule is based on block timestamps, which gives me another idea:

Dear colleagues, BIP3 got merged as Draft on the 20th of February and got one more minor update since

Stack elements in Taproot are limited to 520 bytes. The current proposal for re-activating OP_CAT

Hi All, > You could have CTV commit to two inputs, with the second input's entire > value

If your threat model assumes an attacker can promptly recover the private key from the public key

Hi Weikeng, I'm obviously not opposed to the idea, just not sure what makes one signet more

> Op 17 mrt 2025, om 13:00 heeft Matt Corallo <lf-l...@mattcorallo.com> het volgende

út 18. 3. 2025 v 0:12 odesílatel Olaoluwa Osuntokun <lao...@gmail.com> napsal: > One of the

I wonder, why OP used so much of AI-generated content to make these posts. > What if miners claim

P2TRH doesn't protect against short exposure attacks. Matt Corallo's approach basically

One major issue with a mandatory transition to quantum-resistant addresses that I haven't seen

Bitcoin Knots version 28.1.knots20250305 is now available from: https://bitcoinknots.org/files/28.x/

I opened an issue a while ago on this topic: https://github.com/bitcoin/bitcoin/issues/26113 On

I forgot to add the link for covenants support wiki in last email: https://en.bitcoin.it/wiki/

Hello! I'd like to present to bitcoin-dev an improvement to the BitVMX protocol that enables the

Hi devs, This email is a digest of the ongoing work to improve the transaction-relay protocol among

Hi, good idea and a nice crate! You'll hear from me soon regarding the Rust side on your issue

On Tuesday, February 18th, 2025 at 10:22 AM, John <csdark...@gmail.com> wrote: > Hi

Hi Bitcoin Developers, Pythcoiner had recently [tweeted][0] about the rust implementation of joinstr.

On Thu, 13 Feb 2025 at 15:53, AdamISZ <Ada...@protonmail.com> wrote: > Is there an easy

On Fri, Jan 31, 2025 at 12:02:56PM +0000, 'ArmchairCryptologist' via Bitcoin Development

Hi Greg, On 2025-01-31 08:43, Greg Tonoski wrote: > I agree that -incrementalrelayfee=0 (or

correct, it's an "all full node vaidates" and not "trust miners only" the

> Do I understand correctly that this attack only applies if Alice > attempts to fee bump her

This is a BIP Draft for an unspendable key expression that can be used as the taproot internal key.

BIP375 Sending Silent Payments with PSBTs uses PSBTv2, specifically the PSBT_OUT_SCRIPT field. For

Hi Floppy, As I mentioned before, I believe it's a mistake to structure the table this way.

Any timestamp data that is added to a transaction is not trustworthy, including nLockTime. This

FALCON failed the NIST vetting. Since 2022 they have said they will fix it next year. Same answer in

thanks floppy disk guy, i updated this example with the correct way a single 1c1p spend with no p2a