From: jl2012 <jl2012@xbt•hk>
To: Jonathan Toomim <j@toom•im>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] We can trivially fix quadratic CHECKSIG with a simple soft-fork modifying just SignatureHash()
Date: Tue, 29 Dec 2015 07:55:28 -0500 [thread overview]
Message-ID: <777b112833eb55ae99af8cacaf0e3b5a@xbt.hk> (raw)
In-Reply-To: <77DAE310-204C-4275-A791-4047798FCBFE@toom.im>
What if someone complains? We can't even tell whether a complaint is
legit or just trolling. That's why I think we need some general
consensus rules which is not written in code, but as a social contract.
Breaking those rules would be considered as a hardfork and is allowed
only in exceptional situation.
Jonathan Toomim via bitcoin-dev 於 2015-12-29 07:42 寫到:
> That sounds like a rather unlikely scenario. Unless you have a
> specific reason to suspect that might be the case, I think we don't
> need to worry about it too much. If we announce the intention to
> perform such a soft fork a couple of months before the soft fork
> becomes active, and if nobody complains about it destroying their
> secret stash, then I think that's fair enough and we could proceed.
>
> On Dec 28, 2015, at 11:47 PM, jl2012 via bitcoin-dev
> <bitcoin-dev@lists•linuxfoundation.org> wrote:
>
>> Do we need to consider that someone may have a timelocked big tx, with
>> private key lost?
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
next prev parent reply other threads:[~2015-12-29 12:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-29 5:35 Peter Todd
2015-12-29 7:47 ` jl2012
2015-12-29 12:42 ` Jonathan Toomim
2015-12-29 12:55 ` jl2012 [this message]
2015-12-29 13:00 ` Jonathan Toomim
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=777b112833eb55ae99af8cacaf0e3b5a@xbt.hk \
--to=jl2012@xbt$(echo .)hk \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=j@toom$(echo .)im \
/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