<p>as davec mentioned, btcd is written in go, and thus runs on any platform that go runs on. although not officially supported, go runs on plan 9, and so i run btcd on plan 9. proof: <img src="https://i.sstatic.net/X3bmJ.png" alt="btcd on plan 9"></p>

CC BY-SA 3.0
2013-10-19T00:33:42.403Z
This is awesome.
Colin Dean
CC BY-SA 3.0
2013-10-18T08:33:42.320Z
2013-10-18T08:33:42.320Z
mischief
<p>EDIT (2014-09-05): I have updated this answer to the most recent information.  The previous answer was outdated in regards to the cons.  It was accurate as of version 0.3.0-alpha, however btcd is now in beta, up to version 0.8.0-beta, and nearly all of the previous cons have since been addressed.  Also, I've updated all references to bitcoind to Bitcoin Core to reflect their name change</p>

<p>I'll try to answer this as unbiased as possible, but, as a disclaimer, I am the lead developer for btcd.</p>

<p>First, a small correction.  The initial release is version 0.3.0-alpha (<a href="https://github.com/conformal/btcd/releases">https://github.com/conformal/btcd/releases</a>).  It is not yet up to version 1.0 as we first want to get a ton of public testing from early adopters before claiming it is production ready.  We fully understand the importance of avoid block chain forks and are making herculean efforts to do everything we can to prevent that from happening.</p>

<p>I'll provide a list of pros and cons that I can think of for btcd relative to Bitcoin Core below, but one thing I'd like point out isn't specifically related to btcd or Bitcoin Core, but rather the Bitcoin ecosystem as a whole.</p>

<p>Diversity is something the Bitcoin ecosystem is in dire need of.  Diverse, inter-operating implementations make the Bitcoin network more robust against several things such as denial-of-service attacks, vulnerabilities, and individual application bugs.  History has shown that for any protocol to thrive and gain wide-spread acceptance, multiple implementations on multiple devices is inevitably required.  One prolific example is TCP/IP.  TCP/IP would not be where it is today if only a single implementation existed.</p>

<h2>Pros</h2>

<ul>
<li>btcd offers a unique architecture in that it separates the chain services from the wallet services (see NOTES [a])</li>
<li>btcd is written in Go which has several advantages over C++ (See NOTES [b])</li>
<li>btcd is a clean refactor of the entire Bitcoin protocol rather than one that is monolithic</li>
<li>the btcd codebase strives to provide easy to follow and well-commented code (Bitcoin Core is definitely improving in this area, but there is still a lot of undocumented "magic")</li>
<li>the btcd core packages provide more extensive unit test coverage to help prevent regressions (for example btcwire provides 100% test coverage)</li>
<li>btcd incorporates a package that has been highly optimized specifically for the ECDSA curve parameters used by Bitcoin (secp256k1) making it faster than OpenSSL</li>
<li>btcd is capable of running as a real service on Windows (see NOTES[c])</li>
<li>btcd provides a compatible RPC interface with Bitcoin Core has which makes it relatively straight forward to use it in existing infrastructures</li>
<li>btcd is able to sync the entire block chain from scratch in around 5 hours on an Intel i7 with an SSD</li>
</ul>

<h2>Cons</h2>

<ul>
<li>btcd does not daemonize itself and instead relies on external tools such as daemonize and upstart to perform that function</li>
<li>The uPnP functionality is currently disabled by default and does not appear work with all devices, so it might be necessary to manually open ports on your router and use the --externalip flag</li>
</ul>

<h3>Notes</h3>

<p>[a] A full discussion of the advantages of separating the chain and wallet services would require an entire blog post, but a few examples are that it opens a lot of opportunities for lower powered hardware, offers better multi-user support, and results in less waste in small networks which can share the chain services.</p>

<p>[b] Some advantages we believe Go has over C++</p>

<ul>
<li>Integrated test infrastructure</li>
<li>Platform independent code</li>
<li>Simpler parallelism and excellent support for concurrency</li>
<li>No active memory management which leads to eliminating an entire class of the most common security vulnerabilities like buffer overflows</li>
<li>Built-in profiling and documentation facilities</li>
<li>Significantly faster compilation times</li>
</ul>

<p>[c] The Windows installer does not provide the option to install or run it as a service, however btcd itself has command line options to do so.  To install it as a service: btcd.exe /s install</p>

CC BY-SA 3.0
2014-11-03T18:16:55.470Z
It's times like these one wishes they could cast more than one upvote.
Ethan
CC BY-SA 3.0
2016-11-04T23:19:06.857Z
does it have address index?
Pavel Niedoba
CC BY-SA 3.0
2013-10-06T20:51:43.590Z
2014-09-05T19:54:55.400Z
2014-09-05T19:54:55.400Z
davecgh
<p><a href="https://blog.conformal.com/btcd-not-your-moms-bitcoin-daemon/">btcd 1.0 was released</a> October 3, 2013. Why use it instead of bitcoind?</p>

<bitcoind><btcd>
What are the benefits of using btcd instead of bitcoind?
Colin Dean
# What are the benefits of using btcd instead of bitcoind?

(Asked by: username_0 on 2013-10-05)

[btcd 1.0 was released](https://blog.conformal.com/btcd-not-your-moms-bitcoin-daemon/) October 3, 2013. Why use it instead of bitcoind?

**Tags:** bitcoind, btcd


---

## 2 answers

### Answer by username_2 on 2013-10-06. Score: 29 | Accepted answer

EDIT (2014-09-05): I have updated this answer to the most recent information. The previous answer was outdated in regards to the cons. It was accurate as of version 0.3.0-alpha, however btcd is now in beta, up to version 0.8.0-beta, and nearly all of the previous cons have since been addressed. Also, I've updated all references to bitcoind to Bitcoin Core to reflect their name change

I'll try to answer this as unbiased as possible, but, as a disclaimer, I am the lead developer for btcd.

First, a small correction. The initial release is version 0.3.0-alpha (<https://github.com/conformal/btcd/releases>). It is not yet up to version 1.0 as we first want to get a ton of public testing from early adopters before claiming it is production ready. We fully understand the importance of avoid block chain forks and are making herculean efforts to do everything we can to prevent that from happening.

I'll provide a list of pros and cons that I can think of for btcd relative to Bitcoin Core below, but one thing I'd like point out isn't specifically related to btcd or Bitcoin Core, but rather the Bitcoin ecosystem as a whole.

Diversity is something the Bitcoin ecosystem is in dire need of. Diverse, inter-operating implementations make the Bitcoin network more robust against several things such as denial-of-service attacks, vulnerabilities, and individual application bugs. History has shown that for any protocol to thrive and gain wide-spread acceptance, multiple implementations on multiple devices is inevitably required. One prolific example is TCP/IP. TCP/IP would not be where it is today if only a single implementation existed.

## Pros

* btcd offers a unique architecture in that it separates the chain services from the wallet services (see NOTES [a])
* btcd is written in Go which has several advantages over C++ (See NOTES [b])
* btcd is a clean refactor of the entire Bitcoin protocol rather than one that is monolithic
* the btcd codebase strives to provide easy to follow and well-commented code (Bitcoin Core is definitely improving in this area, but there is still a lot of undocumented "magic")
* the btcd core packages provide more extensive unit test coverage to help prevent regressions (for example btcwire provides 100% test coverage)
* btcd incorporates a package that has been highly optimized specifically for the ECDSA curve parameters used by Bitcoin (secp256k1) making it faster than OpenSSL
* btcd is capable of running as a real service on Windows (see NOTES[c])
* btcd provides a compatible RPC interface with Bitcoin Core has which makes it relatively straight forward to use it in existing infrastructures
* btcd is able to sync the entire block chain from scratch in around 5 hours on an Intel i7 with an SSD

## Cons

* btcd does not daemonize itself and instead relies on external tools such as daemonize and upstart to perform that function
* The uPnP functionality is currently disabled by default and does not appear work with all devices, so it might be necessary to manually open ports on your router and use the --externalip flag

### Notes

[a] A full discussion of the advantages of separating the chain and wallet services would require an entire blog post, but a few examples are that it opens a lot of opportunities for lower powered hardware, offers better multi-user support, and results in less waste in small networks which can share the chain services.

[b] Some advantages we believe Go has over C++

* Integrated test infrastructure
* Platform independent code
* Simpler parallelism and excellent support for concurrency
* No active memory management which leads to eliminating an entire class of the most common security vulnerabilities like buffer overflows
* Built-in profiling and documentation facilities
* Significantly faster compilation times

[c] The Windows installer does not provide the option to install or run it as a service, however btcd itself has command line options to do so. To install it as a service: btcd.exe /s install

> **Comments:**
> **username_3**: It's times like these one wishes they could cast more than one upvote.  
> **username_4**: does it have address index?  

---

### Answer by username_1 on 2013-10-18. Score: 11

as davec mentioned, btcd is written in go, and thus runs on any platform that go runs on. although not officially supported, go runs on plan 9, and so i run btcd on plan 9. proof: ![btcd on plan 9](https://i.sstatic.net/X3bmJ.png)

> **Comments:**
> **username_0**: This is awesome.  

---

