From: Patrick Sharp <psharp.x13@gmail•com>
To: CryptAxe <cryptaxe@gmail•com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] idea post: bitcoin side chain implementation
Date: Mon, 25 Sep 2017 18:07:12 -0600 [thread overview]
Message-ID: <CAES+R-pHkDHSPpTcyJyEv2rSWOvAkG+zUqs8hPwbHigejyFvDw@mail.gmail.com> (raw)
In-Reply-To: <CAF5CFkheg5U0zPLSq9ow2aFZept8nGN94q894yRjiuvAY5s7Fw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 919 bytes --]
I shamefully was not aware. However familiarized myself with them.
Non official chains suffer from the fact that few if any miners are going
to mine them so they lack security on par with the main chain. And more
over most users aren't going to use them because its not magic.
That being said think they are and will always be a great place to develop
and prove out concepts.
If my ultimate goal is official side chains that include part of the reward
such security is at parity between all chains and that the official
software automatically enable users to distribute their burden, would my
course of action be to build an external proof-of-concept side chain of
side chains?
or do you doubt that official reward splitting chains will ever find their
way into bitcoin core?
On Mon, Sep 25, 2017 at 4:58 PM, CryptAxe <cryptaxe@gmail•com> wrote:
> Have you taken a look at Elements or Drivechains yet by chance?
>
[-- Attachment #2: Type: text/html, Size: 1317 bytes --]
next prev parent reply other threads:[~2017-09-26 0:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 21:53 Patrick Sharp
2017-09-25 22:58 ` CryptAxe
2017-09-26 0:07 ` Patrick Sharp [this message]
2017-09-26 0:35 ` ZmnSCPxj
2017-09-26 1:15 ` Patrick Sharp
2017-09-26 0:01 ` ZmnSCPxj
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=CAES+R-pHkDHSPpTcyJyEv2rSWOvAkG+zUqs8hPwbHigejyFvDw@mail.gmail.com \
--to=psharp.x13@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=cryptaxe@gmail$(echo .)com \
/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