summaryrefslogtreecommitdiff
path: root/7c/67aca272ee8733acc388e42d32533c842b2fa6
blob: f2481f7ac5f375412d0dfd664bcd005510b743e3 (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
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <tim.ruffing@mmci.uni-saarland.de>)
	id 1YT8ak-00046L-1D for bitcoin-development@lists.sourceforge.net;
	Wed, 04 Mar 2015 12:39:58 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of
	mmci.uni-saarland.de designates 139.19.1.49 as permitted
	sender) client-ip=139.19.1.49;
	envelope-from=tim.ruffing@mmci.uni-saarland.de;
	helo=hera.mpi-klsb.mpg.de; 
Received: from hera.mpi-klsb.mpg.de ([139.19.1.49])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES128-SHA:128)
	(Exim 4.76) id 1YT8ai-0004ao-0J
	for bitcoin-development@lists.sourceforge.net;
	Wed, 04 Mar 2015 12:39:58 +0000
Received: from zak.mpi-klsb.mpg.de ([139.19.1.29]:37413)
	by hera.mpi-klsb.mpg.de (envelope-from
	<tim.ruffing@mmci.uni-saarland.de>) 
	with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128)
	(Exim 4.80) id 1YT8HA-00051z-K3
	for bitcoin-development@lists.sourceforge.net;
	Wed, 04 Mar 2015 13:19:47 +0100
Received: from 55d40a62.access.ecotel.net ([85.212.10.98]:44442
	helo=calzone.localnet) by zak.mpi-klsb.mpg.de (envelope-from
	<tim.ruffing@mmci.uni-saarland.de>) 
	with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256)
	(Exim 4.80) id 1YT8HA-000082-4y
	for bitcoin-development@lists.sourceforge.net;
	Wed, 04 Mar 2015 13:19:44 +0100
From: Tim Ruffing <tim.ruffing@mmci.uni-saarland.de>
To: bitcoin-development@lists.sourceforge.net
Date: Wed, 04 Mar 2015 13:19:43 +0100
Message-ID: <2225599.NkYGlIqXOH@calzone>
User-Agent: KMail/4.14.5 (Linux/3.18.6-1-ARCH; KDE/4.14.5; x86_64; ; )
In-Reply-To: <CAF7tpEyHyg7cB8DQiwb-gGg5v5Hn1Kurw2GaVtid=LyJrB1XQA@mail.gmail.com>
References: <CAF7tpEyHyg7cB8DQiwb-gGg5v5Hn1Kurw2GaVtid=LyJrB1XQA@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
X-MPI-Local-Sender: true
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 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: 1YT8ai-0004ao-0J
Subject: Re: [Bitcoin-development] New paper: Research Perspectives and
	Challenges for Bitcoin and Cryptocurrencies
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: Wed, 04 Mar 2015 12:39:58 -0000

This is great to see.=20

On Monday 02 March 2015 11:48:24 Andrew Miller wrote:
> One of the main goals of our work is to build a bridge between the
> computer science research community and the cryptocurrency community.=

> Many of the most interesting ideas and proposals for Bitcoin come fro=
m
> this mailing list and forums/wikis/irc channels, where many academic
> researchers simply don=E2=80=99t know to look!=20
This is indeed a problem in the research community. Often ideas from he=
re are=20
just overlooked, and e.g., re-invented or not properly acknowledged. Of=
=20
course, this is (in almost all cases) not intentionally. It's just diff=
icult to=20
keep track of everything.

Your paper is a definitely the right approach to bring the researchers =
closer=20
to the Bitcoin community.

Best,
Tim