public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
* [bitcoin-dev] fork types (Re: An implementation of BIP102 as a softfork.)
@ 2015-12-30 23:05 Adam Back
  2015-12-30 23:10 ` Bryan Bishop
  0 siblings, 1 reply; 2+ messages in thread
From: Adam Back @ 2015-12-30 23:05 UTC (permalink / raw)
  To: Marcel Jamin; +Cc: bitcoin-dev

> 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>:


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2015-12-30 23:10 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-12-30 23:05 [bitcoin-dev] fork types (Re: An implementation of BIP102 as a softfork.) Adam Back
2015-12-30 23:10 ` Bryan Bishop

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox