public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Tier Nolan <tier.nolan@gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Merge of protocol
Date: Wed, 24 Jan 2018 15:02:38 +0000	[thread overview]
Message-ID: <CAE-z3OXJJ=BQhYmjLyq2x8xSwAi5j0cBOvqe3um8_QjV9fSLDA@mail.gmail.com> (raw)
In-Reply-To: <CALTsm7jeqQUhL+REvzBQNUtSMd9i9oVeXEkdCuUuGOpz_V=b8Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2327 bytes --]

If the communities behind two coins wanted to merge, it would be possible,
but difficulty and risky.

It represents a hard fork on both chains.  Not only does each coin's
community need to agree, the two communities need to agree with each other.

They would both have to agree the join point.  The merge block would have 2
parents.


A <- B <- C <- D
                 \
                    J1 <- J2 <- J3 <- J4
                 /
w <- x <- y <- z


In the above example, A, B, C, D is one chain and w, x, y, z is the other.
They combine and then J1, J2, J3, J4 is the combined chain.

Since block "J1" has 2 parents, it commits to the state of the 2 legacy
chains.  If you have coins in each chain at D or z, then you get coins in
the joint chain.

They would both need to agree on what the rules are for their new chain.
Since it is a (double) hard fork, they can do pretty much anything they
want.

The combined chain could continue as before.  It would be a combined chain
and each user's coin total would be unaffected.  The advantage of doing
that is that it causes minimum economic disruption to users.  The mining
power for both chains would be applied to the joint chain, so they combine
their security.

Alternatively, they could agree on an exchange rate.  Users would be given
joint-coins in exchange for their coins on the 2 legacy chains.

For something like Bitcoin Cash and Bitcoin, they could have a
re-combination rule.  1 Bitcoin-Recombined = 1 BTC + 1 BCH.  That doesn't
seem very likely though and also there are more BCH coins than BTC coins.

It might be worth moving this to bitcoin-discuss, since it isn't really
Bitcoin protocol discussion.


Wed, Jan 24, 2018 at 11:56 AM, Ilan Oh via bitcoin-dev <bitcoin-dev@lists.
linuxfoundation.org> wrote:

> 2017 was fork year,
>
> Is it technically possible to merge two protocoles ? And thus bringing the
> strength of both into one resulting coin.
>
> I would not be surprized to see a lot of altcoin wanting to merge with
> bitcoin or between them, especially with LN current development, if it is
> possible,
>
> If anyone has ideas or ressources on this,
>
> Thanks
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>

[-- Attachment #2: Type: text/html, Size: 3825 bytes --]

      reply	other threads:[~2018-01-24 15:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CALTsm7gG6bWJd=HQ5XJTYxWbxNPwZDC6Xefsh_zSAQhk89A4VQ@mail.gmail.com>
     [not found] ` <CALTsm7ir61RCfGSf8r71+soDJH+W9n_dPORS+2+ARKEzhpnXWw@mail.gmail.com>
     [not found]   ` <CALTsm7ii4PZ_of=YPpB2x_nMGGTFrDW8OGOx6LehfyQD22JMYw@mail.gmail.com>
     [not found]     ` <CALTsm7jOPr17d1syFZ9wsYAntcUss+tcrHU_vQKC2TEZ1ong9g@mail.gmail.com>
     [not found]       ` <CALTsm7i=ThDfv2uquHAxvLgQ497oVkYhYF5gNFcv3RxEkDVr5A@mail.gmail.com>
     [not found]         ` <CALTsm7ijaK+fWk9jKUMD0MGqwAeSYwc3XOyGOs8AYZ9AYL_uGA@mail.gmail.com>
2018-01-24 11:56           ` [bitcoin-dev] Merge of protocol Ilan Oh
2018-01-24 15:02             ` Tier Nolan [this message]

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-z3OXJJ=BQhYmjLyq2x8xSwAi5j0cBOvqe3um8_QjV9fSLDA@mail.gmail.com' \
    --to=tier.nolan@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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