diff options
Diffstat (limited to 'doc')
36 files changed, 287 insertions, 287 deletions
diff --git a/doc/Building-Dogecoin-1.14-for-Mac.md b/doc/Building-Dogecoin-1.14-for-Mac.md index 22e2b0fe9..8fcb1d28a 100644 --- a/doc/Building-Dogecoin-1.14-for-Mac.md +++ b/doc/Building-Dogecoin-1.14-for-Mac.md @@ -1,4 +1,4 @@ -### Building dogecoin-qt 1.14 on modern macs. ###
+### Building discoin-qt 1.14 on modern macs. ###
Note that this requires changes made by michilumin on the 1.14-dev branch as well as some changes to BDB.
@@ -6,11 +6,11 @@ Tested on OSX 10.11 El Capitan, 10.13 High Sierra and 11.1 Big Sur. **Paper wallet printing support seems to work fine through this method as well.**
-### Clone dogecoin locally, or check it out, etc. ###
+### Clone discoin locally, or check it out, etc. ###
For this purpose, just indicating the 1.14-branding branch in my repo.
- $git clone -b 1.14-branding --single-branch https://github.com/michilumin/dogecoin.git
+ $git clone -b 1.14-branding --single-branch https://github.com/michilumin/discoin.git
### Set up OSX basic build dependencies. ##
@@ -52,16 +52,16 @@ Patch bdb 5.1.29 from our patchfiles $cd src
$cd dbinc
- $patch -b atomic.h ~/dogecoin/depends/patches/bdb-5.1.29-clang-osx/atomic.h.patch
+ $patch -b atomic.h ~/discoin/depends/patches/bdb-5.1.29-clang-osx/atomic.h.patch
$cd ..
$cd mp
- $patch -b mp_fget.c ~/dogecoin/depends/patches/bdb-5.1.29-clang-osx/mp_fget.c.patch
- $patch -b mp_mvcc.c ~/dogecoin/depends/patches/bdb-5.1.29-clang-osx/mp_mvcc.c.patch
- $patch -b mp_region.c ~/dogecoin/depends/patches/bdb-5.1.29-clang-osx/mp_region.c.patch
+ $patch -b mp_fget.c ~/discoin/depends/patches/bdb-5.1.29-clang-osx/mp_fget.c.patch
+ $patch -b mp_mvcc.c ~/discoin/depends/patches/bdb-5.1.29-clang-osx/mp_mvcc.c.patch
+ $patch -b mp_region.c ~/discoin/depends/patches/bdb-5.1.29-clang-osx/mp_region.c.patch
$cd ..
$cd mutex
- $patch -b mut_method.c ~/dogecoin/depends/patches/bdb-5.1.29-clang-osx/mut_method.c.patch
- $patch -b mut_tas.c ~/dogecoin/depends/patches/bdb-5.1.29-clang-osx/mut_tas.c.patch
+ $patch -b mut_method.c ~/discoin/depends/patches/bdb-5.1.29-clang-osx/mut_method.c.patch
+ $patch -b mut_tas.c ~/discoin/depends/patches/bdb-5.1.29-clang-osx/mut_tas.c.patch
Build BDB 5.1.29
@@ -93,7 +93,7 @@ Build BDB 5.1.29 ### Go back to your Dogecoin repo ###
- $cd ~/dogecoin
+ $cd ~/discoin
$./autogen.sh
$./configure --with-gui=qt5 --with-qrcode=yes
$make
@@ -106,7 +106,7 @@ Go have another beverage. Run it.
- $/usr/local/bin/dogecoin-qt
+ $/usr/local/bin/discoin-qt
diff --git a/doc/FAQ.md b/doc/FAQ.md index d09d60bba..bed5c2178 100644 --- a/doc/FAQ.md +++ b/doc/FAQ.md @@ -1,6 +1,6 @@ ## Very Much Frequently Asked Questions ❓ -### How much doge can exist? – So many puppies! 🐕 +### How much dis can exist? – So many puppies! 🐕 Early 2015 (approximately a year and a half after release) there were approximately 100,000,000,000 coins. Each subsequent block will grant 10,000 coins to encourage miners to continue to diff --git a/doc/README.md b/doc/README.md index 17325b72b..691e66e5d 100644 --- a/doc/README.md +++ b/doc/README.md @@ -3,7 +3,7 @@ Dogecoin Core 0.14.2 Setup --------------------- -[Dogecoin Core](http://dogecoin.com/) is the reference Dogecoin 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. +[Dogecoin Core](http://discoin.com/) is the reference Dogecoin 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. Running --------------------- @@ -13,12 +13,12 @@ The following are some helpful notes on how to run Dogecoin on your native platf Unpack the files into a directory and run: -- `bin/dogecoin-qt` (GUI) or -- `bin/dogecoind` (headless) +- `bin/discoin-qt` (GUI) or +- `bin/discoind` (headless) ### Windows -Unpack the files into a directory, and then run dogecoin-qt.exe. +Unpack the files into a directory, and then run discoin-qt.exe. ### OS X @@ -28,7 +28,7 @@ Drag Dogecoin-Core to your applications folder, and then run Dogecoin-Core. * See the documentation at the [Bitcoin Wiki](https://en.bitcoin.it/wiki/Main_Page) for help and more information. -* Ask for help on [#dogecoin](http://webchat.freenode.net?channels=dogecoin) on Freenode. If you don't have an IRC client use [webchat here](http://webchat.freenode.net?channels=dogecoin). +* Ask for help on [#discoin](http://webchat.freenode.net?channels=discoin) on Freenode. If you don't have an IRC client use [webchat here](http://webchat.freenode.net?channels=discoin). * Ask for help on the [BitcoinTalk](https://bitcointalk.org/) forums, in the [Dogecoin thread](https://bitcointalk.org/index.php?topic=361813.0). Building @@ -59,7 +59,7 @@ The Dogecoin repo's [root README](/README.md) contains relevant information on t ### Resources * Discuss on the [BitcoinTalk](https://bitcointalk.org/) forums, in the [Dogecoin thread](https://bitcointalk.org/index.php?topic=361813.0). -* Discuss on [#dogecoin-dev](http://webchat.freenode.net/?channels=dogecoin-dev) on Freenode. If you don't have an IRC client use [webchat here](http://webchat.freenode.net/?channels=dogecoin-dev). +* Discuss on [#discoin-dev](http://webchat.freenode.net/?channels=discoin-dev) on Freenode. If you don't have an IRC client use [webchat here](http://webchat.freenode.net/?channels=discoin-dev). ### Miscellaneous - [Assets Attribution](assets-attribution.md) diff --git a/doc/README_osx.md b/doc/README_osx.md index ed4dfce2a..ec0cc4058 100644 --- a/doc/README_osx.md +++ b/doc/README_osx.md @@ -92,6 +92,6 @@ build process to remain somewhat deterministic. Here's how it works: that have been previously (deterministically) built in order to create a final dmg. - The Apple keyholder uses this unsigned app to create a detached signature, - using the script that is also included there. Detached signatures are available from this [repository](https://github.com/dogecoin/dogecoin-detached-sigs). + using the script that is also included there. Detached signatures are available from this [repository](https://github.com/discoin/discoin-detached-sigs). - Builders feed the unsigned app + detached signature back into Gitian. It uses the pre-built tools to recombine the pieces into a deterministic dmg. diff --git a/doc/README_windows.txt b/doc/README_windows.txt index 180ecb5f2..3de38fb94 100644 --- a/doc/README_windows.txt +++ b/doc/README_windows.txt @@ -11,7 +11,7 @@ with each other, with the help of a P2P network to check for double-spending. Setup
-----
-Unpack the files into a directory and run dogecoin-qt.exe.
+Unpack the files into a directory and run discoin-qt.exe.
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;
@@ -19,5 +19,5 @@ depending on the speed of your computer and network connection, the synchronizat process can take anywhere from a few hours to a day or more.
See the Dogecoin wiki at:
- https://www.reddit.com/r/dogecoin/wiki/dogecoincoreguide
+ https://www.reddit.com/r/discoin/wiki/discoincoreguide
for more help and information.
diff --git a/doc/REST-interface.md b/doc/REST-interface.md index c3570b390..28eda8e90 100644 --- a/doc/REST-interface.md +++ b/doc/REST-interface.md @@ -95,4 +95,4 @@ Only supports JSON as output format. Risks ------------- -Running a web browser on the same node with a REST enabled dogecoind can be a risk. Accessing prepared XSS websites could read out tx/block data of your node by placing links like `<script src="http://127.0.0.1:8332/rest/tx/1234567890.json">` which might break the nodes privacy.
\ No newline at end of file +Running a web browser on the same node with a REST enabled discoind can be a risk. Accessing prepared XSS websites could read out tx/block data of your node by placing links like `<script src="http://127.0.0.1:8332/rest/tx/1234567890.json">` which might break the nodes privacy.
\ No newline at end of file diff --git a/doc/assets-attribution.md b/doc/assets-attribution.md index a80320940..aea5c42a7 100644 --- a/doc/assets-attribution.md +++ b/doc/assets-attribution.md @@ -1,4 +1,4 @@ -The following is a list of assets used in the dogecoin source and their proper attribution. +The following is a list of assets used in the discoin source and their proper attribution. [Typicons/Stephen Hutchings](http://typicons.com) ----------------------- diff --git a/doc/benchmarking.md b/doc/benchmarking.md index b243551ad..a4c94169a 100644 --- a/doc/benchmarking.md +++ b/doc/benchmarking.md @@ -4,8 +4,8 @@ Benchmarking Dogecoin Core has an internal benchmarking framework, with benchmarks for cryptographic algorithms such as SHA1, SHA256, SHA512 and RIPEMD160. As well as the rolling bloom filter. -After compiling dogecoin-core, the benchmarks can be run with: -`src/bench/bench_dogecoin` +After compiling discoin-core, the benchmarks can be run with: +`src/bench/bench_discoin` The output will look similar to: ``` diff --git a/doc/build-nixos.md b/doc/build-nixos.md index b87e30225..c19068dfc 100644 --- a/doc/build-nixos.md +++ b/doc/build-nixos.md @@ -5,8 +5,8 @@ of the latest changes on NixOS. Clone and enter the repo: - $ git clone https://github.com/dogecoin/dogecoin - $ cd dogecoin + $ git clone https://github.com/discoin/discoin + $ cd discoin Enter the `nix-shell` environment with all the Dogecoin dependencies present: @@ -20,4 +20,4 @@ Run the build steps with flags necessary for NixOS: Start the GUI! - $ ./src/qt/dogecoin-qt + $ ./src/qt/discoin-qt diff --git a/doc/build-openbsd.md b/doc/build-openbsd.md index 64f1e01bf..6a3b48ba1 100644 --- a/doc/build-openbsd.md +++ b/doc/build-openbsd.md @@ -5,7 +5,7 @@ OpenBSD build guide (updated for OpenBSD 6.0) -This guide describes how to build dogecoind and command-line utilities on OpenBSD. +This guide describes how to build discoind and command-line utilities on OpenBSD. As OpenBSD is most common as a server OS, we will not bother with the GUI. @@ -38,14 +38,14 @@ This compiler will not overwrite the system compiler, it will be installed as `e Do not use `pkg_add boost`! The boost version installed thus is compiled using the `g++` compiler not `eg++`, which will result in a conflict between `/usr/local/lib/libestdc++.so.XX.0` and `/usr/lib/libstdc++.so.XX.0`, resulting in a test crash: - test_dogecoin:/usr/lib/libstdc++.so.57.0: /usr/local/lib/libestdc++.so.17.0 : WARNING: symbol(_ZN11__gnu_debug17_S_debug_me ssagesE) size mismatch, relink your program + test_discoin:/usr/lib/libstdc++.so.57.0: /usr/local/lib/libestdc++.so.17.0 : WARNING: symbol(_ZN11__gnu_debug17_S_debug_me ssagesE) size mismatch, relink your program ... Segmentation fault (core dumped) This makes it necessary to build boost, or at least the parts used by Dogecoin Core, manually: ``` -# Pick some path to install boost to, here we create a directory within the dogecoin directory +# Pick some path to install boost to, here we create a directory within the discoin directory BITCOIN_ROOT=$(pwd) BOOST_PREFIX="${BITCOIN_ROOT}/boost" mkdir -p $BOOST_PREFIX @@ -61,7 +61,7 @@ cd boost_1_61_0 # Also here: https://gist.githubusercontent.com/laanwj/bf359281dc319b8ff2e1/raw/92250de8404b97bb99d72ab898f4a8cb35ae1ea3/patch-boost_test_impl_execution_monitor_ipp.patch patch -p0 < /usr/ports/devel/boost/patches/patch-boost_test_impl_execution_monitor_ipp -# Build w/ minimum configuration necessary for dogecoin +# Build w/ minimum configuration necessary for discoin echo 'using gcc : : eg++ : <cxxflags>"-fvisibility=hidden -fPIC" <linkflags>"" <archiver>"ar" <striper>"strip" <ranlib>"ranlib" <rc>"" : ;' > user-config.jam config_opts="runtime-link=shared threadapi=pthread threading=multi link=static variant=release --layout=tagged --build-type=complete --user-config=user-config.jam -sNO_BZIP2=1" ./bootstrap.sh --without-icu --with-libraries=chrono,filesystem,program_options,system,thread,test @@ -77,7 +77,7 @@ See "Berkeley DB" in [build_unix.md](build_unix.md) for instructions on how to b You cannot use the BerkeleyDB library from ports, for the same reason as boost above (g++/libstd++ incompatibility). ```bash -# Pick some path to install BDB to, here we create a directory within the dogecoin directory +# Pick some path to install BDB to, here we create a directory within the discoin directory BITCOIN_ROOT=$(pwd) BDB_PREFIX="${BITCOIN_ROOT}/db4" mkdir -p $BDB_PREFIX diff --git a/doc/build-osx.md b/doc/build-osx.md index 97536bbea..144191bdd 100644 --- a/doc/build-osx.md +++ b/doc/build-osx.md @@ -28,14 +28,14 @@ NOTE: Building with Qt4 is still supported, however, could result in a broken UI Build Dogecoin Core ------------------------ -1. Clone the dogecoin source code and cd into `dogecoin` +1. Clone the discoin source code and cd into `discoin` - git clone https://github.com/dogecoin/dogecoin - cd dogecoin + git clone https://github.com/discoin/discoin + cd discoin -2. Build dogecoin: +2. Build discoin: - Configure and build the headless dogecoin binaries as well as the GUI (if Qt is found). + Configure and build the headless discoin binaries as well as the GUI (if Qt is found). You can disable the GUI build by passing `--without-gui` to configure. @@ -54,15 +54,15 @@ Build Dogecoin Core Running ------- -Dogecoin Core is now available at `./src/dogecoind` +Dogecoin Core is now available at `./src/discoind` Before running, it's recommended you create an RPC configuration file. - echo -e "rpcuser=dogecoinrpc\nrpcpassword=$(xxd -l 16 -p /dev/urandom)" > "/Users/${USER}/Library/Application Support/Dogecoin/dogecoin.conf" + echo -e "rpcuser=discoinrpc\nrpcpassword=$(xxd -l 16 -p /dev/urandom)" > "/Users/${USER}/Library/Application Support/Dogecoin/discoin.conf" - chmod 600 "/Users/${USER}/Library/Application Support/Dogecoin/dogecoin.conf" + chmod 600 "/Users/${USER}/Library/Application Support/Dogecoin/discoin.conf" -The first time you run dogecoind, it will start downloading the blockchain. This process could take several hours. +The first time you run discoind, it will start downloading the blockchain. This process could take several hours. You can monitor the download process by looking at the debug.log file: @@ -71,20 +71,20 @@ You can monitor the download process by looking at the debug.log file: Other commands: ------- - ./src/dogecoind -daemon # Starts the dogecoin daemon. - ./src/dogecoin-cli --help # Outputs a list of command-line options. - ./src/dogecoin-cli help # Outputs a list of RPC commands when the daemon is running. + ./src/discoind -daemon # Starts the discoin daemon. + ./src/discoin-cli --help # Outputs a list of command-line options. + ./src/discoin-cli help # Outputs a list of RPC commands when the daemon is running. Using Qt Creator as IDE ------------------------ -You can use Qt Creator as an IDE, for dogecoin development. +You can use Qt Creator as an IDE, for discoin development. Download and install the community edition of [Qt Creator](https://www.qt.io/download/). Uncheck everything except Qt Creator during the installation process. 1. Make sure you installed everything through Homebrew mentioned above 2. Do a proper ./configure --enable-debug 3. In Qt Creator do "New Project" -> Import Project -> Import Existing Project -4. Enter "dogecoin-qt" as project name, enter src/qt as location +4. Enter "discoin-qt" as project name, enter src/qt as location 5. Leave the file selection as it is 6. Confirm the "summary page" 7. In the "Projects" tab select "Manage Kits..." @@ -97,4 +97,4 @@ Notes * Tested on OS X 10.8 through 10.12 on 64-bit Intel processors only. -* Building with downloaded Qt binaries is not officially supported. See the notes in [#7714](https://github.com/dogecoin/dogecoin/issues/7714) +* Building with downloaded Qt binaries is not officially supported. See the notes in [#7714](https://github.com/discoin/discoin/issues/7714) diff --git a/doc/build-unix.md b/doc/build-unix.md index 21927e149..7e01098d7 100644 --- a/doc/build-unix.md +++ b/doc/build-unix.md @@ -70,7 +70,7 @@ sudo apt-get install libboost-system-dev libboost-filesystem-dev libboost-chrono **Optional dependencies** : ```bash -# Qt (required for dogecoin-qt GUI) +# Qt (required for discoin-qt GUI) sudo apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler libqrencode-dev # BerkeleyDB (version 5.3) @@ -85,7 +85,7 @@ sudo apt-get install libminiupnpc-dev ## Build steps -According to installed dependencies, the following steps will compile `dogecoind`, `dogecoin-cli` and `dogecoin-qt`. +According to installed dependencies, the following steps will compile `discoind`, `discoin-cli` and `discoin-qt`. ```bash ./autogen.sh @@ -100,7 +100,7 @@ See [Build configuration](#build-configuration) for extra settings. Configurations are done during the `./configure` step. Use `--help` to see all available options. #### Enable Qt GUI -Create `dogecoin-qt`, the core wallet GUI. +Create `discoin-qt`, the core wallet GUI. ```bash ./configure --with-gui ``` @@ -188,7 +188,7 @@ Hardening enables the following features: To test that you have built PIE executable, install scanelf, part of paxutils, and use: - `scanelf -e ./dogecoin` + `scanelf -e ./discoin` The output should contain: @@ -202,7 +202,7 @@ Hardening enables the following features: executable without the non-executable stack protection. To verify that the stack is non-executable after compiling, use: - `scanelf -e ./dogecoin` + `scanelf -e ./discoin` the output should contain: `STK/REL/PTL RW- R-- RW-` diff --git a/doc/build-windows.md b/doc/build-windows.md index 437a41a62..c766d5152 100644 --- a/doc/build-windows.md +++ b/doc/build-windows.md @@ -75,7 +75,7 @@ For Ubuntu 18.04 and 20.04, set the default mingw32 g++ compiler option to posix ...Choose the "posix" (vs 'auto' or 'win32') option, and continue. Note that for WSL v1 the Dogecoin Core source path MUST be somewhere in the default mount file system, for -example /usr/src/dogecoin, AND not under, for example, /mnt/d/dogecoin. +example /usr/src/discoin, AND not under, for example, /mnt/d/discoin. If this is not the case the dependency autoconf scripts will fail (silently.) This means you cannot use a directory that is located directly on the host Windows file system to perform the build. @@ -128,6 +128,6 @@ Installation After building using the Windows subsystem it can be useful to copy the compiled executables to a directory on the windows drive in the same directory structure as they appear in the release `.zip` archive. This can be done in the following -way. This will install to `c:\workspace\dogecoin`, for example: +way. This will install to `c:\workspace\discoin`, for example: - make install DESTDIR=/mnt/c/workspace/dogecoin + make install DESTDIR=/mnt/c/workspace/discoin diff --git a/doc/developer-notes.md b/doc/developer-notes.md index 2cea300b8..55aadd343 100644 --- a/doc/developer-notes.md +++ b/doc/developer-notes.md @@ -128,7 +128,7 @@ to see it. **testnet and regtest modes** -Run with the -testnet option to run with "play dogecoins" on the test network, if you +Run with the -testnet option to run with "play discoins" on the test network, if you are testing multi-machine code that needs to operate across the internet. If you are testing something that can run on one machine, run with the -regtest option. @@ -186,7 +186,7 @@ Threads - ThreadRPCServer : Remote procedure call handler, listens on port 22555 for connections and services them. -- DogecoinMiner : Generates dogecoins (if wallet is enabled). +- DogecoinMiner : Generates discoins (if wallet is enabled). - Shutdown : Does an orderly shutdown of everything. @@ -490,7 +490,7 @@ Git and GitHub tips [remote "upstream-pull"] fetch = +refs/pull/*:refs/remotes/upstream-pull/* - url = [email protected]:dogecoin/dogecoin.git + url = [email protected]:discoin/discoin.git This will add an `upstream-pull` remote to your git repository, which can be fetched using `git fetch --all` or `git fetch upstream-pull`. Afterwards, you can use `upstream-pull/NUMBER/head` in arguments to `git show`, diff --git a/doc/dnsseed-policy.md b/doc/dnsseed-policy.md index fa0e58e87..9c0afadb4 100644 --- a/doc/dnsseed-policy.md +++ b/doc/dnsseed-policy.md @@ -44,11 +44,11 @@ related to the DNS seed operation. If these expectations cannot be satisfied the operator should discontinue providing services and contact the active Dogecoin Core development team as well as posting on -[Dogecoin Dev](https://reddit.com/r/dogecoindev). +[Dogecoin Dev](https://reddit.com/r/discoindev). Behavior outside of these expectations may be reasonable in some situations but should be discussed in public in advance. See also ---------- -- [dogecoin-seeder](https://github.com/langerhans/dogecoin-seeder) is a reference implementation of a DNS seed. +- [discoin-seeder](https://github.com/langerhans/discoin-seeder) is a reference implementation of a DNS seed. diff --git a/doc/files.md b/doc/files.md index b090da9fb..dd49d119a 100644 --- a/doc/files.md +++ b/doc/files.md @@ -1,14 +1,14 @@ * banlist.dat: stores the IPs/Subnets of banned nodes -* dogecoin.conf: contains configuration settings for dogecoind or dogecoin-qt -* dogecoind.pid: stores the process id of dogecoind while running +* discoin.conf: contains configuration settings for discoind or discoin-qt +* discoind.pid: stores the process id of discoind while running * blocks/blk000??.dat: block data (custom, 128 MiB per file); since 0.8.0 * blocks/rev000??.dat; block undo data (custom); since 0.8.0 (format changed since pre-0.8) * blocks/index/*; block index (LevelDB); since 0.8.0 * chainstate/*; block chain state database (LevelDB); since 0.8.0 * database/*: BDB database environment; only used for wallet since 0.8.0 * db.log: wallet database log file -* debug.log: contains debug information and general logging generated by dogecoind or dogecoin-qt +* debug.log: contains debug information and general logging generated by discoind or discoin-qt * fee_estimates.dat: stores statistics used to estimate minimum transaction fees and priorities required for confirmation; since 0.10.0 * mempool.dat: dump of the mempool's transactions; since 0.14.0. * peers.dat: peer IP address database (custom format); since 0.7.0 diff --git a/doc/fuzzing.md b/doc/fuzzing.md index 65cc753b8..a8dba5428 100644 --- a/doc/fuzzing.md +++ b/doc/fuzzing.md @@ -1,7 +1,7 @@ Fuzz-testing Dogecoin Core ========================== -A special test harness `test_dogecoin_fuzzy` is provided to provide an easy +A special test harness `test_discoin_fuzzy` is provided to provide an easy entry point for fuzzers and the like. In this document we'll describe how to use it with AFL. @@ -26,7 +26,7 @@ To build Dogecoin Core using AFL instrumentation (this assumes that the ./configure --disable-ccache --disable-shared --enable-tests CC=${AFLPATH}/afl-gcc CXX=${AFLPATH}/afl-g++ export AFL_HARDEN=1 cd src/ -make test/test_dogecoin_fuzzy +make test/test_discoin_fuzzy ``` We disable ccache because we don't want to pollute the ccache with instrumented objects, and similarly don't want to use non-instrumented cached objects linked diff --git a/doc/gitian-building.md b/doc/gitian-building.md index 33348379c..d4fb7f286 100644 --- a/doc/gitian-building.md +++ b/doc/gitian-building.md @@ -11,7 +11,7 @@ the same, tested dependencies are used and statically built into the executable. Multiple developers build the source code by following a specific descriptor ("recipe"), cryptographically sign the result, and upload the resulting signature. These results are compared and only if they match, the build is accepted and uploaded -to dogecoin.com. +to discoin.com. More independent Gitian builders are needed, which is why this guide exists. It is preferred you follow these steps yourself instead of using someone else's @@ -26,7 +26,7 @@ Table of Contents - [Installing Gitian](#installing-gitian) - [Setting up the Gitian image](#setting-up-the-gitian-image) - [Getting and building the inputs](#getting-and-building-the-inputs) -- [Building Dogecoin Core](#building-dogecoin-core) +- [Building Dogecoin Core](#building-discoin-core) - [Building an alternative repository](#building-an-alternative-repository) - [Signing externally](#signing-externally) - [Uploading signatures](#uploading-signatures) @@ -305,12 +305,12 @@ cd .. **Note**: When sudo asks for a password, enter the password for the user *debian* not for *root*. -Clone the git repositories for dogecoin and Gitian. +Clone the git repositories for discoin and Gitian. ```bash git clone https://github.com/devrandom/gitian-builder.git -git clone https://github.com/dogecoin/dogecoin.git -git clone https://github.com/dogecoin/gitian.sigs.git +git clone https://github.com/discoin/discoin.git +git clone https://github.com/discoin/gitian.sigs.git ``` Setting up the Gitian image @@ -339,7 +339,7 @@ Getting and building the inputs At this point you have two options, you can either use the automated script (found in [contrib/gitian-build.sh](/contrib/gitian-build.sh)) or you could manually do everything by following this guide. If you're using the automated script, then run it with the "--setup" command. Afterwards, run it with the "--build" command (example: "contrib/gitian-building.sh -b signer 0.13.0"). Otherwise ignore this. Follow the instructions in [doc/release-process.md](release-process.md#fetch-and-create-inputs-first-time-or-when-dependency-versions-change) -in the dogecoin repository under 'Fetch and create inputs' to install sources which require +in the discoin repository under 'Fetch and create inputs' to install sources which require manual intervention. Also optionally follow the next step: 'Seed the Gitian sources cache and offline git repositories' which will fetch the remaining files required for building offline. @@ -348,7 +348,7 @@ Building Dogecoin Core ---------------- To build Dogecoin Core (for Linux, OS X and Windows) just follow the steps under 'perform -Gitian builds' in [doc/release-process.md](release-process.md#perform-gitian-builds) in the dogecoin repository. +Gitian builds' in [doc/release-process.md](release-process.md#perform-gitian-builds) in the discoin repository. This may take some time as it will build all the dependencies needed for each descriptor. These dependencies will be cached after a successful build to avoid rebuilding them when possible. @@ -362,12 +362,12 @@ tail -f var/build.log Output from `gbuild` will look something like - Initialized empty Git repository in /home/debian/gitian-builder/inputs/dogecoin/.git/ + Initialized empty Git repository in /home/debian/gitian-builder/inputs/discoin/.git/ remote: Counting objects: 57959, done. remote: Total 57959 (delta 0), reused 0 (delta 0), pack-reused 57958 Receiving objects: 100% (57959/57959), 53.76 MiB | 484.00 KiB/s, done. Resolving deltas: 100% (41590/41590), done. - From https://github.com/dogecoin/dogecoin + From https://github.com/discoin/discoin ... (new tags, new branch etc) --- Building for trusty amd64 --- Stopping target if it is up @@ -393,18 +393,18 @@ and inputs. For example: ```bash -URL=https://github.com/laanwj/dogecoin.git +URL=https://github.com/laanwj/discoin.git COMMIT=2014_03_windows_unicode_path -./bin/gbuild --commit dogecoin=${COMMIT} --url dogecoin=${URL} ../dogecoin/contrib/gitian-descriptors/gitian-linux.yml -./bin/gbuild --commit dogecoin=${COMMIT} --url dogecoin=${URL} ../dogecoin/contrib/gitian-descriptors/gitian-win.yml -./bin/gbuild --commit dogecoin=${COMMIT} --url dogecoin=${URL} ../dogecoin/contrib/gitian-descriptors/gitian-osx.yml +./bin/gbuild --commit discoin=${COMMIT} --url discoin=${URL} ../discoin/contrib/gitian-descriptors/gitian-linux.yml +./bin/gbuild --commit discoin=${COMMIT} --url discoin=${URL} ../discoin/contrib/gitian-descriptors/gitian-win.yml +./bin/gbuild --commit discoin=${COMMIT} --url discoin=${URL} ../discoin/contrib/gitian-descriptors/gitian-osx.yml ``` Building fully offline ----------------------- For building fully offline including attaching signatures to unsigned builds, the detached-sigs repository -and the dogecoin git repository with the desired tag must both be available locally, and then gbuild must be +and the discoin git repository with the desired tag must both be available locally, and then gbuild must be told where to find them. It also requires an apt-cacher-ng which is fully-populated but set to offline mode, or manually disabling gitian-builder's use of apt-get to update the VM build environment. @@ -423,7 +423,7 @@ cd /path/to/gitian-builder LXC_ARCH=amd64 LXC_SUITE=trusty on-target -u root apt-get update LXC_ARCH=amd64 LXC_SUITE=trusty on-target -u root \ -e DEBIAN_FRONTEND=noninteractive apt-get --no-install-recommends -y install \ - $( sed -ne '/^packages:/,/[^-] .*/ {/^- .*/{s/"//g;s/- //;p}}' ../dogecoin/contrib/gitian-descriptors/*|sort|uniq ) + $( sed -ne '/^packages:/,/[^-] .*/ {/^- .*/{s/"//g;s/- //;p}}' ../discoin/contrib/gitian-descriptors/*|sort|uniq ) LXC_ARCH=amd64 LXC_SUITE=trusty on-target -u root apt-get -q -y purge grub LXC_ARCH=amd64 LXC_SUITE=trusty on-target -u root -e DEBIAN_FRONTEND=noninteractive apt-get -y dist-upgrade ``` @@ -443,12 +443,12 @@ Then when building, override the remote URLs that gbuild would otherwise pull fr ```bash cd /some/root/path/ -git clone https://github.com/dogecoin/dogecoin-detached-sigs.git +git clone https://github.com/discoin/discoin-detached-sigs.git -BTCPATH=/some/root/path/dogecoin -SIGPATH=/some/root/path/dogecoin-detached-sigs +BTCPATH=/some/root/path/discoin +SIGPATH=/some/root/path/discoin-detached-sigs -./bin/gbuild --url dogecoin=${BTCPATH},signature=${SIGPATH} ../dogecoin/contrib/gitian-descriptors/gitian-win-signer.yml +./bin/gbuild --url discoin=${BTCPATH},signature=${SIGPATH} ../discoin/contrib/gitian-descriptors/gitian-win-signer.yml ``` Signing externally @@ -463,9 +463,9 @@ When you execute `gsign` you will get an error from GPG, which can be ignored. C in `gitian.sigs` to your signing machine and do ```bash - gpg --detach-sign ${VERSION}-linux/${SIGNER}/dogecoin-linux-build.assert - gpg --detach-sign ${VERSION}-win/${SIGNER}/dogecoin-win-build.assert - gpg --detach-sign ${VERSION}-osx-unsigned/${SIGNER}/dogecoin-osx-build.assert + gpg --detach-sign ${VERSION}-linux/${SIGNER}/discoin-linux-build.assert + gpg --detach-sign ${VERSION}-win/${SIGNER}/discoin-win-build.assert + gpg --detach-sign ${VERSION}-osx-unsigned/${SIGNER}/discoin-osx-build.assert ``` This will create the `.sig` files that can be committed together with the `.assert` files to assert your @@ -475,5 +475,5 @@ Uploading signatures --------------------- After building and signing you can push your signatures (both the `.assert` and `.assert.sig` files) to the -[dogecoin/gitian.sigs](https://github.com/dogecoin/gitian.sigs/) repository, or if that's not possible create a pull +[discoin/gitian.sigs](https://github.com/discoin/gitian.sigs/) repository, or if that's not possible create a pull request. You can also mail the files to Wladimir ([email protected]) and he will commit them. diff --git a/doc/init.md b/doc/init.md index aa7102996..b5be33860 100644 --- a/doc/init.md +++ b/doc/init.md @@ -1,36 +1,36 @@ -Sample init scripts and service configuration for dogecoind +Sample init scripts and service configuration for discoind ========================================================== Sample scripts and configuration files for systemd, Upstart and OpenRC can be found in the contrib/init folder. - contrib/init/dogecoind.service: systemd service unit configuration - contrib/init/dogecoind.openrc: OpenRC compatible SysV style init script - contrib/init/dogecoind.openrcconf: OpenRC conf.d file - contrib/init/dogecoind.conf: Upstart service configuration file - contrib/init/dogecoind.init: CentOS compatible SysV style init script + contrib/init/discoind.service: systemd service unit configuration + contrib/init/discoind.openrc: OpenRC compatible SysV style init script + contrib/init/discoind.openrcconf: OpenRC conf.d file + contrib/init/discoind.conf: Upstart service configuration file + contrib/init/discoind.init: CentOS compatible SysV style init script 1. Service User --------------------------------- -All three Linux startup configurations assume the existence of a "dogecoin" user +All three Linux startup configurations assume the existence of a "discoin" user and group. They must be created before attempting to use these scripts. -The OS X configuration assumes dogecoind will be set up for the current user. +The OS X configuration assumes discoind will be set up for the current user. 2. Configuration --------------------------------- -At a bare minimum, dogecoind requires that the rpcpassword setting be set +At a bare minimum, discoind requires that the rpcpassword setting be set when running as a daemon. If the configuration file does not exist or this -setting is not set, dogecoind will shutdown promptly after startup. +setting is not set, discoind will shutdown promptly after startup. This password does not have to be remembered or typed as it is mostly used -as a fixed token that dogecoind and client programs read from the configuration +as a fixed token that discoind and client programs read from the configuration file, however it is recommended that a strong and secure password be used as this password is security critical to securing the wallet should the wallet be enabled. -If dogecoind is run with the "-server" flag (set by default), and no rpcpassword is set, +If discoind is run with the "-server" flag (set by default), and no rpcpassword is set, it will use a special cookie file for authentication. The cookie is generated with random content when the daemon starts, and deleted when it exits. Read access to this file controls who can access it through RPC. @@ -38,13 +38,13 @@ controls who can access it through RPC. By default the cookie is stored in the data directory, but it's location can be overridden with the option '-rpccookiefile'. -This allows for running dogecoind without having to do any manual configuration. +This allows for running discoind without having to do any manual configuration. `conf`, `pid`, and `wallet` accept relative paths which are interpreted as relative to the data directory. `wallet` *only* supports relative paths. For an example configuration file that describes the configuration settings, -see `contrib/debian/examples/dogecoin.conf`. +see `contrib/debian/examples/discoin.conf`. 3. Paths --------------------------------- @@ -53,22 +53,22 @@ see `contrib/debian/examples/dogecoin.conf`. All three configurations assume several paths that might need to be adjusted. -Binary: `/usr/bin/dogecoind` -Configuration file: `/etc/dogecoin/dogecoin.conf` -Data directory: `/var/lib/dogecoind` -PID file: `/var/run/dogecoind/dogecoind.pid` (OpenRC and Upstart) or `/var/lib/dogecoind/dogecoind.pid` (systemd) -Lock file: `/var/lock/subsys/dogecoind` (CentOS) +Binary: `/usr/bin/discoind` +Configuration file: `/etc/discoin/discoin.conf` +Data directory: `/var/lib/discoind` +PID file: `/var/run/discoind/discoind.pid` (OpenRC and Upstart) or `/var/lib/discoind/discoind.pid` (systemd) +Lock file: `/var/lock/subsys/discoind` (CentOS) The configuration file, PID directory (if applicable) and data directory -should all be owned by the dogecoin user and group. It is advised for security +should all be owned by the discoin user and group. It is advised for security reasons to make the configuration file and data directory only readable by the -dogecoin user and group. Access to dogecoin-cli and other dogecoind rpc clients +discoin user and group. Access to discoin-cli and other discoind rpc clients can then be controlled by group membership. 3b) Mac OS X -Binary: `/usr/local/bin/dogecoind` -Configuration file: `~/Library/Application Support/Dogecoin/dogecoin.conf` +Binary: `/usr/local/bin/discoind` +Configuration file: `~/Library/Application Support/Dogecoin/discoin.conf` Data directory: `~/Library/Application Support/Dogecoin` Lock file: `~/Library/Application Support/Dogecoin/.lock` @@ -81,19 +81,19 @@ Installing this .service file consists of just copying it to /usr/lib/systemd/system directory, followed by the command `systemctl daemon-reload` in order to update running systemd configuration. -To test, run `systemctl start dogecoind` and to enable for system startup run -`systemctl enable dogecoind` +To test, run `systemctl start discoind` and to enable for system startup run +`systemctl enable discoind` 4b) OpenRC -Rename dogecoind.openrc to dogecoind and drop it in /etc/init.d. Double +Rename discoind.openrc to discoind and drop it in /etc/init.d. Double check ownership and permissions and make it executable. Test it with -`/etc/init.d/dogecoind start` and configure it to run on startup with -`rc-update add dogecoind` +`/etc/init.d/discoind start` and configure it to run on startup with +`rc-update add discoind` 4c) Upstart (for Debian/Ubuntu based distributions) -Drop dogecoind.conf in /etc/init. Test by running `service dogecoind start` +Drop discoind.conf in /etc/init. Test by running `service discoind start` it will automatically start on reboot. NOTE: This script is incompatible with CentOS 5 and Amazon Linux 2014 as they @@ -101,22 +101,22 @@ use old versions of Upstart and do not supply the start-stop-daemon utility. 4d) CentOS -Copy dogecoind.init to /etc/init.d/dogecoind. Test by running `service dogecoind start`. +Copy discoind.init to /etc/init.d/discoind. Test by running `service discoind start`. -Using this script, you can adjust the path and flags to the dogecoind program by +Using this script, you can adjust the path and flags to the discoind program by setting the DOGECOIND and FLAGS environment variables in the file -/etc/sysconfig/dogecoind. You can also use the DAEMONOPTS environment variable here. +/etc/sysconfig/discoind. You can also use the DAEMONOPTS environment variable here. 4e) Mac OS X -Copy org.dogecoin.dogecoind.plist into ~/Library/LaunchAgents. Load the launch agent by -running `launchctl load ~/Library/LaunchAgents/org.dogecoin.dogecoind.plist`. +Copy org.discoin.discoind.plist into ~/Library/LaunchAgents. Load the launch agent by +running `launchctl load ~/Library/LaunchAgents/org.discoin.discoind.plist`. -This Launch Agent will cause dogecoind to start whenever the user logs in. +This Launch Agent will cause discoind to start whenever the user logs in. -NOTE: This approach is intended for those wanting to run dogecoind as the current user. -You will need to modify org.dogecoin.dogecoind.plist if you intend to use it as a -Launch Daemon with a dedicated dogecoin user. +NOTE: This approach is intended for those wanting to run discoind as the current user. +You will need to modify org.discoin.discoind.plist if you intend to use it as a +Launch Daemon with a dedicated discoin user. 5. Auto-respawn ----------------------------------- diff --git a/doc/man/Makefile.am b/doc/man/Makefile.am index 34dba3ebb..905359f12 100644 --- a/doc/man/Makefile.am +++ b/doc/man/Makefile.am @@ -1,13 +1,13 @@ dist_man1_MANS= if BUILD_BITCOIND - dist_man1_MANS+=dogecoind.1 + dist_man1_MANS+=discoind.1 endif if ENABLE_QT - dist_man1_MANS+=dogecoin-qt.1 + dist_man1_MANS+=discoin-qt.1 endif if BUILD_BITCOIN_UTILS - dist_man1_MANS+=dogecoin-cli.1 dogecoin-tx.1 + dist_man1_MANS+=discoin-cli.1 discoin-tx.1 endif diff --git a/doc/man/dogecoin-cli.1 b/doc/man/dogecoin-cli.1 index b4066a887..ea3613586 100644 --- a/doc/man/dogecoin-cli.1 +++ b/doc/man/dogecoin-cli.1 @@ -1,17 +1,17 @@ .\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.48.4. -.TH DOGECOIN-CLI "1" "August 2021" "dogecoin-cli v1.14.4.0" "User Commands" +.TH DOGECOIN-CLI "1" "August 2021" "discoin-cli v1.14.4.0" "User Commands" .SH NAME -dogecoin-cli \- manual page for dogecoin-cli v1.14.4.0 +discoin-cli \- manual page for discoin-cli v1.14.4.0 .SH DESCRIPTION Dogecoin Core RPC client version v1.14.4.0 .SS "Usage:" .TP -dogecoin\-cli [options] <command> [params] +discoin\-cli [options] <command> [params] Send command to Dogecoin Core .IP -dogecoin\-cli [options] \fB\-named\fR <command> [name=value] ... Send command to Dogecoin Core (with named arguments) -dogecoin\-cli [options] help List commands -dogecoin\-cli [options] help <command> Get help for a command +discoin\-cli [options] \fB\-named\fR <command> [name=value] ... Send command to Dogecoin Core (with named arguments) +discoin\-cli [options] help List commands +discoin\-cli [options] help <command> Get help for a command .SH OPTIONS .HP \-? @@ -20,7 +20,7 @@ This help message .HP \fB\-conf=\fR<file> .IP -Specify configuration file (default: dogecoin.conf) +Specify configuration file (default: discoin.conf) .HP \fB\-datadir=\fR<dir> .IP @@ -74,8 +74,8 @@ Read extra arguments from standard input, one per line until EOF/Ctrl\-D Copyright (C) 2013-2021 The Bitcoin Core and Dogecoin Core developers Please contribute if you find Dogecoin Core useful. Visit -<https://dogecoin.com> for further information about the software. -The source code is available from <https://github.com/dogecoin/dogecoin>. +<https://discoin.com> for further information about the software. +The source code is available from <https://github.com/discoin/discoin>. This is experimental software. Distributed under the MIT software license, see the accompanying file COPYING diff --git a/doc/man/dogecoin-qt.1 b/doc/man/dogecoin-qt.1 index 457ea18fc..2d224c3da 100644 --- a/doc/man/dogecoin-qt.1 +++ b/doc/man/dogecoin-qt.1 @@ -1,12 +1,12 @@ .\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.48.4. -.TH DOGECOIN-QT "1" "August 2021" "dogecoin-qt v1.14.4.0" "User Commands" +.TH DOGECOIN-QT "1" "August 2021" "discoin-qt v1.14.4.0" "User Commands" .SH NAME -dogecoin-qt \- manual page for dogecoin-qt v1.14.4.0 +discoin-qt \- manual page for discoin-qt v1.14.4.0 .SH DESCRIPTION Dogecoin Core version v1.14.4.0 (64\-bit) Usage: .IP -dogecoin\-qt [command\-line options] +discoin\-qt [command\-line options] .SH OPTIONS .HP \-? @@ -42,7 +42,7 @@ testnet: .HP \fB\-conf=\fR<file> .IP -Specify configuration file (default: dogecoin.conf) +Specify configuration file (default: discoin.conf) .HP \fB\-datadir=\fR<dir> .IP @@ -81,7 +81,7 @@ leave that many cores free, default: 0) .HP \fB\-pid=\fR<file> .IP -Specify pid file (default: dogecoind.pid) +Specify pid file (default: discoind.pid) .HP \fB\-prune=\fR<n> .IP @@ -543,8 +543,8 @@ Reset all settings changed in the GUI Copyright (C) 2013-2021 The Bitcoin Core and Dogecoin Core developers Please contribute if you find Dogecoin Core useful. Visit -<https://dogecoin.com> for further information about the software. -The source code is available from <https://github.com/dogecoin/dogecoin>. +<https://discoin.com> for further information about the software. +The source code is available from <https://github.com/discoin/discoin>. This is experimental software. Distributed under the MIT software license, see the accompanying file COPYING diff --git a/doc/man/dogecoin-tx.1 b/doc/man/dogecoin-tx.1 index 55326aeb2..1f817a1e9 100644 --- a/doc/man/dogecoin-tx.1 +++ b/doc/man/dogecoin-tx.1 @@ -1,16 +1,16 @@ .\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.48.4. -.TH DOGECOIN-TX "1" "August 2021" "dogecoin-tx v1.14.4.0" "User Commands" +.TH DOGECOIN-TX "1" "August 2021" "discoin-tx v1.14.4.0" "User Commands" .SH NAME -dogecoin-tx \- manual page for dogecoin-tx v1.14.4.0 +discoin-tx \- manual page for discoin-tx v1.14.4.0 .SH DESCRIPTION -Dogecoin Core dogecoin\-tx utility version v1.14.4.0 +Dogecoin Core discoin\-tx utility version v1.14.4.0 .SS "Usage:" .TP -dogecoin\-tx [options] <hex\-tx> [commands] -Update hex\-encoded dogecoin transaction +discoin\-tx [options] <hex\-tx> [commands] +Update hex\-encoded discoin transaction .TP -dogecoin\-tx [options] \fB\-create\fR [commands] -Create hex\-encoded dogecoin transaction +discoin\-tx [options] \fB\-create\fR [commands] +Create hex\-encoded discoin transaction .SH OPTIONS .HP \-? @@ -110,8 +110,8 @@ Set register NAME to given JSON\-STRING Copyright (C) 2013-2021 The Bitcoin Core and Dogecoin Core developers Please contribute if you find Dogecoin Core useful. Visit -<https://dogecoin.com> for further information about the software. -The source code is available from <https://github.com/dogecoin/dogecoin>. +<https://discoin.com> for further information about the software. +The source code is available from <https://github.com/discoin/discoin>. This is experimental software. Distributed under the MIT software license, see the accompanying file COPYING diff --git a/doc/man/dogecoind.1 b/doc/man/dogecoind.1 index 6d1f016ff..587ab1c0e 100644 --- a/doc/man/dogecoind.1 +++ b/doc/man/dogecoind.1 @@ -1,12 +1,12 @@ .\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.48.4. -.TH DOGECOIND "1" "August 2021" "dogecoind v1.14.4.0" "User Commands" +.TH DOGECOIND "1" "August 2021" "discoind v1.14.4.0" "User Commands" .SH NAME -dogecoind \- manual page for dogecoind v1.14.4.0 +discoind \- manual page for discoind v1.14.4.0 .SH DESCRIPTION Dogecoin Core Daemon version v1.14.4.0 .SS "Usage:" .TP -dogecoind [options] +discoind [options] Start Dogecoin Core Daemon .SH OPTIONS .HP @@ -43,7 +43,7 @@ testnet: .HP \fB\-conf=\fR<file> .IP -Specify configuration file (default: dogecoin.conf) +Specify configuration file (default: discoin.conf) .HP \fB\-daemon\fR .IP @@ -86,7 +86,7 @@ leave that many cores free, default: 0) .HP \fB\-pid=\fR<file> .IP -Specify pid file (default: dogecoind.pid) +Specify pid file (default: discoind.pid) .HP \fB\-prune=\fR<n> .IP @@ -522,8 +522,8 @@ Set the number of threads to service RPC calls (default: 4) Copyright (C) 2013-2021 The Bitcoin Core and Dogecoin Core developers Please contribute if you find Dogecoin Core useful. Visit -<https://dogecoin.com> for further information about the software. -The source code is available from <https://github.com/dogecoin/dogecoin>. +<https://discoin.com> for further information about the software. +The source code is available from <https://github.com/discoin/discoin>. This is experimental software. Distributed under the MIT software license, see the accompanying file COPYING diff --git a/doc/reduce-traffic.md b/doc/reduce-traffic.md index 4ac0a95b4..aacadc75f 100644 --- a/doc/reduce-traffic.md +++ b/doc/reduce-traffic.md @@ -3,7 +3,7 @@ Reduce Traffic Some node operators need to deal with bandwidth caps imposed by their ISPs. -By default, dogecoin-core allows up to 125 connections to different peers, 8 of +By default, discoin-core allows up to 125 connections to different peers, 8 of which are outbound. You can therefore, have at most 117 inbound connections. The default settings can result in relatively significant traffic consumption. diff --git a/doc/release-notes.md b/doc/release-notes.md index bde930ec2..6a451f235 100644 --- a/doc/release-notes.md +++ b/doc/release-notes.md @@ -1,19 +1,19 @@ Dogecoin Core version 1.14.4 is now available from: - <https://github.com/dogecoin/dogecoin/releases/tag/v1.14.4/> + <https://github.com/discoin/discoin/releases/tag/v1.14.4/> This is a new minor version release, including various bugfixes and performance improvements. It is a recommended update for all users. Please report bugs using the issue tracker at github: - <https://github.com/dogecoin/dogecoin/issues> + <https://github.com/discoin/discoin/issues> To receive security and update notifications, please watch reddit or Twitter: - * https://www.reddit.com/r/dogecoin/ + * https://www.reddit.com/r/discoin/ * @Dogecoin on Twitter for high priority announcements - * @dogecoin\_devs on Twitter for updates on development work + * @discoin\_devs on Twitter for updates on development work Compatibility ============== @@ -44,7 +44,7 @@ The main highlights for these enhancements are: * Transaction sizes are no longer rounded up to the nearest kilobyte when deciding if a transaction can be accepted from another node and in applying fee-filter requests from peers, when relaying transactions. -* The default setting shipped with dogecoin core for relay fee has been reduced +* The default setting shipped with discoin core for relay fee has been reduced to 0.001 DOGE (was: 1 DOGE). This can be changed by operators using the `-mintxrelayfee=<amount>` option. * Spam management has been delegated to miners, where currently a default fee diff --git a/doc/release-notes/RELEASE_NOTES_1.8.2.md b/doc/release-notes/RELEASE_NOTES_1.8.2.md index 7e4f5d090..f9df8736e 100644 --- a/doc/release-notes/RELEASE_NOTES_1.8.2.md +++ b/doc/release-notes/RELEASE_NOTES_1.8.2.md @@ -9,7 +9,7 @@ Dogecoin Core 1.8.2 is a bugfix release. It updates OpenSSL to 1.0.1l, mainly fi ## OpenSSL Warning -The main takeaway is that builds from http://dogecoin.com are not affected. But if you build your own version, +The main takeaway is that builds from http://discoin.com are not affected. But if you build your own version, please make sure you update to 1.8.2 **before** updating your OpenSSL! Please refer to this section in the Bitcoin Core release notes for further info: https://github.com/bitcoin/bitcoin/blob/0.9/doc/release-notes.md#openssl-warning diff --git a/doc/release-notes/RELEASE_NOTES_1_8.1.md b/doc/release-notes/RELEASE_NOTES_1_8.1.md index 9bc0a50b9..67802fd86 100644 --- a/doc/release-notes/RELEASE_NOTES_1_8.1.md +++ b/doc/release-notes/RELEASE_NOTES_1_8.1.md @@ -21,7 +21,7 @@ or similar capturing the key from memory or interfering with its generation. * Disable Transifex based translation process (not used by Dogecoin Core) * Add checkpoints around AuxPoW switchover block (371,337) * Disable connections from pre-1.8 Dogecoin Core clients -* Use HTTPS with dogechain.info +* Use HTTPS with dischain.info * Remove unreachable code introduced with AuxPoW support * "blocknotify" option now supports %i as a format parameter, which is replaced by block height * New option "maxoutconnections" to set the maximum number of outbound peer connections. Defaults to 8, minimum is 2, maximum is whatever "maxconnections" is set to (default 125). @@ -40,7 +40,7 @@ below: ## Known Issues -There is a known issue with quantities in JSON used by the RPC interface (https://github.com/dogecoin/dogecoin/issues/134). +There is a known issue with quantities in JSON used by the RPC interface (https://github.com/discoin/discoin/issues/134). This stems from the use of a floating point precision number to hold fixed precision data. Currently looking at solutions, which primarily either involve JSON which is not compliant to the specification, or making the RPC layer slightly incompatible with the conventional diff --git a/doc/release-notes/release-notes-1.14.2.md b/doc/release-notes/release-notes-1.14.2.md index 1a076ddb9..ac8fab0af 100644 --- a/doc/release-notes/release-notes-1.14.2.md +++ b/doc/release-notes/release-notes-1.14.2.md @@ -1,19 +1,19 @@ Dogecoin Core version 1.14.2 is now available from: - <https://github.com/dogecoin/dogecoin/releases/tag/v1.14.2/> + <https://github.com/discoin/discoin/releases/tag/v1.14.2/> This is a new major version release, including new features, various bugfixes and performance improvements, as well as updated translations. Please report bugs using the issue tracker at github: - <https://github.com/dogecoin/dogecoin/issues> + <https://github.com/discoin/discoin/issues> To receive security and update notifications, please watch reddit or Twitter: - * https://www.reddit.com/r/dogecoin/ + * https://www.reddit.com/r/discoin/ * @Dogecoin on Twitter for high priority announcements - * @dogecoin\_devs on Twitter for updates on development work + * @discoin\_devs on Twitter for updates on development work The developers also maintain personal Twitter accounts: diff --git a/doc/release-notes/release-notes-1.14.3.md b/doc/release-notes/release-notes-1.14.3.md index b70a3448c..0e9e20cb0 100644 --- a/doc/release-notes/release-notes-1.14.3.md +++ b/doc/release-notes/release-notes-1.14.3.md @@ -1,19 +1,19 @@ Dogecoin Core version 1.14.3 is now available from: - <https://github.com/dogecoin/dogecoin/releases/tag/v1.14.3/> + <https://github.com/discoin/discoin/releases/tag/v1.14.3/> This is a new minor version release, including various bugfixes and performance improvements. It is a recommended update for all users. Please report bugs using the issue tracker at github: - <https://github.com/dogecoin/dogecoin/issues> + <https://github.com/discoin/discoin/issues> To receive security and update notifications, please watch reddit or Twitter: - * https://www.reddit.com/r/dogecoin/ + * https://www.reddit.com/r/discoin/ * @Dogecoin on Twitter for high priority announcements - * @dogecoin\_devs on Twitter for updates on development work + * @discoin\_devs on Twitter for updates on development work The developers also maintain personal Twitter accounts: @@ -77,7 +77,7 @@ Minor changes * Set BIP65 softfork heights in chainparams.cpp. * Update package links for OSX cross compilation. -* Change IPC prefix from `bitcoin:` to `dogecoin:`. +* Change IPC prefix from `bitcoin:` to `discoin:`. * Locale independent sorting. * Corrections to Italian translation. * Refresh main and test network checkpoints and seeds. diff --git a/doc/release-notes/release-notes-1.7.0.md b/doc/release-notes/release-notes-1.7.0.md index 660c83c93..c91e3f57e 100644 --- a/doc/release-notes/release-notes-1.7.0.md +++ b/doc/release-notes/release-notes-1.7.0.md @@ -28,12 +28,12 @@ Following in the footsteps of Bitcoin (Core), the Dogecoin reference client has been rebranded as "Dogecoin Core". This helps separate its identity from Dogecoin (the network). -dogecoin-cli +discoin-cli ------------ -Where previously commands were sent to dogecoind by running -"dogecoind <command>", 1.7 adopts the model from Bitcoin Core 0.9 where there is -a separate "dogecoin-cli" executable which is used instead. This avoids the risk +Where previously commands were sent to discoind by running +"discoind <command>", 1.7 adopts the model from Bitcoin Core 0.9 where there is +a separate "discoin-cli" executable which is used instead. This avoids the risk of accidentally trying to start two daemons at the same time, for example. @@ -54,4 +54,4 @@ clients. Wallets and addresses are incompatible with the normal Dogecoin network, in order to isolate the two. As "TestDoge" is essentially valueless, it can be acquired easily for testing, -either by mining, or from a faucet such as http://testdoge.lionservers.de/ +either by mining, or from a faucet such as http://testdis.lionservers.de/ diff --git a/doc/release-notes/release-notes-1.8.0.md b/doc/release-notes/release-notes-1.8.0.md index c816ffec2..1c34439e1 100644 --- a/doc/release-notes/release-notes-1.8.0.md +++ b/doc/release-notes/release-notes-1.8.0.md @@ -25,7 +25,7 @@ menu. Ensure your existing wallet software is closed before upgrading. Note that a full reindex is required as part of the upgrade to 1.8, and this will typically take around an hour to complete. If you are running the Qt client you will be prompted to reindex when first running the software, while if you -use "dogecoind" you must run it the first time with the "-reindex" command line +use "discoind" you must run it the first time with the "-reindex" command line option. To ensure a smooth switchover to AuxPoW, 1.8 has safe mode disabled 1 hour before @@ -62,7 +62,7 @@ Dogecoin Core 1.8 adds payment protocol support, which is used to streamline pay being made to merchants. This protocol is defined in DIP0070-DIP0072, based on the BIP standards with the same -assigned numbers. DIP standards can be found at https://github.com/dogecoin/dips/ . +assigned numbers. DIP standards can be found at https://github.com/discoin/dips/ . The key differencs between the Bitcoin and Dogecoin payment protocols are that the Dogecoin payment request uses a "genesis" field containing the hash of the network's genesis block to identify networks instead of the "network" field. Further, MIME types @@ -95,5 +95,5 @@ disposed of in all cases. Tweaked trigger conditions for safe mode to take into account the much faster block time of Dogecoin compared to Bitcoin. This should lead to less false positives. -A problem in parsing mangled dogecoin: URIs under Windows has been resolved, and as -part of this work network detection for dogecoin: URIs is now more robust. +A problem in parsing mangled discoin: URIs under Windows has been resolved, and as +part of this work network detection for discoin: URIs is now more robust. diff --git a/doc/release-process.md b/doc/release-process.md index dc7eeba0f..3dbbf3f28 100644 --- a/doc/release-process.md +++ b/doc/release-process.md @@ -3,9 +3,9 @@ Release Process Before every release candidate: -* Update translations (ping wumpus on IRC) see [translation_process.md](https://github.com/dogecoin/dogecoin/blob/master/doc/translation_process.md#synchronising-translations). +* Update translations (ping wumpus on IRC) see [translation_process.md](https://github.com/discoin/discoin/blob/master/doc/translation_process.md#synchronising-translations). -* Update manpages, see [gen-manpages.sh](https://github.com/dogecoin/dogecoin/blob/master/contrib/devtools/README.md#gen-manpagessh). +* Update manpages, see [gen-manpages.sh](https://github.com/discoin/discoin/blob/master/contrib/devtools/README.md#gen-manpagessh). Before every minor and major release: @@ -21,7 +21,7 @@ Before every minor and major release: Before every major release: -* Update hardcoded [seeds](/contrib/seeds/README.md), see [this pull request](https://github.com/dogecoin/dogecoin/pull/7415) for an example. +* Update hardcoded [seeds](/contrib/seeds/README.md), see [this pull request](https://github.com/discoin/discoin/pull/7415) for an example. * Update [`BLOCK_CHAIN_SIZE`](/src/qt/intro.cpp) to the current size plus some overhead. ### First time / New builders @@ -31,10 +31,10 @@ If you're using the automated script (found in [contrib/gitian-build.sh](/contri Check out the source code in the following directory hierarchy. cd /path/to/your/toplevel/build - git clone https://github.com/dogecoin-core/gitian.sigs.git - git clone https://github.com/dogecoin-core/dogecoin-detached-sigs.git + git clone https://github.com/discoin-core/gitian.sigs.git + git clone https://github.com/discoin-core/discoin-detached-sigs.git git clone https://github.com/devrandom/gitian-builder.git - git clone https://github.com/dogecoin/dogecoin.git + git clone https://github.com/discoin/discoin.git ### Dogecoin maintainers/release engineers, update version in sources @@ -75,7 +75,7 @@ If you're using the automated script (found in [contrib/gitian-build.sh](/contri Setup Gitian descriptors: - pushd ./dogecoin + pushd ./discoin export SIGNER=(your Gitian key, ie bluematt, sipa, etc) export VERSION=(new version, e.g. 0.8.0) git fetch @@ -109,7 +109,7 @@ Create the OS X SDK tarball, see the [OS X readme](README_osx.md) for details, a By default, Gitian will fetch source files as needed. To cache them ahead of time: pushd ./gitian-builder - make -C ../dogecoin/depends download SOURCES_PATH=`pwd`/cache/common + make -C ../discoin/depends download SOURCES_PATH=`pwd`/cache/common popd Only missing files will be fetched, so this is safe to re-run for each build. @@ -117,7 +117,7 @@ Only missing files will be fetched, so this is safe to re-run for each build. NOTE: Offline builds must use the --url flag to ensure Gitian fetches only from local URLs. For example: pushd ./gitian-builder - ./bin/gbuild --url dogecoin=/path/to/dogecoin,signature=/path/to/sigs {rest of arguments} + ./bin/gbuild --url discoin=/path/to/discoin,signature=/path/to/sigs {rest of arguments} popd The gbuild invocations below <b>DO NOT DO THIS</b> by default. @@ -125,42 +125,42 @@ The gbuild invocations below <b>DO NOT DO THIS</b> by default. ### Build and sign Dogecoin Core for Linux, Windows, and OS X: pushd ./gitian-builder - ./bin/gbuild --memory 3000 --commit dogecoin=v${VERSION} ../dogecoin/contrib/gitian-descriptors/gitian-linux.yml - ./bin/gsign --signer $SIGNER --release ${VERSION}-linux --destination ../gitian.sigs/ ../dogecoin/contrib/gitian-descriptors/gitian-linux.yml - mv build/out/dogecoin-*.tar.gz build/out/src/dogecoin-*.tar.gz ../ - - ./bin/gbuild --memory 3000 --commit dogecoin=v${VERSION} ../dogecoin/contrib/gitian-descriptors/gitian-win.yml - ./bin/gsign --signer $SIGNER --release ${VERSION}-win-unsigned --destination ../gitian.sigs/ ../dogecoin/contrib/gitian-descriptors/gitian-win.yml - mv build/out/dogecoin-*-win-unsigned.tar.gz inputs/dogecoin-win-unsigned.tar.gz - mv build/out/dogecoin-*.zip build/out/dogecoin-*.exe ../ - - ./bin/gbuild --memory 3000 --commit dogecoin=v${VERSION} ../dogecoin/contrib/gitian-descriptors/gitian-osx.yml - ./bin/gsign --signer $SIGNER --release ${VERSION}-osx-unsigned --destination ../gitian.sigs/ ../dogecoin/contrib/gitian-descriptors/gitian-osx.yml - mv build/out/dogecoin-*-osx-unsigned.tar.gz inputs/dogecoin-osx-unsigned.tar.gz - mv build/out/dogecoin-*.tar.gz build/out/dogecoin-*.dmg ../ + ./bin/gbuild --memory 3000 --commit discoin=v${VERSION} ../discoin/contrib/gitian-descriptors/gitian-linux.yml + ./bin/gsign --signer $SIGNER --release ${VERSION}-linux --destination ../gitian.sigs/ ../discoin/contrib/gitian-descriptors/gitian-linux.yml + mv build/out/discoin-*.tar.gz build/out/src/discoin-*.tar.gz ../ + + ./bin/gbuild --memory 3000 --commit discoin=v${VERSION} ../discoin/contrib/gitian-descriptors/gitian-win.yml + ./bin/gsign --signer $SIGNER --release ${VERSION}-win-unsigned --destination ../gitian.sigs/ ../discoin/contrib/gitian-descriptors/gitian-win.yml + mv build/out/discoin-*-win-unsigned.tar.gz inputs/discoin-win-unsigned.tar.gz + mv build/out/discoin-*.zip build/out/discoin-*.exe ../ + + ./bin/gbuild --memory 3000 --commit discoin=v${VERSION} ../discoin/contrib/gitian-descriptors/gitian-osx.yml + ./bin/gsign --signer $SIGNER --release ${VERSION}-osx-unsigned --destination ../gitian.sigs/ ../discoin/contrib/gitian-descriptors/gitian-osx.yml + mv build/out/discoin-*-osx-unsigned.tar.gz inputs/discoin-osx-unsigned.tar.gz + mv build/out/discoin-*.tar.gz build/out/discoin-*.dmg ../ popd Build output expected: - 1. source tarball (`dogecoin-${VERSION}.tar.gz`) - 2. linux 32-bit and 64-bit dist tarballs (`dogecoin-${VERSION}-linux[32|64].tar.gz`) - 3. windows 32-bit and 64-bit unsigned installers and dist zips (`dogecoin-${VERSION}-win[32|64]-setup-unsigned.exe`, `dogecoin-${VERSION}-win[32|64].zip`) - 4. OS X unsigned installer and dist tarball (`dogecoin-${VERSION}-osx-unsigned.dmg`, `dogecoin-${VERSION}-osx64.tar.gz`) + 1. source tarball (`discoin-${VERSION}.tar.gz`) + 2. linux 32-bit and 64-bit dist tarballs (`discoin-${VERSION}-linux[32|64].tar.gz`) + 3. windows 32-bit and 64-bit unsigned installers and dist zips (`discoin-${VERSION}-win[32|64]-setup-unsigned.exe`, `discoin-${VERSION}-win[32|64].zip`) + 4. OS X unsigned installer and dist tarball (`discoin-${VERSION}-osx-unsigned.dmg`, `discoin-${VERSION}-osx64.tar.gz`) 5. Gitian signatures (in `gitian.sigs/${VERSION}-<linux|{win,osx}-unsigned>/(your Gitian key)/`) ### Verify other gitian builders signatures to your own. (Optional) Add other gitian builders keys to your gpg keyring, and/or refresh keys. - gpg --import dogecoin/contrib/gitian-keys/*.pgp + gpg --import discoin/contrib/gitian-keys/*.pgp gpg --refresh-keys Verify the signatures pushd ./gitian-builder - ./bin/gverify -v -d ../gitian.sigs/ -r ${VERSION}-linux ../dogecoin/contrib/gitian-descriptors/gitian-linux.yml - ./bin/gverify -v -d ../gitian.sigs/ -r ${VERSION}-win-unsigned ../dogecoin/contrib/gitian-descriptors/gitian-win.yml - ./bin/gverify -v -d ../gitian.sigs/ -r ${VERSION}-osx-unsigned ../dogecoin/contrib/gitian-descriptors/gitian-osx.yml + ./bin/gverify -v -d ../gitian.sigs/ -r ${VERSION}-linux ../discoin/contrib/gitian-descriptors/gitian-linux.yml + ./bin/gverify -v -d ../gitian.sigs/ -r ${VERSION}-win-unsigned ../discoin/contrib/gitian-descriptors/gitian-win.yml + ./bin/gverify -v -d ../gitian.sigs/ -r ${VERSION}-osx-unsigned ../discoin/contrib/gitian-descriptors/gitian-osx.yml popd ### Next steps: @@ -178,25 +178,25 @@ Commit your signature to gitian.sigs: Wait for Windows/OS X detached signatures: - Once the Windows/OS X builds each have 3 matching signatures, they will be signed with their respective release keys. -- Detached signatures will then be committed to the [dogecoin-detached-sigs](https://github.com/doge/dogecoin-detached-sigs) repository, which can be combined with the unsigned apps to create signed binaries. +- Detached signatures will then be committed to the [discoin-detached-sigs](https://github.com/dis/discoin-detached-sigs) repository, which can be combined with the unsigned apps to create signed binaries. Create (and optionally verify) the signed OS X binary: pushd ./gitian-builder - ./bin/gbuild -i --commit signature=v${VERSION} ../dogecoin/contrib/gitian-descriptors/gitian-osx-signer.yml - ./bin/gsign --signer $SIGNER --release ${VERSION}-osx-signed --destination ../gitian.sigs/ ../dogecoin/contrib/gitian-descriptors/gitian-osx-signer.yml - ./bin/gverify -v -d ../gitian.sigs/ -r ${VERSION}-osx-signed ../dogecoin/contrib/gitian-descriptors/gitian-osx-signer.yml - mv build/out/dogecoin-osx-signed.dmg ../dogecoin-${VERSION}-osx.dmg + ./bin/gbuild -i --commit signature=v${VERSION} ../discoin/contrib/gitian-descriptors/gitian-osx-signer.yml + ./bin/gsign --signer $SIGNER --release ${VERSION}-osx-signed --destination ../gitian.sigs/ ../discoin/contrib/gitian-descriptors/gitian-osx-signer.yml + ./bin/gverify -v -d ../gitian.sigs/ -r ${VERSION}-osx-signed ../discoin/contrib/gitian-descriptors/gitian-osx-signer.yml + mv build/out/discoin-osx-signed.dmg ../discoin-${VERSION}-osx.dmg popd Create (and optionally verify) the signed Windows binaries: pushd ./gitian-builder - ./bin/gbuild -i --commit signature=v${VERSION} ../dogecoin/contrib/gitian-descriptors/gitian-win-signer.yml - ./bin/gsign --signer $SIGNER --release ${VERSION}-win-signed --destination ../gitian.sigs/ ../dogecoin/contrib/gitian-descriptors/gitian-win-signer.yml - ./bin/gverify -v -d ../gitian.sigs/ -r ${VERSION}-win-signed ../dogecoin/contrib/gitian-descriptors/gitian-win-signer.yml - mv build/out/dogecoin-*win64-setup.exe ../dogecoin-${VERSION}-win64-setup.exe - mv build/out/dogecoin-*win32-setup.exe ../dogecoin-${VERSION}-win32-setup.exe + ./bin/gbuild -i --commit signature=v${VERSION} ../discoin/contrib/gitian-descriptors/gitian-win-signer.yml + ./bin/gsign --signer $SIGNER --release ${VERSION}-win-signed --destination ../gitian.sigs/ ../discoin/contrib/gitian-descriptors/gitian-win-signer.yml + ./bin/gverify -v -d ../gitian.sigs/ -r ${VERSION}-win-signed ../discoin/contrib/gitian-descriptors/gitian-win-signer.yml + mv build/out/discoin-*win64-setup.exe ../discoin-${VERSION}-win64-setup.exe + mv build/out/discoin-*win32-setup.exe ../discoin-${VERSION}-win32-setup.exe popd Commit your signature for the signed OS X/Windows binaries: @@ -218,23 +218,23 @@ sha256sum * > SHA256SUMS The list of files should be: ``` -dogecoin-${VERSION}-aarch64-linux-gnu.tar.gz -dogecoin-${VERSION}-arm-linux-gnueabihf.tar.gz -dogecoin-${VERSION}-i686-pc-linux-gnu.tar.gz -dogecoin-${VERSION}-x86_64-linux-gnu.tar.gz -dogecoin-${VERSION}-osx64.tar.gz -dogecoin-${VERSION}-osx.dmg -dogecoin-${VERSION}.tar.gz -dogecoin-${VERSION}-win32-setup.exe -dogecoin-${VERSION}-win32.zip -dogecoin-${VERSION}-win64-setup.exe -dogecoin-${VERSION}-win64.zip +discoin-${VERSION}-aarch64-linux-gnu.tar.gz +discoin-${VERSION}-arm-linux-gnueabihf.tar.gz +discoin-${VERSION}-i686-pc-linux-gnu.tar.gz +discoin-${VERSION}-x86_64-linux-gnu.tar.gz +discoin-${VERSION}-osx64.tar.gz +discoin-${VERSION}-osx.dmg +discoin-${VERSION}.tar.gz +discoin-${VERSION}-win32-setup.exe +discoin-${VERSION}-win32.zip +discoin-${VERSION}-win64-setup.exe +discoin-${VERSION}-win64.zip ``` The `*-debug*` files generated by the gitian build contain debug symbols for troubleshooting by developers. It is assumed that anyone that is interested in debugging can run gitian to generate the files for themselves. To avoid end-user confusion about which file to pick, as well as save storage -space *do not upload these to the dogecoin.com server, nor put them in the torrent*. +space *do not upload these to the discoin.com server, nor put them in the torrent*. - GPG-sign it, delete the unsigned file: ``` @@ -244,23 +244,23 @@ rm SHA256SUMS (the digest algorithm is forced to sha256 to avoid confusion of the `Hash:` header that GPG adds with the SHA256 used for the files) Note: check that SHA256SUMS itself doesn't end up in SHA256SUMS, which is a spurious/nonsensical entry. -- Upload zips and installers, as well as `SHA256SUMS.asc` from last step, to the dogecoin.com Github repo +- Upload zips and installers, as well as `SHA256SUMS.asc` from last step, to the discoin.com Github repo -- Create a [new GitHub release](https://github.com/dogecoin/dogecoin/releases/new) with a link to the archived release notes. +- Create a [new GitHub release](https://github.com/discoin/discoin/releases/new) with a link to the archived release notes. -- Update dogecoin.com version - Langerhans to do +- Update discoin.com version - Langerhans to do - Announce the release: - - Release sticky on Dogecoin Forums: http://forum.dogecoin.com/forum/news-community/community-announcements + - Release sticky on Dogecoin Forums: http://forum.discoin.com/forum/news-community/community-announcements - Dogecoin-development mailing list - - Twitter, reddit /r/dogecoin + - Twitter, reddit /r/discoin - - Update title of #dogecoin on Freenode IRC + - Update title of #discoin on Freenode IRC - - Announce on reddit /r/dogecoin, /r/dogecoindev + - Announce on reddit /r/discoin, /r/discoindev - Add release notes for the new version to the directory `doc/release-notes` in git master diff --git a/doc/shared-libraries.md b/doc/shared-libraries.md index 2a147c0fa..596c6a221 100644 --- a/doc/shared-libraries.md +++ b/doc/shared-libraries.md @@ -1,21 +1,21 @@ Shared Libraries ================ -## dogecoinconsensus +## discoinconsensus The purpose of this library is to make the verification functionality that is critical to Dogecoin's consensus available to other applications, e.g. to language bindings. ### API -The interface is defined in the C header `dogecoinconsensus.h` located in `src/script/dogecoinconsensus.h`. +The interface is defined in the C header `discoinconsensus.h` located in `src/script/discoinconsensus.h`. #### Version -`dogecoinconsensus_version` returns an `unsigned int` with the API version *(currently at an experimental `0`)*. +`discoinconsensus_version` returns an `unsigned int` with the API version *(currently at an experimental `0`)*. #### Script Validation -`dogecoinconsensus_verify_script` returns an `int` with the status of the verification. It will be `1` if the input script correctly spends the previous output `scriptPubKey`. +`discoinconsensus_verify_script` returns an `int` with the status of the verification. It will be `1` if the input script correctly spends the previous output `scriptPubKey`. ##### Parameters - `const unsigned char *scriptPubKey` - The previous output script that encumbers spending. @@ -24,26 +24,26 @@ The interface is defined in the C header `dogecoinconsensus.h` located in `src/ - `unsigned int txToLen` - The number of bytes for the `txTo`. - `unsigned int nIn` - The index of the input in `txTo` that spends the `scriptPubKey`. - `unsigned int flags` - The script validation flags *(see below)*. -- `dogecoinconsensus_error* err` - Will have the error/success code for the operation *(see below)*. +- `discoinconsensus_error* err` - Will have the error/success code for the operation *(see below)*. ##### Script Flags -- `dogecoinconsensus_SCRIPT_FLAGS_VERIFY_NONE` -- `dogecoinconsensus_SCRIPT_FLAGS_VERIFY_P2SH` - Evaluate P2SH ([BIP16](https://github.com/bitcoin/bips/blob/master/bip-0016.mediawiki)) subscripts -- `dogecoinconsensus_SCRIPT_FLAGS_VERIFY_DERSIG` - Enforce strict DER ([BIP66](https://github.com/bitcoin/bips/blob/master/bip-0066.mediawiki)) compliance -- `dogecoinconsensus_SCRIPT_FLAGS_VERIFY_NULLDUMMY` - Enforce NULLDUMMY ([BIP147](https://github.com/bitcoin/bips/blob/master/bip-0147.mediawiki)) -- `dogecoinconsensus_SCRIPT_FLAGS_VERIFY_CHECKLOCKTIMEVERIFY` - Enable CHECKLOCKTIMEVERIFY ([BIP65](https://github.com/bitcoin/bips/blob/master/bip-0065.mediawiki)) -- `dogecoinconsensus_SCRIPT_FLAGS_VERIFY_CHECKSEQUENCEVERIFY` - Enable CHECKSEQUENCEVERIFY ([BIP112](https://github.com/bitcoin/bips/blob/master/bip-0112.mediawiki)) -- `dogecoinconsensus_SCRIPT_FLAGS_VERIFY_WITNESS` - Enable WITNESS ([BIP141](https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki)) +- `discoinconsensus_SCRIPT_FLAGS_VERIFY_NONE` +- `discoinconsensus_SCRIPT_FLAGS_VERIFY_P2SH` - Evaluate P2SH ([BIP16](https://github.com/bitcoin/bips/blob/master/bip-0016.mediawiki)) subscripts +- `discoinconsensus_SCRIPT_FLAGS_VERIFY_DERSIG` - Enforce strict DER ([BIP66](https://github.com/bitcoin/bips/blob/master/bip-0066.mediawiki)) compliance +- `discoinconsensus_SCRIPT_FLAGS_VERIFY_NULLDUMMY` - Enforce NULLDUMMY ([BIP147](https://github.com/bitcoin/bips/blob/master/bip-0147.mediawiki)) +- `discoinconsensus_SCRIPT_FLAGS_VERIFY_CHECKLOCKTIMEVERIFY` - Enable CHECKLOCKTIMEVERIFY ([BIP65](https://github.com/bitcoin/bips/blob/master/bip-0065.mediawiki)) +- `discoinconsensus_SCRIPT_FLAGS_VERIFY_CHECKSEQUENCEVERIFY` - Enable CHECKSEQUENCEVERIFY ([BIP112](https://github.com/bitcoin/bips/blob/master/bip-0112.mediawiki)) +- `discoinconsensus_SCRIPT_FLAGS_VERIFY_WITNESS` - Enable WITNESS ([BIP141](https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki)) ##### Errors -- `dogecoinconsensus_ERR_OK` - No errors with input parameters *(see the return value of `dogecoinconsensus_verify_script` for the verification status)* -- `dogecoinconsensus_ERR_TX_INDEX` - An invalid index for `txTo` -- `dogecoinconsensus_ERR_TX_SIZE_MISMATCH` - `txToLen` did not match with the size of `txTo` -- `dogecoinconsensus_ERR_DESERIALIZE` - An error deserializing `txTo` -- `dogecoinconsensus_ERR_AMOUNT_REQUIRED` - Input amount is required if WITNESS is used +- `discoinconsensus_ERR_OK` - No errors with input parameters *(see the return value of `discoinconsensus_verify_script` for the verification status)* +- `discoinconsensus_ERR_TX_INDEX` - An invalid index for `txTo` +- `discoinconsensus_ERR_TX_SIZE_MISMATCH` - `txToLen` did not match with the size of `txTo` +- `discoinconsensus_ERR_DESERIALIZE` - An error deserializing `txTo` +- `discoinconsensus_ERR_AMOUNT_REQUIRED` - Input amount is required if WITNESS is used ### Example Implementations - [NBitcoin](https://github.com/NicolasDorier/NBitcoin/blob/master/NBitcoin/Script.cs#L814) (.NET Bindings) -- [node-libdogecoinconsensus](https://github.com/bitpay/node-libdogecoinconsensus) (Node.js Bindings) -- [java-libdogecoinconsensus](https://github.com/dexX7/java-libdogecoinconsensus) (Java Bindings) -- [dogecoinconsensus-php](https://github.com/Bit-Wasp/dogecoinconsensus-php) (PHP Bindings) +- [node-libdiscoinconsensus](https://github.com/bitpay/node-libdiscoinconsensus) (Node.js Bindings) +- [java-libdiscoinconsensus](https://github.com/dexX7/java-libdiscoinconsensus) (Java Bindings) +- [discoinconsensus-php](https://github.com/Bit-Wasp/discoinconsensus-php) (PHP Bindings) diff --git a/doc/tor.md b/doc/tor.md index 00af4aee4..d45c1ba5f 100644 --- a/doc/tor.md +++ b/doc/tor.md @@ -31,7 +31,7 @@ outgoing connections be anonymized, but more is possible. In a typical situation, this suffices to run behind a Tor proxy: - ./dogecoin -proxy=127.0.0.1:9050 + ./discoin -proxy=127.0.0.1:9050 2. Run a Dogecoin hidden server @@ -41,17 +41,17 @@ If you configure your Tor system accordingly, it is possible to make your node a reachable from the Tor network. Add these lines to your /etc/tor/torrc (or equivalent config file): - HiddenServiceDir /var/lib/tor/dogecoin-service/ + HiddenServiceDir /var/lib/tor/discoin-service/ HiddenServicePort 22556 127.0.0.1:22556 HiddenServicePort 44556 127.0.0.1:44556 The directory can be different of course, but (both) port numbers should be equal to -your dogecoind's P2P listen port (22556 by default). +your discoind's P2P listen port (22556 by default). -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/dogecoin-service/hostname. Onion addresses are given + /var/lib/tor/discoin-service/hostname. Onion addresses are given preference for your node to advertise itself with, for connections coming from unroutable addresses (such as 127.0.0.1, where the Tor proxy typically runs). @@ -68,25 +68,25 @@ your dogecoind's P2P listen port (22556 by default). In a typical situation, where you're only reachable via Tor, this should suffice: - ./dogecoind -proxy=127.0.0.1:9050 -externalip=57qr3yd1nyntf5k.onion -listen + ./discoind -proxy=127.0.0.1:9050 -externalip=57qr3yd1nyntf5k.onion -listen (obviously, replace the Onion address with your own). It should be noted that you still listen on all devices and another node could establish a clearnet connection, when knowing your address. To mitigate this, additionally bind the address of your Tor proxy: - ./dogecoind ... -bind=127.0.0.1 + ./discoind ... -bind=127.0.0.1 If you don't care too much about hiding your node, and want to be reachable on IPv4 as well, use `discover` instead: - ./dogecoind ... -discover + ./discoind ... -discover and open port 22556 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: - ./dogecoin -onion=127.0.0.1:9050 -externalip=57qr3yd1nyntf5k.onion -discover + ./discoin -onion=127.0.0.1:9050 -externalip=57qr3yd1nyntf5k.onion -discover 3. Automatically listen on Tor -------------------------------- @@ -105,12 +105,12 @@ and, if not disabled, configured using the `-torcontrol` and `-torpassword` sett To show verbose debugging information, pass `-debug=tor`. Connecting to Tor's control socket API requires one of two authentication methods to be -configured. For cookie authentication the user running dogecoind must have write access +configured. For cookie authentication the user running discoind must have write access to the `CookieAuthFile` specified in Tor configuration. In some cases this is preconfigured and the creation of a hidden service is automatic. If permission problems are seen with `-debug=tor` they can be resolved by adding both the user running tor and -the user running dogecoind to the same group and setting permissions appropriately. On -Debian-based systems the user running dogecoind can be added to the debian-tor group, +the user running discoind to the same group and setting permissions appropriately. On +Debian-based systems the user running discoind can be added to the debian-tor group, which has the appropriate permissions. An alternative authentication method is the use of the `-torpassword` flag and a `hash-password` which can be enabled and specified in Tor configuration. @@ -118,7 +118,7 @@ Tor configuration. 4. Privacy recommendations --------------------------- -- Do not add anything but dogecoin ports to the hidden service created in section 2. +- Do not add anything but discoin ports to the hidden service created in section 2. If you run a web service too, create a new hidden service for that. Otherwise it is trivial to link them, which may reduce privacy. Hidden services created automatically (as in section 3) always have only one port diff --git a/doc/zmq.md b/doc/zmq.md index a35b8a76f..ca056bbdd 100644 --- a/doc/zmq.md +++ b/doc/zmq.md @@ -6,7 +6,7 @@ providing various message-oriented semantics such as publish/subscribe, request/reply, and push/pull. The Dogecoin Core daemon can be configured to act as a trusted "border -router", implementing the dogecoin wire protocol and relay, making +router", implementing the discoin wire protocol and relay, making consensus decisions, maintaining the local blockchain database, broadcasting locally generated transactions into the network, and providing a queryable RPC interface to interact on a polled basis for @@ -45,7 +45,7 @@ operation. By default, the ZeroMQ feature is automatically compiled in if the necessary prerequisites are found. To disable, use --disable-zmq -during the *configure* step of building dogecoind: +during the *configure* step of building discoind: $ ./configure --disable-zmq (other options) @@ -66,8 +66,8 @@ address. The same address can be used in more than one notification. For instance: - $ dogecoind -zmqpubhashtx=tcp://127.0.0.1:28332 \ - -zmqpubrawtx=ipc:///tmp/dogecoind.tx.raw + $ discoind -zmqpubhashtx=tcp://127.0.0.1:28332 \ + -zmqpubrawtx=ipc:///tmp/discoind.tx.raw Each PUB notification has a topic and body, where the header corresponds to the notification type. For instance, for the @@ -75,7 +75,7 @@ notification `-zmqpubhashtx` the topic is `hashtx` (no null terminator) and the body is the hexadecimal transaction hash (32 bytes). -These options can also be provided in dogecoin.conf. +These options can also be provided in discoin.conf. ZeroMQ endpoint specifiers for TCP (and others) are documented in the [ZeroMQ API](http://api.zeromq.org/4-0:_start). @@ -87,9 +87,9 @@ arriving. Please see `contrib/zmq/zmq_sub.py` for a working example. ## Remarks -From the perspective of dogecoind, the ZeroMQ socket is write-only; PUB +From the perspective of discoind, the ZeroMQ socket is write-only; PUB sockets don't even have a read function. Thus, there is no state -introduced into dogecoind directly. Furthermore, no information is +introduced into discoind directly. Furthermore, no information is broadcast that wasn't already received from the public P2P network. No authentication or authorization is done on connecting clients; it |