1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
|
Return-Path: <jtimon@jtimon.cc>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 49507D74
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 11 Dec 2015 15:36:50 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-vk0-f44.google.com (mail-vk0-f44.google.com
[209.85.213.44])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 854AE144
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 11 Dec 2015 15:36:49 +0000 (UTC)
Received: by vkha189 with SMTP id a189so117757370vkh.2
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 11 Dec 2015 07:36:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=jtimon-cc.20150623.gappssmtp.com; s=20150623;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type;
bh=JMYykT73ZTaJZ/ApIeNJ/bE2+D46rzKWUki/DRdv8yw=;
b=esamduweC2ELAsRb6AuGyf2XfRMR9v2NiR3Uc4tpHnWTm2i4yGtORKv99fqv8S2fyJ
qF7z9Vt5zQacBfn2wUocEniXBpEn4CFmTpt/f5CSg7Vki5sXP83EZTMHYSfa634EQYeb
f3m0QbUzhOeS+IGrtkUFoXO/0N2mmTmWlGJdkym/C4f3zx9K8a24/cbrYSwkxonao+IU
hr6OLGFG1VnUlfyeBWisfunrOhgnbFFE+yhq+slwTDMBS4c54r5hhq+a9yZ62mSnTj8B
DdBb5CckV9lN2b5t7scwyLN88aayRuBsULrzNqf2eFIdC06bBtQGJdvm0ohvPiMQ/OWo
KyuA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:date
:message-id:subject:from:to:cc:content-type;
bh=JMYykT73ZTaJZ/ApIeNJ/bE2+D46rzKWUki/DRdv8yw=;
b=WJ2ZNTPoEXvWIBA0IvhSusqAB2Hxu6WSIKne+lcNbioGiwpSUzbcaqHTahRRsY4Ib0
mII/BF5aeai20g6cGcFX6cGjq1M3UJxDtHQpVZyNzrhi64HoHvColhUiO9NbAa3MSprf
4bhPF7Z1uGC3s6w3UMNVkhpuGCqeESn7nFjqGKs1GEREbZ14Bzs3jT9YeDXrxmN4d2/k
c3WegyQmUagHZ6CKyIaQiPDHA58inudyzztrd4LiF5Fgc4W8RxGher7jX1x0xFHSSXUK
mo09quyos+X8pHpxi5W3YKM4GG0IQrZuiU3P3AowajCMg3NhKPG+D2iFoDdoAu4ky9K5
QhqA==
X-Gm-Message-State: ALoCoQm+6SEggZ9KtG/GnBW37qKGg6uPAjwA8VHtLxFlQZRVgBpqyXrnoD29KUVSBl0Wfmplrtb4O64dytUnLdHlYmoru4TDSQ==
MIME-Version: 1.0
X-Received: by 10.31.169.137 with SMTP id s131mr14919200vke.144.1449848208738;
Fri, 11 Dec 2015 07:36:48 -0800 (PST)
Received: by 10.31.236.70 with HTTP; Fri, 11 Dec 2015 07:36:48 -0800 (PST)
Received: by 10.31.236.70 with HTTP; Fri, 11 Dec 2015 07:36:48 -0800 (PST)
In-Reply-To: <CAEj3M+ze9HU1KWoWT2nugw9hYY97jk_xsL8WUWqThq_wrXSAVg@mail.gmail.com>
References: <CAEj3M+wYicoACcpG5YUU6vF8vg98XCcJWmgBiyrJj-xHHxrhig@mail.gmail.com>
<CABm2gDq3K2uUWx_itZQJH53EFOJKAWOLiy3NdHWGPvUOCm33wA@mail.gmail.com>
<CAEj3M+ze9HU1KWoWT2nugw9hYY97jk_xsL8WUWqThq_wrXSAVg@mail.gmail.com>
Date: Fri, 11 Dec 2015 16:36:48 +0100
Message-ID: <CABm2gDr5rKNMerPebJ6b3ayJznEAAvu_zM76syooH-3MepSzXg@mail.gmail.com>
From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
To: Luke Durback <luke.durback@gmail.com>
Content-Type: multipart/alternative; boundary=001a11425bf0760b8c0526a11794
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Standard BIP Draft: Turing Pseudo-Completeness
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Dec 2015 15:36:50 -0000
--001a11425bf0760b8c0526a11794
Content-Type: text/plain; charset=UTF-8
On Dec 10, 2015 7:36 AM, "Luke Durback" <luke.durback@gmail.com> wrote:
>
> Tomorrow, I'll work on writing a way to do voting on proposals with BTC
used as voting shares (This will be difficult as I do not know FORTH).
That seems like a fairly simple, useful example that will require loops and
reused functions. I'll add a fee that goes to the creator.
If it's voting for something consensus, you will need something special. If
it's not consensus (ie external) thw voting doesn't have to hit the chain
at all.
I don't see how "loops and reused functions" are needed in the scripting
language for this use case, but I'm probably missing some details. Please,
the more concrete you make your example, the easiest it will be for me to
understand.
> IMO, if you write a complicated system of scripts that's used frequently,
it makes sense to charge a fee for its usage.
But each scriptSig is only executed once with its corresponding
scriptPubKey. Are you proposing we change that?
> A decentralized exchange between colored coins, for instance might take
a small fee on each trade.
I've been researching the topic of decentralized exchange from before the
term "colored coins" was first used (now there's multiple designs and
implementations); contributed to and reviewed many designs: none of them
(colored coins or not) required turing completeness.
I'm sorry, but what you are saying here is too vague for me to concretely
be able to refute the low level "needs" you claim your use cases to have.
> On Dec 10, 2015 10:10 AM, "Luke Durback via bitcoin-dev" <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> > This, combined with the ability to make new transactions arbitrarily
would allow a function to pay its creator.
>
> I don't understand what you mean by "a function" in this context, I
assume you mean a scriptSig, but then "paying its creator" doesn't make
much sense to me .
>
> Could you provide some high level examples of the use cases you would
like to support with this?
--001a11425bf0760b8c0526a11794
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<p dir=3D"ltr"><br>
On Dec 10, 2015 7:36 AM, "Luke Durback" <<a href=3D"mailto:luk=
e.durback@gmail.com">luke.durback@gmail.com</a>> wrote:<br>
><br>
> Tomorrow, I'll work on writing a way to do voting on proposals wit=
h BTC used as voting shares (This will be difficult as I do not know FORTH)=
.=C2=A0 That seems like a fairly simple, useful example that will require l=
oops and reused functions.=C2=A0 I'll add a fee that goes to the creato=
r.</p>
<p dir=3D"ltr">If it's voting for something consensus, you will need so=
mething special. If it's not consensus (ie external) thw voting doesn&#=
39;t have to hit the chain at all.<br>
I don't see how "loops and reused functions" are needed in th=
e scripting language for this use case, but I'm probably missing some d=
etails. Please, the more concrete you make your example, the easiest it wil=
l be for me to understand.</p>
<p dir=3D"ltr">> IMO, if you write a complicated system of scripts that&=
#39;s used frequently, it makes sense to charge a fee for its usage.</p>
<p dir=3D"ltr">But each scriptSig is only executed once with its correspond=
ing scriptPubKey. Are you proposing we change that?</p>
<p dir=3D"ltr">>=C2=A0 A decentralized exchange between colored coins, f=
or instance might take a small fee on each trade.</p>
<p dir=3D"ltr">I've been researching the topic of decentralized exchang=
e from before the term "colored coins" was first used (now there&=
#39;s multiple designs and implementations); contributed to and reviewed ma=
ny designs: none of them (colored coins or not) required turing completenes=
s.<br>
I'm sorry, but what you are saying here is too vague for me to concrete=
ly be able to refute the low level "needs" you claim your use cas=
es to have.<br></p>
<p dir=3D"ltr">> On Dec 10, 2015 10:10 AM, "Luke Durback via bitcoi=
n-dev" <<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bi=
tcoin-dev@lists.linuxfoundation.org</a>> wrote:<br>
> > This, combined with the ability to make new transactions arbitrar=
ily would allow a function to pay its creator.<br>
><br>
> I don't understand what you mean by "a function" in this=
context, I assume you mean a scriptSig, but then "paying its creator&=
quot; doesn't make much sense to me .<br>
><br>
> Could you provide some high level examples of the use cases you would =
like to support with this?</p>
--001a11425bf0760b8c0526a11794--
|
