Dogecoin Core 1.10
Dogecoin Core is the reference Dogecoin client and it builds the backbone of the network. However, it downloads and stores the entire history of Dogecoin transactions (which is currently several GBs); depending on the speed of your computer and network connection, the synchronization process can take anywhere from a few hours to a day or more.
The following are some helpful notes on how to run Dogecoin on your native platform.
You need the Qt4 run-time libraries to run Dogecoin-Qt. On Debian or Ubuntu:
sudo apt-get install libqtgui4
Unpack the files into a directory and run:
- bin/32/dogecoin-qt (GUI, 32-bit) or bin/32/dogecoind (headless, 32-bit)
- bin/64/dogecoin-qt (GUI, 64-bit) or bin/64/dogecoind (headless, 64-bit)
Unpack the files into a directory, and then run dogecoin-qt.exe.
Drag Dogecoin-Qt to your applications folder, and then run Dogecoin-Qt.
- See the documentation at the Bitcoin Wiki for help and more information.
- Ask for help on #dogecoin on Freenode. If you don't have an IRC client use webchat here.
- Ask for help on the BitcoinTalk forums, in the Dogecoin thread.
The following are developer notes on how to build Dogecoin on your native platform. They are not complete guides, but include notes on the necessary libraries, compile flags, etc.
The Dogecoin repo's root README contains relevant information on the development process and automated testing.
- Developer Notes
- Multiwallet Qt Development
- Release Notes
- Release Process
- Translation Process
- Translation Strings Policy
- Unit Tests
- Unauthenticated REST Interface
- Dnsseed Policy
- Discuss on the BitcoinTalk forums, in the Dogecoin thread.
- Discuss on #dogecoin-dev on Freenode. If you don't have an IRC client use webchat here.
Distributed under the MIT software license. This product includes software developed by the Bitcoin developers for use in Bitcoin Core. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. This product includes cryptographic software written by Eric Young (email@example.com), and UPnP software written by Thomas Bernard.