@ -7,7 +7,7 @@ dnl Output: If qt version is auto, set bitcoin_enable_qt to false. Else, exit.
@@ -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])
@ -583,7 +583,7 @@ A few guidelines for introducing and reviewing new RPC interfaces:
@@ -583,7 +583,7 @@ A few guidelines for introducing and reviewing new RPC interfaces:
- Try not to overload methods on argument type. E.g. don't make `getblock(true)` and `getblock("hash")`
do different things.
- *Rationale*: This is impossible to use with `bitcoin-cli`, and can be surprising to users.
- *Rationale*: This is impossible to use with `litecoin-cli`, and can be surprising to users.
- *Exception*: Some RPC calls can take both an `int` and `bool`, most notably when a bool was switched
to a multi-value, or due to other historical reasons. **Always** have false map to 0 and
@ -602,7 +602,7 @@ A few guidelines for introducing and reviewing new RPC interfaces:
@@ -602,7 +602,7 @@ A few guidelines for introducing and reviewing new RPC interfaces:
- Add every non-string RPC argument `(method, idx, name)` to the table `vRPCConvertParams` in `rpc/client.cpp`.
- *Rationale*: `bitcoin-cli` and the GUI debug console use this table to determine how to
- *Rationale*: `litecoin-cli` and the GUI debug console use this table to determine how to
convert a plaintext command line to JSON. If the types don't match, the method can be unusable
litecoin-cli \- manual page for litecoin-cli v0.15.0.1
litecoin-cli \- manual page for litecoin-cli v0.15.1.0
.SHDESCRIPTION
Litecoin Core RPC client version v0.15.0.1\-dirty
Litecoin Core RPC client version v0.15.1.0\-dirty
.SS"Usage:"
.TP
litecoin\-cli [options] <command> [params]
@ -78,12 +78,13 @@ Send RPC for non\-default wallet on RPC server (argument is wallet
@@ -78,12 +78,13 @@ Send RPC for non\-default wallet on RPC server (argument is wallet
filename in litecoind directory, required if litecoind/\-Qt runs
with multiple wallets)
.SHCOPYRIGHT
Copyright (C) 2009-2017 The Bitcoin Core developers
Copyright (C) 2011-2017 The Litecoin Core developers
Copyright (C) 2011-2018 The Litecoin Core developers
Copyright (C) 2009-2018 The Bitcoin Core developers
Please contribute if you find Litecoin Core useful. Visit
<https://litecoin.org> for further information about the software.
The source code is available from <https://github.com/litecoin-project/litecoin>.
The source code is available from
<https://github.com/litecoin-project/litecoin>.
This is experimental software.
Distributed under the MIT software license, see the accompanying file COPYING
@ -58,7 +58,7 @@ Keep at most <n> unconnectable transactions in memory (default: 100)
@@ -58,7 +58,7 @@ Keep at most <n> unconnectable transactions in memory (default: 100)
.HP
\fB\-maxmempool=\fR<n>
.IP
Keep the transaction memory pool below <n> megabytes (default: 5)
Keep the transaction memory pool below <n> megabytes (default: 300)
.HP
\fB\-mempoolexpiry=\fR<n>
.IP
@ -76,12 +76,12 @@ Extra transactions to keep in memory for compact block reconstructions
@@ -76,12 +76,12 @@ Extra transactions to keep in memory for compact block reconstructions
.HP
\fB\-par=\fR<n>
.IP
Set the number of script verification threads (\fB\-6\fR to 16, 0 = auto, <0 =
Set the number of script verification threads (\fB\-4\fR to 16, 0 = auto, <0 =
Maximum allowed median peer time offset adjustment. Local perspective of
time may be influenced by peers forward or backward by this
amount. (default: 4200 seconds)
amount. (default: 2100 seconds)
.HP
\fB\-onion=\fR<ip:port>
.IP
@ -206,7 +206,7 @@ Support filtering of blocks and transaction with bloom filters (default:
@@ -206,7 +206,7 @@ Support filtering of blocks and transaction with bloom filters (default:
.HP
\fB\-port=\fR<port>
.IP
Listen for connections on <port> (default: 8333 or testnet: 18333)
Listen for connections on <port> (default: 9333 or testnet: 19335)
.HP
\fB\-proxy=\fR<ip:port>
.IP
@ -269,7 +269,7 @@ Set key pool size to <n> (default: 1000)
@@ -269,7 +269,7 @@ Set key pool size to <n> (default: 1000)
\fB\-fallbackfee=\fR<amt>
.IP
A fee rate (in LTC/kB) that will be used when fee estimation has
insufficient data (default: 0.002)
insufficient data (default: 0.02)
.HP
\fB\-discardfee=\fR<amt>
.IP
@ -427,12 +427,12 @@ Maximum size of data in data carrier transactions we relay and mine
@@ -427,12 +427,12 @@ Maximum size of data in data carrier transactions we relay and mine
.HP
\fB\-mempoolreplacement\fR
.IP
Enable transaction replacement in the memory pool (default: 1)
Enable transaction replacement in the memory pool (default: 0)
.HP
\fB\-minrelaytxfee=\fR<amt>
.IP
Fees (in LTC/kB) smaller than this are considered zero fee for relaying,
mining and transaction creation (default: 0.001)
mining and transaction creation (default: 0.00001)
@ -63,7 +63,7 @@ Keep at most <n> unconnectable transactions in memory (default: 100)
@@ -63,7 +63,7 @@ Keep at most <n> unconnectable transactions in memory (default: 100)
.HP
\fB\-maxmempool=\fR<n>
.IP
Keep the transaction memory pool below <n> megabytes (default: 5)
Keep the transaction memory pool below <n> megabytes (default: 300)
.HP
\fB\-mempoolexpiry=\fR<n>
.IP
@ -81,12 +81,12 @@ Extra transactions to keep in memory for compact block reconstructions
@@ -81,12 +81,12 @@ Extra transactions to keep in memory for compact block reconstructions
.HP
\fB\-par=\fR<n>
.IP
Set the number of script verification threads (\fB\-6\fR to 16, 0 = auto, <0 =
Set the number of script verification threads (\fB\-4\fR to 16, 0 = auto, <0 =
Maximum allowed median peer time offset adjustment. Local perspective of
time may be influenced by peers forward or backward by this
amount. (default: 4200 seconds)
amount. (default: 2100 seconds)
.HP
\fB\-onion=\fR<ip:port>
.IP
@ -211,7 +211,7 @@ Support filtering of blocks and transaction with bloom filters (default:
@@ -211,7 +211,7 @@ Support filtering of blocks and transaction with bloom filters (default:
.HP
\fB\-port=\fR<port>
.IP
Listen for connections on <port> (default: 8333 or testnet: 18333)
Listen for connections on <port> (default: 9333 or testnet: 19335)
.HP
\fB\-proxy=\fR<ip:port>
.IP
@ -274,11 +274,11 @@ Set key pool size to <n> (default: 1000)
@@ -274,11 +274,11 @@ Set key pool size to <n> (default: 1000)
\fB\-fallbackfee=\fR<amt>
.IP
A fee rate (in LTC/kB) that will be used when fee estimation has
insufficient data (default: 0.002)
insufficient data (default: 0.02)
.HP
\fB\-discardfee=\fR<amt>
.IP
The fee rate (in BTC/kB) that indicates your tolerance for discarding
The fee rate (in LTC/kB) that indicates your tolerance for discarding
change by adding it to the fee (default: 0.0001). Note: An output
is discarded if it is dust at this rate, but we will always
discard up to the dust relay fee and a discard fee above that is
@ -432,11 +432,11 @@ Maximum size of data in data carrier transactions we relay and mine
@@ -432,11 +432,11 @@ Maximum size of data in data carrier transactions we relay and mine
.HP
\fB\-mempoolreplacement\fR
.IP
Enable transaction replacement in the memory pool (default: 1)
Enable transaction replacement in the memory pool (default: 0)
.HP
\fB\-minrelaytxfee=\fR<amt>
.IP
Fees (in BTC/kB) smaller than this are considered zero fee for relaying,
Fees (in LTC/kB) smaller than this are considered zero fee for relaying,
mining and transaction creation (default: 0.00001)
strUsage+=HelpMessageOpt("-rpcpassword=<pw>",_("Password for JSON-RPC connections"));
strUsage+=HelpMessageOpt("-rpcclienttimeout=<n>",strprintf(_("Timeout in seconds during HTTP requests, or 0 for no timeout. (default: %d)"),DEFAULT_HTTP_CLIENT_TIMEOUT));
strUsage+=HelpMessageOpt("-stdin",_("Read extra arguments from standard input, one per line until EOF/Ctrl-D (recommended for sensitive information such as passphrases)"));
strUsage+=HelpMessageOpt("-rpcwallet=<walletname>",_("Send RPC for non-default wallet on RPC server (argument is wallet filename in bitcoind directory, required if bitcoind/-Qt runs with multiple wallets)"));
strUsage+=HelpMessageOpt("-rpcwallet=<walletname>",_("Send RPC for non-default wallet on RPC server (argument is wallet filename in litecoind directory, required if litecoind/-Qt runs with multiple wallets)"));
returnstrUsage;
}
@ -339,7 +339,7 @@ int CommandLineRPC(int argc, char *argv[])
@@ -339,7 +339,7 @@ int CommandLineRPC(int argc, char *argv[])
This directory contains integration tests that test bitcoind and its
This directory contains integration tests that test litecoind and its
utilities in their entirety. It does not contain unit tests, which
can be found in [/src/test](/src/test), [/src/wallet/test](/src/wallet/test),
etc.
@ -6,10 +6,10 @@ etc.
@@ -6,10 +6,10 @@ etc.
There are currently two sets of tests in this directory:
- [functional](/test/functional) which test the functionality of
bitcoind and bitcoin-qt by interacting with them through the RPC and P2P
litecoind and litecoin-qt by interacting with them through the RPC and P2P
interfaces.
- [util](test/util) which tests the bitcoin utilities, currently only
bitcoin-tx.
- [util](test/util) which tests the litecoin utilities, currently only
litecoin-tx.
The util tests are run as part of `make check` target. The functional
tests are run by the travis continuous build process whenever a pull
@ -70,29 +70,29 @@ options. Run `test_runner.py -h` to see them all.
@@ -70,29 +70,29 @@ options. Run `test_runner.py -h` to see them all.
##### Resource contention
The P2P and RPC ports used by the bitcoind nodes-under-test are chosen to make
conflicts with other processes unlikely. However, if there is another bitcoind
The P2P and RPC ports used by the litecoind nodes-under-test are chosen to make
conflicts with other processes unlikely. However, if there is another litecoind
process running on the system (perhaps from a previous test which hasn't successfully
killed all its bitcoind nodes), then there may be a port conflict which will
killed all its litecoind nodes), then there may be a port conflict which will
cause the test to fail. It is recommended that you run the tests on a system
where no other bitcoind processes are running.
where no other litecoind processes are running.
On linux, the test_framework will warn if there is another
bitcoind process running when the tests are started.
litecoind process running when the tests are started.
If there are zombie bitcoind processes after test failure, you can kill them
If there are zombie litecoind processes after test failure, you can kill them
by running the following commands. **Note that these commands will kill all
bitcoind processes running on the system, so should not be used if any non-test
bitcoind processes are being run.**
litecoind processes running on the system, so should not be used if any non-test
litecoind processes are being run.**
```bash
killall bitcoind
killall litecoind
```
or
```bash
pkill -9 bitcoind
pkill -9 litecoind
```
@ -103,11 +103,11 @@ functional test is run and is stored in test/cache. This speeds up
@@ -103,11 +103,11 @@ functional test is run and is stored in test/cache. This speeds up
test startup times since new blockchains don't need to be generated for
each test. However, the cache may get into a bad state, in which case
tests will fail. If this happens, remove the cache directory (and make
@ -60,10 +60,10 @@ over the network (`CBlock`, `CTransaction`, etc, along with the network-level
@@ -60,10 +60,10 @@ over the network (`CBlock`, `CTransaction`, etc, along with the network-level
wrappers for them, `msg_block`, `msg_tx`, etc).
- P2P tests have two threads. One thread handles all network communication
with the bitcoind(s) being tested (using python's asyncore package); the other
with the litecoind(s) being tested (using python's asyncore package); the other
implements the test logic.
- `NodeConn` is the class used to connect to a bitcoind. If you implement
- `NodeConn` is the class used to connect to a litecoind. If you implement
a callback class that derives from `NodeConnCB` and pass that to the
`NodeConn` object, your code will receive the appropriate callbacks when
events of interest arrive.
@ -78,14 +78,14 @@ Examples tests are `p2p-accept-block.py`, `p2p-compactblocks.py`.
@@ -78,14 +78,14 @@ Examples tests are `p2p-accept-block.py`, `p2p-compactblocks.py`.
#### Comptool
- Comptool is a Testing framework for writing tests that compare the block/tx acceptance
behavior of a bitcoind against 1 or more other bitcoind instances. It should not be used
behavior of a litecoind against 1 or more other litecoind instances. It should not be used
to write static tests with known outcomes, since that type of test is easier to write and
maintain using the standard BitcoinTestFramework.
- Set the `num_nodes` variable (defined in `ComparisonTestFramework`) to start up
1 or more nodes. If using 1 node, then `--testbinary` can be used as a command line
option to change the bitcoind binary used by the test. If using 2 or more nodes,
then `--refbinary` can be optionally used to change the bitcoind that will be used
option to change the litecoind binary used by the test. If using 2 or more nodes,
then `--refbinary` can be optionally used to change the litecoind that will be used
on nodes 2 and up.
- Implement a (generator) function called `get_tests()` which yields `TestInstance`s.
@ -94,13 +94,13 @@ Each `TestInstance` consists of:
@@ -94,13 +94,13 @@ Each `TestInstance` consists of:
* `object` is a `CBlock`, `CTransaction`, or
`CBlockHeader`. `CBlock`'s and `CTransaction`'s are tested for
acceptance. `CBlockHeader`s can be used so that the test runner can deliver
complete headers-chains when requested from the bitcoind, to allow writing
complete headers-chains when requested from the litecoind, to allow writing
tests where blocks can be delivered out of order but still processed by
headers-first bitcoind's.
headers-first litecoind's.
* `outcome` is `True`, `False`, or `None`. If `True`
or `False`, the tip is compared with the expected tip -- either the
block passed in, or the hash specified as the optional 3rd entry. If
`None` is specified, then the test will compare all the bitcoind's
`None` is specified, then the test will compare all the litecoind's
being tested to see if they all agree on what the best tip is.
* `hash` is the block hash of the tip to compare against. Optional to
specify; if left out then the hash of the block passed in will be used as
@ -114,7 +114,7 @@ Each `TestInstance` consists of:
@@ -114,7 +114,7 @@ Each `TestInstance` consists of:
sequence and synced (this is slower when processing many blocks).
- `sync_every_transaction`: `True/False`. Analogous to
`sync_every_block`, except if the outcome on the last tx is "None",
then the contents of the entire mempool are compared across all bitcoind
then the contents of the entire mempool are compared across all litecoind
connections. If `True` or `False`, then only the last tx's
acceptance is tested against the given outcome.
@ -133,7 +133,7 @@ Base class for functional tests.
@@ -133,7 +133,7 @@ Base class for functional tests.
Adrian Gallagher
6 years ago
committed by