From: Tier Nolan <tier.nolan@gmail•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP CPRKV: Check private key verify
Date: Thu, 11 Feb 2016 23:04:37 +0000 [thread overview]
Message-ID: <CAE-z3OU1UR1BY0Z++ZdkaLV+t9ygJm7OhaowQr2ksQHf0h_4=A@mail.gmail.com> (raw)
In-Reply-To: <CAHv+tb7CMEpR9hLp6pJE9Nt=j5zvChNr1CvDXn8Pb-d2sRZSEA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1231 bytes --]
On Thu, Feb 11, 2016 at 10:20 PM, Thomas Kerin <thomas.kerin@gmail•com>
wrote:
> I wonder if this is possible as a soft fork without using segwit?
Increasing the sigop count for a NOP would be a hard fork, but such a
change would be fine with a new segwit version. It might require specific
support in the altcoin, which might be troublesome..
It is a soft fork since it makes things that were previous allowed
disallowed. If it decreased the sigop count, then you could create a block
that had to many sigops due to the old rules.
With this rule, it increases the count. If the sigop count is valid under
the new rules, it is also valid under the old rules.
There is no need for specific support on the altcoin. It allows the
Bitcoin network act as trusted 3rd party so that you can do channels safely
on the altcoin, even though the altcoin still suffers from malleability and
doesn't have OP_CHECKLOCKTIMEVERIFY.
With regards to seg-witness, Ideally, the opcode would work in both old and
new scripts by re-purposing OP_NOP3.
<https://www.avast.com/sig-email> This email has been sent from a
virus-free computer protected by Avast.
www.avast.com <https://www.avast.com/sig-email>
<#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
[-- Attachment #2: Type: text/html, Size: 1952 bytes --]
next prev parent reply other threads:[~2016-02-11 23:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 20:05 Tier Nolan
2016-02-11 22:20 ` Thomas Kerin
2016-02-11 23:04 ` Tier Nolan [this message]
2016-02-12 5:02 ` jl2012
2016-02-12 10:05 ` Tier Nolan
2016-02-29 10:58 ` Mats Jerratsch
2016-02-29 11:52 ` Tier Nolan
2016-04-18 19:03 ` 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='CAE-z3OU1UR1BY0Z++ZdkaLV+t9ygJm7OhaowQr2ksQHf0h_4=A@mail.gmail.com' \
--to=tier.nolan@gmail$(echo .)com \
--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