Bitcoin Development Mailing List

> The only question left for this technique is a cryptography one: > Is it possible to create

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.

Bitcoin Core version 28.1 is now available from: <https://bitcoincore.org/bin/bitcoin-core-28.1

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

Hi List, There have been complaints voiced about being too paiful to work with CTV. Especially when

Hi conduition, > For P2PK, the solution there seems deadly obvious: Just don't use raw

Okay, that sounds like a simple and clever approach without the need for a hard fork. On Thursday,

Binaries for Bitcoin Core version v28.1rc2 are available from: https://bitcoincore.org/bin/bitcoin-

We made many changes, improvements, and cleanups to our BIP draft since our first announcement to

Dear John, Thank you for the write up. To further explore this idea, did you consider the idea of

Some contributions of my own to add to this conversation. FALCON wasn't approved by NIST because

On 2024-12-10 (Tue) at 10:51:38 +1030, Rusty Russell wrote: > Brandon Black <freedom@

Hi AJ, On 2024-12-11 (Wed) at 23:28:42 +1000, Anthony Towns wrote: > On Mon, Dec 09, 2024 at 12:45

Hey y'all, After going through the review comments following my prior email from September and

Hi Eric, Going back to this thread with a bit of delay... tl;dr: See specifically comment on the lack

Hi all, I'm writing a report to disclose a new transaction-relay jamming attack affecting bitcoin

Binaries for Bitcoin Core version v28.1rc1 are available from: https://bitcoincore.org/bin/bitcoin-

Great point, for the most part I agree with this analysis around difficulty applying this to vaults

> If I'm understanding correctly, the trick is about proving that y(y1 = y2) both in Big

Slashing covenants is a protocol for covenants in Bitcoin via incentives. A covenant is a set of

Dear List, Can anyone think of a reason to keep OP_CHECKSIGFROMSTACKVERIFY as NOP5 available in

Hi everyone, As part of my investigation in the Consensus Cleanup proposal [0] i suggested we include

Hi Ali, For the process of compiling Windows on the ARM instruction set architecture it's about

On 2024-11-19 (Tue) at 16:38:21 +0000, moonsettler wrote: > I think we should discuss back-porting

Using Collider Script or Functional Encryption you can do introspection on Bitcoin today, ie, without

Hi All, We propose to add a new opcode to tapscript, the newest member of the LNhance opcode family,