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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <watsonbladd@gmail.com>) id 1S3Ybe-0004Bp-27
for bitcoin-development@lists.sourceforge.net;
Fri, 02 Mar 2012 19:57:34 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.160.47 as permitted sender)
client-ip=209.85.160.47; envelope-from=watsonbladd@gmail.com;
helo=mail-pw0-f47.google.com;
Received: from mail-pw0-f47.google.com ([209.85.160.47])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1S3Ybd-0003qi-EJ
for bitcoin-development@lists.sourceforge.net;
Fri, 02 Mar 2012 19:57:34 +0000
Received: by pbbrp12 with SMTP id rp12so2513852pbb.34
for <bitcoin-development@lists.sourceforge.net>;
Fri, 02 Mar 2012 11:57:27 -0800 (PST)
Received-SPF: pass (google.com: domain of watsonbladd@gmail.com designates
10.68.229.104 as permitted sender) client-ip=10.68.229.104;
Authentication-Results: mr.google.com;
spf=pass (google.com: domain of watsonbladd@gmail.com
designates 10.68.229.104 as permitted sender)
smtp.mail=watsonbladd@gmail.com;
dkim=pass header.i=watsonbladd@gmail.com
Received: from mr.google.com ([10.68.229.104])
by 10.68.229.104 with SMTP id sp8mr20260396pbc.8.1330718247662
(num_hops = 1); Fri, 02 Mar 2012 11:57:27 -0800 (PST)
MIME-Version: 1.0
Received: by 10.68.229.104 with SMTP id sp8mr16925861pbc.8.1330718247612; Fri,
02 Mar 2012 11:57:27 -0800 (PST)
Sender: watsonbladd@gmail.com
Received: by 10.142.153.8 with HTTP; Fri, 2 Mar 2012 11:57:27 -0800 (PST)
In-Reply-To: <CACsn0c=P1veYnmXe4E3qU0OC=Xr9Aw6Fy=6Zm0sUAaSBEDvpMA@mail.gmail.com>
References: <CACsn0c=P1veYnmXe4E3qU0OC=Xr9Aw6Fy=6Zm0sUAaSBEDvpMA@mail.gmail.com>
Date: Fri, 2 Mar 2012 13:57:27 -0600
X-Google-Sender-Auth: WsOh7ikiLht0324reS3ztfSIT9k
Message-ID: <CACsn0cne5An+SyKDf9w4o4Secn7C9wqqbG7ff0HB3Dvk-XxHRg@mail.gmail.com>
From: Watson Ladd <wbl@uchicago.edu>
To: bitcoin-development@lists.sourceforge.net
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.5 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(watsonbladd[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1S3Ybd-0003qi-EJ
Subject: [Bitcoin-development] Fwd: Proposal for a new opcode
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2012 19:57:34 -0000
Dear all,
I am proposing a new opcode for the purposes of anonymous
transactions. This new opcode enables scripts to be given proof that
the receiver can carry out or has carried out a previous transaction.
I'm currently working on a paper that discusses using this opcode for
anonymous transactions.
Name: OP_CHECKEXPSIG
Stack before: <sig><pk><hash>
Stack after: T/F, where is true if sig is a ECDSA signature under pk
for the hash hash. (Hash is the hash of a message).
Uses: Preexisting digital cash techniques relied on keeping track of a
list of turned in notes to forbid double spending. Using
OP_CHECKEXPSIG we can instead pass the script that gives the nth note
value proof that the notes {1,...n-1} were turned in and are distinct.
This enables a coupling of the strong double spend protection of
Bitcoin with traditional digital cash's strong anonymity.
Sincerely,
Watson Ladd
|
