From: Luke Dashjr <luke@dashjr•org>
To: Johnson Lau <jl2012@xbt•hk>
Cc: bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP141 segwit consensus rule update: extension of witness program definition
Date: Wed, 8 Jun 2016 16:45:10 +0000 [thread overview]
Message-ID: <201606081645.12598.luke@dashjr.org> (raw)
In-Reply-To: <D192E876-1A4F-4B06-86F6-54F1BDEC857D@xbt.hk>
On Wednesday, June 08, 2016 8:23:51 AM Johnson Lau wrote:
> If someday 32 bytes hash is deemed to be unsafe, the txid would also be
> unsafe and a hard fork might be needed. Therefore, I don’t see how a
> witness program larger than 40 bytes would be useful in any case (as it is
> more expensive and takes more UTXO space). I think Pieter doesn’t want to
> make it unnecessarily lenient.
There is no harm in being lenient, but it limits the ability to do softfork
upgrades in the future. I appreciate Pieter's concern that we'd need to do
more development and testing to go to this extreme, which is why I am only
asking the limit raised to 75 bytes.
Luke
next prev parent reply other threads:[~2016-06-08 16:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 5:57 Johnson Lau
2016-06-08 7:29 ` Luke Dashjr
2016-06-08 8:23 ` Johnson Lau
2016-06-08 16:45 ` Luke Dashjr [this message]
2016-06-12 14:40 ` Pieter Wuille
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=201606081645.12598.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=jl2012@xbt$(echo .)hk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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