Re: [bitcoin-dev] Adding SIGHASH to TXID

2022-07-03 Thread vjudeu via bitcoin-dev
> Have you seen the inherited ID proposal from John Law on this list? I didn't see that before posting, I'm still trying to get more familiar with that (and with proposals, where every single field in each transaction is controlled for inclusion or exclusion). > Honestly, I've yet to fully

Re: [bitcoin-dev] Adding SIGHASH to TXID

2022-05-07 Thread Jeremy Rubin via bitcoin-dev
Have you seen the inherited ID proposal from John Law on this list? It's a pretty thorough treatment of this type of proposal, curious if you think it overlaps what you had in mind? Honestly, I've yet to fully load in exactly how the applications of it work, but I'd be interested to hear your

[bitcoin-dev] Adding SIGHASH to TXID

2022-05-07 Thread vjudeu via bitcoin-dev
For now, we have txid:vout as a previous transaction output. This means that to have a stable TXID, we are forced to use SIGHASH_ALL somewhere, just to prevent any transaction modifications that can happen during adding some inputs and outputs. But it seems that new sighashes could be far more