From ec7aad5ba419beba85ccc64b7f4be7baf5125c68 Mon Sep 17 00:00:00 2001 From: Adrian Gallagher Date: Tue, 1 Nov 2016 05:28:11 -0700 Subject: [PATCH] Litecoin: Branding --- .github/ISSUE_TEMPLATE.md | 8 +- .gitignore | 26 +-- CONTRIBUTING.md | 35 ++-- COPYING | 1 + INSTALL.md | 4 +- Makefile.am | 10 +- build-aux/m4/bitcoin_qt.m4 | 4 +- configure.ac | 30 ++-- contrib/README.md | 8 +- contrib/devtools/gen-manpages.sh | 12 +- contrib/gitian-keys/README.md | 2 +- contrib/install_db4.sh | 4 +- contrib/linearize/README.md | 8 +- contrib/linearize/example-linearize.cfg | 16 +- contrib/linearize/linearize-hashes.py | 2 +- contrib/macdeploy/README.md | 2 +- contrib/macdeploy/custom_dsstore.py | 6 +- contrib/macdeploy/detached-sig-create.sh | 2 +- contrib/macdeploy/fancy.plist | 2 +- contrib/macdeploy/macdeployqtplus | 4 +- contrib/seeds/README.md | 4 +- contrib/seeds/generate-seeds.py | 2 +- contrib/testgen/README.md | 2 +- contrib/zmq/zmq_sub.py | 4 +- contrib/zmq/zmq_sub3.4.py | 4 +- depends/README.md | 6 +- depends/description.md | 2 +- doc/README.md | 32 ++-- doc/README_windows.txt | 14 +- doc/REST-interface.md | 8 +- doc/assets-attribution.md | 2 +- doc/benchmarking.md | 8 +- doc/build-freebsd.md | 6 +- doc/build-netbsd.md | 6 +- doc/build-openbsd.md | 6 +- doc/build-osx.md | 42 +++-- doc/build-unix.md | 32 ++-- doc/build-windows.md | 26 +-- doc/dependencies.md | 2 +- doc/descriptors.md | 12 +- doc/developer-notes.md | 48 ++--- doc/dnsseed-policy.md | 16 +- doc/files.md | 6 +- doc/fuzzing.md | 4 +- doc/man/Makefile.am | 8 +- doc/reduce-traffic.md | 4 +- doc/release-process.md | 166 ++++++++---------- doc/tor.md | 44 ++--- doc/zmq.md | 20 +-- .../examples/{bitcoin.conf => litecoin.conf} | 22 +-- share/qt/Info.plist.in | 20 +-- share/rpcauth/rpcauth.py | 2 +- share/setup.nsi.in | 8 +- src/Makefile.am | 64 +++---- src/Makefile.bench.include | 24 +-- src/Makefile.qt.include | 34 ++-- src/Makefile.qttest.include | 32 ++-- src/Makefile.test.include | 26 +-- src/bench/.gitignore | 2 +- src/bench/bench_bitcoin.cpp | 2 +- src/bitcoin-cli-res.rc | 10 +- src/bitcoin-cli.cpp | 14 +- src/bitcoin-tx-res.rc | 10 +- src/bitcoin-tx.cpp | 6 +- src/bitcoind-res.rc | 10 +- src/bitcoind.cpp | 6 +- src/clientversion.cpp | 2 +- src/httpserver.cpp | 4 +- src/init.cpp | 8 +- src/net.cpp | 2 +- src/net_processing.cpp | 2 +- src/policy/feerate.cpp | 2 +- src/qt/README.md | 12 +- src/qt/addressbookpage.cpp | 4 +- src/qt/askpassphrasedialog.cpp | 4 +- src/qt/bitcoin.cpp | 2 +- src/qt/bitcoingui.cpp | 16 +- src/qt/bitcoinunits.cpp | 16 +- src/qt/editaddressdialog.cpp | 2 +- src/qt/forms/coincontroldialog.ui | 8 +- src/qt/forms/modaloverlay.ui | 4 +- src/qt/forms/optionsdialog.ui | 6 +- src/qt/forms/overviewpage.ui | 20 +-- src/qt/forms/receivecoinsdialog.ui | 4 +- src/qt/forms/sendcoinsdialog.ui | 12 +- src/qt/forms/sendcoinsentry.ui | 6 +- src/qt/forms/signverifymessagedialog.ui | 10 +- src/qt/guiconstants.h | 10 +- src/qt/guiutil.cpp | 16 +- src/qt/intro.cpp | 4 +- src/qt/macnotificationhandler.mm | 2 +- src/qt/openuridialog.cpp | 4 +- src/qt/paymentrequest.proto | 2 +- src/qt/paymentserver.cpp | 18 +- src/qt/res/bitcoin-qt-res.rc | 8 +- src/qt/sendcoinsdialog.cpp | 2 +- src/qt/test/test_main.cpp | 4 +- src/qt/utilitydialog.cpp | 2 +- src/rpc/blockchain.cpp | 12 +- src/rpc/mining.cpp | 8 +- src/rpc/misc.cpp | 22 +-- src/rpc/rawtransaction.cpp | 18 +- src/rpc/server.cpp | 6 +- src/test/README.md | 18 +- src/test/data/README.md | 2 +- src/test/getarg_tests.cpp | 2 +- src/test/test_bitcoin.cpp | 2 +- src/util/system.cpp | 10 +- src/util/system.h | 2 +- src/validation.cpp | 8 +- src/wallet/db.cpp | 2 +- src/wallet/rpcdump.cpp | 18 +- src/wallet/rpcwallet.cpp | 120 ++++++------- test/README.md | 46 ++--- test/functional/README.md | 8 +- test/functional/feature_help.py | 8 +- test/functional/feature_proxy.py | 10 +- test/functional/interface_rest.py | 2 +- test/functional/rpc_bind.py | 2 +- test/functional/test_framework/mininode.py | 4 +- test/functional/test_framework/test_node.py | 2 +- test/functional/test_framework/util.py | 6 +- test/functional/test_runner.py | 2 +- test/util/bitcoin-util-test.py | 2 +- 124 files changed, 779 insertions(+), 795 deletions(-) rename share/examples/{bitcoin.conf => litecoin.conf} (87%) diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md index 8768a8ca6b..ee95bd824e 100644 --- a/.github/ISSUE_TEMPLATE.md +++ b/.github/ISSUE_TEMPLATE.md @@ -1,8 +1,8 @@ - @@ -13,7 +13,7 @@ If the node is "stuck" during sync or giving "block checksum mismatch" errors, p - + diff --git a/.gitignore b/.gitignore index be784024a0..43ffbec691 100644 --- a/.gitignore +++ b/.gitignore @@ -1,14 +1,14 @@ *.tar.gz *.exe -src/bitcoin -src/bitcoind -src/bitcoin-cli -src/bitcoin-tx -src/bitcoin-wallet -src/test/test_bitcoin -src/test/test_bitcoin_fuzzy -src/qt/test/test_bitcoin-qt +src/litecoin +src/litecoind +src/litecoin-cli +src/litecoin-tx +src/litecoin-wallet +src/test/test_litecoin +src/test/test_litecoin_fuzzy +src/qt/test/test_litecoin-qt # autoreconf Makefile.in @@ -54,6 +54,7 @@ src/qt/bitcoin-qt.includes .deps .dirstamp .libs +.vscode .*.swp *.*~* *.bak @@ -82,17 +83,16 @@ src/qt/bitcoin-qt.includes # Compilation and Qt preprocessor part *.qm Makefile -bitcoin-qt -Bitcoin-Qt.app +litecoin-qt +litecoin-Qt.app background.tiff* # Unit-tests Makefile.test -bitcoin-qt_test +litecoin-qt_test # Resources cpp qrc_*.cpp - # Mac specific .DS_Store build @@ -101,7 +101,7 @@ build *.gcno *.gcda /*.info -test_bitcoin.coverage/ +test_litecoin.coverage/ total.coverage/ coverage_percent.txt diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 139fe7dc52..91decb34fe 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1,7 +1,7 @@ -Contributing to Bitcoin Core +Contributing to Litecoin Core ============================ -The Bitcoin Core project operates an open contributor model where anyone is +The Litecoin Core project operates an open contributor model where anyone is welcome to contribute towards development in the form of peer review, testing and patches. This document explains the practical process and guidelines for contributing. @@ -14,25 +14,18 @@ purposes. As such there are repository "maintainers" who are responsible for merging pull requests as well as a "lead maintainer" who is responsible for the release cycle, overall merging, moderation and appointment of maintainers. -If you're looking for somewhere to start contributing, check out the -[good first issue](https://github.com/bitcoin/bitcoin/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22) -list. - Communication Channels ---------------------- -Most communication about Bitcoin Core development happens on IRC, in the -#bitcoin-core-dev channel on Freenode. The easiest way to participate on IRC is -with the web client, [webchat.freenode.net](https://webchat.freenode.net/). Chat -history logs can be found -on [http://www.erisian.com.au/bitcoin-core-dev/](http://www.erisian.com.au/bitcoin-core-dev/) -and [http://gnusha.org/bitcoin-core-dev/](http://gnusha.org/bitcoin-core-dev/). +Most communication about Litecoin Core development happens on IRC, in the +#litecoin-dev channel on Freenode. The easiest way to participate on IRC is +with the web client, [webchat.freenode.net](https://webchat.freenode.net/). Discussion about code base improvements happens in GitHub issues and on pull requests. The developer -[mailing list](https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev) +[mailing list](https://groups.google.com/forum/#!forum/litecoin-dev) should be used to discuss complicated or controversial changes before working on a patch set. @@ -81,12 +74,12 @@ the pull request affects. Valid areas as: - *Consensus* for changes to consensus critical code - *Docs* for changes to the documentation - - *Qt* for changes to bitcoin-qt + - *Qt* for changes to litecoin-qt - *Mining* for changes to the mining code - *Net* or *P2P* for changes to the peer-to-peer network code - *RPC/REST/ZMQ* for changes to the RPC, REST or ZMQ APIs - *Scripts and tools* for changes to the scripts and tools - - *Tests* for changes to the bitcoin unit tests or QA tests + - *Tests* for changes to the litecoin unit tests or QA tests - *Trivial* should **only** be used for PRs that do not change generated executable code. Notably, refactors (change of function arguments and code reorganization) and changes in behavior should **not** be marked as trivial. @@ -199,11 +192,11 @@ workload on reviewing. "Decision Making" Process ------------------------- -The following applies to code changes to the Bitcoin Core project (and related -projects such as libsecp256k1), and is not to be confused with overall Bitcoin +The following applies to code changes to the Litecoin Core project (and related +projects such as libsecp256k1), and is not to be confused with overall Litecoin Network Protocol consensus changes. -Whether a pull request is merged into Bitcoin Core rests with the project merge +Whether a pull request is merged into Litecoin Core rests with the project merge maintainers and ultimately the project lead. Maintainers will take into consideration if a patch is in line with the general @@ -221,7 +214,7 @@ In general, all pull requests must: - Where bugs are fixed, where possible, there should be unit tests demonstrating the bug and also proving the fix. This helps prevent regression. -Patches that change Bitcoin consensus rules are considerably more involved than +Patches that change Litecoin consensus rules are considerably more involved than normal because they affect the entire ecosystem and so must be preceded by extensive mailing list discussions and have a numbered BIP. While each case will be different, one should be prepared to expend more time and effort than for @@ -262,7 +255,7 @@ higher in terms of discussion and peer review requirements, keeping in mind that mistakes could be very costly to the wider community. This includes refactoring of consensus critical code. -Where a patch set proposes to change the Bitcoin consensus, it must have been +Where a patch set proposes to change the Litecoin consensus, it must have been discussed extensively on the mailing list and IRC, be accompanied by a widely discussed BIP and have a generally widely perceived technical consensus of being a worthwhile change based on the judgement of the maintainers. @@ -302,7 +295,7 @@ about: Release Policy -------------- -The project leader is the release manager for each Bitcoin Core release. +The project leader is the release manager for each Litecoin Core release. Copyright --------- diff --git a/COPYING b/COPYING index 9d54ecbde1..149ca3e7e5 100644 --- a/COPYING +++ b/COPYING @@ -2,6 +2,7 @@ The MIT License (MIT) Copyright (c) 2009-2019 The Bitcoin Core developers Copyright (c) 2009-2019 Bitcoin Developers +Copyright (c) 2011-2019 The Litecoin Core developers Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal diff --git a/INSTALL.md b/INSTALL.md index 520a47d960..be23c6088d 100644 --- a/INSTALL.md +++ b/INSTALL.md @@ -1,5 +1,5 @@ -Building Bitcoin +Building Litecoin ================ See doc/build-*.md for instructions on building the various -elements of the Bitcoin Core reference implementation of Bitcoin. +elements of the Litecoin Core reference implementation of Litecoin. diff --git a/Makefile.am b/Makefile.am index 85674f819a..b77a5afb82 100644 --- a/Makefile.am +++ b/Makefile.am @@ -26,7 +26,7 @@ BITCOIN_WIN_INSTALLER=$(PACKAGE)-$(PACKAGE_VERSION)-win$(WINDOWS_BITS)-setup$(EX empty := space := $(empty) $(empty) -OSX_APP=Bitcoin-Qt.app +OSX_APP=Litecoin-Qt.app OSX_VOLNAME = $(subst $(space),-,$(PACKAGE_NAME)) OSX_DMG = $(OSX_VOLNAME).dmg OSX_BACKGROUND_SVG=background.svg @@ -98,7 +98,7 @@ $(OSX_APP)/Contents/Resources/bitcoin.icns: $(OSX_INSTALLER_ICONS) $(MKDIR_P) $(@D) $(INSTALL_DATA) $< $@ -$(OSX_APP)/Contents/MacOS/Bitcoin-Qt: all-recursive +$(OSX_APP)/Contents/MacOS/Litecoin-Qt: all-recursive $(MKDIR_P) $(@D) STRIPPROG="$(STRIP)" $(INSTALL_STRIP_PROGRAM) $(BITCOIN_QT_BIN) $@ @@ -108,7 +108,7 @@ $(OSX_APP)/Contents/Resources/Base.lproj/InfoPlist.strings: OSX_APP_BUILT=$(OSX_APP)/Contents/PkgInfo $(OSX_APP)/Contents/Resources/empty.lproj \ $(OSX_APP)/Contents/Resources/bitcoin.icns $(OSX_APP)/Contents/Info.plist \ - $(OSX_APP)/Contents/MacOS/Bitcoin-Qt $(OSX_APP)/Contents/Resources/Base.lproj/InfoPlist.strings + $(OSX_APP)/Contents/MacOS/Litecoin-Qt $(OSX_APP)/Contents/Resources/Base.lproj/InfoPlist.strings osx_volname: echo $(OSX_VOLNAME) >$@ @@ -133,7 +133,7 @@ $(APP_DIST_DIR)/Applications: @rm -f $@ @cd $(@D); $(LN_S) /Applications $(@F) -$(APP_DIST_EXTRAS): $(APP_DIST_DIR)/$(OSX_APP)/Contents/MacOS/Bitcoin-Qt +$(APP_DIST_EXTRAS): $(APP_DIST_DIR)/$(OSX_APP)/Contents/MacOS/Litecoin-Qt $(OSX_DMG): $(APP_DIST_EXTRAS) $(GENISOIMAGE) -no-cache-inodes -D -l -probe -V "$(OSX_VOLNAME)" -no-pad -r -dir-mode 0755 -apple -o $@ dist @@ -148,7 +148,7 @@ $(APP_DIST_DIR)/.background/$(OSX_BACKGROUND_IMAGE): $(OSX_BACKGROUND_IMAGE_DPIF $(APP_DIST_DIR)/.DS_Store: $(OSX_DSSTORE_GEN) $(PYTHON) $< "$@" "$(OSX_VOLNAME)" -$(APP_DIST_DIR)/$(OSX_APP)/Contents/MacOS/Bitcoin-Qt: $(OSX_APP_BUILT) $(OSX_PACKAGING) +$(APP_DIST_DIR)/$(OSX_APP)/Contents/MacOS/Litecoin-Qt: $(OSX_APP_BUILT) $(OSX_PACKAGING) INSTALLNAMETOOL=$(INSTALLNAMETOOL) OTOOL=$(OTOOL) STRIP=$(STRIP) $(PYTHON) $(OSX_DEPLOY_SCRIPT) $(OSX_APP) -translations-dir=$(QT_TRANSLATION_DIR) -add-qt-tr $(OSX_QT_TRANSLATIONS) -verbose 2 deploydir: $(APP_DIST_EXTRAS) diff --git a/build-aux/m4/bitcoin_qt.m4 b/build-aux/m4/bitcoin_qt.m4 index 1a7c5d5f7d..e13d12019d 100644 --- a/build-aux/m4/bitcoin_qt.m4 +++ b/build-aux/m4/bitcoin_qt.m4 @@ -7,7 +7,7 @@ dnl Output: If qt version is auto, set bitcoin_enable_qt to false. Else, exit. AC_DEFUN([BITCOIN_QT_FAIL],[ if test "x$bitcoin_qt_want_version" = xauto && test "x$bitcoin_qt_force" != xyes; then if test "x$bitcoin_enable_qt" != xno; then - AC_MSG_WARN([$1; bitcoin-qt frontend will not be built]) + AC_MSG_WARN([$1; litecoin-qt frontend will not be built]) fi bitcoin_enable_qt=no bitcoin_enable_qt_test=no @@ -54,7 +54,7 @@ AC_DEFUN([BITCOIN_QT_INIT],[ dnl enable qt support AC_ARG_WITH([gui], [AS_HELP_STRING([--with-gui@<:@=no|qt5|auto@:>@], - [build bitcoin-qt GUI (default=auto)])], + [build litecoin-qt GUI (default=auto)])], [ bitcoin_qt_want_version=$withval if test "x$bitcoin_qt_want_version" = xyes; then diff --git a/configure.ac b/configure.ac index b73c7f8950..1a990791bc 100644 --- a/configure.ac +++ b/configure.ac @@ -8,18 +8,18 @@ define(_CLIENT_VERSION_RC, 0) define(_CLIENT_VERSION_IS_RELEASE, true) define(_COPYRIGHT_YEAR, 2019) define(_COPYRIGHT_HOLDERS,[The %s developers]) -define(_COPYRIGHT_HOLDERS_SUBSTITUTION,[[Bitcoin Core]]) -AC_INIT([Bitcoin Core],m4_join([.], _CLIENT_VERSION_MAJOR, _CLIENT_VERSION_MINOR, _CLIENT_VERSION_REVISION, m4_if(_CLIENT_VERSION_BUILD, [0], [], _CLIENT_VERSION_BUILD))m4_if(_CLIENT_VERSION_RC, [0], [], [rc]_CLIENT_VERSION_RC),[https://github.com/bitcoin/bitcoin/issues],[bitcoin],[https://bitcoincore.org/]) +define(_COPYRIGHT_HOLDERS_SUBSTITUTION,[[Litecoin Core]]) +AC_INIT([Litecoin Core],m4_join([.], _CLIENT_VERSION_MAJOR, _CLIENT_VERSION_MINOR, _CLIENT_VERSION_REVISION, m4_if(_CLIENT_VERSION_BUILD, [0], [], _CLIENT_VERSION_BUILD))m4_if(_CLIENT_VERSION_RC, [0], [], [rc]_CLIENT_VERSION_RC),[https://github.com/litecoin-project/litecoin/issues],[litecoin],[https://litecoin.org/]) AC_CONFIG_SRCDIR([src/validation.cpp]) AC_CONFIG_HEADERS([src/config/bitcoin-config.h]) AC_CONFIG_AUX_DIR([build-aux]) AC_CONFIG_MACRO_DIR([build-aux/m4]) -BITCOIN_DAEMON_NAME=bitcoind -BITCOIN_GUI_NAME=bitcoin-qt -BITCOIN_CLI_NAME=bitcoin-cli -BITCOIN_TX_NAME=bitcoin-tx -BITCOIN_WALLET_TOOL_NAME=bitcoin-wallet +BITCOIN_DAEMON_NAME=litecoind +BITCOIN_GUI_NAME=litecoin-qt +BITCOIN_CLI_NAME=litecoin-cli +BITCOIN_TX_NAME=litecoin-tx +BITCOIN_WALLET_TOOL_NAME=litecoin-wallet dnl Unless the user specified ARFLAGS, force it to be cr AC_ARG_VAR(ARFLAGS, [Flags for the archiver, defaults to if not set]) @@ -426,7 +426,7 @@ CPPFLAGS="$CPPFLAGS -DHAVE_BUILD_INFO -D__STDC_FORMAT_MACROS" AC_ARG_WITH([utils], [AS_HELP_STRING([--with-utils], - [build bitcoin-cli bitcoin-tx bitcoin-wallet (default=yes)])], + [build litecoin-cli litecoin-tx litecoin-wallet (default=yes)])], [build_bitcoin_utils=$withval], [build_bitcoin_utils=yes]) @@ -456,7 +456,7 @@ AC_ARG_WITH([libs], AC_ARG_WITH([daemon], [AS_HELP_STRING([--with-daemon], - [build bitcoind daemon (default=yes)])], + [build litecoind daemon (default=yes)])], [build_bitcoind=$withval], [build_bitcoind=yes]) @@ -1253,19 +1253,19 @@ if test x$have_protobuf != xno && BITCOIN_QT_PATH_PROGS([PROTOC], [protoc],$protoc_bin_path) fi -AC_MSG_CHECKING([whether to build bitcoind]) +AC_MSG_CHECKING([whether to build litecoind]) AM_CONDITIONAL([BUILD_BITCOIND], [test x$build_bitcoind = xyes]) AC_MSG_RESULT($build_bitcoind) -AC_MSG_CHECKING([whether to build bitcoin-cli]) +AC_MSG_CHECKING([whether to build litecoin-cli]) AM_CONDITIONAL([BUILD_BITCOIN_CLI], [test x$build_bitcoin_cli = xyes]) AC_MSG_RESULT($build_bitcoin_cli) -AC_MSG_CHECKING([whether to build bitcoin-tx]) +AC_MSG_CHECKING([whether to build litecoin-tx]) AM_CONDITIONAL([BUILD_BITCOIN_TX], [test x$build_bitcoin_tx = xyes]) AC_MSG_RESULT($build_bitcoin_tx) -AC_MSG_CHECKING([whether to build bitcoin-wallet]) +AC_MSG_CHECKING([whether to build litecoin-wallet]) AM_CONDITIONAL([BUILD_BITCOIN_WALLET], [test x$build_bitcoin_wallet = xyes]) AC_MSG_RESULT($build_bitcoin_wallet) @@ -1366,7 +1366,7 @@ if test x$bitcoin_enable_qt != xno; then AC_MSG_WARN("xgettext is required to update qt translations") fi - AC_MSG_CHECKING([whether to build test_bitcoin-qt]) + AC_MSG_CHECKING([whether to build test_litecoin-qt]) if test x$use_gui_tests$bitcoin_enable_qt_test = xyesyes; then AC_MSG_RESULT([yes]) BUILD_TEST_QT="yes" @@ -1394,7 +1394,7 @@ fi AM_CONDITIONAL([ENABLE_ZMQ], [test "x$use_zmq" = "xyes"]) -AC_MSG_CHECKING([whether to build test_bitcoin]) +AC_MSG_CHECKING([whether to build test_litecoin]) if test x$use_tests = xyes; then AC_MSG_RESULT([yes]) BUILD_TEST="yes" diff --git a/contrib/README.md b/contrib/README.md index 8915919766..ce41361e54 100644 --- a/contrib/README.md +++ b/contrib/README.md @@ -13,7 +13,7 @@ Construct a linear, no-fork, best version of the blockchain. ### [Qos](/contrib/qos) ### -A Linux bash script that will set up traffic control (tc) to limit the outgoing bandwidth for connections to the Bitcoin network. This means one can have an always-on bitcoind instance running, and another local bitcoind/bitcoin-qt instance which connects to this node and receives blocks from it. +A Linux bash script that will set up traffic control (tc) to limit the outgoing bandwidth for connections to the Litecoin network. This means one can have an always-on litecoind instance running, and another local litecoind/litecoin-qt instance which connects to this node and receives blocks from it. ### [Seeds](/contrib/seeds) ### Utility to generate the pnSeed[] array that is compiled into the client. @@ -30,7 +30,7 @@ All other packaging related files can be found in the [bitcoin-core/packaging](h Files used during the gitian build process. For more information about gitian, see the [the Bitcoin Core documentation repository](https://github.com/bitcoin-core/docs). ### [Gitian-keys](/contrib/gitian-keys) -PGP keys used for signing Bitcoin Core [Gitian release](/doc/release-process.md) results. +PGP keys used for signing Litecoin Core [Gitian release](/doc/release-process.md) results. ### [MacDeploy](/contrib/macdeploy) ### Scripts and notes for Mac builds. @@ -42,7 +42,7 @@ Test and Verify Tools --------------------- ### [TestGen](/contrib/testgen) ### -Utilities to generate test vectors for the data-driven Bitcoin tests. +Utilities to generate test vectors for the data-driven Litecoin tests. ### [Verify Binaries](/contrib/verifybinaries) ### -This script attempts to download and verify the signature file SHA256SUMS.asc from bitcoin.org. +This script attempts to download and verify the signature file SHA256SUMS.asc from litecoin.org. diff --git a/contrib/devtools/gen-manpages.sh b/contrib/devtools/gen-manpages.sh index 63b9847100..092db2d061 100755 --- a/contrib/devtools/gen-manpages.sh +++ b/contrib/devtools/gen-manpages.sh @@ -7,11 +7,11 @@ BUILDDIR=${BUILDDIR:-$TOPDIR} BINDIR=${BINDIR:-$BUILDDIR/src} MANDIR=${MANDIR:-$TOPDIR/doc/man} -BITCOIND=${BITCOIND:-$BINDIR/bitcoind} -BITCOINCLI=${BITCOINCLI:-$BINDIR/bitcoin-cli} -BITCOINTX=${BITCOINTX:-$BINDIR/bitcoin-tx} -WALLET_TOOL=${WALLET_TOOL:-$BINDIR/bitcoin-wallet} -BITCOINQT=${BITCOINQT:-$BINDIR/qt/bitcoin-qt} +BITCOIND=${BITCOIND:-$BINDIR/litecoind} +BITCOINCLI=${BITCOINCLI:-$BINDIR/litecoin-cli} +BITCOINTX=${BITCOINTX:-$BINDIR/litecoin-tx} +WALLET_TOOL=${WALLET_TOOL:-$BINDIR/litecoin-wallet} +BITCOINQT=${BITCOINQT:-$BINDIR/qt/litecoin-qt} [ ! -x $BITCOIND ] && echo "$BITCOIND not found or not executable." && exit 1 @@ -22,7 +22,7 @@ BTCVER=($($BITCOINCLI --version | head -n1 | awk -F'[ -]' '{ print $6, $7 }')) # This gets autodetected fine for bitcoind if --version-string is not set, # but has different outcomes for bitcoin-qt and bitcoin-cli. echo "[COPYRIGHT]" > footer.h2m -$BITCOIND --version | sed -n '1!p' >> footer.h2m +$LITECOIND --version | sed -n '1!p' >> footer.h2m for cmd in $BITCOIND $BITCOINCLI $BITCOINTX $WALLET_TOOL $BITCOINQT; do cmdname="${cmd##*/}" diff --git a/contrib/gitian-keys/README.md b/contrib/gitian-keys/README.md index ffe4fb144b..da965ec26b 100644 --- a/contrib/gitian-keys/README.md +++ b/contrib/gitian-keys/README.md @@ -24,4 +24,4 @@ while read fingerprint keyholder_name; do gpg --keyserver hkp://subset.pool.sks- ``` Add your key to the list if you provided Gitian signatures for two major or -minor releases of Bitcoin Core. +minor releases of Litecoin Core. diff --git a/contrib/install_db4.sh b/contrib/install_db4.sh index 088d1c9dce..dbf454f4fe 100755 --- a/contrib/install_db4.sh +++ b/contrib/install_db4.sh @@ -9,7 +9,7 @@ if [ -z "${1}" ]; then echo "Usage: $0 [ ...]" echo echo "Must specify a single argument: the directory in which db4 will be built." - echo "This is probably \`pwd\` if you're at the root of the bitcoin repository." + echo "This is probably \`pwd\` if you're at the root of the litecoin repository." exit 1 fi @@ -81,7 +81,7 @@ make install echo echo "db4 build complete." echo -echo 'When compiling bitcoind, run `./configure` in the following way:' +echo 'When compiling litecoind, run `./configure` in the following way:' echo echo " export BDB_PREFIX='${BDB_PREFIX}'" echo ' ./configure BDB_LIBS="-L${BDB_PREFIX}/lib -ldb_cxx-4.8" BDB_CFLAGS="-I${BDB_PREFIX}/include" ...' diff --git a/contrib/linearize/README.md b/contrib/linearize/README.md index 2985106982..fb36bed86c 100644 --- a/contrib/linearize/README.md +++ b/contrib/linearize/README.md @@ -1,5 +1,5 @@ # Linearize -Construct a linear, no-fork, best version of the Bitcoin blockchain. The scripts +Construct a linear, no-fork, best version of the Litecoin blockchain. The scripts run using Python 3 but are compatible with Python 2. ## Step 1: Download hash list @@ -12,7 +12,7 @@ Required configuration file settings for linearize-hashes: Optional config file setting for linearize-hashes: * RPC: `host` (Default: `127.0.0.1`) -* RPC: `port` (Default: `8332`) +* RPC: `port` (Default: `9332`) * Blockchain: `min_height`, `max_height` * `rev_hash_bytes`: If true, the written block hash list will be byte-reversed. (In other words, the hash returned by getblockhash will have its @@ -21,7 +21,7 @@ standalone hash lists but safe to use with linearize-data.py, which will output the same data no matter which byte format is chosen. The `linearize-hashes` script requires a connection, local or remote, to a -JSON-RPC server. Running `bitcoind` or `bitcoin-qt -server` will be sufficient. +JSON-RPC server. Running `litecoind` or `litecoin-qt -server` will be sufficient. ## Step 2: Copy local block data @@ -39,7 +39,7 @@ will be printed. respectively, to the current time and to the timestamp of the most recent block written to the script's blockchain. * `genesis`: The hash of the genesis block in the blockchain. -* `input`: bitcoind blocks/ directory containing blkNNNNN.dat +* `input`: litecoind blocks/ directory containing blkNNNNN.dat * `hashlist`: text file containing list of block hashes created by linearize-hashes.py. * `max_out_sz`: Maximum size for files created by the `output_file` option. diff --git a/contrib/linearize/example-linearize.cfg b/contrib/linearize/example-linearize.cfg index 84129f204a..84dc588a74 100644 --- a/contrib/linearize/example-linearize.cfg +++ b/contrib/linearize/example-linearize.cfg @@ -1,7 +1,7 @@ -# bitcoind RPC settings (linearize-hashes) +# litecoind RPC settings (linearize-hashes) rpcuser=someuser rpcpassword=somepassword -#datadir=~/.bitcoin +#datadir=~/.litecoin host=127.0.0.1 #mainnet default @@ -19,14 +19,14 @@ max_height=313000 # bootstrap.dat input/output settings (linearize-data) # mainnet -netmagic=f9beb4d9 -genesis=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f -input=/home/example/.bitcoin/blocks +netmagic=fbc0b6db +genesis=12a765e31ffd4059bada1e25190f6e98c99d9714d334efa41a195a7e7e04bfe2 +input=/home/example/.litecoin/blocks # testnet -#netmagic=0b110907 -#genesis=000000000933ea01ad0ee984209779baaec3ced90fa3f408719526f8d77f4943 -#input=/home/example/.bitcoin/testnet3/blocks +#netmagic=fdd2c8f1 +#genesis=4966625a4b2851d9fdee139e56211a0d88575f59ed816ff5e6a63deb4e3e29a0 +#input=/home/example/.litecoin/testnet3/blocks # "output" option causes blockchain files to be written to the given location, # with "output_file" ignored. If not used, "output_file" is used instead. diff --git a/contrib/linearize/linearize-hashes.py b/contrib/linearize/linearize-hashes.py index 8529470e09..d9efc13cd4 100755 --- a/contrib/linearize/linearize-hashes.py +++ b/contrib/linearize/linearize-hashes.py @@ -120,7 +120,7 @@ if __name__ == '__main__': if 'host' not in settings: settings['host'] = '127.0.0.1' if 'port' not in settings: - settings['port'] = 8332 + settings['port'] = 9332 if 'min_height' not in settings: settings['min_height'] = 0 if 'max_height' not in settings: diff --git a/contrib/macdeploy/README.md b/contrib/macdeploy/README.md index 6163734e62..50cc94d20e 100644 --- a/contrib/macdeploy/README.md +++ b/contrib/macdeploy/README.md @@ -11,5 +11,5 @@ This script should not be run manually, instead, after building as usual: During the process, the disk image window will pop up briefly where the fancy settings are applied. This is normal, please do not interfere. -When finished, it will produce `Bitcoin-Core.dmg`. +When finished, it will produce `Litecoin-Core.dmg`. diff --git a/contrib/macdeploy/custom_dsstore.py b/contrib/macdeploy/custom_dsstore.py index dc1c1882dd..be48310758 100755 --- a/contrib/macdeploy/custom_dsstore.py +++ b/contrib/macdeploy/custom_dsstore.py @@ -44,8 +44,8 @@ alias = Alias.from_bytes(icvp['backgroundImageAlias']) alias.volume.name = package_name_ns alias.volume.posix_path = '/Volumes/' + package_name_ns alias.volume.disk_image_alias.target.filename = package_name_ns + '.temp.dmg' -alias.volume.disk_image_alias.target.carbon_path = 'Macintosh HD:Users:\x00bitcoinuser:\x00Documents:\x00bitcoin:\x00bitcoin:\x00' + package_name_ns + '.temp.dmg' -alias.volume.disk_image_alias.target.posix_path = 'Users/bitcoinuser/Documents/bitcoin/bitcoin/' + package_name_ns + '.temp.dmg' +alias.volume.disk_image_alias.target.carbon_path = 'Macintosh HD:Users:\x00litecoinuser:\x00Documents:\x00litecoin:\x00litecoin:\x00' + package_name_ns + '.temp.dmg' +alias.volume.disk_image_alias.target.posix_path = 'Users/litecoinuser/Documents/litecoin/litecoin/' + package_name_ns + '.temp.dmg' alias.target.carbon_path = package_name_ns + ':.background:\x00background.tiff' icvp['backgroundImageAlias'] = biplist.Data(alias.to_bytes()) ds['.']['icvp'] = icvp @@ -53,7 +53,7 @@ ds['.']['icvp'] = icvp ds['.']['vSrn'] = ('long', 1) ds['Applications']['Iloc'] = (370, 156) -ds['Bitcoin-Qt.app']['Iloc'] = (128, 156) +ds['Litecoin-Qt.app']['Iloc'] = (128, 156) ds.flush() ds.close() diff --git a/contrib/macdeploy/detached-sig-create.sh b/contrib/macdeploy/detached-sig-create.sh index 5281ebcc47..b116044d6d 100755 --- a/contrib/macdeploy/detached-sig-create.sh +++ b/contrib/macdeploy/detached-sig-create.sh @@ -7,7 +7,7 @@ export LC_ALL=C set -e ROOTDIR=dist -BUNDLE="${ROOTDIR}/Bitcoin-Qt.app" +BUNDLE="${ROOTDIR}/Litecoin-Qt.app" CODESIGN=codesign TEMPDIR=sign.temp TEMPLIST=${TEMPDIR}/signatures.txt diff --git a/contrib/macdeploy/fancy.plist b/contrib/macdeploy/fancy.plist index ef277a7f14..1dd36c9d1b 100644 --- a/contrib/macdeploy/fancy.plist +++ b/contrib/macdeploy/fancy.plist @@ -22,7 +22,7 @@ 370 156 - Bitcoin-Qt.app + Litecoin-Qt.app 128 156 diff --git a/contrib/macdeploy/macdeployqtplus b/contrib/macdeploy/macdeployqtplus index 9da03e5b02..d4034d0c2e 100755 --- a/contrib/macdeploy/macdeployqtplus +++ b/contrib/macdeploy/macdeployqtplus @@ -154,7 +154,7 @@ class FrameworkInfo(object): class ApplicationBundleInfo(object): def __init__(self, path): self.path = path - appName = "Bitcoin-Qt" + appName = "Litecoin-Qt" self.binaryPath = os.path.join(path, "Contents", "MacOS", appName) if not os.path.exists(self.binaryPath): raise RuntimeError("Could not find bundle binary for " + path) @@ -596,7 +596,7 @@ else: # ------------------------------------------------ -target = os.path.join("dist", "Bitcoin-Qt.app") +target = os.path.join("dist", "Litecoin-Qt.app") if verbose >= 2: print("+ Copying source bundle +") diff --git a/contrib/seeds/README.md b/contrib/seeds/README.md index 502c20d0d6..149092adc9 100644 --- a/contrib/seeds/README.md +++ b/contrib/seeds/README.md @@ -8,9 +8,9 @@ and remove old versions as necessary (at a minimum when GetDesirableServiceFlags changes its default return value, as those are the services which seeds are added to addrman with). -The seeds compiled into the release are created from sipa's DNS seed data, like this: +The seeds compiled into the release are created from poolers's DNS seed data, like this: - curl -s http://bitcoin.sipa.be/seeds.txt.gz | gzip -dc > seeds_main.txt + curl -s https://www.litecoinpool.org/seeds.txt > seeds_main.txt python3 makeseeds.py < seeds_main.txt > nodes_main.txt python3 generate-seeds.py . > ../../src/chainparamsseeds.h diff --git a/contrib/seeds/generate-seeds.py b/contrib/seeds/generate-seeds.py index ab96d33744..b9c3a5751c 100755 --- a/contrib/seeds/generate-seeds.py +++ b/contrib/seeds/generate-seeds.py @@ -121,7 +121,7 @@ def main(): g.write('#ifndef BITCOIN_CHAINPARAMSSEEDS_H\n') g.write('#define BITCOIN_CHAINPARAMSSEEDS_H\n') g.write('/**\n') - g.write(' * List of fixed seed nodes for the bitcoin network\n') + g.write(' * List of fixed seed nodes for the litecoin network\n') g.write(' * AUTOGENERATED by contrib/seeds/generate-seeds.py\n') g.write(' *\n') g.write(' * Each line contains a 16-byte IPv6 address and a port.\n') diff --git a/contrib/testgen/README.md b/contrib/testgen/README.md index 580ed541cf..5615877f0a 100644 --- a/contrib/testgen/README.md +++ b/contrib/testgen/README.md @@ -1,6 +1,6 @@ ### TestGen ### -Utilities to generate test vectors for the data-driven Bitcoin tests. +Utilities to generate test vectors for the data-driven Litecoin tests. Usage: diff --git a/contrib/zmq/zmq_sub.py b/contrib/zmq/zmq_sub.py index 06893407f5..acb6d6dee2 100644 --- a/contrib/zmq/zmq_sub.py +++ b/contrib/zmq/zmq_sub.py @@ -6,8 +6,8 @@ """ ZMQ example using python3's asyncio - Bitcoin should be started with the command line arguments: - bitcoind -testnet -daemon \ + Litecoind should be started with the command line arguments: + litecoind -testnet -daemon \ -zmqpubrawtx=tcp://127.0.0.1:28332 \ -zmqpubrawblock=tcp://127.0.0.1:28332 \ -zmqpubhashtx=tcp://127.0.0.1:28332 \ diff --git a/contrib/zmq/zmq_sub3.4.py b/contrib/zmq/zmq_sub3.4.py index 66fdf7887f..61477309e1 100644 --- a/contrib/zmq/zmq_sub3.4.py +++ b/contrib/zmq/zmq_sub3.4.py @@ -6,8 +6,8 @@ """ ZMQ example using python3's asyncio - Bitcoin should be started with the command line arguments: - bitcoind -testnet -daemon \ + Litecoin should be started with the command line arguments: + litecoind -testnet -daemon \ -zmqpubrawtx=tcp://127.0.0.1:28332 \ -zmqpubrawblock=tcp://127.0.0.1:28332 \ -zmqpubhashtx=tcp://127.0.0.1:28332 \ diff --git a/depends/README.md b/depends/README.md index 763b27c2ce..6ed552ec4c 100644 --- a/depends/README.md +++ b/depends/README.md @@ -12,9 +12,9 @@ For example: make HOST=x86_64-w64-mingw32 -j4 -A prefix will be generated that's suitable for plugging into Bitcoin's +A prefix will be generated that's suitable for plugging into Litecoin's configure. In the above example, a dir named x86_64-w64-mingw32 will be -created. To use it for Bitcoin: +created. To use it for Litecoin: ./configure --prefix=`pwd`/depends/x86_64-w64-mingw32 @@ -77,7 +77,7 @@ The following can be set when running make: make FOO=bar BUILD_ID_SALT: Optional salt to use when generating build package ids If some packages are not built, for example `make NO_WALLET=1`, the appropriate -options will be passed to bitcoin's configure. In this case, `--disable-wallet`. +options will be passed to litecoin's configure. In this case, `--disable-wallet`. ### Additional targets diff --git a/depends/description.md b/depends/description.md index 9fc7093be4..832b0736ed 100644 --- a/depends/description.md +++ b/depends/description.md @@ -1,4 +1,4 @@ -This is a system of building and caching dependencies necessary for building Bitcoin. +This is a system of building and caching dependencies necessary for building Litecoin. There are several features that make it different from most similar systems: ### It is designed to be builder and host agnostic diff --git a/doc/README.md b/doc/README.md index b4fa933c8e..d96c57d47d 100644 --- a/doc/README.md +++ b/doc/README.md @@ -1,41 +1,41 @@ -Bitcoin Core +Litecoin Core ============= Setup --------------------- -Bitcoin Core is the original Bitcoin client and it builds the backbone of the network. It downloads and, by default, stores the entire history of Bitcoin transactions, which requires a few hundred gigabytes of disk space. 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. +Litecoin Core is the original Litecoin client and it builds the backbone of the network. It downloads and, by default, stores the entire history of Litecoin transactions, which requires approximately 22 gigabytes of disk space. 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. -To download Bitcoin Core, visit [bitcoincore.org](https://bitcoincore.org/en/download/). +To download Litecoin Core, visit [litecoin.org](https://litecoin.org/). Running --------------------- -The following are some helpful notes on how to run Bitcoin Core on your native platform. +The following are some helpful notes on how to run Litecoin Core on your native platform. ### Unix Unpack the files into a directory and run: -- `bin/bitcoin-qt` (GUI) or -- `bin/bitcoind` (headless) +- `bin/litecoin-qt` (GUI) or +- `bin/litecoind` (headless) ### Windows -Unpack the files into a directory, and then run bitcoin-qt.exe. +Unpack the files into a directory, and then run litecoin-qt.exe. ### macOS -Drag Bitcoin Core to your applications folder, and then run Bitcoin Core. +Drag Litecoin Core to your applications folder, and then run Litecoin Core. ### Need Help? -* See the documentation at the [Bitcoin Wiki](https://en.bitcoin.it/wiki/Main_Page) +* See the documentation at the [Litecoin Wiki](https://litecoin.info/) 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). +* Ask for help on [#litecoin](http://webchat.freenode.net?channels=litecoin) on Freenode. If you don't have an IRC client use [webchat here](http://webchat.freenode.net?channels=litecoin). +* Ask for help on the [LitecoinTalk](https://litecointalk.io/) forums, in the [Technical Support section](https://litecointalk.io/c/technical-support). Building --------------------- -The following are developer notes on how to build Bitcoin Core 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 Litecoin Core on your native platform. They are not complete guides, but include notes on the necessary libraries, compile flags, etc. - [Dependencies](dependencies.md) - [macOS Build Notes](build-osx.md) @@ -48,13 +48,12 @@ The following are developer notes on how to build Bitcoin Core on your native pl Development --------------------- -The Bitcoin repo's [root README](/README.md) contains relevant information on the development process and automated testing. +The Litecoin repo's [root README](/README.md) contains relevant information on the development process and automated testing. - [Developer Notes](developer-notes.md) - [Productivity Notes](productivity.md) - [Release Notes](release-notes.md) - [Release Process](release-process.md) -- [Source Code Documentation (External Link)](https://dev.visucore.com/bitcoin/doxygen/) - [Translation Process](translation_process.md) - [Translation Strings Policy](translation_strings_policy.md) - [JSON-RPC Interface](JSON-RPC-interface.md) @@ -65,9 +64,8 @@ The Bitcoin repo's [root README](/README.md) contains relevant information on th - [Benchmarking](benchmarking.md) ### Resources -* Discuss on the [BitcoinTalk](https://bitcointalk.org/) forums, in the [Development & Technical Discussion board](https://bitcointalk.org/index.php?board=6.0). -* Discuss project-specific development on #bitcoin-core-dev on Freenode. If you don't have an IRC client, use [webchat here](http://webchat.freenode.net/?channels=bitcoin-core-dev). -* Discuss general Bitcoin development on #bitcoin-dev on Freenode. If you don't have an IRC client, use [webchat here](http://webchat.freenode.net/?channels=bitcoin-dev). +* Discuss on the [LitecoinTalk](https://litecointalk.io/) forums. +* Discuss general Litecoin development on #litecoin-dev on Freenode. If you don't have an IRC client use [webchat here](http://webchat.freenode.net/?channels=litecoin-dev. ### Miscellaneous - [Assets Attribution](assets-attribution.md) diff --git a/doc/README_windows.txt b/doc/README_windows.txt index 07d61b3bda..d3885952b4 100644 --- a/doc/README_windows.txt +++ b/doc/README_windows.txt @@ -1,9 +1,9 @@ -Bitcoin Core +Litecoin Core ============= Intro ----- -Bitcoin is a free open source peer-to-peer electronic cash system that is +Litecoin 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. @@ -11,13 +11,13 @@ with each other, with the help of a P2P network to check for double-spending. Setup ----- -Unpack the files into a directory and run bitcoin-qt.exe. +Unpack the files into a directory and run litecoin-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; +Litecoin Core is the original Litecoin client and it builds the backbone of the network. +However, it downloads and stores the entire history of Litecoin 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: - https://en.bitcoin.it/wiki/Main_Page +See the litecoin wiki at: + https://litecoin.info/ for more help and information. diff --git a/doc/REST-interface.md b/doc/REST-interface.md index 001f6d763a..2616e3ed30 100644 --- a/doc/REST-interface.md +++ b/doc/REST-interface.md @@ -3,8 +3,8 @@ Unauthenticated REST Interface The REST API can be enabled with the `-rest` option. -The interface runs on the same port as the JSON-RPC interface, by default port 8332 for mainnet, port 18332 for testnet, -and port 18443 for regtest. +The interface runs on the same port as the JSON-RPC interface, by default port 9332 for mainnet, port 19332 for testnet, +and port 19443 for regtest. REST Interface consistency guarantees ------------------------------------- @@ -105,7 +105,7 @@ Only supports JSON as output format. * bytes : (numeric) size of the TX mempool in bytes * usage : (numeric) total TX mempool memory usage * maxmempool : (numeric) maximum memory usage for the mempool in bytes -* mempoolminfee : (numeric) minimum feerate (BTC per KB) for tx to be accepted +* mempoolminfee : (numeric) minimum feerate (LTC per KB) for tx to be accepted `GET /rest/mempool/contents.json` @@ -114,4 +114,4 @@ Only supports JSON as output format. Risks ------------- -Running a web browser on the same node with a REST enabled bitcoind can be a risk. Accessing prepared XSS websites could read out tx/block data of your node by placing links like `