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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <martin.habovstiak@gmail.com>) id 1YHMtn-0003vV-T8
for bitcoin-development@lists.sourceforge.net;
Sat, 31 Jan 2015 01:30:59 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.170 as permitted sender)
client-ip=74.125.82.170;
envelope-from=martin.habovstiak@gmail.com;
helo=mail-we0-f170.google.com;
Received: from mail-we0-f170.google.com ([74.125.82.170])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YHMtm-0004aj-68
for bitcoin-development@lists.sourceforge.net;
Sat, 31 Jan 2015 01:30:59 +0000
Received: by mail-we0-f170.google.com with SMTP id w55so24614244wes.1
for <bitcoin-development@lists.sourceforge.net>;
Fri, 30 Jan 2015 17:30:52 -0800 (PST)
X-Received: by 10.180.221.201 with SMTP id qg9mr36644wic.29.1422667852196;
Fri, 30 Jan 2015 17:30:52 -0800 (PST)
Received: from [192.168.2.14] (chello085216130096.chello.sk. [85.216.130.96])
by mx.google.com with ESMTPSA id
k1sm17206791wjn.9.2015.01.30.17.30.50
for <bitcoin-development@lists.sourceforge.net>
(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Fri, 30 Jan 2015 17:30:51 -0800 (PST)
Message-ID: <1422667849.25602.6.camel@TARDIS>
From: Martin =?UTF-8?Q?Habov=C5=A1tiak?= <martin.habovstiak@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Date: Sat, 31 Jan 2015 02:30:49 +0100
Content-Type: multipart/signed; micalg="pgp-sha256";
protocol="application/pgp-signature"; boundary="=-X7CFX9yJSSwBViu62/i1"
X-Mailer: Evolution 3.2.3-0ubuntu6
Mime-Version: 1.0
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-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
(martin.habovstiak[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1YHMtm-0004aj-68
Subject: [Bitcoin-development] New BIP: protocol for multisignature payments
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: Sat, 31 Jan 2015 01:31:00 -0000
--=-X7CFX9yJSSwBViu62/i1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Hello,
I've been thinking about how to solve security problems of the servers
holding huge amounts of bitcoins (exchanges, markets...) and came up
with this idea: https://gist.github.com/Kixunil/2ec79cf40a53fb899ac5
TL;DR: it's extension of BIP70 (but not fully compatible due to security
reasons) which supports making of multisig transactions dynamically.
(The most important thing is that the user provides his address.)
What do you think? Is it a good way to solve the problem or do you know
about something better? I would really like this or something similar
implemented by wallets.
Thank you for your feedback!
Martin
--=-X7CFX9yJSSwBViu62/i1
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQIcBAABCAAGBQJUzDBJAAoJEGEElF3FmNb3tEIP+wcQ4hifygROSsmTxz74rM0F
0rf2jhzCGqFq9BFGrIIyohDrHdHLOip1GCgNQtzl4uwLhinzdHeWBEuR7J0SmWOs
objymjSjvWBUrXcS14NldnlctQKHE+nUDWao9AQkbcxBJkeGs/aeyWTF6W20uxtl
F4khTpiWkGyIPCWckO+iz4bIpcytbcozgy+UtqtbHd1i2aZIX2KeHmqFfRM/cpzw
H/I+hfPUON7OJQ7LXziPAP7miR7RqDbs5Hg9DOCFP/guw0qvHShDt1bCIbGJIJ2H
BabMoc8Wlinfa+0SPrTaQvZ42bb1tJZsrhzSgigSCnVHiD2DHiACBgDWfNrIMCxU
oAe6ckvHqfiHTnBZn/gnHfTcu5Xr8YPgGZQL6s70RPg9sTwnb5T32Ax1lEMIQwwK
dnn7yCmd0dqIETS60j/NB4WjsVnp4U1GqHxq0J5CTmumVk2UVrbSASBRijbFcBmb
miq1rfOmPjZpMAWAkPs7bqxfq+ZLc+Y7udT4ATzF70mEEpk0dlrmf2wd/uuV3owu
F0jxcPcqFT6K+ovXN+Jr0T4h0EY2T/PN1r+c2Ifjfwcd2YkNP64JYnqlPFT8LRY6
os6Wyoc3vMkZnZ8FnSLs11MmUN7TZtd2ovNqUVEtpPYCwgDd7rJ3m+iPyRf8/ub5
q4MI/NAqA/07FQxHg4JA
=D7xM
-----END PGP SIGNATURE-----
--=-X7CFX9yJSSwBViu62/i1--
|
