Update references of 'bitcoin' to 'dogecoin'.
Update references of 'litecoin' to 'dogecoin'. Fix spelling error of 'anonimized' to 'anonymized'.
This commit is contained in:
iglvzx
parent
2ee5cb3396
commit
e15a9342f8
|
|
@ -1,7 +1,9 @@
|
|||
Litecoin 0.6 BETA
|
||||
DogeCoin 0.6 BETA
|
||||
|
||||
Copyright (c) 2009-2012 Bitcoin Developers
|
||||
Copyright (c) 2011-2012 Litecoin Developers
|
||||
Copyright (c) 2013 DogeCoin Developers
|
||||
|
||||
Distributed under the MIT/X11 software license, see the accompanying
|
||||
file COPYING or http://www.opensource.org/licenses/mit-license.php.
|
||||
This product includes software developed by the OpenSSL Project for use in
|
||||
|
|
@ -11,7 +13,7 @@ cryptographic software written by Eric Young (eay@cryptsoft.com).
|
|||
|
||||
Intro
|
||||
-----
|
||||
Litecoin 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.
|
||||
|
|
@ -19,17 +21,17 @@ with each other, with the help of a P2P network to check for double-spending.
|
|||
|
||||
Setup
|
||||
-----
|
||||
Unpack the files into a directory and run litecoin-qt.exe.
|
||||
Unpack the files into a directory and run dogecoin-qt.exe.
|
||||
|
||||
If you have Microsoft Security Essentials, you need to add litecoin-qt.exe to its
|
||||
If you have Microsoft Security Essentials, you need to add dogecoin-qt.exe to its
|
||||
"Excluded processes" list. Microsoft Security Essentials->Settings tab,
|
||||
select Excluded processes, press Add, select litecoin-qt.exe, OK, Save changes.
|
||||
select Excluded processes, press Add, select dogecoin-qt.exe, OK, Save changes.
|
||||
|
||||
The software automatically finds other nodes to connect to. You can
|
||||
enable Universal Plug and Play using a menu entry or set your firewall
|
||||
to forward port 9333 (TCP) to your computer so you can receive
|
||||
incoming connections. Litecoin works without incoming connections,
|
||||
but allowing incoming connections helps the Litecoin network.
|
||||
incoming connections. DogeCoin works without incoming connections,
|
||||
but allowing incoming connections helps the DogeCoin network.
|
||||
|
||||
See the bitcoin wiki at:
|
||||
https://en.bitcoin.it/wiki/Main_Page
|
||||
|
|
|
|||
29
doc/Tor.txt
29
doc/Tor.txt
|
|
@ -1,7 +1,7 @@
|
|||
TOR SUPPORT IN BITCOIN
|
||||
TOR SUPPORT IN DOGECOIN
|
||||
======================
|
||||
|
||||
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 assumes 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.
|
||||
|
|
@ -10,11 +10,11 @@ https://www.torproject.org/docs/faq.html.en#TBBSocksPort for how to properly
|
|||
configure Tor.
|
||||
|
||||
|
||||
1. Run bitcoin behind a Tor proxy
|
||||
1. Run dogecoin behind a Tor proxy
|
||||
---------------------------------
|
||||
|
||||
The first step is running Bitcoin behind a Tor proxy. This will already make all
|
||||
outgoing connections be anonimized, but more is possible.
|
||||
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
|
||||
of doing a (leaking) local DNS lookup. SOCKS5 is the default,
|
||||
|
|
@ -43,26 +43,26 @@ outgoing connections be anonimized, but more is possible.
|
|||
|
||||
In a typical situation, this suffices to run behind a Tor proxy:
|
||||
|
||||
./bitcoin -proxy=127.0.0.1:9050
|
||||
./dogecoind -proxy=127.0.0.1:9050
|
||||
|
||||
|
||||
2. Run a bitcoin hidden server
|
||||
2. Run a dogecoin hidden server
|
||||
------------------------------
|
||||
|
||||
If you configure your Tor system accordingly, it is possible to make your node also
|
||||
reachable from the Tor network. Add these lines to your /etc/tor/torrc (or equivalent
|
||||
config file):
|
||||
|
||||
HiddenServiceDir /var/lib/tor/bitcoin-service/
|
||||
HiddenServiceDir /var/lib/tor/dogecoin-service/
|
||||
HiddenServicePort 9333 127.0.0.1:9333
|
||||
|
||||
The directory can be different of course, but (both) 9333's should be equal to your
|
||||
bitcoind's P2P listen port (9333 by default).
|
||||
dogecoind's P2P listen port (9333 by default).
|
||||
|
||||
-externalip=X You can tell bitcoin about its publicly reachable address using
|
||||
-externalip=X You can tell dogecoin about its publicly reachable address using
|
||||
this option, and this can be a .onion address. Given the above
|
||||
configuration, you can find your onion address in
|
||||
/var/lib/tor/bitcoin-service/hostname. Onion addresses are given
|
||||
/var/lib/tor/dogecoin-service/hostname. Onion addresses are given
|
||||
preference for your node to advertize itself with, for connections
|
||||
coming from unroutable addresses (such as 127.0.0.1, where the
|
||||
Tor proxy typically runs).
|
||||
|
|
@ -79,18 +79,17 @@ bitcoind's P2P listen port (9333 by default).
|
|||
|
||||
In a typical situation, where you're only reachable via Tor, this should suffice:
|
||||
|
||||
./bitcoind -proxy=127.0.0.1:9050 -externalip=57qr3yd1nyntf5k.onion -listen
|
||||
./dogecoind -proxy=127.0.0.1:9050 -externalip=57qr3yd1nyntf5k.onion -listen
|
||||
|
||||
(obviously replace the Onion address with your own). If you don't care too much
|
||||
about hiding your node, and want to be reachable on IPv4 as well, additionally
|
||||
specify:
|
||||
|
||||
./bitcoind ... -discover
|
||||
./dogecoind ... -discover
|
||||
|
||||
and open port 9333 on your firewall (or use -upnp).
|
||||
|
||||
If you only want to use Tor to reach onion addresses, but not use it as a proxy
|
||||
for normal IPv4/IPv6 communication, use:
|
||||
|
||||
./bitcoin -tor=127.0.0.1:9050 -externalip=57qr3yd1nyntf5k.onion -discover
|
||||
|
||||
./dogecoind -tor=127.0.0.1:9050 -externalip=57qr3yd1nyntf5k.onion -discover
|
||||
|
|
|
|||
|
|
@ -1,5 +1,7 @@
|
|||
Copyright (c) 2009-2012 Bitcoin Developers
|
||||
Copyright (c) 2011-2012 Litecoin Developers
|
||||
Copyright (c) 2013 DogeCoin Developers
|
||||
|
||||
Distributed under the MIT/X11 software license, see the accompanying
|
||||
file COPYING or http://www.opensource.org/licenses/mit-license.php.
|
||||
This product includes software developed by the OpenSSL Project for use in
|
||||
|
|
@ -8,7 +10,7 @@ cryptographic software written by Eric Young (eay@cryptsoft.com) and UPnP
|
|||
software written by Thomas Bernard.
|
||||
|
||||
|
||||
See readme-qt.rst for instructions on building Litecoin-QT, the
|
||||
See readme-qt.rst for instructions on building DogeCoin-QT, the
|
||||
graphical user interface.
|
||||
|
||||
WINDOWS BUILD NOTES
|
||||
|
|
@ -77,9 +79,9 @@ make -f Makefile.mingw
|
|||
mkdir miniupnpc
|
||||
cp *.h miniupnpc/
|
||||
|
||||
Litecoin
|
||||
DogeCoin
|
||||
-------
|
||||
DOS prompt:
|
||||
cd \litecoin\src
|
||||
cd \dogecoin\src
|
||||
mingw32-make -f makefile.mingw
|
||||
strip litecoind.exe
|
||||
strip dogecoind.exe
|
||||
|
|
|
|||
|
|
@ -90,7 +90,7 @@ in 500ms.
|
|||
ThreadRPCServer : Remote procedure call handler, listens on port 9332
|
||||
for connections and services them.
|
||||
|
||||
ThreadBitcoinMiner : Generates litecoins
|
||||
ThreadBitcoinMiner : Generates dogecoins
|
||||
|
||||
ThreadMapPort : Universal plug-and-play startup/shutdown
|
||||
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ handle those translations.
|
|||
Files and Folders
|
||||
-----------------
|
||||
|
||||
### bitcoin-qt.pro
|
||||
### dogecoin-qt.pro
|
||||
|
||||
This file takes care of generating `.qm` files from `.ts` files. It is mostly
|
||||
automated.
|
||||
|
|
|
|||
Loading…
Reference in a new issue