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
|
Return-Path: <luke.durback@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 64A76D3E
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 10 Dec 2015 06:36:48 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-ig0-f172.google.com (mail-ig0-f172.google.com
[209.85.213.172])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 040CF2F
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 10 Dec 2015 06:36:47 +0000 (UTC)
Received: by mail-ig0-f172.google.com with SMTP id ph11so7171373igc.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 09 Dec 2015 22:36:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:cc:content-type;
bh=NgHJ0SHXt0YO6S0IZjgk/Jg7e08bX8Tj2Xq0Pdypocs=;
b=EZv/QTzg+qUPWLbpL/ZGKv/KQ9redNK/hVDl7Gkm7UziSaiZXINPcxqYmlsFaQFyru
VavIp44u79BPfGmE7AZaFfL7yDqXgywfw8/zacIyW1acLiA6BU93ODqq9Ne1f3+RW6sF
m8S6+bp2efqO11iL3wt+0NSsejVQBEitpDNN5nGTsmpRAhTH3xUa8kFqlIu1uecAu3/i
wVwbFzFtyShu2QuF2g5XGuvjBHMlctannAST+rfvEHk+CAS9HfKQDRnZ9D/zuACwCcXl
vLS3iU/mXlg+aW7R2x6I3Ft+JY3c4teZG1xY7jwO2KwY17/aXv4RXjmy+MGOuSPwZ89u
XQKQ==
X-Received: by 10.50.7.9 with SMTP id f9mr32458135iga.6.1449729407472; Wed, 09
Dec 2015 22:36:47 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.12.177 with HTTP; Wed, 9 Dec 2015 22:36:28 -0800 (PST)
In-Reply-To: <CABm2gDq3K2uUWx_itZQJH53EFOJKAWOLiy3NdHWGPvUOCm33wA@mail.gmail.com>
References: <CAEj3M+wYicoACcpG5YUU6vF8vg98XCcJWmgBiyrJj-xHHxrhig@mail.gmail.com>
<CABm2gDq3K2uUWx_itZQJH53EFOJKAWOLiy3NdHWGPvUOCm33wA@mail.gmail.com>
From: Luke Durback <luke.durback@gmail.com>
Date: Thu, 10 Dec 2015 01:36:28 -0500
Message-ID: <CAEj3M+ze9HU1KWoWT2nugw9hYY97jk_xsL8WUWqThq_wrXSAVg@mail.gmail.com>
To: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
Content-Type: multipart/alternative; boundary=089e011836345a5c800526856e73
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,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
X-Mailman-Approved-At: Thu, 10 Dec 2015 06:59:57 +0000
Cc: Bitcoin development mailing list <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: Thu, 10 Dec 2015 06:36:48 -0000
--089e011836345a5c800526856e73
Content-Type: text/plain; charset=UTF-8
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.
IMO, if you write a complicated system of scripts that's used frequently,
it makes sense to charge a fee for its usage. A decentralized exchange
between colored coins, for instance might take a small fee on each trade.
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?
--089e011836345a5c800526856e73
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><p dir=3D"ltr">Tomorrow, I'll work on writing a way to=
do voting on proposals with BTC used as voting shares (This will be diffic=
ult as I do not know FORTH).=C2=A0 That seems like a fairly simple, useful =
example that will require loops and reused functions.=C2=A0 I'll add a =
fee that goes to the creator.</p><p>IMO, if you write a complicated system =
of scripts that's used frequently, it makes sense to charge a fee for i=
ts usage.=C2=A0 A decentralized exchange between colored coins, for instanc=
e might take a small fee on each trade.</p>
<div style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-co=
lor:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><p dir=3D"lt=
r"><br>
On Dec 10, 2015 10:10 AM, "Luke Durback via bitcoin-dev" <<a h=
ref=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">bitc=
oin-dev@lists.linuxfoundation.org</a>> wrote:<br>
> This, combined with the ability to make new transactions arbitrarily w=
ould allow a function to pay its creator.</p>
<p dir=3D"ltr">I don't understand what you mean by "a function&quo=
t; in this context, I assume you mean a scriptSig, but then "paying it=
s creator" doesn't make much sense to me .</p>
<p dir=3D"ltr">Could you provide some high level examples of the use cases =
you would like to support with this?</p>
</div>
</div>
--089e011836345a5c800526856e73--
|
