From: Ariel Lorenzo-Luaces <arielluaces@gmail•com>
To: ZmnSCPxj <zmnscpxj@protonmail.com>,bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Smart Contracts Unchained
Date: Wed, 03 Apr 2019 20:37:47 -0700 [thread overview]
Message-ID: <77b8f255-8f70-431e-839c-b99361d1dac7@gmail.com> (raw)
In-Reply-To: <IAFPSZAn6TYt348fmmnPznQ_ApG7pa48eMjzTgrjuVAt6fS1tNieRxlcIXyTATy2vjZCUn4wVQcsyDlyb_3Ip46BstFRikB95-lKewAZBEE=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 1404 bytes --]
Hello ZmnSCPxj
I like the proposal because it generalizes escrow type mechanisms and I think it's a useful train of thought for distributed exchanges.
However, consider the situation where a group of participants are playing poker. One participant loses all their funds and decides to present to the escrow the contract+an old contract state+a signed message following the contract rules (eg. an independently signed cashing out message). How would the escrow know that the contract state is old and the operation is disallowed, without using a consensus mechanism like a blockchain?
Cheers
Ariel Lorenzo-Luaces
On Apr 3, 2019, 7:14 PM, at 7:14 PM, ZmnSCPxj via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
>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
[-- Attachment #2: Type: text/html, Size: 1936 bytes --]
next prev parent reply other threads:[~2019-04-04 3:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 1:55 ZmnSCPxj
2019-04-04 2:35 ` Tamas Blummer
2019-04-04 3:37 ` Ariel Lorenzo-Luaces [this message]
2019-04-04 7:07 ` ZmnSCPxj
2019-04-04 15:03 ` ZmnSCPxj
2019-04-04 17:18 ` Aymeric Vitte
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=77b8f255-8f70-431e-839c-b99361d1dac7@gmail.com \
--to=arielluaces@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=zmnscpxj@protonmail$(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