blob: efb49b6dc26d9004cc0eeb9775204be77274f0bd (
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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <thomasV1@gmx.de>) id 1RrvdZ-0002wT-Kc
for bitcoin-development@lists.sourceforge.net;
Mon, 30 Jan 2012 18:07:29 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmx.de
designates 213.165.64.23 as permitted sender)
client-ip=213.165.64.23; envelope-from=thomasV1@gmx.de;
helo=mailout-de.gmx.net;
Received: from mailout-de.gmx.net ([213.165.64.23])
by sog-mx-4.v43.ch3.sourceforge.com with smtp (Exim 4.76)
id 1RrvdU-0005Vp-3M for bitcoin-development@lists.sourceforge.net;
Mon, 30 Jan 2012 18:07:29 +0000
Received: (qmail 18615 invoked by uid 0); 30 Jan 2012 18:07:18 -0000
Received: from 152.81.11.206 by www005.gmx.net with HTTP;
Mon, 30 Jan 2012 19:07:16 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Date: Mon, 30 Jan 2012 19:07:16 +0100
From: thomasV1@gmx.de
Message-ID: <20120130180716.261910@gmx.net>
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
X-Authenticated: #19670841
X-Flags: 0001
X-Mailer: WWW-Mail 6100 (Global Message Exchange)
X-Priority: 3
X-Provags-ID: V01U2FsdGVkX19P+FF6Q59PvDgYEvWF6ezLmcjLNynk8l97XYx+Ib
rTkgK0rR/Ot1FgJTxuSo33jhIgVeheoFBq6A==
Content-Transfer-Encoding: 8bit
X-GMX-UID: A7lUbysHeSEqUFhER3UhvfN+IGRvbwB9
X-Spam-Score: -1.2 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
no trust [213.165.64.23 listed in list.dnswl.org]
-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
(thomasv1[at]gmx.de)
-0.0 SPF_PASS SPF: sender matches SPF record
0.2 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in
digit (thomasv1[at]gmx.de)
0.0 FAKE_REPLY_C FAKE_REPLY_C
X-Headers-End: 1RrvdU-0005Vp-3M
Subject: Re: [Bitcoin-development] BIP 21 (modification BIP 20)
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, 30 Jan 2012 18:07:29 -0000
I too support BIP21 over BIP20. However, I do not understand the "Sending money via private key" feature; in which situation would such a URI be useful?
Also, I posted a proposal in the forum, to extend the URI syntax with signatures. The goal would be to provide a proof of identity of the recipient; genjix told me that it would be more appropriate to post that here.
My proposal is described here: http://ecdsa.org/bitcoin_URIs.html
My original forum post is here: https://bitcointalk.org/index.php?topic=58534.msg689190#msg689190
--
Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
|
