public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Eric Martindale <eric@ericmartindale.com>
To: Ricardo Filipe <ricardojdfilipe@gmail.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Draft BIP for seamless website authentication using Bitcoin address
Date: Mon, 7 Apr 2014 15:00:47 -0700	[thread overview]
Message-ID: <CAAf19WrOUtXna4MuKTyB9EEWaJkM9+rY4W5eiFCAtqcTvi4k=Q@mail.gmail.com> (raw)
In-Reply-To: <CALC81CN42NYkAWcrVks=DySb=H_YY1YV504UP0J4rqv_YMBY2A@mail.gmail.com>

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

This is toying with the economics of cryptofinance in a way that needs to
be understood before being put under consideration for implementation in
Bitcoin.  This is an opportunity for an altcoin to explore the implications
of these proposals prior to changing the properties of an already
precarious system.

Eric Martindale
Developer Evangelist, BitPay
+1 (919) 374-2020
On Apr 7, 2014 2:55 PM, "Ricardo Filipe" <ricardojdfilipe@gmail.com> wrote:

> 2014-04-07 21:08 GMT+01:00 Troy Benjegerdes <hozer@hozed.org>:
> > I have to play dissenter here again..
> >
> > Using a bitcoin address as a persistent identity key is the first
> real-world
> > use of Bitcoin that I can imagine will make it a 'killer app' that
> everyone
> > and their grandma will want to use.
> >
>
> I am of the same opinion, although i understand Gavin's point. Would
> the multisig seed work for this purpose?
> I have been toying with this idea and I think that for this BIP to
> make sense it would require a "root" key as your login. Then if you
> need to make transfers the system would request you to create and
> associate a new key to your account for each purchase (signing the new
> key with the root one for example).
>
>
> ------------------------------------------------------------------------------
> Put Bad Developers to Shame
> Dominate Development with Jenkins Continuous Integration
> Continuously Automate Build, Test & Deployment
> Start a new project now. Try Jenkins in the cloud.
> http://p.sf.net/sfu/13600_Cloudbees
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>

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

  reply	other threads:[~2014-04-07 22:00 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-04 12:15 [Bitcoin-development] Draft BIP for seamless website authentication using Bitcoin address Eric Larchevêque
2014-04-04 13:08 ` Mike Hearn
2014-04-04 13:22   ` Eric Larchevêque
2014-04-04 13:32     ` Gavin Andresen
2014-04-04 13:47       ` Eric Larchevêque
2014-04-07 20:08       ` Troy Benjegerdes
2014-04-07 21:55         ` Ricardo Filipe
2014-04-07 22:00           ` Eric Martindale [this message]
2014-04-04 13:43     ` Mike Hearn
2014-04-04 13:47       ` Jeff Garzik
2014-04-04 13:54       ` Mike Hearn
2014-04-04 14:42         ` Eric Larchevêque
2014-04-04 14:51           ` Mike Hearn
2014-04-04 14:56             ` Eric Larchevêque
2014-04-08  3:28               ` Jeff Garzik
2014-04-08  8:13                 ` Mike Hearn
2014-04-08 15:19                   ` Jeff Garzik
2014-04-22  6:34                     ` Jan Møller
2014-04-22  8:57                       ` Eric Larchevêque
2014-04-04 15:00             ` slush
2014-04-04 14:56           ` slush
2014-04-04 15:09             ` Eric Larchevêque
2014-04-04 15:28               ` slush
2014-04-04 15:37               ` Mike Hearn
2014-04-04 15:42                 ` slush
2014-04-04 16:00                 ` Eric Larchevêque
2014-04-04 15:03       ` Eric Larchevêque

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='CAAf19WrOUtXna4MuKTyB9EEWaJkM9+rY4W5eiFCAtqcTvi4k=Q@mail.gmail.com' \
    --to=eric@ericmartindale.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=ricardojdfilipe@gmail.com \
    /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