netcraft
/
litecoin
mirror of https://github.com/litecoin-project/litecoin
6
0
Fork 0
Code Issues Projects Releases Wiki Activity

Minor changes for 0.15 (#445)

Browse Source 
* Litecoin: Branding

* Litecoin: Update man files

* Litecoin: Update Qt translations
0.15 v0.15.1
Adrian Gallagher 7 years ago committed by GitHub
parent 845fc69ab3
commit 0b47699b90
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
21 changed files with 195 additions and 189 deletions
Show Stats Download Patch File Download Diff File

4
CONTRIBUTING.md
Unescape View File

@ -57,12 +57,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.

4
INSTALL.md
Unescape View File

@ -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.

4
build-aux/m4/bitcoin_qt.m4
Unescape View File

@ -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|qt4|qt5|auto@:>@],
[build bitcoin-qt GUI (default=auto, qt5 tried first)])],
[build litecoin-qt GUI (default=auto, qt5 tried first)])],
[
bitcoin_qt_want_version=$withval
if test x$bitcoin_qt_want_version = xyes; then

4
configure.ac
Unescape View File

@ -297,7 +297,7 @@ CPPFLAGS="$CPPFLAGS -DHAVE_BUILD_INFO -D__STDC_FORMAT_MACROS"
AC_ARG_WITH([utils],
[AS_HELP_STRING([--with-utils],
[build bitcoin-cli bitcoin-tx (default=yes)])],
[build litecoin-cli litecoin-tx (default=yes)])],
[build_bitcoin_utils=$withval],
[build_bitcoin_utils=yes])
@ -309,7 +309,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])

24
contrib/devtools/gen-manpages.sh
Unescape View File

@ -1,29 +1,29 @@
#!/bin/sh
#!/bin/bash
TOPDIR=${TOPDIR:-$(git rev-parse --show-toplevel)}
SRCDIR=${SRCDIR:-$TOPDIR/src}
MANDIR=${MANDIR:-$TOPDIR/doc/man}
BITCOIND=${BITCOIND:-$SRCDIR/litecoind}
BITCOINCLI=${BITCOINCLI:-$SRCDIR/litecoin-cli}
BITCOINTX=${BITCOINTX:-$SRCDIR/litecoin-tx}
BITCOINQT=${BITCOINQT:-$SRCDIR/qt/litecoin-qt}
LITECOIND=${LITECOIND:-$SRCDIR/litecoind}
LITECOINCLI=${LITECOINCLI:-$SRCDIR/litecoin-cli}
LITECOINTX=${LITECOINTX:-$SRCDIR/litecoin-tx}
LITECOINQT=${LITECOINQT:-$SRCDIR/qt/litecoin-qt}
[ ! -x $BITCOIND ] && echo "$LITECOIND not found or not executable." && exit 1
[ ! -x $LITECOIND ] && echo "$LITECOIND not found or not executable." && exit 1
# The autodetected version git tag can screw up manpage output a little bit
BTCVER=($($LITECOINCLI --version | head -n1 | awk -F'[ -]' '{ print $6, $7 }'))
LTCVER=($($LITECOINCLI --version | head -n1 | awk -F'[ -]' '{ print $6, $7 }'))
# Create a footer file with copyright content.
# 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 $BITCOINQT; do
for cmd in $LITECOIND $LITECOINCLI $LITECOINTX $LITECOINQT; do
cmdname="${cmd##*/}"
help2man -N --version-string=${BTCVER[0]} --include=footer.h2m -o ${MANDIR}/${cmdname}.1 ${cmd}
sed -i "s/\\\-${BTCVER[1]}//g" ${MANDIR}/${cmdname}.1
help2man -N --version-string=${LTCVER[0]} --include=footer.h2m -o ${MANDIR}/${cmdname}.1 ${cmd}
sed -i "s/\\\-${LTCVER[1]}//g" ${MANDIR}/${cmdname}.1
done
rm -f footer.h2m
rm -f footer.h2m

2
contrib/linearize/example-linearize.cfg
Unescape View File

@ -1,7 +1,7 @@
# litecoind RPC settings (linearize-hashes)
rpcuser=someuser
rpcpassword=somepassword
#datadir=~/.bitcoin
#datadir=~/.litecoin
host=127.0.0.1
port=9332
#port=19332

4
doc/developer-notes.md
Unescape View File

@ -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:
- 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
from there.

13
doc/man/litecoin-cli.1
Unescape View File

@ -1,9 +1,9 @@
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.47.3.
.TH LITECOIN-CLI "1" "September 2017" "litecoin-cli v0.15.0.1" "User Commands"
.TH LITECOIN-CLI "1" "February 2018" "litecoin-cli v0.15.1.0" "User Commands"
.SH NAME
litecoin-cli \- manual page for litecoin-cli v0.15.0.1
litecoin-cli \- manual page for litecoin-cli v0.15.1.0
.SH DESCRIPTION
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
filename in litecoind directory, required if litecoind/\-Qt runs
with multiple wallets)
.SH COPYRIGHT
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

38
doc/man/litecoin-qt.1
Unescape View File

@ -1,9 +1,9 @@
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.47.3.
.TH LITECOIN-QT "1" "September 2017" "litecoin-qt v0.15.0.1" "User Commands"
.TH LITECOIN-QT "1" "February 2018" "litecoin-qt v0.15.1.0" "User Commands"
.SH NAME
litecoin-qt \- manual page for litecoin-qt v0.15.0.1
litecoin-qt \- manual page for litecoin-qt v0.15.1.0
.SH DESCRIPTION
Litecoin Core version v0.15.0.1\-dirty (64\-bit)
Litecoin Core version v0.15.1.0\-dirty (64\-bit)
Usage:
.IP
litecoin\-qt [command\-line options]
@ -32,9 +32,9 @@ block hash)
If this block is in the chain assume that it and its ancestors are valid
and potentially skip their script verification (0 to verify all,
default:
29c8c00e1a5f446a6364a29633d3f1ee16428d87c8d3851a1c570be8170b04c2,
59c9b9d3fec105bdc716d84caa7579503d5b05b73618d0bf2d5fa639f780a011,
testnet:
ad8ff6c2f5580d2b50bd881e11312425ea84fa99f322bf132beb722f97971bba)
a0afbded94d4be233e191525dc2d467af5c7eab3143c852c3cd549831022aad6)
.HP
\fB\-conf=\fR<file>
.IP
@ -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
.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 =
leave that many cores free, default: 0)
.HP
\fB\-pid=\fR<file>
.IP
Specify pid file (default: litecoind.pid)
Specify pid file (default: litecoin.pid)
.HP
\fB\-prune=\fR<n>
.IP
@ -184,7 +184,7 @@ Maximum per\-connection send buffer, <n>*1000 bytes (default: 1000)
.IP
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:
.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)
\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
.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)
.HP
\fB\-whitelistrelay\fR
.IP
@ -448,11 +448,12 @@ Block creation options:
.HP
\fB\-blockmaxweight=\fR<n>
.IP
Set maximum BIP141 block weight (default: 3000000)
Set maximum BIP141 block weight (default: 3996000)
.HP
\fB\-blockmaxsize=\fR<n>
.IP
Set maximum block size in bytes (default: 750000)
Set maximum BIP141 block weight to this * 4. Deprecated, use
blockmaxweight
.HP
\fB\-blockmintxfee=\fR<amt>
.IP
@ -546,12 +547,13 @@ Show splash screen on startup (default: 1)
.IP
Reset all settings changed in the GUI
.SH COPYRIGHT
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

13
doc/man/litecoin-tx.1
Unescape View File

@ -1,9 +1,9 @@
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.47.3.
.TH LITECOIN-TX "1" "September 2017" "litecoin-tx v0.15.0.1" "User Commands"
.TH LITECOIN-TX "1" "February 2018" "litecoin-tx v0.15.1.0" "User Commands"
.SH NAME
litecoin-tx \- manual page for litecoin-tx v0.15.0.1
litecoin-tx \- manual page for litecoin-tx v0.15.1.0
.SH DESCRIPTION
Litecoin Core litecoin\-tx utility version v0.15.0.1\-dirty
Litecoin Core litecoin\-tx utility version v0.15.1.0\-dirty
.SS "Usage:"
.TP
litecoin\-tx [options] <hex\-tx> [commands]
@ -112,12 +112,13 @@ set=NAME:JSON\-STRING
.IP
Set register NAME to given JSON\-STRING
.SH COPYRIGHT
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

40
doc/man/litecoind.1
Unescape View File

@ -1,9 +1,9 @@
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.47.3.
.TH LITECOIND "1" "September 2017" "litecoind v0.15.0.1" "User Commands"
.TH LITECOIND "1" "February 2018" "litecoind v0.15.1.0" "User Commands"
.SH NAME
litecoind \- manual page for litecoind v0.15.0.1
litecoind \- manual page for litecoind v0.15.1.0
.SH DESCRIPTION
Litecoin Core Daemon version v0.15.0.1\-dirty
Litecoin Core Daemon version v0.15.1.0\-dirty
.SS "Usage:"
.TP
litecoind [options]
@ -33,9 +33,9 @@ block hash)
If this block is in the chain assume that it and its ancestors are valid
and potentially skip their script verification (0 to verify all,
default:
29c8c00e1a5f446a6364a29633d3f1ee16428d87c8d3851a1c570be8170b04c2,
59c9b9d3fec105bdc716d84caa7579503d5b05b73618d0bf2d5fa639f780a011,
testnet:
ad8ff6c2f5580d2b50bd881e11312425ea84fa99f322bf132beb722f97971bba)
a0afbded94d4be233e191525dc2d467af5c7eab3143c852c3cd549831022aad6)
.HP
\fB\-conf=\fR<file>
.IP
@ -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
.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 =
leave that many cores free, default: 0)
.HP
\fB\-pid=\fR<file>
.IP
Specify pid file (default: litecoind.pid)
Specify pid file (default: litecoin.pid)
.HP
\fB\-prune=\fR<n>
.IP
@ -189,7 +189,7 @@ Maximum per\-connection send buffer, <n>*1000 bytes (default: 1000)
.IP
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:
.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)
\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
.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)
.HP
\fB\-whitelistrelay\fR
@ -453,11 +453,12 @@ Block creation options:
.HP
\fB\-blockmaxweight=\fR<n>
.IP
Set maximum BIP141 block weight (default: 3000000)
Set maximum BIP141 block weight (default: 3996000)
.HP
\fB\-blockmaxsize=\fR<n>
.IP
Set maximum block size in bytes (default: 750000)
Set maximum BIP141 block weight to this * 4. Deprecated, use
blockmaxweight
.HP
\fB\-blockmintxfee=\fR<amt>
.IP
@ -525,12 +526,13 @@ non\-verbose mode, non\-segwit(0) or segwit(1) (default: 1)
.IP
Set the number of threads to service RPC calls (default: 4)
.SH COPYRIGHT
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

4
src/bitcoin-cli.cpp
Unescape View File

@ -46,7 +46,7 @@ std::string HelpMessageCli()
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)"));
return strUsage;
}
@ -339,7 +339,7 @@ int CommandLineRPC(int argc, char *argv[])
strPrint += "error message:\n"+errMsg.get_str();
if (errCode.isNum() && errCode.get_int() == RPC_WALLET_NOT_SPECIFIED) {
strPrint += "\nTry adding \"-rpcwallet=<filename>\" option to bitcoin-cli command line.";
strPrint += "\nTry adding \"-rpcwallet=<filename>\" option to litecoin-cli command line.";
}
}
} else {

4
src/qt/intro.cpp
Unescape View File

@ -127,7 +127,7 @@ Intro::Intro(QWidget *parent) :
.arg(tr(PACKAGE_NAME))
.arg(BLOCK_CHAIN_SIZE)
.arg(2009)
.arg(tr("Bitcoin"))
.arg(tr("Litecoin"))
);
ui->lblExplanation2->setText(ui->lblExplanation2->text().arg(tr(PACKAGE_NAME)));
@ -146,7 +146,7 @@ Intro::Intro(QWidget *parent) :
}
requiredSpace += CHAIN_STATE_SIZE;
ui->sizeWarningLabel->setText(
tr("%1 will download and store a copy of the Bitcoin block chain.").arg(tr(PACKAGE_NAME)) + " " +
tr("%1 will download and store a copy of the Litecoin block chain.").arg(tr(PACKAGE_NAME)) + " " +
storageRequiresMsg.arg(requiredSpace) + " " +
tr("The wallet will also be stored in this directory.")
);

150
src/qt/locale/bitcoin_de.ts
Unescape View File

@ -43,11 +43,11 @@
</message>
<message>
<source>Choose the address to send coins to</source>
<translation>Wählen Sie die Adresse aus, an die Sie Bitcoins überweisen möchten</translation>
<translation>Wählen Sie die Adresse aus, an die Sie Litecoins überweisen möchten</translation>
</message>
<message>
<source>Choose the address to receive coins with</source>
<translation>Wählen Sie die Adresse aus, über die Sie Bitcoins empfangen wollen</translation>
<translation>Wählen Sie die Adresse aus, über die Sie Litecoins empfangen wollen</translation>
</message>
<message>
<source>C&amp;hoose</source>
@ -62,12 +62,12 @@
<translation>Empfangsadressen</translation>
</message>
<message>
<source>These are your Bitcoin addresses for sending payments. Always check the amount and the receiving address before sending coins.</source>
<translation>Dies sind ihre Bitcoin-Adressen zum Tätigen von Überweisungen. Bitte prüfen Sie den Betrag und die Empfangsadresse, bevor Sie Bitcoins überweisen.</translation>
<source>These are your Litecoin addresses for sending payments. Always check the amount and the receiving address before sending coins.</source>
<translation>Dies sind ihre Litecoin-Adressen zum Tätigen von Überweisungen. Bitte prüfen Sie den Betrag und die Empfangsadresse, bevor Sie Litecoins überweisen.</translation>
</message>
<message>
<source>These are your Bitcoin addresses for receiving payments. It is recommended to use a new receiving address for each transaction.</source>
<translation>Dies sind Ihre Bitcoin-Adressen zum Empfangen von Zahlungen. Es wird empfohlen, für jede Transaktion eine neue Empfangsadresse zu verwenden.</translation>
<source>These are your Litecoin addresses for receiving payments. It is recommended to use a new receiving address for each transaction.</source>
<translation>Dies sind Ihre Litecoin-Adressen zum Empfangen von Zahlungen. Es wird empfohlen, für jede Transaktion eine neue Empfangsadresse zu verwenden.</translation>
</message>
<message>
<source>&amp;Copy Address</source>
@ -168,8 +168,8 @@
<translation>Brieftaschen-Verschlüsselung bestätigen</translation>
</message>
<message>
<source>Warning: If you encrypt your wallet and lose your passphrase, you will &lt;b&gt;LOSE ALL OF YOUR BITCOINS&lt;/b&gt;!</source>
<translation>Warnung: Wenn Sie Ihre Brieftasche verschlüsseln und Ihre Passphrase verlieren, werden Sie &lt;b&gt;alle Ihre Bitcoins verlieren&lt;/b&gt;!</translation>
<source>Warning: If you encrypt your wallet and lose your passphrase, you will &lt;b&gt;LOSE ALL OF YOUR LITECOINS&lt;/b&gt;!</source>
<translation>Warnung: Wenn Sie Ihre Brieftasche verschlüsseln und Ihre Passphrase verlieren, werden Sie &lt;b&gt;alle Ihre Litecoins verlieren&lt;/b&gt;!</translation>
</message>
<message>
<source>Are you sure you wish to encrypt your wallet?</source>
@ -180,8 +180,8 @@
<translation>Brieftasche verschlüsselt</translation>
</message>
<message>
<source>%1 will close now to finish the encryption process. Remember that encrypting your wallet cannot fully protect your bitcoins from being stolen by malware infecting your computer.</source>
<translation>%1 wird jetzt beendet, um den Verschlüsselungsprozess abzuschließen. Bitte beachten Sie, dass die Brieftaschen-Verschlüsselung nicht vollständig vor Diebstahl Ihrer Bitcoins durch Schadprogramme schützt, die Ihren Computer befällt.</translation>
<source>%1 will close now to finish the encryption process. Remember that encrypting your wallet cannot fully protect your litecoins from being stolen by malware infecting your computer.</source>
<translation>%1 wird jetzt beendet, um den Verschlüsselungsprozess abzuschließen. Bitte beachten Sie, dass die Brieftaschen-Verschlüsselung nicht vollständig vor Diebstahl Ihrer Litecoins durch Schadprogramme schützt, die Ihren Computer befällt.</translation>
</message>
<message>
<source>IMPORTANT: Any previous backups you have made of your wallet file should be replaced with the newly generated, encrypted wallet file. For security reasons, previous backups of the unencrypted wallet file will become useless as soon as you start using the new, encrypted wallet.</source>
@ -338,8 +338,8 @@
<translation>Reindiziere Blöcke auf Datenträger...</translation>
</message>
<message>
<source>Send coins to a Bitcoin address</source>
<translation>Bitcoins an eine Bitcoin-Adresse überweisen</translation>
<source>Send coins to a Litecoin address</source>
<translation>Litecoins an eine Litecoin-Adresse überweisen</translation>
</message>
<message>
<source>Backup wallet to another location</source>
@ -362,8 +362,8 @@
<translation>Nachricht &amp;verifizieren...</translation>
</message>
<message>
<source>Bitcoin</source>
<translation>Bitcoin</translation>
<source>Litecoin</source>
<translation>Litecoin</translation>
</message>
<message>
<source>Wallet</source>
@ -390,12 +390,12 @@
<translation>Verschlüsselt die zu Ihrer Wallet gehörenden privaten Schlüssel</translation>
</message>
<message>
<source>Sign messages with your Bitcoin addresses to prove you own them</source>
<translation>Nachrichten signieren, um den Besitz Ihrer Bitcoin-Adressen zu beweisen</translation>
<source>Sign messages with your Litecoin addresses to prove you own them</source>
<translation>Nachrichten signieren, um den Besitz Ihrer Litecoin-Adressen zu beweisen</translation>
</message>
<message>
<source>Verify messages to ensure they were signed with specified Bitcoin addresses</source>
<translation>Nachrichten verifizieren, um sicherzustellen, dass diese mit den angegebenen Bitcoin-Adressen signiert wurden</translation>
<source>Verify messages to ensure they were signed with specified Litecoin addresses</source>
<translation>Nachrichten verifizieren, um sicherzustellen, dass diese mit den angegebenen Litecoin-Adressen signiert wurden</translation>
</message>
<message>
<source>&amp;File</source>
@ -414,8 +414,8 @@
<translation>Registerkartenleiste</translation>
</message>
<message>
<source>Request payments (generates QR codes and bitcoin: URIs)</source>
<translation>Zahlungen anfordern (erzeugt QR-Codes und "bitcoin:"-URIs)</translation>
<source>Request payments (generates QR codes and litecoin: URIs)</source>
<translation>Zahlungen anfordern (erzeugt QR-Codes und "litecoin:"-URIs)</translation>
</message>
<message>
<source>Show the list of used sending addresses and labels</source>
@ -426,16 +426,16 @@
<translation>Liste verwendeter Empfangsadressen und Bezeichnungen anzeigen</translation>
</message>
<message>
<source>Open a bitcoin: URI or payment request</source>
<translation>Eine "bitcoin:"-URI oder Zahlungsanforderung öffnen</translation>
<source>Open a litecoin: URI or payment request</source>
<translation>Eine "litecoin:"-URI oder Zahlungsanforderung öffnen</translation>
</message>
<message>
<source>&amp;Command-line options</source>
<translation>&amp;Kommandozeilenoptionen</translation>
</message>
<message numerus="yes">
<source>%n active connection(s) to Bitcoin network</source>
<translation><numerusform>%n aktive Verbindung zum Bitcoin-Netzwerk</numerusform><numerusform>%n aktive Verbindungen zum Bitcoin-Netzwerk</numerusform></translation>
<source>%n active connection(s) to Litecoin network</source>
<translation><numerusform>%n aktive Verbindung zum Litecoin-Netzwerk</numerusform><numerusform>%n aktive Verbindungen zum Litecoin-Netzwerk</numerusform></translation>
</message>
<message>
<source>Indexing blocks on disk...</source>
@ -478,7 +478,7 @@
<translation>Auf aktuellem Stand</translation>
</message>
<message>
<source>Show the %1 help message to get a list with possible Bitcoin command-line options</source>
<source>Show the %1 help message to get a list with possible Litecoin command-line options</source>
<translation>Zeige den "%1"-Hilfetext, um eine Liste mit möglichen Kommandozeilenoptionen zu erhalten</translation>
</message>
<message>
@ -548,8 +548,8 @@
<translation>Wallet ist &lt;b&gt;verschlüsselt&lt;/b&gt; und aktuell &lt;b&gt;gesperrt&lt;/b&gt;</translation>
</message>
<message>
<source>A fatal error occurred. Bitcoin can no longer continue safely and will quit.</source>
<translation>Ein schwerer Fehler ist aufgetreten. Bitcoin kann nicht stabil weiter ausgeführt werden und wird beendet.</translation>
<source>A fatal error occurred. Litecoin can no longer continue safely and will quit.</source>
<translation>Ein schwerer Fehler ist aufgetreten. Litecoin kann nicht stabil weiter ausgeführt werden und wird beendet.</translation>
</message>
</context>
<context>
@ -742,8 +742,8 @@
<translation>Zahlungsadresse bearbeiten</translation>
</message>
<message>
<source>The entered address "%1" is not a valid Bitcoin address.</source>
<translation>Die eingegebene Adresse "%1" ist keine gültige Bitcoin-Adresse.</translation>
<source>The entered address "%1" is not a valid Litecoin address.</source>
<translation>Die eingegebene Adresse "%1" ist keine gültige Litecoin-Adresse.</translation>
</message>
<message>
<source>The entered address "%1" is already in the address book.</source>
@ -851,7 +851,7 @@
<translation>Da Sie das Programm gerade zum ersten Mal starten, können Sie nun auswählen wo %1 seine Daten ablegen wird.</translation>
</message>
<message>
<source>%1 will download and store a copy of the Bitcoin block chain. At least %2GB of data will be stored in this directory, and it will grow over time. The wallet will also be stored in this directory.</source>
<source>%1 will download and store a copy of the Litecoin block chain. At least %2GB of data will be stored in this directory, and it will grow over time. The wallet will also be stored in this directory.</source>
<translation>%1 wird eine Kopie der Blockkette herunterladen und speichern. Mindestens %2GB Daten werden in diesem Verzeichnis abgelegt und die Datenmenge wächst über die Zeit an. Auch die Wallet wird in diesem Verzeichnis abgelegt.</translation>
</message>
<message>
@ -886,12 +886,12 @@
<translation>Formular</translation>
</message>
<message>
<source>Recent transactions may not yet be visible, and therefore your wallet's balance might be incorrect. This information will be correct once your wallet has finished synchronizing with the bitcoin network, as detailed below.</source>
<translation>Neueste Transaktionen werden eventuell noch nicht angezeigt, daher könnte Ihr Kontostand veraltet sein. Er wird korrigiert, sobald Ihr Wallet die Synchronisation mit dem Bitcoin-Netzwerk erfolgreich abgeschlossen. Details dazu finden sich weiter unten.</translation>
<source>Recent transactions may not yet be visible, and therefore your wallet's balance might be incorrect. This information will be correct once your wallet has finished synchronizing with the litecoin network, as detailed below.</source>
<translation>Neueste Transaktionen werden eventuell noch nicht angezeigt, daher könnte Ihr Kontostand veraltet sein. Er wird korrigiert, sobald Ihr Wallet die Synchronisation mit dem Litecoin-Netzwerk erfolgreich abgeschlossen. Details dazu finden sich weiter unten.</translation>
</message>
<message>
<source>Attempting to spend bitcoins that are affected by not-yet-displayed transactions will not be accepted by the network.</source>
<translation>Versuche, Bitcoins aus noch nicht angezeigten Transaktionen auszugeben, werden vom Netzwerk nicht akzeptiert.</translation>
<source>Attempting to spend litecoins that are affected by not-yet-displayed transactions will not be accepted by the network.</source>
<translation>Versuche, Litecoins aus noch nicht angezeigten Transaktionen auszugeben, werden vom Netzwerk nicht akzeptiert.</translation>
</message>
<message>
<source>Number of blocks left</source>
@ -1048,16 +1048,16 @@
<translation>&amp;Unbestätigtes Wechselgeld darf ausgegeben werden</translation>
</message>
<message>
<source>Automatically open the Bitcoin client port on the router. This only works when your router supports UPnP and it is enabled.</source>
<translation>Automatisch den Bitcoin-Clientport auf dem Router öffnen. Dies funktioniert nur, wenn Ihr Router UPnP unterstützt und dies aktiviert ist.</translation>
<source>Automatically open the Litecoin client port on the router. This only works when your router supports UPnP and it is enabled.</source>
<translation>Automatisch den Litecoin-Clientport auf dem Router öffnen. Dies funktioniert nur, wenn Ihr Router UPnP unterstützt und dies aktiviert ist.</translation>
</message>
<message>
<source>Map port using &amp;UPnP</source>
<translation>Portweiterleitung via &amp;UPnP</translation>
</message>
<message>
<source>Connect to the Bitcoin network through a SOCKS5 proxy.</source>
<translation>Über einen SOCKS5-Proxy mit dem Bitcoin-Netzwerk verbinden.</translation>
<source>Connect to the Litecoin network through a SOCKS5 proxy.</source>
<translation>Über einen SOCKS5-Proxy mit dem Litecoin-Netzwerk verbinden.</translation>
</message>
<message>
<source>&amp;Connect through SOCKS5 proxy (default proxy):</source>
@ -1096,8 +1096,8 @@
<translation>Tor</translation>
</message>
<message>
<source>Connect to the Bitcoin network through a separate SOCKS5 proxy for Tor hidden services.</source>
<translation>Über einen separaten SOCKS5 Proxy für Tor Services mit dem Bitcoint Netzwerk verbinden.</translation>
<source>Connect to the Litecoin network through a separate SOCKS5 proxy for Tor hidden services.</source>
<translation>Über einen separaten SOCKS5 Proxy für Tor Services mit dem Litecoint Netzwerk verbinden.</translation>
</message>
<message>
<source>Use separate SOCKS5 proxy to reach peers via Tor hidden services:</source>
@ -1145,7 +1145,7 @@
</message>
<message>
<source>Choose the default subdivision unit to show in the interface and when sending coins.</source>
<translation>Wählen Sie die standardmäßige Untereinheit, die in der Benutzeroberfläche und beim Überweisen von Bitcoins angezeigt werden soll.</translation>
<translation>Wählen Sie die standardmäßige Untereinheit, die in der Benutzeroberfläche und beim Überweisen von Litecoins angezeigt werden soll.</translation>
</message>
<message>
<source>Whether to show coin control features or not.</source>
@ -1195,8 +1195,8 @@
<translation>Formular</translation>
</message>
<message>
<source>The displayed information may be out of date. Your wallet automatically synchronizes with the Bitcoin network after a connection is established, but this process has not completed yet.</source>
<translation>Die angezeigten Informationen sind möglicherweise nicht mehr aktuell. Ihre Wallet wird automatisch synchronisiert, nachdem eine Verbindung zum Bitcoin-Netzwerk hergestellt wurde. Dieser Prozess ist jedoch derzeit noch nicht abgeschlossen.</translation>
<source>The displayed information may be out of date. Your wallet automatically synchronizes with the Litecoin network after a connection is established, but this process has not completed yet.</source>
<translation>Die angezeigten Informationen sind möglicherweise nicht mehr aktuell. Ihre Wallet wird automatisch synchronisiert, nachdem eine Verbindung zum Litecoin-Netzwerk hergestellt wurde. Dieser Prozess ist jedoch derzeit noch nicht abgeschlossen.</translation>
</message>
<message>
<source>Watch-only:</source>
@ -1270,8 +1270,8 @@
<translation>fehlerhafte Zahlungsanforderung</translation>
</message>
<message>
<source>Cannot start bitcoin: click-to-pay handler</source>
<translation>Kann Bitcoin nicht starten: Klicken-zum-Bezahlen-Handler</translation>
<source>Cannot start litecoin: click-to-pay handler</source>
<translation>Kann Litecoin nicht starten: Klicken-zum-Bezahlen-Handler</translation>
</message>
<message>
<source>URI handling</source>
@ -1286,8 +1286,8 @@
<translation>Ungültige Zahlungsadresse %1</translation>
</message>
<message>
<source>URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters.</source>
<translation>URI kann nicht analysiert werden! Dies kann durch eine ungültige Bitcoin-Adresse oder fehlerhafte URI-Parameter verursacht werden.</translation>
<source>URI cannot be parsed! This can be caused by an invalid Litecoin address or malformed URI parameters.</source>
<translation>URI kann nicht analysiert werden! Dies kann durch eine ungültige Litecoin-Adresse oder fehlerhafte URI-Parameter verursacht werden.</translation>
</message>
<message>
<source>Payment request file handling</source>
@ -1380,8 +1380,8 @@
<translation>Betrag</translation>
</message>
<message>
<source>Enter a Bitcoin address (e.g. %1)</source>
<translation>Bitcoin-Adresse eingeben (z.B. %1)</translation>
<source>Enter a Litecoin address (e.g. %1)</source>
<translation>Litecoin-Adresse eingeben (z.B. %1)</translation>
</message>
<message>
<source>%1 d</source>
@ -1800,8 +1800,8 @@
<translation>Vorhandene Empfangsadresse &amp;wiederverwenden (nicht empfohlen)</translation>
</message>
<message>
<source>An optional message to attach to the payment request, which will be displayed when the request is opened. Note: The message will not be sent with the payment over the Bitcoin network.</source>
<translation>Eine optionale Nachricht, die an die Zahlungsanforderung angehängt wird. Sie wird angezeigt, wenn die Anforderung geöffnet wird. Hinweis: Diese Nachricht wird nicht mit der Zahlung über das Bitcoin-Netzwerk gesendet.</translation>
<source>An optional message to attach to the payment request, which will be displayed when the request is opened. Note: The message will not be sent with the payment over the Litecoin network.</source>
<translation>Eine optionale Nachricht, die an die Zahlungsanforderung angehängt wird. Sie wird angezeigt, wenn die Anforderung geöffnet wird. Hinweis: Diese Nachricht wird nicht mit der Zahlung über das Litecoin-Netzwerk gesendet.</translation>
</message>
<message>
<source>An optional label to associate with the new receiving address.</source>
@ -1954,7 +1954,7 @@
<name>SendCoinsDialog</name>
<message>
<source>Send Coins</source>
<translation>Bitcoins überweisen</translation>
<translation>Litecoins überweisen</translation>
</message>
<message>
<source>Coin Control Features</source>
@ -2033,8 +2033,8 @@
<translation>Mindestbetrag</translation>
</message>
<message>
<source>Paying only the minimum fee is just fine as long as there is less transaction volume than space in the blocks. But be aware that this can end up in a never confirming transaction once there is more demand for bitcoin transactions than the network can process.</source>
<translation>Nur die minimale Gebühr zu bezahlen ist so lange in Ordnung, wie weniger Transaktionsvolumen als Platz in den Blöcken vorhanden ist. Aber Vorsicht, diese Option kann dazu führen, dass Transaktionen nicht bestätigt werden, wenn mehr Bedarf an Bitcoin-Transaktionen besteht als das Netzwerk verarbeiten kann.</translation>
<source>Paying only the minimum fee is just fine as long as there is less transaction volume than space in the blocks. But be aware that this can end up in a never confirming transaction once there is more demand for litecoin transactions than the network can process.</source>
<translation>Nur die minimale Gebühr zu bezahlen ist so lange in Ordnung, wie weniger Transaktionsvolumen als Platz in den Blöcken vorhanden ist. Aber Vorsicht, diese Option kann dazu führen, dass Transaktionen nicht bestätigt werden, wenn mehr Bedarf an Litecoin-Transaktionen besteht als das Netzwerk verarbeiten kann.</translation>
</message>
<message>
<source>(read the tooltip)</source>
@ -2197,8 +2197,8 @@
<translation><numerusform>Voraussichtlicher Beginn der Bestätigung innerhalb von %n Block.</numerusform><numerusform>Voraussichtlicher Beginn der Bestätigung innerhalb von %n Blöcken.</numerusform></translation>
</message>
<message>
<source>Warning: Invalid Bitcoin address</source>
<translation>Warnung: Ungültige Bitcoin-Adresse</translation>
<source>Warning: Invalid Litecoin address</source>
<translation>Warnung: Ungültige Litecoin-Adresse</translation>
</message>
<message>
<source>Warning: Unknown change address</source>
@ -2240,7 +2240,7 @@
<translation>Dies ist eine normale Überweisung.</translation>
</message>
<message>
<source>The Bitcoin address to send the payment to</source>
<source>The Litecoin address to send the payment to</source>
<translation>Die Zahlungsadresse der Überweisung</translation>
</message>
<message>
@ -2260,8 +2260,8 @@
<translation>Diesen Eintrag entfernen</translation>
</message>
<message>
<source>The fee will be deducted from the amount being sent. The recipient will receive less bitcoins than you enter in the amount field. If multiple recipients are selected, the fee is split equally.</source>
<translation>Die Gebühr wird vom zu überweisenden Betrag abgezogen. Der Empfänger wird also weniger Bitcoins erhalten, als Sie im Betrags-Feld eingegeben haben. Falls mehrere Empfänger ausgewählt wurden, wird die Gebühr gleichmäßig verteilt.</translation>
<source>The fee will be deducted from the amount being sent. The recipient will receive less litecoins than you enter in the amount field. If multiple recipients are selected, the fee is split equally.</source>
<translation>Die Gebühr wird vom zu überweisenden Betrag abgezogen. Der Empfänger wird also weniger Litecoins erhalten, als Sie im Betrags-Feld eingegeben haben. Falls mehrere Empfänger ausgewählt wurden, wird die Gebühr gleichmäßig verteilt.</translation>
</message>
<message>
<source>S&amp;ubtract fee from amount</source>
@ -2284,8 +2284,8 @@
<translation>Adressbezeichnung eingeben, die dann zusammen mit der Adresse der Liste bereits verwendeter Adressen hinzugefügt wird.</translation>
</message>
<message>
<source>A message that was attached to the bitcoin: URI which will be stored with the transaction for your reference. Note: This message will not be sent over the Bitcoin network.</source>
<translation>Eine an die "bitcoin:"-URI angefügte Nachricht, die zusammen mit der Transaktion gespeichert wird. Hinweis: Diese Nachricht wird nicht über das Bitcoin-Netzwerk gesendet.</translation>
<source>A message that was attached to the litecoin: URI which will be stored with the transaction for your reference. Note: This message will not be sent over the Litecoin network.</source>
<translation>Eine an die "litecoin:"-URI angefügte Nachricht, die zusammen mit der Transaktion gespeichert wird. Hinweis: Diese Nachricht wird nicht über das Litecoin-Netzwerk gesendet.</translation>
</message>
<message>
<source>Pay To:</source>
@ -2329,12 +2329,12 @@
<translation>Nachricht &amp;signieren</translation>
</message>
<message>
<source>You can sign messages/agreements with your addresses to prove you can receive bitcoins sent to them. Be careful not to sign anything vague or random, as phishing attacks may try to trick you into signing your identity over to them. Only sign fully-detailed statements you agree to.</source>
<translation>Sie können Nachrichten/Vereinbarungen mit Hilfe Ihrer Adressen signieren, um zu beweisen, dass Sie Bitcoins empfangen können, die an diese Adressen überwiesen werden. Seien Sie vorsichtig und signieren Sie nichts Vages oder Willkürliches, um Ihre Indentität vor Phishingangriffen zu schützen. Signieren Sie nur vollständig-detaillierte Aussagen, mit denen Sie auch einverstanden sind.</translation>
<source>You can sign messages/agreements with your addresses to prove you can receive litecoins sent to them. Be careful not to sign anything vague or random, as phishing attacks may try to trick you into signing your identity over to them. Only sign fully-detailed statements you agree to.</source>
<translation>Sie können Nachrichten/Vereinbarungen mit Hilfe Ihrer Adressen signieren, um zu beweisen, dass Sie Litecoins empfangen können, die an diese Adressen überwiesen werden. Seien Sie vorsichtig und signieren Sie nichts Vages oder Willkürliches, um Ihre Indentität vor Phishingangriffen zu schützen. Signieren Sie nur vollständig-detaillierte Aussagen, mit denen Sie auch einverstanden sind.</translation>
</message>
<message>
<source>The Bitcoin address to sign the message with</source>
<translation>Die Bitcoin-Adresse mit der die Nachricht signiert wird</translation>
<source>The Litecoin address to sign the message with</source>
<translation>Die Litecoin-Adresse mit der die Nachricht signiert wird</translation>
</message>
<message>
<source>Choose previously used address</source>
@ -2365,8 +2365,8 @@
<translation>Aktuelle Signatur in die Zwischenablage kopieren</translation>
</message>
<message>
<source>Sign the message to prove you own this Bitcoin address</source>
<translation>Die Nachricht signieren, um den Besitz dieser Bitcoin-Adresse zu beweisen</translation>
<source>Sign the message to prove you own this Litecoin address</source>
<translation>Die Nachricht signieren, um den Besitz dieser Litecoin-Adresse zu beweisen</translation>
</message>
<message>
<source>Sign &amp;Message</source>
@ -2389,12 +2389,12 @@
<translation>Geben Sie die Zahlungsadresse des Empfängers, Nachricht (achten Sie darauf Zeilenumbrüche, Leerzeichen, Tabulatoren usw. exakt zu kopieren) und Signatur unten ein, um die Nachricht zu verifizieren. Vorsicht, interpretieren Sie nicht mehr in die Signatur hinein, als in der signierten Nachricht selber enthalten ist, um nicht von einem Man-in-the-middle-Angriff hinters Licht geführt zu werden. Beachten Sie dass dies nur beweißt, dass die signierende Partei über diese Adresse Überweisungen empfangen kann.</translation>
</message>
<message>
<source>The Bitcoin address the message was signed with</source>
<translation>Die Bitcoin-Adresse mit der die Nachricht signiert wurde</translation>
<source>The Litecoin address the message was signed with</source>
<translation>Die Litecoin-Adresse mit der die Nachricht signiert wurde</translation>
</message>
<message>
<source>Verify the message to ensure it was signed with the specified Bitcoin address</source>
<translation>Die Nachricht verifizieren, um sicherzustellen, dass diese mit der angegebenen Bitcoin-Adresse signiert wurde</translation>
<source>Verify the message to ensure it was signed with the specified Litecoin address</source>
<translation>Die Nachricht verifizieren, um sicherzustellen, dass diese mit der angegebenen Litecoin-Adresse signiert wurde</translation>
</message>
<message>
<source>Verify &amp;Message</source>
@ -2619,7 +2619,7 @@
</message>
<message>
<source>Generated coins must mature %1 blocks before they can be spent. When you generated this block, it was broadcast to the network to be added to the block chain. If it fails to get into the chain, its state will change to "not accepted" and it won't be spendable. This may occasionally happen if another node generates a block within a few seconds of yours.</source>
<translation>Erzeugte Bitcoins müssen %1 Blöcke lang reifen, bevor sie ausgegeben werden können. Als Sie diesen Block erzeugten, wurde er an das Netzwerk übertragen, um ihn der Blockkette hinzuzufügen. Falls dies fehlschlägt wird der Status in "nicht angenommen" geändert und Sie werden keine Bitcoins gutgeschrieben bekommen. Das kann gelegentlich passieren, wenn ein anderer Knoten einen Block fast zeitgleich erzeugt.</translation>
<translation>Erzeugte Litecoins müssen %1 Blöcke lang reifen, bevor sie ausgegeben werden können. Als Sie diesen Block erzeugten, wurde er an das Netzwerk übertragen, um ihn der Blockkette hinzuzufügen. Falls dies fehlschlägt wird der Status in "nicht angenommen" geändert und Sie werden keine Litecoins gutgeschrieben bekommen. Das kann gelegentlich passieren, wenn ein anderer Knoten einen Block fast zeitgleich erzeugt.</translation>
</message>
<message>
<source>Debug information</source>
@ -2945,7 +2945,7 @@
<name>WalletModel</name>
<message>
<source>Send Coins</source>
<translation>Bitcoins überweisen</translation>
<translation>Litecoins überweisen</translation>
</message>
</context>
<context>
@ -3054,8 +3054,8 @@
<translation>Kann HTTP Server nicht starten. Siehe debug log für Details.</translation>
</message>
<message>
<source>Bitcoin Core</source>
<translation>Bitcoin Core</translation>
<source>Litecoin Core</source>
<translation>Litecoin Core</translation>
</message>
<message>
<source>The %s developers</source>

2
src/qt/test/test_main.cpp
Unescape View File

@ -54,7 +54,7 @@ int main(int argc, char *argv[])
SelectParams(CBaseChainParams::MAIN);
noui_connect();
ClearDatadirCache();
fs::path pathTemp = fs::temp_directory_path() / strprintf("test_bitcoin-qt_%lu_%i", (unsigned long)GetTime(), (int)GetRand(100000));
fs::path pathTemp = fs::temp_directory_path() / strprintf("test_litecoin-qt_%lu_%i", (unsigned long)GetTime(), (int)GetRand(100000));
fs::create_directories(pathTemp);
gArgs.ForceSetArg("-datadir", pathTemp.string());

2
src/wallet/rpcdump.cpp
Unescape View File

@ -1156,7 +1156,7 @@ UniValue importmulti(const JSONRPCRequest& mainRequest)
"block from time %d, which is after or within %d seconds of key creation, and "
"could contain transactions pertaining to the key. As a result, transactions "
"and coins using this key may not appear in the wallet. This error could be "
"caused by pruning or data corruption (see bitcoind log for details) and could "
"caused by pruning or data corruption (see litecoind log for details) and could "
"be dealt with by downloading and rescanning the relevant blocks (see -reindex "
"and -rescan options).",
GetImportTimestamp(request, now), scannedTime - TIMESTAMP_WINDOW - 1, TIMESTAMP_WINDOW)));

2
src/wallet/test/wallet_tests.cpp
Unescape View File

@ -435,7 +435,7 @@ BOOST_FIXTURE_TEST_CASE(rescan, TestChain100Setup)
"timestamp %d. There was an error reading a block from time %d, which is after or within %d "
"seconds of key creation, and could contain transactions pertaining to the key. As a result, "
"transactions and coins using this key may not appear in the wallet. This error could be caused "
"by pruning or data corruption (see bitcoind log for details) and could be dealt with by "
"by pruning or data corruption (see litecoind log for details) and could be dealt with by "
"downloading and rescanning the relevant blocks (see -reindex and -rescan "
"options).\"}},{\"success\":true}]",
0, oldTip->GetBlockTimeMax(), TIMESTAMP_WINDOW));

44
test/README.md
Unescape View File

@ -1,4 +1,4 @@
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.
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.
##### 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
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
sure bitcoind processes are stopped as above):
sure litecoind processes are stopped as above):
```bash
rm -rf cache
killall bitcoind
killall litecoind
```
##### Test logging
@ -120,13 +120,13 @@ default:
- when run directly, *all* logs are written to `test_framework.log` and INFO
level and above are output to the console.
- when run on Travis, no logs are output to the console. However, if a test
fails, the `test_framework.log` and bitcoind `debug.log`s will all be dumped
fails, the `test_framework.log` and litecoind `debug.log`s will all be dumped
to the console to help troubleshooting.
To change the level of logs output to the console, use the `-l` command line
argument.
`test_framework.log` and bitcoind `debug.log`s can be combined into a single
`test_framework.log` and litecoind `debug.log`s can be combined into a single
aggregate log by running the `combine_logs.py` script. The output can be plain
text, colorized text or html. For example:
@ -153,9 +153,9 @@ import pdb; pdb.set_trace()
```
anywhere in the test. You will then be able to inspect variables, as well as
call methods that interact with the bitcoind nodes-under-test.
call methods that interact with the litecoind nodes-under-test.
If further introspection of the bitcoind instances themselves becomes
If further introspection of the litecoind instances themselves becomes
necessary, this can be accomplished by first setting a pdb breakpoint
at an appropriate location, running the test to that point, then using
`gdb` to attach to the process and debug.
@ -169,8 +169,8 @@ For instance, to attach to `self.node[1]` during a run:
use the directory path to get the pid from the pid file:
```bash
cat /tmp/user/1000/testo9vsdjo3/node1/regtest/bitcoind.pid
gdb /home/example/bitcoind <pid>
cat /tmp/user/1000/testo9vsdjo3/node1/regtest/litecoind.pid
gdb /home/example/litecoind <pid>
```
Note: gdb attach step may require `sudo`

20
test/functional/README.md
Unescape View File

@ -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`.
#### 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:
* `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:
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.
Generally useful functions.
#### [test_framework/mininode.py](test_framework/mininode.py)
Basic code to support P2P connectivity to a bitcoind.
Basic code to support P2P connectivity to a litecoind.
#### [test_framework/comptool.py](test_framework/comptool.py)
Framework for comparison-tool style, P2P tests.

2
test/functional/bitcoin_cli.py
Unescape View File

@ -15,7 +15,7 @@ class TestBitcoinCli(BitcoinTestFramework):
def run_test(self):
"""Main test logic"""
self.log.info("Compare responses from getinfo RPC and `bitcoin-cli getinfo`")
self.log.info("Compare responses from getinfo RPC and `litecoin-cli getinfo`")
cli_get_info = self.nodes[0].cli.getinfo()
rpc_get_info = self.nodes[0].getinfo()

4
test/functional/p2p-acceptblock.py
Unescape View File

@ -60,8 +60,8 @@ from test_framework.blocktools import create_block, create_coinbase, create_tran
class AcceptBlockTest(BitcoinTestFramework):
def add_options(self, parser):
parser.add_option("--testbinary", dest="testbinary",
default=os.getenv("BITCOIND", "bitcoind"),
help="bitcoind binary to test")
default=os.getenv("LITECOIND", "litecoind"),
help="litecoind binary to test")
def set_test_params(self):
self.setup_clean_chain = True

Write Preview
Loading…
Cancel
Save