From: Adam Back <adam@cypherspace•org>
To: Marcel Jamin <marcel@jamin•net>
Cc: bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] fork types (Re: An implementation of BIP102 as a softfork.)
Date: Wed, 30 Dec 2015 23:05:57 +0000 [thread overview]
Message-ID: <CALqxMTF_PundsEawyYcinJHyvJJTN-iK0MjWfzpD7QDN448P1Q@mail.gmail.com> (raw)
> I guess the same could be said about the softfork flavoured SW implementation
No, segregated witness
https://bitcoin.org/en/bitcoin-core/capacity-increases-faq is a
soft-fork maybe loosely similar to P2SH - particularly it is backwards
and forwards compatible by design.
These firm forks have the advantage over hard forks that there is no
left-over weak chain that is at risk of losing money (because it
becomes a consensus rule that old transactions are blocked).
There is also another type of fork a firm hard fork that can do the
same but for format changes that are not possible with a soft-fork.
Extension blocks show a more general backwards and forwards compatible
soft-fork is also possible.
Segregated witness is simpler.
Adam
On 30 December 2015 at 13:57, Marcel Jamin via bitcoin-dev
<bitcoin-dev@lists•linuxfoundation.org> wrote:
> I guess the same could be said about the softfork flavoured SW
> implementation. In any case, the strategy pattern helps with code structure
> in situations like this.
>
> 2015-12-30 14:29 GMT+01:00 Jonathan Toomim via bitcoin-dev
> <bitcoin-dev@lists•linuxfoundation.org>:
next reply other threads:[~2015-12-30 23:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 23:05 Adam Back [this message]
2015-12-30 23:10 ` Bryan Bishop
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=CALqxMTF_PundsEawyYcinJHyvJJTN-iK0MjWfzpD7QDN448P1Q@mail.gmail.com \
--to=adam@cypherspace$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=marcel@jamin$(echo .)net \
/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