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
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <ctpacia@gmail.com>) id 1Wlh9b-00085E-3y
for bitcoin-development@lists.sourceforge.net;
Sat, 17 May 2014 16:08:07 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.192.41 as permitted sender)
client-ip=209.85.192.41; envelope-from=ctpacia@gmail.com;
helo=mail-qg0-f41.google.com;
Received: from mail-qg0-f41.google.com ([209.85.192.41])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Wlh9X-00028O-Dz
for bitcoin-development@lists.sourceforge.net;
Sat, 17 May 2014 16:08:07 +0000
Received: by mail-qg0-f41.google.com with SMTP id j5so6246128qga.14
for <bitcoin-development@lists.sourceforge.net>;
Sat, 17 May 2014 09:07:58 -0700 (PDT)
X-Received: by 10.224.122.211 with SMTP id m19mr11722911qar.6.1400342878010;
Sat, 17 May 2014 09:07:58 -0700 (PDT)
Received: from [192.168.1.4] (pool-72-73-200-73.cmdnnj.east.verizon.net.
[72.73.200.73])
by mx.google.com with ESMTPSA id 20sm7279611qgg.1.2014.05.17.09.07.57
for <bitcoin-development@lists.sourceforge.net>
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Sat, 17 May 2014 09:07:57 -0700 (PDT)
Message-ID: <5377892C.8080402@gmail.com>
Date: Sat, 17 May 2014 12:07:08 -0400
From: Chris Pacia <ctpacia@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
References: <BAY173-W1475F72C70BC089A82C20FCC300@phx.gbl>
In-Reply-To: <BAY173-W1475F72C70BC089A82C20FCC300@phx.gbl>
X-Enigmail-Version: 1.6
Content-Type: multipart/alternative;
boundary="------------080306070809020702080405"
X-Spam-Score: -0.6 (/)
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
(ctpacia[at]gmail.com)
-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
no trust [209.85.192.41 listed in list.dnswl.org]
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
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: 1Wlh9X-00028O-Dz
Subject: Re: [Bitcoin-development] Paper Currency
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: Sat, 17 May 2014 16:08:07 -0000
This is a multi-part message in MIME format.
--------------080306070809020702080405
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Since these notes have to be redeemed immediately the number of use
cases seems limited. I can't really just hand someone the note and walk
away because they have to scan it to see if it is actually valid.
Otherwise someone could just pass fake notes if they felt the recipient
wouldn't redeem them on the spot. This doesn't seem like an improvement
over just sending the coins via phone.
The use case with poor internet connection wouldn't work as well since,
presumably, the recipient would also have poor reception and couldn't
verify the note was actually loaded with bitcoins.
Also, I REALLY don't like the name bit reserve.
-Chris
On 05/17/2014 11:31 AM, Jerry Felix wrote:
> It seems to me that there's a huge need for a paper currency that is
> counterfeit-resistant, inexpensive to print, internationally
> recognized (border-less), fits in a wallet, and machine readable.
>
> I pitched this idea at the Cincinnati Bitcoin meetup last week, and I
> didn't get thrown out, so I took the time to document a proposed
> standard to accomplish this. I've put my ideas into BIP format, so
> that you can see what I have in mind, although I picked some
> BIP numbers myself that seem to be available. Call them "proposed
> proposals", or "provisional BIPs". I've numbered them provisionally
> BIP-80 to BIP-84.
>
> If you guys think that this idea has some merit, let's discuss.
>
> https://github.com/jerfelix/provisional_bips/blob/master/README.mediawiki
>
> Submitted with humility and some fear of getting laughed out of here...
> - Jerry
>
>
>
>
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.
> Get unparalleled scalability from the best Selenium testing platform available
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
>
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
--------------080306070809020702080405
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Since these notes have to be redeemed immediately the number of use
cases seems limited. I can't really just hand someone the note and
walk away because they have to scan it to see if it is actually
valid. Otherwise someone could just pass fake notes if they felt the
recipient wouldn't redeem them on the spot. This doesn't seem like
an improvement over just sending the coins via phone. <br>
<br>
The use case with poor internet connection wouldn't work as well
since, presumably, the recipient would also have poor reception and
couldn't verify the note was actually loaded with bitcoins. <br>
<br>
Also, I REALLY don't like the name bit reserve. <br>
<br>
-Chris<br>
<br>
<div class="moz-cite-prefix">On 05/17/2014 11:31 AM, Jerry Felix
wrote:<br>
</div>
<blockquote cite="mid:BAY173-W1475F72C70BC089A82C20FCC300@phx.gbl"
type="cite">
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style>
<div dir="ltr">It seems to me that there's a huge need for a paper
currency that is counterfeit-resistant, inexpensive to print,
internationally recognized (border-less), fits in a wallet, and
machine readable.<br>
<br>
I pitched this idea at the Cincinnati Bitcoin meetup last week,
and I didn't get thrown out, so I took the time to document a
proposed standard to accomplish this. I've put my ideas into
BIP format, so that you can see what I have in mind, although I
picked some <br>
BIP numbers myself that seem to be available. Call them
"proposed proposals", or "provisional BIPs". I've numbered them
provisionally BIP-80 to BIP-84.<br>
<br>
If you guys think that this idea has some merit, let's discuss.<br>
<br>
<a class="moz-txt-link-freetext" href="https://github.com/jerfelix/provisional_bips/blob/master/README.mediawiki">https://github.com/jerfelix/provisional_bips/blob/master/README.mediawiki</a><br>
<br>
Submitted with humility and some fear of getting laughed out of
here...<br>
- Jerry<br>
<br>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
<a class="moz-txt-link-freetext" href="http://p.sf.net/sfu/SauceLabs">http://p.sf.net/sfu/SauceLabs</a></pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Bitcoin-development mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-development@lists.sourceforge.net</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/bitcoin-development">https://lists.sourceforge.net/lists/listinfo/bitcoin-development</a>
</pre>
</blockquote>
<br>
</body>
</html>
--------------080306070809020702080405--
|
