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
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
|
Return-Path: <ac89@buffalo.edu>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 8DCD8112F
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 28 Oct 2019 14:19:06 +0000 (UTC)
X-Greylist: delayed 00:06:13 by SQLgrey-1.7.6
Received: from mtareserve211.acsu.buffalo.edu (mtareserve211.acsu.buffalo.edu
[128.205.7.68])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 9F1E963D
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 28 Oct 2019 14:19:05 +0000 (UTC)
Received: from appmailb.acsu.buffalo.edu (appmailb.acsu.buffalo.edu
[128.205.4.58])
by mtareserve211.acsu.buffalo.edu (Postfix) with ESMTP id
471xWR6jFyz60SdT for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 28 Oct 2019 10:12:51 -0400 (EDT)
Received: from appmailb.acsu.buffalo.edu (localhost [127.0.0.1])
by localhost (Postfix) with SMTP id E422D7AB42F3
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 28 Oct 2019 10:12:51 -0400 (EDT)
Received: from appmailb.acsu.buffalo.edu (localhost [127.0.0.1])
by appmailb.acsu.buffalo.edu (Postfix) with ESMTP id C01777AB42DC
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 28 Oct 2019 10:12:49 -0400 (EDT)
Received: from MBX-NR8.itorg.ad.buffalo.edu (mbx-nr8.acsu.buffalo.edu
[128.205.7.211])
by appmailb.acsu.buffalo.edu (Prefixe) with ESMTP id BE7DB7AB42DB
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 28 Oct 2019 10:12:49 -0400 (EDT)
Received: from MBX-NR5.itorg.ad.buffalo.edu (128.205.7.196) by
MBX-NR8.itorg.ad.buffalo.edu (128.205.7.211) with Microsoft SMTP Server
(TLS) id 15.0.1263.5; Mon, 28 Oct 2019 10:12:49 -0400
Received: from MBX-NR5.itorg.ad.buffalo.edu ([192.168.101.115]) by
MBX-NR5.itorg.ad.buffalo.edu ([192.168.101.115]) with mapi id
15.00.1263.000; Mon, 28 Oct 2019 10:12:49 -0400
From: "Casciano, Anthony" <ac89@buffalo.edu>
To: "bitcoin-dev@lists.linuxfoundation.org"
<bitcoin-dev@lists.linuxfoundation.org>
Thread-Topic: Ring VS Schnorr signatures
Thread-Index: AQHVjZdhcWdv1iLydUKzAopeKm2/Mg==
Date: Mon, 28 Oct 2019 14:12:49 +0000
Message-ID: <1572271969224.87029@buffalo.edu>
References: <mailman.27.1572264008.20057.bitcoin-dev@lists.linuxfoundation.org>
In-Reply-To: <mailman.27.1572264008.20057.bitcoin-dev@lists.linuxfoundation.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [128.205.83.188]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PM-EL-Spam-Prob: : 8%
X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED
autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Sat, 02 Nov 2019 15:20:26 +0000
Subject: Re: [bitcoin-dev] Ring VS Schnorr signatures
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Oct 2019 14:19:06 -0000
In the world of architectural trade-offs, specifically: confidentiality ver=
sus base layer performance, and=0A=
in the current regulatory environment, as global monetary affairs begin to =
get "more real," I'm now leaning towards greater confidentiality rather tha=
n my earlier preference for performance.=0A=
=0A=
Do Ring sigs with Stealth addresses impede blockchain performance or do the=
y mis-align with Bitcoin's longer term=0A=
dev roadmap?=0A=
=0A=
=0A=
~ TC=0A=
=0A=
________________________________________=0A=
From: bitcoin-dev-bounces@lists.linuxfoundation.org <bitcoin-dev-bounces@li=
sts.linuxfoundation.org> on behalf of bitcoin-dev-request@lists.linuxfounda=
tion.org <bitcoin-dev-request@lists.linuxfoundation.org>=0A=
Sent: Monday, October 28, 2019 8:00 AM=0A=
To: bitcoin-dev@lists.linuxfoundation.org=0A=
Subject: bitcoin-dev Digest, Vol 53, Issue 41=0A=
=0A=
Send bitcoin-dev mailing list submissions to=0A=
bitcoin-dev@lists.linuxfoundation.org=0A=
=0A=
To subscribe or unsubscribe via the World Wide Web, visit=0A=
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev=0A=
or, via email, send a message with subject or body 'help' to=0A=
bitcoin-dev-request@lists.linuxfoundation.org=0A=
=0A=
You can reach the person managing the list at=0A=
bitcoin-dev-owner@lists.linuxfoundation.org=0A=
=0A=
When replying, please edit your Subject line so it is more specific=0A=
than "Re: Contents of bitcoin-dev digest..."=0A=
=0A=
=0A=
Today's Topics:=0A=
=0A=
1. Fwd: node-Tor is now open source in clear (and modular)=0A=
(Aymeric Vitte)=0A=
=0A=
=0A=
----------------------------------------------------------------------=0A=
=0A=
Message: 1=0A=
Date: Mon, 28 Oct 2019 11:33:32 +0100=0A=
From: Aymeric Vitte <vitteaymeric@gmail.com>=0A=
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>=0A=
Subject: [bitcoin-dev] Fwd: node-Tor is now open source in clear (and=0A=
modular)=0A=
Message-ID: <70e77789-9fce-0d54-0aed-361035e79c1d@gmail.com>=0A=
Content-Type: text/plain; charset=3D"utf-8"=0A=
=0A=
FYI, javascript implementation of the Tor protocol on server side and=0A=
inside browsers=0A=
=0A=
Not related directly to bitcoin-dev but might be of some use one day to=0A=
anonymize bitcoin apps (light wallets for example)=0A=
=0A=
=0A=
-------- Message transf?r? --------=0A=
Sujet?: node-Tor is now open source in clear (and modular)=0A=
Date?: Thu, 24 Oct 2019 18:02:42 +0200=0A=
De?: Aymeric Vitte <vitteaymeric@gmail.com>=0A=
Pour?: tor-talk@lists.torproject.org=0A=
=0A=
=0A=
=0A=
Please see https://github.com/Ayms/node-Tor and http://peersm.com/peersm2=
=0A=
=0A=
This is a javascript implementation of the Tor protocol on server side=0A=
(nodejs) and inside browsers, please note that it is not intended to add=0A=
nodes into the Tor network, neither to implement the Tor Browser=0A=
features, it is intended to build projects using the Tor protocol from=0A=
the browser and/or servers (most likely P2P projects), the Onion Proxy=0A=
and Onion Router functions are available directly inside the browser=0A=
which establishes circuits with other nodes understanding the Tor=0A=
protocol (so it's not a "dumb" proxy), but it can of course establish=0A=
circuits with the Tor network nodes (see=0A=
https://github.com/Ayms/node-Tor#test-configuration-and-use) and act as=0A=
a Tor node=0A=
=0A=
It is financed by NLnet via EU Horizon 2020 Next Generation Internet=0A=
Privacy & Trust Enhancing Technologies, now open source under a MIT=0A=
license and we made it modular, it is fast (extensively tested when=0A=
video streaming was there, especially with bittorrent or ORDB concept)=0A=
and the total unminified code=0A=
(https://github.com/Ayms/node-Tor/blob/master/html/browser.js) is only 1=0A=
MB (so ~600 kB minified) which is quite small for what it does, this is=0A=
not a browser extension/module but pure js=0A=
=0A=
Possible next steps are to implement elliptic crypto and connections via=0A=
WebRTC Snowflake (peersm2 above uses WebSockets a bit the way flashproxy=0A=
was working, ie implementing the ws interface on bridges side), as well=0A=
as integrating it with "Discover and move your coins by yourself"=0A=
(https://peersm.com/wallet) for anonymous blockchain search and=0A=
anonymous sending of transactions from the browser=0A=
=0A=
--=0A=
Move your coins by yourself (browser version): https://peersm.com/wallet=0A=
Bitcoin transactions made simple: https://github.com/Ayms/bitcoin-transacti=
ons=0A=
Zcash wallets made simple: https://github.com/Ayms/zcash-wallets=0A=
Bitcoin wallets made simple: https://github.com/Ayms/bitcoin-wallets=0A=
Get the torrent dynamic blocklist: http://peersm.com/getblocklist=0A=
Check the 10 M passwords list: http://peersm.com/findmyass=0A=
Anti-spies and private torrents, dynamic blocklist: http://torrent-live.org=
=0A=
Peersm : http://www.peersm.com=0A=
torrent-live: https://github.com/Ayms/torrent-live=0A=
node-Tor : https://www.github.com/Ayms/node-Tor=0A=
GitHub : https://www.github.com/Ayms=0A=
=0A=
-------------- next part --------------=0A=
An HTML attachment was scrubbed...=0A=
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20=
191028/1c6957c0/attachment-0001.html>=0A=
=0A=
------------------------------=0A=
=0A=
_______________________________________________=0A=
bitcoin-dev mailing list=0A=
bitcoin-dev@lists.linuxfoundation.org=0A=
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev=0A=
=0A=
=0A=
End of bitcoin-dev Digest, Vol 53, Issue 41=0A=
*******************************************=0A=
|
