summaryrefslogtreecommitdiff
path: root/bd/328d84a5b434fc5c57d542a2800ee109d4a72a
blob: e4d0e5dc3e02ea85a3a0b105f52c8f5d88f15804 (plain)
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
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 <eric@ericmartindale.com>) 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 <bitcoin-development@lists.sourceforge.net>;
	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 <bitcoin-development@lists.sourceforge.net>
	(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 <bitcoin-development@lists.sourceforge.net>;
	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: <CALC81CN42NYkAWcrVks=DySb=H_YY1YV504UP0J4rqv_YMBY2A@mail.gmail.com>
References: <CA+WZAEp3HsW5ESGUZ7YfR1MZXGC5jd+LucUt_MUP8K94Xwhuhg@mail.gmail.com>
	<CANEZrP0KVyp2Va7Wyy=t0qYkLNK9BDUaSzBfuzQss+=weLJ1Fw@mail.gmail.com>
	<CA+WZAEqYKv8T1OMCKhOJvf5FAy=WujJ=OhtsYP9aBf=4ZPNxmw@mail.gmail.com>
	<CABsx9T0FJGn3a+JjiLK6yhLN4psqgqhX766FY+5r-mK9v_aYnw@mail.gmail.com>
	<20140407200838.GR3180@nl.grid.coop>
	<CALC81CN42NYkAWcrVks=DySb=H_YY1YV504UP0J4rqv_YMBY2A@mail.gmail.com>
Date: Mon, 7 Apr 2014 15:00:47 -0700
Message-ID: <CAAf19WrOUtXna4MuKTyB9EEWaJkM9+rY4W5eiFCAtqcTvi4k=Q@mail.gmail.com>
From: Eric Martindale <eric@ericmartindale.com>
To: Ricardo Filipe <ricardojdfilipe@gmail.com>
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: <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: 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" <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
>

--089e01419c6af0c35f04f67aff6f
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">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.</p>

<p dir=3D"ltr">Eric Martindale <br>
Developer Evangelist, BitPay<br>
+1 (919) 374-2020</p>
<div class=3D"gmail_quote">On Apr 7, 2014 2:55 PM, &quot;Ricardo Filipe&quo=
t; &lt;<a href=3D"mailto:ricardojdfilipe@gmail.com">ricardojdfilipe@gmail.c=
om</a>&gt; wrote:<br type=3D"attribution"><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
2014-04-07 21:08 GMT+01:00 Troy Benjegerdes &lt;<a href=3D"mailto:hozer@hoz=
ed.org">hozer@hozed.org</a>&gt;:<br>
&gt; I have to play dissenter here again..<br>
&gt;<br>
&gt; Using a bitcoin address as a persistent identity key is the first real=
-world<br>
&gt; use of Bitcoin that I can imagine will make it a &#39;killer app&#39; =
that everyone<br>
&gt; and their grandma will want to use.<br>
&gt;<br>
<br>
I am of the same opinion, although i understand Gavin&#39;s point. Would<br=
>
the multisig seed work for this purpose?<br>
I have been toying with this idea and I think that for this BIP to<br>
make sense it would require a &quot;root&quot; key as your login. Then if y=
ou<br>
need to make transfers the system would request you to create and<br>
associate a new key to your account for each purchase (signing the new<br>
key with the root one for example).<br>
<br>
---------------------------------------------------------------------------=
---<br>
Put Bad Developers to Shame<br>
Dominate Development with Jenkins Continuous Integration<br>
Continuously Automate Build, Test &amp; Deployment<br>
Start a new project now. Try Jenkins in the cloud.<br>
<a href=3D"http://p.sf.net/sfu/13600_Cloudbees" target=3D"_blank">http://p.=
sf.net/sfu/13600_Cloudbees</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</blockquote></div>

--089e01419c6af0c35f04f67aff6f--