From mboxrd@z Thu Jan 1 00:00:00 1970 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 ) 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 ; 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 (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 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: In-Reply-To: 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 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--