From: rze <rzeqeu@gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] Considering starting a toy full-node implementation. Any advice?
Date: Tue, 6 Nov 2018 23:21:11 +0200 [thread overview]
Message-ID: <1D59197E-93ED-42CE-9DB1-EC3219540C02@gmail.com> (raw)
Hello,
I'm considering to start developing a toy full validating node implementation (no wallet, no mining) for educational purposes.
Some questions:
1) which resource do you suggest for as a reference for the protocol?
2) which part do you suggest to start with?
3) I was thinking to use btcd as a reference since I'm not familiar with C++ (bitcoind)
4) are there any other general advice or tips for such endeavours?
Thanks in advance.
next reply other threads:[~2018-11-06 21:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 21:21 rze [this message]
[not found] <mailman.37.1541592011.22359.bitcoin-dev@lists.linuxfoundation.org>
2018-11-07 13:20 ` [bitcoin-dev] Considering starting a toy full-node implementation. Any advice? Артём Литвинович
2018-11-07 16:19 ` John C. Vernaleo
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=1D59197E-93ED-42CE-9DB1-EC3219540C02@gmail.com \
--to=rzeqeu@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/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