public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Mike Hearn <mike@plan99.net>
To: gabe appleton <gappleto97@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Where do I start?
Date: Thu, 16 Apr 2015 13:33:56 +0100	[thread overview]
Message-ID: <CANEZrP0vJug1tGNiL5wQUuA0-rr3eM1Yp8DbO3Apiu1CX=j3bQ@mail.gmail.com> (raw)
In-Reply-To: <CANJO25KXoYXKZf-TZRD3HviU141+rYUB2d=4Xf9DqRrzD9P94w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 557 bytes --]

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.

[-- Attachment #2: Type: text/html, Size: 851 bytes --]

  reply	other threads:[~2015-04-16 12:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CANJO25K1Lox5aU-NN-j0An2ujNNHwPWNqX1ZXMs+z1udDZ1LOA@mail.gmail.com>
2015-04-16  2:14 ` [Bitcoin-development] Where do I start? gabe appleton
2015-04-16 12:33   ` Mike Hearn [this message]
2015-04-30  8:08     ` Jorge Timón
2015-04-30  9:35       ` Telephone Lemien
2015-04-30 10:28         ` Jorge Timón
2015-04-30 15:50           ` Thomas Kerin
2015-04-16  3:42 Thy Shizzle

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='CANEZrP0vJug1tGNiL5wQUuA0-rr3eM1Yp8DbO3Apiu1CX=j3bQ@mail.gmail.com' \
    --to=mike@plan99.net \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=gappleto97@gmail.com \
    /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