diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md index eedeeb4e5..c898767e9 100644 --- a/.github/ISSUE_TEMPLATE.md +++ b/.github/ISSUE_TEMPLATE.md @@ -1,8 +1,8 @@ - - + diff --git a/.gitignore b/.gitignore index b44614f24..2e38d7b44 100644 --- a/.gitignore +++ b/.gitignore @@ -60,6 +60,7 @@ src/qt/bitcoin-qt.includes .deps .dirstamp .libs +.vscode .*.swp *.*~* *.bak @@ -105,7 +106,6 @@ litecoin-qt_test # Resources cpp qrc_*.cpp - # Mac specific .DS_Store build @@ -117,7 +117,7 @@ releases *.gcno *.gcda /*.info -test_bitcoin.coverage/ +test_litecoin.coverage/ total.coverage/ fuzz.coverage/ coverage_percent.txt diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 2e1147438..a5b4a5798 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. @@ -25,7 +25,7 @@ as a new contributor. It also will teach you much more about the code and process than opening pull requests. Please refer to the [peer review](#peer-review) section below. -Before you start contributing, familiarize yourself with the Bitcoin Core build +Before you start contributing, familiarize yourself with the Litecoin Core build system and tests. Refer to the documentation in the repository on how to build Bitcoin Core and how to run the unit tests, functional tests, and fuzz tests. @@ -67,7 +67,7 @@ Discussion about codebase improvements happens in GitHub issues and 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 consensus or P2P protocol changes before working on a patch set. @@ -143,7 +143,7 @@ the pull request affects. Valid areas as: - `consensus` for changes to consensus critical code - `doc` for changes to the documentation - - `qt` or `gui` for changes to bitcoin-qt + - `qt` or `gui` for changes to litecoin-qt - `log` for changes to log messages - `mining` for changes to the mining code - `net` or `p2p` for changes to the peer-to-peer network code @@ -282,11 +282,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 @@ -305,7 +305,7 @@ In general, all pull requests must: demonstrating the bug and also proving the fix. This helps prevent regression. - Change relevant comments and documentation when behaviour of code changes. -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 @@ -358,7 +358,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. @@ -425,7 +425,7 @@ https://github.com/bitcoin-core/bitcoin-maintainer-tools#backport). 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 461bc7310..14806a682 100644 --- a/COPYING +++ b/COPYING @@ -2,6 +2,7 @@ The MIT License (MIT) Copyright (c) 2009-2020 The Bitcoin Core developers Copyright (c) 2009-2020 Bitcoin Developers +Copyright (c) 2011-2020 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 520a47d96..be23c6088 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/configure.ac b/configure.ac index 6344f32b1..009519213 100644 --- a/configure.ac +++ b/configure.ac @@ -1475,7 +1475,7 @@ if test x$build_multiprocess != xno; then AC_SUBST(MPGEN_PREFIX) 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) diff --git a/contrib/README.md b/contrib/README.md index 361975baa..54be50a18 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 7cc5c18ba..6de459ed2 100755 --- a/contrib/devtools/gen-manpages.sh +++ b/contrib/devtools/gen-manpages.sh @@ -25,7 +25,7 @@ read -r -a BTCVER <<< "$($BITCOINCLI --version | head -n1 | awk -F'[ -]' '{ prin # 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 ffe4fb144..da965ec26 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 9f8abe665..ce63d87df 100755 --- a/contrib/install_db4.sh +++ b/contrib/install_db4.sh @@ -12,7 +12,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 Litecoin repository." + echo "This is probably \`pwd\` if you're at the root of the litecoin repository." exit 1 fi diff --git a/contrib/linearize/README.md b/contrib/linearize/README.md index 25a1c7351..1448f7954 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. +Construct a linear, no-fork, best version of the Litecoin blockchain. ## Step 1: Download hash list @@ -11,7 +11,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 @@ -20,7 +20,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 @@ -38,7 +38,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 96e65964e..f3ce69ff5 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 @@ -22,14 +22,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 # regtest #netmagic=fabfb5da diff --git a/contrib/linearize/linearize-hashes.py b/contrib/linearize/linearize-hashes.py index fed6e665b..b826e53d6 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 fe677e3a1..58bef4db5 100644 --- a/contrib/macdeploy/README.md +++ b/contrib/macdeploy/README.md @@ -10,7 +10,7 @@ During the deployment process, the disk image window will pop up briefly when the fancy settings are applied. This is normal, please do not interfere, the process will unmount the DMG and cleanup before finishing. -When complete, it will have produced `Bitcoin-Qt.dmg`. +When complete, it will have produced `Litecoin-Qt.dmg`. ## SDK Extraction diff --git a/contrib/macdeploy/custom_dsstore.py b/contrib/macdeploy/custom_dsstore.py index dc1c1882d..be4831075 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/seeds/README.md b/contrib/seeds/README.md index 502c20d0d..149092adc 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 2bb439b06..257474e00 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 fcc5a378e..2a9d92222 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 8b8503331..4c4bbf93e 100755 --- 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/depends/README.md b/depends/README.md index 5225a6d5c..f5a0ec5fb 100644 --- a/depends/README.md +++ b/depends/README.md @@ -12,11 +12,11 @@ For example: make HOST=x86_64-w64-mingw32 -j4 -**Bitcoin Core's configure script by default will ignore the depends output.** In +**Litecoin Core's configure script by default will ignore the depends output.** In order for it to pick up libraries, tools, and settings from the depends build, you must point it at the appropriate `--prefix` directory generated by the build. In the above example, a prefix 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 @@ -124,7 +124,7 @@ from llvm.org. Clang 8 or later is required. 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 0a6f2e644..62281f843 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 19d8204d8..35972c4ca 100644 --- a/doc/README.md +++ b/doc/README.md @@ -1,41 +1,40 @@ -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) -for help and more information. -* Ask for help on [#bitcoin](https://webchat.freenode.net/#bitcoin) on Freenode. If you don't have an IRC client, use [webchat here](https://webchat.freenode.net/#bitcoin). -* Ask for help on the [BitcoinTalk](https://bitcointalk.org/) forums, in the [Technical Support board](https://bitcointalk.org/index.php?board=4.0). +* See the documentation at the [Litecoin Wiki](https://litecoin.info/) for help and more information. +* Ask for help on [#litecoin](https://webchat.freenode.net/#litecoin) on Freenode. If you don't have an IRC client, use [webchat here](https://webchat.freenode.net/#litecoin). +* Ask for help on the [LitecoinTalk](https://litecointalk.io/) forums, in the [Technical Support board](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,7 +47,7 @@ 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) @@ -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](https://webchat.freenode.net/#bitcoin-core-dev). -* Discuss general Bitcoin development on #bitcoin-dev on Freenode. If you don't have an IRC client, use [webchat here](https://webchat.freenode.net/#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](https://webchat.freenode.net/#litecoin-dev). ### Miscellaneous - [Assets Attribution](assets-attribution.md) diff --git a/doc/README_windows.txt b/doc/README_windows.txt index 07d61b3bd..d3885952b 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 4d2a95816..3187321ff 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 ------------------------------------- @@ -116,7 +116,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` @@ -125,4 +125,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 `