Replaced simple references to Bitcoin, with Dogecoin.
This commit is contained in:
parent
72c98023e8
commit
88b50afb67
|
@ -1,4 +1,4 @@
|
|||
Bitcoin 0.9.0rc1 BETA
|
||||
Dogecoin 0.9.0rc1 BETA
|
||||
=====================
|
||||
|
||||
Copyright (c) 2009-2014 Bitcoin Developers
|
||||
|
@ -6,15 +6,15 @@ Copyright (c) 2009-2014 Bitcoin Developers
|
|||
|
||||
Setup
|
||||
---------------------
|
||||
[Bitcoin Core](http://bitcoin.org/en/download) is the original Bitcoin client and it builds the backbone of the network. However, it downloads and stores the entire history of Bitcoin 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. Thankfully you only have to do this once. If you would like the process to go faster you can [download the blockchain directly](https://bitcointalk.org/index.php?topic=145386.0).
|
||||
[Dogecoin Core](http://bitcoin.org/en/download) is the original 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. Thankfully you only have to do this once. If you would like the process to go faster you can [download the blockchain directly](https://bitcointalk.org/index.php?topic=145386.0).
|
||||
|
||||
Running
|
||||
---------------------
|
||||
The following are some helpful notes on how to run Bitcoin on your native platform.
|
||||
The following are some helpful notes on how to run Dogecoin on your native platform.
|
||||
|
||||
### Unix
|
||||
|
||||
You need the Qt4 run-time libraries to run Bitcoin-Qt. On Debian or Ubuntu:
|
||||
You need the Qt4 run-time libraries to run Dogecoin-Qt. On Debian or Ubuntu:
|
||||
|
||||
sudo apt-get install libqtgui4
|
||||
|
||||
|
@ -31,18 +31,18 @@ Unpack the files into a directory, and then run bitcoin-qt.exe.
|
|||
|
||||
### OSX
|
||||
|
||||
Drag Bitcoin-Qt to your applications folder, and then run Bitcoin-Qt.
|
||||
Drag Dogecoin-Qt to your applications folder, and then run Dogecoin-Qt.
|
||||
|
||||
### Need Help?
|
||||
|
||||
* See the documentation at the [Bitcoin Wiki](https://en.bitcoin.it/wiki/Main_Page)
|
||||
* See the documentation at the [Dogecoin Wiki](https://en.bitcoin.it/wiki/Main_Page)
|
||||
for help and more information.
|
||||
* Ask for help on [#bitcoin](http://webchat.freenode.net?channels=bitcoin) on Freenode. If you don't have an IRC client use [webchat here](http://webchat.freenode.net?channels=bitcoin).
|
||||
* Ask for help on the [BitcoinTalk](https://bitcointalk.org/) forums, in the [Technical Support board](https://bitcointalk.org/index.php?board=4.0).
|
||||
|
||||
Building
|
||||
---------------------
|
||||
The following are developer notes on how to build Bitcoin on your native platform. They are not complete guides, but include notes on the necessary libraries, compile flags, etc.
|
||||
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.
|
||||
|
||||
- [OSX Build Notes](build-osx.md)
|
||||
- [Unix Build Notes](build-unix.md)
|
||||
|
@ -50,7 +50,7 @@ The following are developer notes on how to build Bitcoin on your native platfor
|
|||
|
||||
Development
|
||||
---------------------
|
||||
The Bitcoin repo's [root README](https://github.com/bitcoin/bitcoin/blob/master/README.md) contains relevant information on the development process and automated testing.
|
||||
The Dogecoin repo's [root README](https://github.com/bitcoin/bitcoin/blob/master/README.md) contains relevant information on the development process and automated testing.
|
||||
|
||||
- [Coding Guidelines](coding.md)
|
||||
- [Multiwallet Qt Development](multiwallet-qt.md)
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
Bitcoin 0.9.0rc1 BETA
|
||||
Dogecoin 0.9.0rc1 BETA
|
||||
|
||||
Copyright (c) 2009-2014 Bitcoin Core Developers
|
||||
|
||||
|
@ -11,7 +11,7 @@ cryptographic software written by Eric Young (eay@cryptsoft.com).
|
|||
|
||||
Intro
|
||||
-----
|
||||
Bitcoin is a free open source peer-to-peer electronic cash system that is
|
||||
Dogecoin is a free open source peer-to-peer electronic cash system that is
|
||||
completely decentralized, without the need for a central server or trusted
|
||||
parties. Users hold the crypto keys to their own money and transact directly
|
||||
with each other, with the help of a P2P network to check for double-spending.
|
||||
|
@ -21,11 +21,11 @@ Setup
|
|||
-----
|
||||
Unpack the files into a directory and run bitcoin-qt.exe.
|
||||
|
||||
Bitcoin Core is the original Bitcoin client and it builds the backbone of the network.
|
||||
However, it downloads and stores the entire history of Bitcoin transactions;
|
||||
Dogecoin Core is the original Dogecoin client and it builds the backbone of the network.
|
||||
However, it downloads and stores the entire history of Dogecoin transactions;
|
||||
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.
|
||||
|
||||
See the bitcoin wiki at:
|
||||
See the Dogecoin wiki at:
|
||||
https://en.bitcoin.it/wiki/Main_Page
|
||||
for more help and information.
|
||||
|
|
|
@ -72,7 +72,7 @@ MSYS shell:
|
|||
mkdir miniupnpc
|
||||
cp *.h miniupnpc/
|
||||
|
||||
Bitcoin
|
||||
Dogecoin
|
||||
-------
|
||||
MSYS shell:
|
||||
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
Mac OS X Build Instructions and Notes
|
||||
====================================
|
||||
This guide will show you how to build bitcoind(headless client) for OSX.
|
||||
This guide will show you how to build dogecoind(headless client) for OSX.
|
||||
|
||||
Notes
|
||||
-----
|
||||
|
@ -52,14 +52,14 @@ Optional: install Qt4
|
|||
|
||||
sudo port install qt4-mac qrencode protobuf-cpp
|
||||
|
||||
### Building `bitcoind`
|
||||
### Building `dogecoind`
|
||||
|
||||
1. Clone the github tree to get the source code and go into the directory.
|
||||
|
||||
git clone git@github.com:bitcoin/bitcoin.git bitcoin
|
||||
cd bitcoin
|
||||
git clone git@github.com:dogecoin/dogecoin.git dogecoin
|
||||
cd dogecoin
|
||||
|
||||
2. Build bitcoind (and Bitcoin-Qt, if configured):
|
||||
2. Build dogecoind (and Dogecoin-Qt, if configured):
|
||||
|
||||
./autogen.sh
|
||||
./configure
|
||||
|
@ -88,14 +88,14 @@ If not, you can ensure that the Homebrew OpenSSL is correctly linked by running
|
|||
|
||||
Rerunning "openssl version" should now return the correct version.
|
||||
|
||||
### Building `bitcoind`
|
||||
### Building `dogecoind`
|
||||
|
||||
1. Clone the github tree to get the source code and go into the directory.
|
||||
|
||||
git clone https://github.com/bitcoin/bitcoin.git
|
||||
cd bitcoin
|
||||
git clone https://github.com/dogecoin/dogecoin.git
|
||||
cd dogecoin
|
||||
|
||||
2. Build bitcoind:
|
||||
2. Build dogecoind:
|
||||
|
||||
./autogen.sh
|
||||
./configure
|
||||
|
@ -107,11 +107,11 @@ Rerunning "openssl version" should now return the correct version.
|
|||
|
||||
Creating a release build
|
||||
------------------------
|
||||
You can ignore this section if you are building `bitcoind` for your own use.
|
||||
You can ignore this section if you are building `dogecoind` for your own use.
|
||||
|
||||
bitcoind/bitcoin-cli binaries are not included in the Bitcoin-Qt.app bundle.
|
||||
dogecoind/dogecoin-cli binaries are not included in the Dogecoin-Qt.app bundle.
|
||||
|
||||
If you are building `bitcoind` or `Bitcoin-Qt` for others, your build machine should be set up
|
||||
If you are building `dogecoind` or `Dogecoin-Qt` for others, your build machine should be set up
|
||||
as follows for maximum compatibility:
|
||||
|
||||
All dependencies should be compiled with these flags:
|
||||
|
@ -132,29 +132,29 @@ As of December 2012, the `boost` port does not obey `macosx_deployment_target`.
|
|||
Download `http://gavinandresen-bitcoin.s3.amazonaws.com/boost_macports_fix.zip`
|
||||
for a fix.
|
||||
|
||||
Once dependencies are compiled, see release-process.md for how the Bitcoin-Qt.app
|
||||
Once dependencies are compiled, see release-process.md for how the Dogecoin-Qt.app
|
||||
bundle is packaged and signed to create the .dmg disk image that is distributed.
|
||||
|
||||
Running
|
||||
-------
|
||||
|
||||
It's now available at `./bitcoind`, provided that you are still in the `src`
|
||||
It's now available at `./dogecoind`, provided that you are still in the `src`
|
||||
directory. We have to first create the RPC configuration file, though.
|
||||
|
||||
Run `./bitcoind` to get the filename where it should be put, or just try these
|
||||
Run `./dogecoind` to get the filename where it should be put, or just try these
|
||||
commands:
|
||||
|
||||
echo -e "rpcuser=bitcoinrpc\nrpcpassword=$(xxd -l 16 -p /dev/urandom)" > "/Users/${USER}/Library/Application Support/Bitcoin/bitcoin.conf"
|
||||
chmod 600 "/Users/${USER}/Library/Application Support/Bitcoin/bitcoin.conf"
|
||||
echo -e "rpcuser=dogecoinrpc\nrpcpassword=$(xxd -l 16 -p /dev/urandom)" > "/Users/${USER}/Library/Application Support/Dogecoin/dogecoin.conf"
|
||||
chmod 600 "/Users/${USER}/Library/Application Support/Dogecoin/dogecoin.conf"
|
||||
|
||||
When next you run it, it will start downloading the blockchain, but it won't
|
||||
output anything while it's doing this. This process may take several hours;
|
||||
you can monitor its process by looking at the debug.log file, like this:
|
||||
|
||||
tail -f $HOME/Library/Application\ Support/Bitcoin/debug.log
|
||||
tail -f $HOME/Library/Application\ Support/Dogecoin/debug.log
|
||||
|
||||
Other commands:
|
||||
|
||||
./bitcoind -daemon # to start the bitcoin daemon.
|
||||
./bitcoin-cli --help # for a list of command-line options.
|
||||
./bitcoin-cli help # When the daemon is running, to get a list of RPC commands
|
||||
./dogecoind -daemon # to start the dogecoin daemon.
|
||||
./dogecoin-cli --help # for a list of command-line options.
|
||||
./dogecoin-cli help # When the daemon is running, to get a list of RPC commands
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
UNIX BUILD NOTES
|
||||
====================
|
||||
Some notes on how to build Bitcoin in Unix.
|
||||
Some notes on how to build Dogecoin in Unix.
|
||||
|
||||
To Build
|
||||
---------------------
|
||||
|
@ -101,7 +101,7 @@ Optional:
|
|||
Dependencies for the GUI: Ubuntu & Debian
|
||||
-----------------------------------------
|
||||
|
||||
If you want to build Bitcoin-Qt, make sure that the required packages for Qt development
|
||||
If you want to build Dogecoin-Qt, make sure that the required packages for Qt development
|
||||
are installed. Either Qt 4 or Qt 5 are necessary to build the GUI.
|
||||
If both Qt 4 and Qt 5 are installed, Qt 4 will be used. Pass `--with-gui=qt5` to configure to choose Qt5.
|
||||
To build without GUI pass `--without-gui`.
|
||||
|
|
|
@ -112,9 +112,9 @@ repackage gitian builds for release as stand-alone zip/tar/installer exe
|
|||
export QTDIR=/opt/local/share/qt4 # needed to find translations/qt_*.qm files
|
||||
T=$(contrib/qt_translations.py $QTDIR/translations src/qt/locale)
|
||||
export CODESIGNARGS='--keychain ...path_to_keychain --sign "Developer ID Application: BITCOIN FOUNDATION, INC., THE"'
|
||||
python2.7 contrib/macdeploy/macdeployqtplus Bitcoin-Qt.app -sign -add-qt-tr $T -dmg -fancy contrib/macdeploy/fancy.plist
|
||||
python2.7 contrib/macdeploy/macdeployqtplus Dogecoin-Qt.app -sign -add-qt-tr $T -dmg -fancy contrib/macdeploy/fancy.plist
|
||||
|
||||
Build output expected: Bitcoin-Qt.dmg
|
||||
Build output expected: Dogecoin-Qt.dmg
|
||||
|
||||
###Next steps:
|
||||
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
TOR SUPPORT IN BITCOIN
|
||||
======================
|
||||
|
||||
It is possible to run Bitcoin as a Tor hidden service, and connect to such services.
|
||||
It is possible to run Dogecoin as a Tor hidden service, and connect to such services.
|
||||
|
||||
The following directions assume you have a Tor proxy running on port 9050. Many distributions default to having a SOCKS proxy listening on port 9050, but others may not. In particular, the Tor Browser Bundle defaults to listening on a random port. See [Tor Project FAQ:TBBSocksPort](https://www.torproject.org/docs/faq.html.en#TBBSocksPort) for how to properly
|
||||
configure Tor.
|
||||
|
@ -10,7 +10,7 @@ configure Tor.
|
|||
1. Run bitcoin behind a Tor proxy
|
||||
---------------------------------
|
||||
|
||||
The first step is running Bitcoin behind a Tor proxy. This will already make all
|
||||
The first step is running Dogecoin behind a Tor proxy. This will already make all
|
||||
outgoing connections be anonymized, but more is possible.
|
||||
|
||||
-socks=5 SOCKS5 supports connecting-to-hostname, which can be used instead
|
||||
|
|
Loading…
Reference in a new issue