From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WXHb6-000071-S3 for bitcoin-development@lists.sourceforge.net; Mon, 07 Apr 2014 22:00:56 +0000 X-ACL-Warn: Received: from mail-wi0-f171.google.com ([209.85.212.171]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WXHb5-0007JV-IZ for bitcoin-development@lists.sourceforge.net; Mon, 07 Apr 2014 22:00:56 +0000 Received: by mail-wi0-f171.google.com with SMTP id q5so5978031wiv.10 for ; Mon, 07 Apr 2014 15:00:49 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=v5FDirtDaDHU+qXkghUdSHX9qr3fq0YojDs8g9rdrsQ=; b=K+0QliDaSaMBwrgI3vfRakP0SFxZkf/DCEe5vv8fuOpB0BYwFyZBSYWUNfGu1YiXS/ Qg2ycQUskGYLqqsICX0YMw3qCVF18EcTMLyloYBaqtRKTMABM4vAPtTaCKFA//8UoRCj 6PYLMzTkgjZr7S+uifHgeq3uJ6ndBRWp6OtnnJIaGyS4JtXnJratAizjEcaZdPhOJ/lc 5mEIwUyqQSo0yV46vOSpBqt1cHk+q2WEczzyV5kcIpwEciEbVVj4fmjYU3ebP71+uw0E X/YXsdoQxgiHQNCR3TZufBk/af0qpk0N1GSP+hH1W16ZhDdedjsuB0aXs4hQMSGkT9JN P5Yw== X-Gm-Message-State: ALoCoQnZiABieDndGCCmRUBpW0B3YgDtBjBw1/98HeqyfGZXpmaG8XJnWYbD+1RuFs/Smf49qgcE X-Received: by 10.194.203.170 with SMTP id kr10mr45293069wjc.19.1396908048954; Mon, 07 Apr 2014 15:00:48 -0700 (PDT) Received: from mail-wi0-f181.google.com (mail-wi0-f181.google.com [209.85.212.181]) by mx.google.com with ESMTPSA id r4sm104669wjz.28.2014.04.07.15.00.47 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 07 Apr 2014 15:00:47 -0700 (PDT) Received: by mail-wi0-f181.google.com with SMTP id hm4so313499wib.8 for ; Mon, 07 Apr 2014 15:00:47 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.194.161.168 with SMTP id xt8mr45382815wjb.35.1396908047251; Mon, 07 Apr 2014 15:00:47 -0700 (PDT) Received: by 10.227.6.8 with HTTP; Mon, 7 Apr 2014 15:00:47 -0700 (PDT) Received: by 10.227.6.8 with HTTP; Mon, 7 Apr 2014 15:00:47 -0700 (PDT) In-Reply-To: References: <20140407200838.GR3180@nl.grid.coop> Date: Mon, 7 Apr 2014 15:00:47 -0700 Message-ID: From: Eric Martindale To: Ricardo Filipe Content-Type: multipart/alternative; boundary=089e01419c6af0c35f04f67aff6f X-Spam-Score: 1.0 (+) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 1.0 HTML_MESSAGE BODY: HTML included in message X-Headers-End: 1WXHb5-0007JV-IZ Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] Draft BIP for seamless website authentication using Bitcoin address 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: Mon, 07 Apr 2014 22:00:57 -0000 --089e01419c6af0c35f04f67aff6f Content-Type: text/plain; charset=ISO-8859-1 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" wrote: > 2014-04-07 21:08 GMT+01:00 Troy Benjegerdes : > > 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 > --089e01419c6af0c35f04f67aff6f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

This is toying with the economics of cryptofinance in a way = that needs to be understood before being put under consideration for implem= entation in Bitcoin.=A0 This is an opportunity for an altcoin to explore th= e implications of these proposals prior to changing the properties of an al= ready precarious system.

Eric Martindale
Developer Evangelist, BitPay
+1 (919) 374-2020

On Apr 7, 2014 2:55 PM, "Ricardo Filipe&quo= t; <ricardojdfilipe@gmail.c= om> 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 y= ou
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-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment
--089e01419c6af0c35f04f67aff6f--