From: Chris Priest <cp368202@ohiou.edu>
To: Peter Todd <pete@petertodd.org>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Segregated witness softfork with moderate adoption has very small block size effect
Date: Sat, 19 Dec 2015 19:37:26 -0800 [thread overview]
Message-ID: <CAAcC9yvBQj=UtbcmnSpMvmwaaRd1ftfg2VLq3JuU2wmp9Vah=Q@mail.gmail.com> (raw)
In-Reply-To: <20151219174309.GB30640@muck>
By that same logic, any wallet that implemented P2SH is also voting
for an increased block size, since P2SH results in smaller
transactions, in the same way SW results in smaller transactions.
On 12/19/15, Peter Todd via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> On Sat, Dec 19, 2015 at 11:49:25AM -0500, jl2012 via bitcoin-dev wrote:
>> I have done some calculation for the effect of a SW softfork on the
>> actual total block size.
>
> Note how the fact that segwit needs client-side adoption to enable an
> actual blocksize increase can be a good thing: it's a clear sign that
> the ecosystem as a whole has opted-into a blocksize increase.
>
> Not as good as a direct proof-of-stake vote, and somewhat coercive as a
> vote as you pay lower fees, but it's an interesting side-effect.
>
> --
> 'peter'[:-1]@petertodd.org
> 00000000000000000188b6321da7feae60d74c7b0becbdab3b1a0bd57f10947d
>
next prev parent reply other threads:[~2015-12-20 3:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-19 16:49 [bitcoin-dev] Segregated witness softfork with moderate adoption has very small block size effect jl2012
2015-12-19 17:43 ` Peter Todd
2015-12-19 18:37 ` Santino Napolitano
2015-12-19 18:48 ` Peter Todd
2015-12-20 3:37 ` Chris Priest [this message]
2015-12-19 17:55 ` Justus Ranvier
2015-12-20 1:19 ` Douglas Roark
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='CAAcC9yvBQj=UtbcmnSpMvmwaaRd1ftfg2VLq3JuU2wmp9Vah=Q@mail.gmail.com' \
--to=cp368202@ohiou.edu \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=pete@petertodd.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