From: Justus Ranvier <justus@openbitcoinprivacyproject•org>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Compatibility requirements for hard or soft forks
Date: Sun, 1 Nov 2015 08:36:35 -0600 [thread overview]
Message-ID: <56362373.9080105@openbitcoinprivacyproject.org> (raw)
In-Reply-To: <8737wrwvn2.fsf@rustcorp.com.au>
[-- Attachment #1.1: Type: text/plain, Size: 732 bytes --]
On 10/30/2015 10:43 PM, Rusty Russell via bitcoin-dev wrote:
> By that benchmark, we should aim for "reasonable certainty". A
> transaction which would never have been generated by any known software
> is the minimum bar. Adding "...which would have to be deliberately
> stupid with many redundant OP_CHECKSIG etc" surpasses it. The only extra
> safeguard I can think of is clear, widespread notification of the
> change.
If the policy of Bitcoin Core development includes a willingness to
makes the utxos created by software other than Bitcoin Core unspendable,
then it certainly merits clear, widespread notification.
Even if that is actually a good policy, the reasons why should be made
abundantly clear.
[-- Attachment #1.2: 0xEAD9E623.asc --]
[-- Type: application/pgp-keys, Size: 23699 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2015-11-01 14:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 14:06 Gavin Andresen
2015-10-31 3:43 ` Rusty Russell
2015-11-01 14:36 ` Justus Ranvier [this message]
2015-11-01 17:28 ` jl2012
2015-11-01 23:46 ` Tier Nolan
2015-11-02 0:23 ` Justus Ranvier
2015-11-02 0:33 ` Luke Dashjr
2015-11-02 1:30 ` Tier Nolan
2015-11-02 4:15 ` Justus Ranvier
2015-11-02 6:12 ` Justus Ranvier
2015-11-02 20:33 ` Gavin Andresen
2015-11-02 22:12 ` Justus Ranvier
2015-11-03 5:32 ` jl2012
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=56362373.9080105@openbitcoinprivacyproject.org \
--to=justus@openbitcoinprivacyproject$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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