summaryrefslogtreecommitdiff
path: root/43/6130ef9fd2031d58a87a380cbd5244e2a2590e
blob: 566924a4e93828ad1932c9b311e7c964d84f2327 (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
95
96
97
98
99
100
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 <mh.in.england@gmail.com>) id 1Yiizc-00059i-Di
	for bitcoin-development@lists.sourceforge.net;
	Thu, 16 Apr 2015 12:34:04 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.212.175 as permitted sender)
	client-ip=209.85.212.175; envelope-from=mh.in.england@gmail.com;
	helo=mail-wi0-f175.google.com; 
Received: from mail-wi0-f175.google.com ([209.85.212.175])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1Yiizb-0002qm-0v
	for bitcoin-development@lists.sourceforge.net;
	Thu, 16 Apr 2015 12:34:04 +0000
Received: by wiun10 with SMTP id n10so95275681wiu.1
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 16 Apr 2015 05:33:57 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.194.61.82 with SMTP id n18mr57067474wjr.35.1429187637037;
	Thu, 16 Apr 2015 05:33:57 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.194.188.11 with HTTP; Thu, 16 Apr 2015 05:33:56 -0700 (PDT)
In-Reply-To: <CANJO25KXoYXKZf-TZRD3HviU141+rYUB2d=4Xf9DqRrzD9P94w@mail.gmail.com>
References: <CANJO25K1Lox5aU-NN-j0An2ujNNHwPWNqX1ZXMs+z1udDZ1LOA@mail.gmail.com>
	<CANJO25KXoYXKZf-TZRD3HviU141+rYUB2d=4Xf9DqRrzD9P94w@mail.gmail.com>
Date: Thu, 16 Apr 2015 13:33:56 +0100
X-Google-Sender-Auth: 41jurXALcAz1ufqizbKsO_9sJjs
Message-ID: <CANEZrP0vJug1tGNiL5wQUuA0-rr3eM1Yp8DbO3Apiu1CX=j3bQ@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: gabe appleton <gappleto97@gmail.com>
Content-Type: multipart/alternative; boundary=047d7ba977806c51d10513d6ad78
X-Spam-Score: -0.5 (/)
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
	(mh.in.england[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	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: 1Yiizb-0002qm-0v
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Where do I start?
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: Thu, 16 Apr 2015 12:34:04 -0000

--047d7ba977806c51d10513d6ad78
Content-Type: text/plain; charset=UTF-8

Hey Gabe,

That's diving into the deep end for sure! :)

> What are some current things that are lacking in Bitcoin core? Or am I
> better off making something else for the ecosystem?
>
That depends on your interests.

Many of the highest priority tasks in Bitcoin Core are rather complicated,
unfortunately, even for people with experience. You can consult the issue
tracker to get a feel for it.

Alternatively, there are lots of wallet apps out there and plenty of more
straightforward projects on them. However they may have less of a research
flavour.

--047d7ba977806c51d10513d6ad78
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hey Gabe,<div><br></div><div>That&#39;s diving into the de=
ep end for sure! :)</div><div class=3D"gmail_extra"><div class=3D"gmail_quo=
te"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex"><p dir=3D"ltr">What are some current thi=
ngs that are lacking in Bitcoin core? Or am I better off making something e=
lse for the ecosystem?</p></blockquote><div>That depends on your interests.=
</div><div><br></div><div>Many of the highest priority tasks in Bitcoin Cor=
e are rather complicated, unfortunately, even for people with experience. Y=
ou can consult the issue tracker to get a feel for it.</div><div><br></div>=
<div>Alternatively, there are lots of wallet apps out there and plenty of m=
ore straightforward projects on them. However they may have less of a resea=
rch flavour.</div></div></div></div>

--047d7ba977806c51d10513d6ad78--