From: Thomas Kerin <me@thomaskerin•io>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Where do I start?
Date: Thu, 30 Apr 2015 16:50:34 +0100 [thread overview]
Message-ID: <55424F4A.2080802@thomaskerin.io> (raw)
In-Reply-To: <CABm2gDpJqV7YGYCaubBbnSyMO-Q8Nv1w2T4msUbQzYJX_Xpn8A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4666 bytes --]
When dealing with any of the libraries or API's it's helps to know
what's going on under the hood. I find these pages to be invaluable.
https://en.bitcoin.it/wiki/Transactions
https://en.bitcoin.it/wiki/Protocol_specification
https://en.bitcoin.it/wiki/Script
On 30/04/15 11:28, Jorge Timón wrote:
> Well, if you're interested in learning java while learning bitcoin,
> probably you should be looking at https://github.com/bitcoinj/bitcoinj
> or one of its related project (like the android bitcoin wallet based
> on it).
> There's a getting sterted page: https://bitcoinj.github.io/#getting-started
>
> These links my be useful too:
>
> https://bitcoin.org/en/bitcoin-for-developers
> https://bitcoin.org/en/developer-documentation
>
>
> On Thu, Apr 30, 2015 at 11:35 AM, Telephone Lemien
> <lemientelephone@gmail•com> wrote:
>> Hello,
>> I'm a beginner in Bitcoin and I want to know, what are things those allo me
>> to understand Bitcoin protocol and make progress in java to become a good
>> developper.
>> Please tell me how I can begin.
>> Best regards
>>
>> 2015-04-30 10:08 GMT+02:00 Jorge Timón <jtimon@jtimon•cc>:
>>> As Mike says it depends on your interests. But one thing that is almost
>>> always welcomed is improving the tests, and it is unlikely that it conflicts
>>> with other people's PRs (unless they're changing that part of the code and
>>> need to update those tests. Improving documentation is also good and you can
>>> do that while reading the code. Usually I just start cloning, compiling and
>>> changing things as I read, "if I understand this correctly, this change
>>> should not break the tests, if I understand this, this other change should
>>> break the build", etc.
>>> But again, is up to you.
>>>
>>> On Apr 16, 2015 2:34 PM, "Mike Hearn" <mike@plan99•net> wrote:
>>>> 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.
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
>>>> Develop your own process in accordance with the BPMN 2 standard
>>>> Learn Process modeling best practices with Bonita BPM through live
>>>> exercises
>>>> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-
>>>> event?utm_
>>>> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
>>>> _______________________________________________
>>>> Bitcoin-development mailing list
>>>> Bitcoin-development@lists•sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>>>
>>>
>>> ------------------------------------------------------------------------------
>>> One dashboard for servers and applications across Physical-Virtual-Cloud
>>> Widest out-of-the-box monitoring support with 50+ applications
>>> Performance metrics, stats and reports that give you Actionable Insights
>>> Deep dive visibility with transaction tracing using APM Insight.
>>> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
>>> _______________________________________________
>>> Bitcoin-development mailing list
>>> Bitcoin-development@lists•sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>>
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
--
Thomas Kerin
------------------------------------------------------------------------
My PGP key can be found here <http://pgp.mit.edu/pks/lookup?op=get&search=0x3F0D2F83A2966155>
[-- Attachment #2: Type: text/html, Size: 7092 bytes --]
next prev parent reply other threads:[~2015-04-30 16:06 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 ` gabe appleton
2015-04-16 12:33 ` Mike Hearn
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 [this message]
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=55424F4A.2080802@thomaskerin.io \
--to=me@thomaskerin$(echo .)io \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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