Mac OS X Build Instructions and Notes
This guide will show you how to build dogecoind(headless client) for OSX.
-* Tested on OS X 10.6 through 10.9 on 64-bit Intel processors only.
Older OSX releases or 32-bit processors are no longer supported.
*Setup instructions for a gitian build of Dogecoin using a Debian VM or physical
Gitian is the deterministic build
Core executables . It provides
executables are really built from
the same, tested dependencies are
UNIX BUILD NOTES
Some notes on how to build Dogecoin in Unix.
This will build dogecoin-qt as well if the dependencies are met.
| SSL Support
| Secure commu
Multiwallet Qt Development and Integration Strategy
In order to support loading of multiple wallets in dogecoin-qt, a few changes in
the UI architecture will be needed.
Fortunately, only four of the files in the existing project are affected by this
TOR SUPPORT IN DOGECOIN
It is possible to run Dogecoin as a Tor hidden service, and connect to such
The following directions assume you have a Tor proxy running on port 9050. Many
distributions default to having a SOCKS proxy listening on port
Compiling/running unit tests
-Unit tests will be automatically compiled if dependencies were met in configure
and tests weren't explicitly disabled.
After configuring, they can be run with 'make check'.
To run the dogecoind tests manually, launch src/test
* update translations (ping wumpus, Diapolo or tcatm on IRC)
* * *
#update (commit) version in sources
The Qt GUI can be easily translated into other languages. Here's how we
handle those translations.
Files and Folders
This file takes care of generating `.qm` files from `.ts` files. It is mostly
# Dogecoin Core 1.8.1
Dogecoin Core 1.8.1 is primarily a bugfix release, bringing Dogecoin Core in
line with Bitcoin 0.9.3. Dogecoin Core 1.8.1 also adds in support for printing
paper wallets, and disables connections to pre-1.8 clients. This is a
# Dogecoin Core 1.7 Alpha
Dogecoin Core 1.7 is a complete re-architecture of Dogecoin, changing from
using the Litecoin client as its base, to Bitcoin 0.9. It's still Dogecoin,
with the same Scrypt PoW algorithm, same reward schedule, but there are a
Please be consistent with the existing coding style.
bool Function(char* psz, int n)
/ Comment summarising what this section of code does
for (int i = 0; i < n; i+)
/ When something fails, return early
# Bootstrap the Blockchain Synchronization
Normally the Dogecoin Core client will download the transaction and network
information, called the blockchain, from network by syncing with the other
clients. This can be a process that can take multiple days as
The following is a list of assets used in the bitcoin source and their proper
[Wladimir van der Laan](https:/github.com/laanwj)
* License: MIT
# Assets Used
WINDOWS BUILD NOTES
-Compilation under Windows is supported using MinGW (http:/www.mingw.org/)
-To build Dogecoin for Windows, there are number of libraries you need to
separately and build. Note that, for those
Used in 0.8.0
-* wallet.dat: personal wallet (BDB) with keys and transactions
* peers.dat: peer IP address database (custom format); since 0.7.0
* blocks/blk000?.dat: block data (custom, 128 MiB per file); since 0.8.0
* blocks/rev000?.dat; block undo data
# Dogecoin Core 1.8
Dogecoin Core 1.8 introduces AuxPoW from block 371,337. AuxPoW is a technology
which enables miners to submit work done while mining other coins, as work
on the Dogecoin block chain. Dogecoin Core 1.8 also enables payment protocol