From: Tier Nolan <tier.nolan@gmail.com>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] A new payment address format for segregated witness or not?
Date: Mon, 21 Dec 2015 15:48:23 +0000 [thread overview]
Message-ID: <CAE-z3OVV5ozYqj4ziZ8J0-8LAnFd+zhC2HO9OzkPpwZGBsEKxA@mail.gmail.com> (raw)
In-Reply-To: <537b176b25a681255eee5f6c4268ab6e@xbt.hk>
[-- Attachment #1: Type: text/plain, Size: 622 bytes --]
On Mon, Dec 21, 2015 at 5:14 AM, jl2012 via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> The SW in P2SH is worse in terms of:
> 1. It requires an additional push in scriptSig, which is not prunable in
> transmission, and is counted as part of the core block size
>
"Prunable in transmission" means that you have to include it when not
sending the witnesses?
That is a name collision with UTXO set prunable. My initial thought when
reading that was "but scriptSigs are inherently prunable, it is
scriptPubKeys that have to be held in the UTXO database" until I saw the
"in transmission" clarification.
[-- Attachment #2: Type: text/html, Size: 1013 bytes --]
prev parent reply other threads:[~2015-12-21 15:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 5:14 [bitcoin-dev] A new payment address format for segregated witness or not? jl2012
2015-12-21 15:48 ` Tier Nolan [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=CAE-z3OVV5ozYqj4ziZ8J0-8LAnFd+zhC2HO9OzkPpwZGBsEKxA@mail.gmail.com \
--to=tier.nolan@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/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