public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Chris Pacia <ctpacia@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Paper Currency
Date: Sat, 17 May 2014 12:07:08 -0400	[thread overview]
Message-ID: <5377892C.8080402@gmail.com> (raw)
In-Reply-To: <BAY173-W1475F72C70BC089A82C20FCC300@phx.gbl>

[-- Attachment #1: Type: text/plain, Size: 2159 bytes --]

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


[-- Attachment #2: Type: text/html, Size: 3534 bytes --]

  parent reply	other threads:[~2014-05-17 16:08 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-17 15:31 [Bitcoin-development] Paper Currency Jerry Felix
2014-05-17 15:45 ` Matt Whitlock
2014-05-17 16:07 ` Chris Pacia [this message]
2014-05-17 16:40   ` Gregory Maxwell
2014-05-18 11:47     ` Alex Kotenko
2014-05-18 12:14       ` Andreas Schildbach
2014-05-18 12:51         ` Alex Kotenko
2014-05-19 13:06           ` Brooks Boyd
2014-05-19 13:50             ` Alex Kotenko
2014-05-18 13:50       ` Natanael
2014-05-18 18:47         ` Alex Kotenko
2014-05-18 20:10           ` Natanael
2014-05-19 10:26             ` Alex Kotenko
2014-05-19 12:55       ` Sergio Lerner
2014-05-19 13:34         ` Martin Sip
2014-05-19 13:53         ` Alex Kotenko
2014-05-19 14:47         ` [Bitcoin-development] patents Adam Back
2014-05-19 15:09           ` Mike Hearn
2014-05-19 18:27             ` Peter Todd
2014-05-19 18:40               ` Mike Hearn
2014-05-19 18:43             ` Gregory Maxwell
2014-05-19 18:46               ` Peter Todd
2014-05-19 18:49               ` Mike Hearn
2014-05-19 22:15             ` Bernd Jendrissek
2014-05-20 10:30           ` Jeff Garzik
2014-05-18 13:50 ` [Bitcoin-development] Paper Currency Andreas Schildbach
2014-05-19 12:21 ` Mike Hearn
2014-05-19 18:20   ` Justus Ranvier
2014-05-19 18:39     ` Peter Todd
2014-05-18 19:54 Jerry Felix

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5377892C.8080402@gmail.com \
    --to=ctpacia@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox