From: Aymeric Vitte <vitteaymeric@gmail.com>
To: ZmnSCPxj <ZmnSCPxj@protonmail.com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Smart Contracts Unchained
Date: Thu, 4 Apr 2019 19:18:30 +0200 [thread overview]
Message-ID: <d1cfa2e9-69e4-ee02-4c10-23b2b1a30e00@gmail.com> (raw)
In-Reply-To: <IAFPSZAn6TYt348fmmnPznQ_ApG7pa48eMjzTgrjuVAt6fS1tNieRxlcIXyTATy2vjZCUn4wVQcsyDlyb_3Ip46BstFRikB95-lKewAZBEE=@protonmail.com>
What if the smart contract platform(s) disappear?
The proposal induces a very centralized system, to my knowledge all of
existing sidechains whether on bitcoin or ethereum are centralized,
except lightning (if we forget that someone must watch what others are
doing when you are on a trek in Nepal)
Now I don't get why a sidechain should be a blockchain on top on another
one (given also that we can't consider bitcoin or ethereum as
decentralized today, so the path might be long for the sidechains...),
the latest is used to store the final state, the former does not have to
store forever the intermediate states, then it could just use a
decentralized system (not necessarilly blockchain-like) to store the
intermediate states and maybe be a distributed escrow
I know, easy to say, please do it (why not), now the fact that
sidechains claim to be decentralized or that they will be is just
misleading people (that's not the case of your proposal but it does not
say what happens if the platforms go down)
Le 04/04/2019 à 03:55, ZmnSCPxj via bitcoin-dev a écrit :
> https://zmnscpxj.github.io/bitcoin/unchained.html
>
> Smart contracts have traditionally been implemented as part of the consensus rules of some blokchain. Often this means creating a new blockchain, or at least a sidechain to an existing blockchain. This writeup proposes an alternative method without launching a separate blockchain or sidechain, while achieving security similar to federated sidechains and additional benefits to privacy and smart-contract-patching.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
--
Peersm : http://www.peersm.com
node-Tor : https://www.github.com/Ayms/node-Tor
GitHub : https://www.github.com/Ayms
next prev parent reply other threads:[~2019-04-04 17:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 1:55 [bitcoin-dev] Smart Contracts Unchained ZmnSCPxj
2019-04-04 2:35 ` Tamas Blummer
2019-04-04 3:37 ` Ariel Lorenzo-Luaces
2019-04-04 7:07 ` ZmnSCPxj
2019-04-04 15:03 ` ZmnSCPxj
2019-04-04 17:18 ` Aymeric Vitte [this message]
2019-04-04 23:52 ` ZmnSCPxj
2019-04-05 17:46 ` Aymeric Vitte
2019-04-08 10:45 ` ZmnSCPxj
2019-04-08 16:28 ` Aymeric Vitte
2019-04-05 6:00 ` ZmnSCPxj
2019-04-17 16:17 ` Nadav Kohen
2019-04-18 5:33 ` 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=d1cfa2e9-69e4-ee02-4c10-23b2b1a30e00@gmail.com \
--to=vitteaymeric@gmail.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