From: Robin Linus <robinlinus@protonmail.com>
To: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Coins: A trustless sidechain protocol
Date: Sat, 18 Jan 2020 08:21:36 +0000 [thread overview]
Message-ID: <nFmYwRlcPEVdyxh35Rn8WgbP15JKjj9TqMss3nFXohUDH_YHOhTVfnmyjMGojZWaTHJV9HiGzw8KoGYi3pDz5Ne0FaBIEfnstPfUsW1fqr0=@protonmail.com> (raw)
In-Reply-To: <lUnYaQ3Ubk82XnFs9TFXpsjzPGqS7jAGWJNIqOPKmchkAGANZ5JmrErRs_29HVNdm_KlMXuP6l45TYBglItGDZ1Szefz7FazxuBG52lOprQ=@protonmail.com>
Goog morning ZmnSCPxj,
> Unless of course you propose to have the sidechain issue its own coin, in which case it is not much more than an altcoin.
Okay, call it an altcoin consensus mechanism. Because sidechains do have to issue their own coins.
Still, I am not proposing independent altcoins. Bitcoin is the only unit of account. I am proposing bitcoin derivatives only as means of bitcoin transfer. Think of gold vs cash.
> Still, the real-world value of the total block rewards for that altcoin will have to match the real-world value of the total block rewards of Bitcoin in order to have security even approaching Bitcoin.
My point is that, assuming equal rewards, PoW and bitcoin-backed PoS do offer the same level of security.
So in theory, you are right. In practice, a sidechain does not need to be as secure as bitcoin. It requires only a sufficient user base.
Thanks again for your detailed answer,
-Robin
prev parent reply other threads:[~2020-01-18 8:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-12 18:54 [bitcoin-dev] Coins: A trustless sidechain protocol Robin Linus
2020-01-13 0:21 ` ZmnSCPxj
2020-01-13 2:02 ` Robin Linus
2020-01-13 2:33 ` ZmnSCPxj
2020-01-13 17:34 ` Joachim Strömbergson
2020-01-13 22:05 ` Jeremy
2020-01-16 1:21 ` Angel Leon
2020-01-13 18:06 ` Joachim Strömbergson
2020-01-13 19:47 ` Robin Linus
2020-01-13 20:49 ` Joachim Strömbergson
2020-01-13 22:22 ` Robin Linus
2020-01-14 0:53 ` ZmnSCPxj
2020-01-14 2:19 ` Robin Linus
2020-01-14 2:59 ` ZmnSCPxj
2020-01-14 4:12 ` Robin Linus
2020-01-14 15:06 ` Joachim Strömbergson
2020-01-14 15:26 ` ZmnSCPxj
2020-01-15 1:43 ` Robin Linus
2020-01-15 5:46 ` ZmnSCPxj
2020-01-17 4:17 ` Robin Linus
2020-01-17 13:54 ` ZmnSCPxj
2020-01-18 8:21 ` Robin Linus [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='nFmYwRlcPEVdyxh35Rn8WgbP15JKjj9TqMss3nFXohUDH_YHOhTVfnmyjMGojZWaTHJV9HiGzw8KoGYi3pDz5Ne0FaBIEfnstPfUsW1fqr0=@protonmail.com' \
--to=robinlinus@protonmail.com \
--cc=ZmnSCPxj@protonmail.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