public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Tim Ruffing <tim.ruffing@mmci.uni-saarland.de>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] New paper: Research Perspectives and Challenges for Bitcoin and Cryptocurrencies
Date: Wed, 04 Mar 2015 13:19:43 +0100	[thread overview]
Message-ID: <2225599.NkYGlIqXOH@calzone> (raw)
In-Reply-To: <CAF7tpEyHyg7cB8DQiwb-gGg5v5Hn1Kurw2GaVtid=LyJrB1XQA@mail.gmail.com>

This is great to see. 

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 from
> this mailing list and forums/wikis/irc channels, where many academic
> researchers simply don’t know to look! 
This is indeed a problem in the research community. Often ideas from here are 
just overlooked, and e.g., re-invented or not properly acknowledged. Of 
course, this is (in almost all cases) not intentionally. It's just difficult to 
keep track of everything.

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

Best,
Tim



  parent reply	other threads:[~2015-03-04 12:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-02 16:48 [Bitcoin-development] New paper: Research Perspectives and Challenges for Bitcoin and Cryptocurrencies Andrew Miller
2015-03-03  1:57 ` Ricardo Filipe
2015-03-04 12:19 ` Tim Ruffing [this message]
2015-03-04 15:28 ` Mike Hearn
2015-03-08 12:23   ` Pindar Wong
2015-03-05  5:06 Stephen Reed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2225599.NkYGlIqXOH@calzone \
    --to=tim.ruffing@mmci.uni-saarland.de \
    --cc=bitcoin-development@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox