From: Gregory Maxwell <greg@xiph.org>
To: Praveen Baratam <praveen.baratam@gmail.com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Why SegWit Anyway?
Date: Mon, 20 Nov 2017 18:59:34 +0000 [thread overview]
Message-ID: <CAAS2fgSX9XKtwzJ9z5SLJGQHHv+4jUDCKHpcb7V8XEhFuxL=Nw@mail.gmail.com> (raw)
In-Reply-To: <CAAQs3wuDPktHc6kiZXqTaatOheX4KP=TRgje0_-ED5h8iNs-MA@mail.gmail.com>
On Mon, Nov 20, 2017 at 5:24 PM, Praveen Baratam via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> Bitcoin Noob here. Please forgive my ignorance.
>
> From what I understand, in SegWit, the transaction needs to be serialized
> into a data structure that is different from the current one where
> signatures are separated from the rest of the transaction data.
>
> Why change the format at all? Why cant we just compute the Transaction ID
> the same way the hash for signing the transaction is computed?
That is effectively what segwit does, upto engineering minutia and
compatibility details.
Segwit does not serialize transactions in to a data structure where
signatures are separated from the rest of the transaction data; this
is a misunderstanding. The "segregated" refers to them being excluded
from the TXID. The serialization of segwit on the p2p network in
transactions and in blocks encodes the witness field inside the
transactions, immediately prior to the nlocktime field.
prev parent reply other threads:[~2017-11-20 18:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 17:24 [bitcoin-dev] Why SegWit Anyway? Praveen Baratam
2017-11-20 17:39 ` Ariel Lorenzo-Luaces
2017-11-20 17:45 ` Johnson Lau
[not found] ` <CAAUFj10ZRQrtEzB_2wp-WS8Q-FGcSegpc_Z6kqvqnDLzNn=DrA@mail.gmail.com>
[not found] ` <CAAUFj11_Vh2K4MrmuBre5KaX6F16Jg3PYAsj6SSfzoYYRz_WyA@mail.gmail.com>
2017-11-20 18:04 ` Dan Bryant
2017-11-21 13:10 ` Steve Shadders
2017-11-21 13:16 ` Adán Sánchez de Pedro Crespo
2017-11-25 15:41 ` CANNON
2017-11-20 18:07 ` Praveen Baratam
2017-11-20 19:58 ` Johnson Lau
2017-11-20 18:59 ` Gregory Maxwell [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAAS2fgSX9XKtwzJ9z5SLJGQHHv+4jUDCKHpcb7V8XEhFuxL=Nw@mail.gmail.com' \
--to=greg@xiph.org \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=praveen.baratam@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox