From 14c5e6c59a5605f4da19a504d9da14ddc504ec29 Mon Sep 17 00:00:00 2001 From: barrystyle Date: Thu, 6 Jun 2019 01:36:37 +0800 Subject: [PATCH] final rebranding to NYC3 --- CONTRIBUTING.md | 12 +++--- INSTALL.md | 2 +- README.md | 2 +- build_msvc/README.md | 4 +- build_msvc/bitcoin_config.h | 6 +-- configure.ac | 2 +- contrib/README.md | 4 +- contrib/debian/copyright | 4 +- contrib/devtools/README.md | 2 +- contrib/devtools/copyright_header.py | 2 +- contrib/devtools/github-merge.py | 2 +- contrib/gitian-keys/README.md | 2 +- contrib/init/bitcoind.conf | 2 +- contrib/init/bitcoind.openrc | 2 +- contrib/verifybinaries/README.md | 4 +- contrib/verifybinaries/verify.sh | 2 +- doc/Doxyfile.in | 2 +- doc/JSON-RPC-interface.md | 30 +++++++------- doc/README.md | 12 +++--- doc/README_windows.txt | 4 +- doc/benchmarking.md | 2 +- doc/bips.md | 4 +- doc/build-freebsd.md | 2 +- doc/build-netbsd.md | 2 +- doc/build-openbsd.md | 2 +- doc/build-osx.md | 12 +++--- doc/build-unix.md | 16 ++++---- doc/build-windows.md | 14 +++---- doc/dependencies.md | 2 +- doc/descriptors.md | 8 ++-- doc/developer-notes.md | 22 +++++------ doc/dnsseed-policy.md | 2 +- doc/fuzzing.md | 4 +- doc/gitian-building.md | 2 +- doc/man/bitcoin-cli.1 | 8 ++-- doc/man/bitcoin-qt.1 | 4 +- doc/man/bitcoin-tx.1 | 4 +- doc/man/bitcoin-wallet.1 | 6 +-- doc/man/bitcoind.1 | 6 +-- doc/psbt.md | 10 ++--- doc/reduce-traffic.md | 2 +- doc/release-notes.md | 10 ++--- doc/release-notes/release-notes-0.10.0.md | 20 +++++----- doc/release-notes/release-notes-0.10.1.md | 4 +- doc/release-notes/release-notes-0.10.2.md | 4 +- doc/release-notes/release-notes-0.10.3.md | 6 +-- doc/release-notes/release-notes-0.10.4.md | 10 ++--- doc/release-notes/release-notes-0.11.0.md | 8 ++-- doc/release-notes/release-notes-0.11.1.md | 6 +-- doc/release-notes/release-notes-0.11.2.md | 10 ++--- doc/release-notes/release-notes-0.12.0.md | 42 ++++++++++---------- doc/release-notes/release-notes-0.12.1.md | 8 ++-- doc/release-notes/release-notes-0.13.0.md | 10 ++--- doc/release-notes/release-notes-0.13.1.md | 10 ++--- doc/release-notes/release-notes-0.13.2.md | 4 +- doc/release-notes/release-notes-0.14.0.md | 14 +++---- doc/release-notes/release-notes-0.14.1.md | 6 +-- doc/release-notes/release-notes-0.14.2.md | 8 ++-- doc/release-notes/release-notes-0.14.3.md | 8 ++-- doc/release-notes/release-notes-0.15.0.1.md | 6 +-- doc/release-notes/release-notes-0.15.0.md | 26 ++++++------ doc/release-notes/release-notes-0.15.1.md | 8 ++-- doc/release-notes/release-notes-0.15.2.md | 8 ++-- doc/release-notes/release-notes-0.16.0.md | 12 +++--- doc/release-notes/release-notes-0.16.1.md | 6 +-- doc/release-notes/release-notes-0.16.2.md | 6 +-- doc/release-notes/release-notes-0.16.3.md | 8 ++-- doc/release-notes/release-notes-0.17.0.1.md | 2 +- doc/release-notes/release-notes-0.17.0.md | 8 ++-- doc/release-notes/release-notes-0.17.1.md | 6 +-- doc/release-notes/release-notes-0.9.0.md | 8 ++-- doc/release-notes/release-notes-0.9.1.md | 4 +- doc/release-notes/release-notes-0.9.2.1.md | 2 +- doc/release-notes/release-notes-0.9.2.md | 2 +- doc/release-notes/release-notes-0.9.3.md | 4 +- doc/release-notes/release-notes-0.9.4.md | 8 ++-- doc/release-notes/release-notes-0.9.5.md | 4 +- doc/release-process.md | 4 +- doc/tor.md | 16 ++++---- doc/translation_strings_policy.md | 2 +- doc/travis-ci.md | 2 +- doc/zmq.md | 4 +- src/init.cpp | 8 ++-- src/nyc3-wallet.cpp | 2 +- src/protocol.h | 6 +-- src/qt/addresstablemodel.h | 2 +- src/qt/editaddressdialog.cpp | 2 +- src/qt/forms/sendcoinsentry.ui | 2 +- src/qt/forms/signverifymessagedialog.ui | 8 ++-- src/qt/guiutil.cpp | 2 +- src/qt/locale/nyc3_af.ts | 12 +++--- src/qt/locale/nyc3_af_ZA.ts | 4 +- src/qt/locale/nyc3_ar.ts | 22 +++++------ src/qt/locale/nyc3_be_BY.ts | 6 +-- src/qt/locale/nyc3_bg.ts | 14 +++---- src/qt/locale/nyc3_bg_BG.ts | 2 +- src/qt/locale/nyc3_ca.ts | 24 +++++------ src/qt/locale/nyc3_ca@valencia.ts | 24 +++++------ src/qt/locale/nyc3_ca_ES.ts | 24 +++++------ src/qt/locale/nyc3_cs.ts | 24 +++++------ src/qt/locale/nyc3_cy.ts | 4 +- src/qt/locale/nyc3_da.ts | 24 +++++------ src/qt/locale/nyc3_de.ts | 24 +++++------ src/qt/locale/nyc3_el_GR.ts | 20 +++++----- src/qt/locale/nyc3_en.ts | 30 +++++++------- src/qt/locale/nyc3_en_GB.ts | 44 ++++++++++----------- src/qt/locale/nyc3_eo.ts | 10 ++--- src/qt/locale/nyc3_es.ts | 24 +++++------ src/qt/locale/nyc3_es_CL.ts | 20 +++++----- src/qt/locale/nyc3_es_CO.ts | 8 ++-- src/qt/locale/nyc3_es_DO.ts | 8 ++-- src/qt/locale/nyc3_es_ES.ts | 24 +++++------ src/qt/locale/nyc3_es_MX.ts | 4 +- src/qt/locale/nyc3_es_UY.ts | 2 +- src/qt/locale/nyc3_es_VE.ts | 6 +-- src/qt/locale/nyc3_et.ts | 16 ++++---- src/qt/locale/nyc3_et_EE.ts | 4 +- src/qt/locale/nyc3_fa.ts | 18 ++++----- src/qt/locale/nyc3_fa_IR.ts | 10 ++--- src/qt/locale/nyc3_fi.ts | 22 +++++------ src/qt/locale/nyc3_fr.ts | 24 +++++------ src/qt/locale/nyc3_fr_FR.ts | 12 +++--- src/qt/locale/nyc3_gl.ts | 8 ++-- src/qt/locale/nyc3_he.ts | 22 +++++------ src/qt/locale/nyc3_hr.ts | 24 +++++------ src/qt/locale/nyc3_hu.ts | 24 +++++------ src/qt/locale/nyc3_id.ts | 2 +- src/qt/locale/nyc3_id_ID.ts | 14 +++---- src/qt/locale/nyc3_is.ts | 4 +- src/qt/locale/nyc3_it.ts | 24 +++++------ src/qt/locale/nyc3_it_IT.ts | 4 +- src/qt/locale/nyc3_ja.ts | 22 +++++------ src/qt/locale/nyc3_ka.ts | 10 ++--- src/qt/locale/nyc3_ko.ts | 2 +- src/qt/locale/nyc3_ko_KR.ts | 22 +++++------ src/qt/locale/nyc3_la.ts | 8 ++-- src/qt/locale/nyc3_lt.ts | 8 ++-- src/qt/locale/nyc3_lv_LV.ts | 8 ++-- src/qt/locale/nyc3_mk_MK.ts | 4 +- src/qt/locale/nyc3_ms_MY.ts | 2 +- src/qt/locale/nyc3_nb.ts | 24 +++++------ src/qt/locale/nyc3_ne.ts | 4 +- src/qt/locale/nyc3_nl.ts | 24 +++++------ src/qt/locale/nyc3_pam.ts | 14 +++---- src/qt/locale/nyc3_pl.ts | 24 +++++------ src/qt/locale/nyc3_pt_BR.ts | 24 +++++------ src/qt/locale/nyc3_pt_PT.ts | 24 +++++------ src/qt/locale/nyc3_ro.ts | 6 +-- src/qt/locale/nyc3_ro_RO.ts | 22 +++++------ src/qt/locale/nyc3_ru_RU.ts | 28 ++++++------- src/qt/locale/nyc3_sk.ts | 24 +++++------ src/qt/locale/nyc3_sl_SI.ts | 18 ++++----- src/qt/locale/nyc3_sn.ts | 2 +- src/qt/locale/nyc3_sq.ts | 2 +- src/qt/locale/nyc3_sr.ts | 2 +- src/qt/locale/nyc3_sr@latin.ts | 6 +-- src/qt/locale/nyc3_sv.ts | 24 +++++------ src/qt/locale/nyc3_szl.ts | 14 +++---- src/qt/locale/nyc3_ta.ts | 6 +-- src/qt/locale/nyc3_th_TH.ts | 2 +- src/qt/locale/nyc3_tr.ts | 22 +++++------ src/qt/locale/nyc3_tr_TR.ts | 10 ++--- src/qt/locale/nyc3_uk.ts | 24 +++++------ src/qt/locale/nyc3_uz@Cyrl.ts | 8 ++-- src/qt/locale/nyc3_vi.ts | 42 ++++++++++---------- src/qt/locale/nyc3_vi_VN.ts | 6 +-- src/qt/locale/nyc3_zh.ts | 8 ++-- src/qt/locale/nyc3_zh_CN.ts | 24 +++++------ src/qt/locale/nyc3_zh_HK.ts | 4 +- src/qt/locale/nyc3_zh_TW.ts | 24 +++++------ src/qt/nyc3.h | 2 +- src/qt/nyc3addressvalidator.cpp | 2 +- src/qt/nyc3addressvalidator.h | 2 +- src/qt/nyc3gui.cpp | 2 +- src/qt/nyc3strings.cpp | 2 +- src/qt/paymentserver.cpp | 2 +- src/qt/sendcoinsdialog.cpp | 2 +- src/qt/splashscreen.h | 2 +- src/rpc/rawtransaction.cpp | 4 +- src/test/scriptnum10.h | 2 +- src/tinyformat.h | 2 +- src/univalue/include/univalue.h | 2 +- src/univalue/lib/univalue.cpp | 2 +- src/univalue/lib/univalue_get.cpp | 2 +- src/util/system.cpp | 4 +- src/wallet/rpcdump.cpp | 6 +-- src/wallet/rpcwallet.cpp | 18 ++++----- test/README.md | 2 +- test/functional/README.md | 2 +- test/functional/feature_filelock.py | 2 +- test/functional/interface_bitcoin_cli.py | 2 +- test/functional/test_framework/mininode.py | 2 +- 192 files changed, 935 insertions(+), 937 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 139fe7dc5..7f5b0e471 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1,7 +1,7 @@ -Contributing to Bitcoin Core +Contributing to NYC3 ============================ -The Bitcoin Core project operates an open contributor model where anyone is +The NYC3 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. @@ -21,7 +21,7 @@ list. Communication Channels ---------------------- -Most communication about Bitcoin Core development happens on IRC, in the +Most communication about NYC3 development happens on IRC, in the #bitcoin-core-dev channel on Freenode. The easiest way to participate on IRC is with the web client, [webchat.freenode.net](https://webchat.freenode.net/). Chat history logs can be found @@ -199,11 +199,11 @@ workload on reviewing. "Decision Making" Process ------------------------- -The following applies to code changes to the Bitcoin Core project (and related +The following applies to code changes to the NYC3 project (and related projects such as libsecp256k1), and is not to be confused with overall Bitcoin 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 NYC3 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 @@ -302,7 +302,7 @@ about: Release Policy -------------- -The project leader is the release manager for each Bitcoin Core release. +The project leader is the release manager for each NYC3 release. Copyright --------- diff --git a/INSTALL.md b/INSTALL.md index 520a47d96..bc29c6280 100644 --- a/INSTALL.md +++ b/INSTALL.md @@ -2,4 +2,4 @@ Building Bitcoin ================ See doc/build-*.md for instructions on building the various -elements of the Bitcoin Core reference implementation of Bitcoin. +elements of the NYC3 reference implementation of Bitcoin. diff --git a/README.md b/README.md index 665bc1a1e..0440c0627 100644 --- a/README.md +++ b/README.md @@ -2,7 +2,7 @@ NYC3 (NewYorkCoin3) integration/staging tree ============================================ -Built upon Bitcoin Core 0.18; NYC3 offers a blocktime of 10 seconds, consensus operates using the 'Parallel' password hashing algorithm in a POW configuration (SHA512-based) and uses LWMA3 to regulate block-spacing. +Built upon NYC3 0.18; NYC3 offers a blocktime of 10 seconds, consensus operates using the 'Parallel' password hashing algorithm in a POW configuration (SHA512-based) and uses LWMA3 to regulate block-spacing. License diff --git a/build_msvc/README.md b/build_msvc/README.md index 63c5babf3..3d5e0bd71 100644 --- a/build_msvc/README.md +++ b/build_msvc/README.md @@ -1,9 +1,9 @@ -Building Bitcoin Core with Visual Studio +Building NYC3 with Visual Studio ======================================== Introduction --------------------- -Solution and project files to build the Bitcoin Core applications (except Qt dependent ones) with Visual Studio 2017 can be found in the build_msvc directory. +Solution and project files to build the NYC3 applications (except Qt dependent ones) with Visual Studio 2017 can be found in the build_msvc directory. Building with Visual Studio is an alternative to the Linux based [cross-compiler build](https://github.com/bitcoin/bitcoin/blob/master/doc/build-windows.md). diff --git a/build_msvc/bitcoin_config.h b/build_msvc/bitcoin_config.h index 4ac27dae3..4d22f0f7b 100644 --- a/build_msvc/bitcoin_config.h +++ b/build_msvc/bitcoin_config.h @@ -26,7 +26,7 @@ #define COPYRIGHT_HOLDERS_FINAL "The Bitcoin Core developers" /* Replacement for %s in copyright holders string */ -#define COPYRIGHT_HOLDERS_SUBSTITUTION "Bitcoin Core" +#define COPYRIGHT_HOLDERS_SUBSTITUTION "NYC3" /* Copyright year */ #define COPYRIGHT_YEAR 2018 @@ -343,10 +343,10 @@ #define PACKAGE_BUGREPORT "https://github.com/bitcoin/bitcoin/issues" /* Define to the full name of this package. */ -#define PACKAGE_NAME "Bitcoin Core" +#define PACKAGE_NAME "NYC3" /* Define to the full name and version of this package. */ -#define PACKAGE_STRING "Bitcoin Core 0.17.99" +#define PACKAGE_STRING "NYC3 0.17.99" /* Define to the one symbol short name of this package. */ #define PACKAGE_TARNAME "bitcoin" diff --git a/configure.ac b/configure.ac index 732cff873..4b8688e56 100644 --- a/configure.ac +++ b/configure.ac @@ -9,7 +9,7 @@ define(_CLIENT_VERSION_IS_RELEASE, true) define(_COPYRIGHT_YEAR, 2019) define(_COPYRIGHT_HOLDERS,[The %s developers]) define(_COPYRIGHT_HOLDERS_SUBSTITUTION,[[nyc3]]) -AC_INIT([Bitcoin Core],m4_join([.], _CLIENT_VERSION_MAJOR, _CLIENT_VERSION_MINOR, _CLIENT_VERSION_REVISION, m4_if(_CLIENT_VERSION_BUILD, [0], [], _CLIENT_VERSION_BUILD))m4_if(_CLIENT_VERSION_RC, [0], [], [rc]_CLIENT_VERSION_RC),[https://github.com/bitcoin/bitcoin/issues],[bitcoin],[https://bitcoincore.org/]) +AC_INIT([NYC3],m4_join([.], _CLIENT_VERSION_MAJOR, _CLIENT_VERSION_MINOR, _CLIENT_VERSION_REVISION, m4_if(_CLIENT_VERSION_BUILD, [0], [], _CLIENT_VERSION_BUILD))m4_if(_CLIENT_VERSION_RC, [0], [], [rc]_CLIENT_VERSION_RC),[https://github.com/bitcoin/bitcoin/issues],[bitcoin],[https://bitcoincore.org/]) AC_CONFIG_SRCDIR([src/validation.cpp]) AC_CONFIG_HEADERS([src/config/bitcoin-config.h]) AC_CONFIG_AUX_DIR([build-aux]) diff --git a/contrib/README.md b/contrib/README.md index 891591976..44cdba646 100644 --- a/contrib/README.md +++ b/contrib/README.md @@ -27,10 +27,10 @@ The [Debian](/contrib/debian) subfolder contains the copyright file. All other packaging related files can be found in the [bitcoin-core/packaging](https://github.com/bitcoin-core/packaging) repository. ### [Gitian-descriptors](/contrib/gitian-descriptors) ### -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). +Files used during the gitian build process. For more information about gitian, see the [the NYC3 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 NYC3 [Gitian release](/doc/release-process.md) results. ### [MacDeploy](/contrib/macdeploy) ### Scripts and notes for Mac builds. diff --git a/contrib/debian/copyright b/contrib/debian/copyright index 2d5b0188d..11992809f 100644 --- a/contrib/debian/copyright +++ b/contrib/debian/copyright @@ -5,9 +5,9 @@ Upstream-Contact: Satoshi Nakamoto Source: https://github.com/bitcoin/bitcoin Files: * -Copyright: 2009-2019, Bitcoin Core Developers +Copyright: 2009-2019, NYC3 Developers License: Expat -Comment: The Bitcoin Core Developers encompasses the current developers listed on bitcoin.org, +Comment: The NYC3 Developers encompasses the current developers listed on bitcoin.org, as well as the numerous contributors to the project. Files: debian/* diff --git a/contrib/devtools/README.md b/contrib/devtools/README.md index 6ee65f40b..27e555545 100644 --- a/contrib/devtools/README.md +++ b/contrib/devtools/README.md @@ -17,7 +17,7 @@ git diff -U0 HEAD~1.. | ./contrib/devtools/clang-format-diff.py -p1 -i -v copyright\_header.py ==================== -Provides utilities for managing copyright headers of `The Bitcoin Core +Provides utilities for managing copyright headers of `The NYC3 developers` in repository source files. It has three subcommands: ``` diff --git a/contrib/devtools/copyright_header.py b/contrib/devtools/copyright_header.py index f2987f226..726e03b0c 100755 --- a/contrib/devtools/copyright_header.py +++ b/contrib/devtools/copyright_header.py @@ -90,7 +90,7 @@ def compile_copyright_regex(copyright_style, year_style, name): EXPECTED_HOLDER_NAMES = [ "Satoshi Nakamoto\n", "The Bitcoin Core developers\n", - "Bitcoin Core Developers\n", + "NYC3 Developers\n", "BitPay Inc\.\n", "University of Illinois at Urbana-Champaign\.\n", "Pieter Wuille\n", diff --git a/contrib/devtools/github-merge.py b/contrib/devtools/github-merge.py index ab834b762..e103f59d1 100755 --- a/contrib/devtools/github-merge.py +++ b/contrib/devtools/github-merge.py @@ -1,5 +1,5 @@ #!/usr/bin/env python3 -# Copyright (c) 2016-2017 Bitcoin Core Developers +# Copyright (c) 2016-2017 NYC3 Developers # Distributed under the MIT software license, see the accompanying # file COPYING or http://www.opensource.org/licenses/mit-license.php. diff --git a/contrib/gitian-keys/README.md b/contrib/gitian-keys/README.md index ffe4fb144..f38743549 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 NYC3. diff --git a/contrib/init/bitcoind.conf b/contrib/init/bitcoind.conf index de4ea0ed5..77553a676 100644 --- a/contrib/init/bitcoind.conf +++ b/contrib/init/bitcoind.conf @@ -1,4 +1,4 @@ -description "Bitcoin Core Daemon" +description "NYC3 Daemon" start on runlevel [2345] stop on starting rc RUNLEVEL=[016] diff --git a/contrib/init/bitcoind.openrc b/contrib/init/bitcoind.openrc index 86222295d..55a043c6b 100644 --- a/contrib/init/bitcoind.openrc +++ b/contrib/init/bitcoind.openrc @@ -18,7 +18,7 @@ BITCOIND_BIN=${BITCOIND_BIN:-/usr/bin/bitcoind} BITCOIND_NICE=${BITCOIND_NICE:-${NICELEVEL:-0}} BITCOIND_OPTS="${BITCOIND_OPTS:-${BITCOIN_OPTS}}" -name="Bitcoin Core Daemon" +name="NYC3 Daemon" description="Bitcoin cryptocurrency P2P network daemon" command="/usr/bin/bitcoind" diff --git a/contrib/verifybinaries/README.md b/contrib/verifybinaries/README.md index 3ffe0a2f2..14fd541cf 100644 --- a/contrib/verifybinaries/README.md +++ b/contrib/verifybinaries/README.md @@ -5,10 +5,10 @@ Make sure you obtain the proper release signing key and verify the fingerprint with several independent sources. ```sh -$ gpg --fingerprint "Bitcoin Core binary release signing key" +$ gpg --fingerprint "NYC3 binary release signing key" pub 4096R/36C2E964 2015-06-24 [expires: 2017-02-13] Key fingerprint = 01EA 5486 DE18 A882 D4C2 6845 90C8 019E 36C2 E964 -uid Wladimir J. van der Laan (Bitcoin Core binary release signing key) +uid Wladimir J. van der Laan (NYC3 binary release signing key) ``` #### Usage: diff --git a/contrib/verifybinaries/verify.sh b/contrib/verifybinaries/verify.sh index fc7492ad3..956390a3b 100755 --- a/contrib/verifybinaries/verify.sh +++ b/contrib/verifybinaries/verify.sh @@ -124,7 +124,7 @@ if [ $RET -ne 0 ]; then echo "Bad signature." elif [ $RET -eq 2 ]; then #or if a gpg error has occurred - echo "gpg error. Do you have the Bitcoin Core binary release signing key installed?" + echo "gpg error. Do you have the NYC3 binary release signing key installed?" fi echo "gpg output:" diff --git a/doc/Doxyfile.in b/doc/Doxyfile.in index 58c65fb7e..5d4dd50c8 100644 --- a/doc/Doxyfile.in +++ b/doc/Doxyfile.in @@ -32,7 +32,7 @@ DOXYFILE_ENCODING = UTF-8 # title of most generated pages and in a few other places. # The default value is: My Project. -PROJECT_NAME = "Bitcoin Core" +PROJECT_NAME = "NYC3" # The PROJECT_NUMBER tag can be used to enter a project or revision number. This # could be handy for archiving the generated documentation or if some version diff --git a/doc/JSON-RPC-interface.md b/doc/JSON-RPC-interface.md index a0cfe84a3..35a984b98 100644 --- a/doc/JSON-RPC-interface.md +++ b/doc/JSON-RPC-interface.md @@ -7,7 +7,7 @@ Dialog. ## Versioning -The RPC interface might change from one major version of Bitcoin Core to the +The RPC interface might change from one major version of NYC3 to the next. This makes the RPC interface implicitly versioned on the major version. The version tuple can be retrieved by e.g. the `getnetworkinfo` RPC in `version`. @@ -19,21 +19,21 @@ were deprecated and how to re-enable them temporarily. ## Security -The RPC interface allows other programs to control Bitcoin Core, +The RPC interface allows other programs to control NYC3, including the ability to spend funds from your wallets, affect consensus verification, read private data, and otherwise perform operations that can cause loss of money, data, or privacy. This section suggests how -you should use and configure Bitcoin Core to reduce the risk that its +you should use and configure NYC3 to reduce the risk that its RPC interface will be abused. - **Securing the executable:** Anyone with physical or remote access to - the computer, container, or virtual machine running Bitcoin Core can + the computer, container, or virtual machine running NYC3 can compromise either the whole program or just the RPC interface. This includes being able to record any passphrases you enter for unlocking - your encrypted wallets or changing settings so that your Bitcoin Core + your encrypted wallets or changing settings so that your NYC3 program tells you that certain transactions have multiple confirmations even when they aren't part of the best block chain. For - this reason, you should not use Bitcoin Core for security sensitive + this reason, you should not use NYC3 for security sensitive operations on systems you do not exclusively control, such as shared computers or virtual private servers. @@ -43,19 +43,19 @@ RPC interface will be abused. and passphrase). Any program on your computer with access to the file system and local network can obtain this level of access. Additionally, other programs on your computer can attempt to provide - an RPC interface on the same port as used by Bitcoin Core in order to + an RPC interface on the same port as used by NYC3 in order to trick you into revealing your authentication credentials. For this - reason, it is important to only use Bitcoin Core for + reason, it is important to only use NYC3 for security-sensitive operations on a computer whose other programs you trust. - **Securing remote network access:** You may optionally allow other - computers to remotely control Bitcoin Core by setting the `rpcallowip` + computers to remotely control NYC3 by setting the `rpcallowip` and `rpcbind` configuration parameters. These settings are only meant for enabling connections over secure private networks or connections that have been otherwise secured (e.g. using a VPN or port forwarding with SSH or stunnel). **Do not enable RPC connections over the public - Internet.** Although Bitcoin Core's RPC interface does use + Internet.** Although NYC3's RPC interface does use authentication, it does not use encryption, so your login credentials are sent as clear text that can be read by anyone on your network path. Additionally, the RPC interface has not been hardened to @@ -65,21 +65,21 @@ RPC interface will be abused. `bitcoind -help` for more information about these settings and other settings described in this document. - Related, if you use Bitcoin Core inside a Docker container, you may + Related, if you use NYC3 inside a Docker container, you may need to expose the RPC port to the host system. The default way to do this in Docker also exposes the port to the public Internet. Instead, expose it only on the host system's localhost, for example: `-p 127.0.0.1:8332:8332` -- **Secure authentication:** By default, Bitcoin Core generates unique +- **Secure authentication:** By default, NYC3 generates unique login credentials each time it restarts and puts them into a file - readable only by the user that started Bitcoin Core, allowing any of + readable only by the user that started NYC3, allowing any of that user's RPC clients with read access to the file to login - automatically. The file is `.cookie` in the Bitcoin Core + automatically. The file is `.cookie` in the NYC3 configuration directory, and using these credentials is the preferred RPC authentication method. If you need to generate static login credentials for your programs, you can use the script in the - `share/rpcauth` directory in the Bitcoin Core source tree. As a final + `share/rpcauth` directory in the NYC3 source tree. As a final fallback, you can directly use manually-chosen `rpcuser` and `rpcpassword` configuration parameters---but you must ensure that you choose a strong and unique passphrase (and still don't use insecure diff --git a/doc/README.md b/doc/README.md index 8876ffdd7..8be3c6cbc 100644 --- a/doc/README.md +++ b/doc/README.md @@ -1,15 +1,15 @@ -Bitcoin Core +NYC3 ============= 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. +NYC3 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. -To download Bitcoin Core, visit [bitcoincore.org](https://bitcoincore.org/en/download/). +To download NYC3, visit [bitcoincore.org](https://bitcoincore.org/en/download/). 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 NYC3 on your native platform. ### Unix @@ -24,7 +24,7 @@ Unpack the files into a directory, and then run bitcoin-qt.exe. ### macOS -Drag Bitcoin Core to your applications folder, and then run Bitcoin Core. +Drag NYC3 to your applications folder, and then run NYC3. ### Need Help? @@ -35,7 +35,7 @@ for help and more information. 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 NYC3 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) diff --git a/doc/README_windows.txt b/doc/README_windows.txt index 07d61b3bd..822c8d4b6 100644 --- a/doc/README_windows.txt +++ b/doc/README_windows.txt @@ -1,4 +1,4 @@ -Bitcoin Core +NYC3 ============= Intro @@ -13,7 +13,7 @@ Setup ----- Unpack the files into a directory and run bitcoin-qt.exe. -Bitcoin Core is the original Bitcoin client and it builds the backbone of the network. +NYC3 is the original Bitcoin client and it builds the backbone of the network. However, it downloads and stores the entire history of Bitcoin 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. diff --git a/doc/benchmarking.md b/doc/benchmarking.md index 48f81cf6c..1d2e0ef10 100644 --- a/doc/benchmarking.md +++ b/doc/benchmarking.md @@ -1,7 +1,7 @@ Benchmarking ============ -Bitcoin Core has an internal benchmarking framework, with benchmarks +NYC3 has an internal benchmarking framework, with benchmarks for cryptographic algorithms (e.g. SHA1, SHA256, SHA512, RIPEMD160), as well as the rolling bloom filter. Running diff --git a/doc/bips.md b/doc/bips.md index eb24ce6f6..026817aa7 100644 --- a/doc/bips.md +++ b/doc/bips.md @@ -1,4 +1,4 @@ -BIPs that are implemented by Bitcoin Core (up-to-date up to **v0.18.0**): +BIPs that are implemented by NYC3 (up-to-date up to **v0.18.0**): * [`BIP 9`](https://github.com/bitcoin/bips/blob/master/bip-0009.mediawiki): The changes allowing multiple soft-forks to be deployed in parallel have been implemented since **v0.12.1** ([PR #7575](https://github.com/bitcoin/bitcoin/pull/7575)) * [`BIP 11`](https://github.com/bitcoin/bips/blob/master/bip-0011.mediawiki): Multisig outputs are standard since **v0.6.0** ([PR #669](https://github.com/bitcoin/bitcoin/pull/669)). @@ -19,7 +19,7 @@ BIPs that are implemented by Bitcoin Core (up-to-date up to **v0.18.0**): * [`BIP 65`](https://github.com/bitcoin/bips/blob/master/bip-0065.mediawiki): The CHECKLOCKTIMEVERIFY softfork was merged in **v0.12.0** ([PR #6351](https://github.com/bitcoin/bitcoin/pull/6351)), and backported to **v0.11.2** and **v0.10.4**. Mempool-only CLTV was added in [PR #6124](https://github.com/bitcoin/bitcoin/pull/6124). * [`BIP 66`](https://github.com/bitcoin/bips/blob/master/bip-0066.mediawiki): The strict DER rules and associated version 3 blocks have been implemented since **v0.10.0** ([PR #5713](https://github.com/bitcoin/bitcoin/pull/5713)). * [`BIP 68`](https://github.com/bitcoin/bips/blob/master/bip-0068.mediawiki): Sequence locks have been implemented as of **v0.12.1** ([PR #7184](https://github.com/bitcoin/bitcoin/pull/7184)), and have been activated since *block 419328*. -* [`BIP 70`](https://github.com/bitcoin/bips/blob/master/bip-0070.mediawiki) [`71`](https://github.com/bitcoin/bips/blob/master/bip-0071.mediawiki) [`72`](https://github.com/bitcoin/bips/blob/master/bip-0072.mediawiki): Payment Protocol support has been available in Bitcoin Core GUI since **v0.9.0** ([PR #5216](https://github.com/bitcoin/bitcoin/pull/5216)). Support can be optionally disabled at build time since **v0.18.0** ([PR 14451](https://github.com/bitcoin/bitcoin/pull/14451)). +* [`BIP 70`](https://github.com/bitcoin/bips/blob/master/bip-0070.mediawiki) [`71`](https://github.com/bitcoin/bips/blob/master/bip-0071.mediawiki) [`72`](https://github.com/bitcoin/bips/blob/master/bip-0072.mediawiki): Payment Protocol support has been available in NYC3 GUI since **v0.9.0** ([PR #5216](https://github.com/bitcoin/bitcoin/pull/5216)). Support can be optionally disabled at build time since **v0.18.0** ([PR 14451](https://github.com/bitcoin/bitcoin/pull/14451)). * [`BIP 90`](https://github.com/bitcoin/bips/blob/master/bip-0090.mediawiki): Trigger mechanism for activation of BIPs 34, 65, and 66 has been simplified to block height checks since **v0.14.0** ([PR #8391](https://github.com/bitcoin/bitcoin/pull/8391)). * [`BIP 111`](https://github.com/bitcoin/bips/blob/master/bip-0111.mediawiki): `NODE_BLOOM` service bit added, and enforced for all peer versions as of **v0.13.0** ([PR #6579](https://github.com/bitcoin/bitcoin/pull/6579) and [PR #6641](https://github.com/bitcoin/bitcoin/pull/6641)). * [`BIP 112`](https://github.com/bitcoin/bips/blob/master/bip-0112.mediawiki): The CHECKSEQUENCEVERIFY opcode has been implemented since **v0.12.1** ([PR #7524](https://github.com/bitcoin/bitcoin/pull/7524)) and has been activated since *block 419328*. diff --git a/doc/build-freebsd.md b/doc/build-freebsd.md index d22b6e838..6e6bc320d 100644 --- a/doc/build-freebsd.md +++ b/doc/build-freebsd.md @@ -34,7 +34,7 @@ BerkeleyDB is only necessary for the wallet functionality. To skip this, pass export BDB_PREFIX="$PWD/db4" ``` -## Building Bitcoin Core +## Building NYC3 **Important**: Use `gmake` (the non-GNU `make` will exit with an error): diff --git a/doc/build-netbsd.md b/doc/build-netbsd.md index ab422f6aa..165ada3c5 100644 --- a/doc/build-netbsd.md +++ b/doc/build-netbsd.md @@ -47,7 +47,7 @@ from the root of the repository. Then set `BDB_PREFIX` for the next section: export BDB_PREFIX="$PWD/db4" ``` -### Building Bitcoin Core +### Building NYC3 **Important**: Use `gmake` (the non-GNU `make` will exit with an error). diff --git a/doc/build-openbsd.md b/doc/build-openbsd.md index dad2566a6..f9ca4b2c8 100644 --- a/doc/build-openbsd.md +++ b/doc/build-openbsd.md @@ -48,7 +48,7 @@ from the root of the repository. Then set `BDB_PREFIX` for the next section: export BDB_PREFIX="$PWD/db4" ``` -### Building Bitcoin Core +### Building NYC3 **Important**: use `gmake`, not `make`. The non-GNU `make` will exit with a horrible error. diff --git a/doc/build-osx.md b/doc/build-osx.md index d28a3d97a..39b086a8d 100644 --- a/doc/build-osx.md +++ b/doc/build-osx.md @@ -38,17 +38,17 @@ from the root of the repository. **Note**: You only need Berkeley DB if the wallet is enabled (see [*Disable-wallet mode*](/doc/build-osx.md#disable-wallet-mode)). -Build Bitcoin Core +Build NYC3 ------------------------ -1. Clone the Bitcoin Core source code: +1. Clone the NYC3 source code: git clone https://github.com/bitcoin/bitcoin cd bitcoin -2. Build Bitcoin Core: +2. Build NYC3: - Configure and build the headless Bitcoin Core binaries as well as the GUI (if Qt is found). + Configure and build the headless NYC3 binaries as well as the GUI (if Qt is found). You can disable the GUI build by passing `--without-gui` to configure. @@ -66,7 +66,7 @@ Build Bitcoin Core Disable-wallet mode -------------------- -When the intention is to run only a P2P node without a wallet, Bitcoin Core may be compiled in +When the intention is to run only a P2P node without a wallet, NYC3 may be compiled in disable-wallet mode with: ./configure --disable-wallet @@ -78,7 +78,7 @@ Mining is also possible in disable-wallet mode using the `getblocktemplate` RPC Running ------- -Bitcoin Core is now available at `./src/bitcoind` +NYC3 is now available at `./src/bitcoind` Before running, you may create an empty configuration file: diff --git a/doc/build-unix.md b/doc/build-unix.md index da65bc347..c19d16548 100644 --- a/doc/build-unix.md +++ b/doc/build-unix.md @@ -1,12 +1,12 @@ UNIX BUILD NOTES ==================== -Some notes on how to build Bitcoin Core in Unix. +Some notes on how to build NYC3 in Unix. (For BSD specific instructions, see `build-*bsd.md` in this directory.) Note --------------------- -Always use absolute paths to configure and compile Bitcoin Core and the dependencies. +Always use absolute paths to configure and compile NYC3 and the dependencies. For example, when specifying the path of the dependency: ../dist/configure --enable-cxx --disable-shared --with-pic --prefix=$BDB_PREFIX @@ -55,7 +55,7 @@ Memory Requirements -------------------- C++ compilers are memory-hungry. It is recommended to have at least 1.5 GB of -memory available when compiling Bitcoin Core. On systems with less, gcc can be +memory available when compiling NYC3. On systems with less, gcc can be tuned to conserve memory with additional CXXFLAGS: @@ -85,7 +85,7 @@ pass `--with-incompatible-bdb` to configure. Otherwise, you can build from self-compiled `depends` (see above). -To build Bitcoin Core without wallet, see [*Disable-wallet mode*](/doc/build-unix.md#disable-wallet-mode) +To build NYC3 without wallet, see [*Disable-wallet mode*](/doc/build-unix.md#disable-wallet-mode) Optional (see --with-miniupnpc and --enable-upnp-default): @@ -177,7 +177,7 @@ If you need to build Boost yourself: Security -------- -To help make your Bitcoin Core installation more secure by making certain attacks impossible to +To help make your NYC3 installation more secure by making certain attacks impossible to exploit even if a vulnerability is found, binaries are hardened by default. This can be disabled with: @@ -207,7 +207,7 @@ Hardening enables the following features: ET_DYN * _Non-executable Stack_: If the stack is executable then trivial stack-based buffer overflow exploits are possible if - vulnerable buffers are found. By default, Bitcoin Core should be built with a non-executable stack, + vulnerable buffers are found. By default, NYC3 should be built with a non-executable stack, but if one of the libraries it uses asks for an executable stack or someone makes a mistake and uses a compiler extension which requires an executable stack, it will silently build an executable without the non-executable stack protection. @@ -223,7 +223,7 @@ Hardening enables the following features: Disable-wallet mode -------------------- -When the intention is to run only a P2P node without a wallet, Bitcoin Core may be compiled in +When the intention is to run only a P2P node without a wallet, NYC3 may be compiled in disable-wallet mode with: ./configure --disable-wallet @@ -254,7 +254,7 @@ Note: Enabling wallet support requires either compiling against a Berkeley DB newer than 4.8 (package `db`) using `--with-incompatible-bdb`, or building and depending on a local version of Berkeley DB 4.8. The readily available Arch Linux packages are currently built using `--with-incompatible-bdb` according to the [PKGBUILD](https://projects.archlinux.org/svntogit/community.git/tree/bitcoin/trunk/PKGBUILD). -As mentioned above, when maintaining portability of the wallet between the standard Bitcoin Core distributions and independently built +As mentioned above, when maintaining portability of the wallet between the standard NYC3 distributions and independently built node software is desired, Berkeley DB 4.8 must be used. diff --git a/doc/build-windows.md b/doc/build-windows.md index 9641e0d3f..322e902e5 100644 --- a/doc/build-windows.md +++ b/doc/build-windows.md @@ -1,12 +1,12 @@ WINDOWS BUILD NOTES ==================== -Below are some notes on how to build Bitcoin Core for Windows. +Below are some notes on how to build NYC3 for Windows. -The options known to work for building Bitcoin Core on Windows are: +The options known to work for building NYC3 on Windows are: * On Linux, using the [Mingw-w64](https://mingw-w64.org/doku.php) cross compiler tool chain. Ubuntu Bionic 18.04 is required -and is the platform used to build the Bitcoin Core Windows release binaries. +and is the platform used to build the NYC3 Windows release binaries. * On Windows, using [Windows Subsystem for Linux (WSL)](https://msdn.microsoft.com/commandline/wsl/about) and the Mingw-w64 cross compiler tool chain. @@ -83,7 +83,7 @@ Ubuntu Bionic 18.04 [1](#footnote1): Once the toolchain is installed the build steps are common: -Note that for WSL the Bitcoin Core source path MUST be somewhere in the default mount file system, for +Note that for WSL the NYC3 source path MUST be somewhere in the default mount file system, for example /usr/src/bitcoin, AND not under /mnt/d/. If this is not the case the dependency autoconf scripts will fail. This means you cannot use a directory that is located directly on the host Windows file system to perform the build. @@ -111,7 +111,7 @@ For Ubuntu Bionic 18.04 and Windows Subsystem for Linux [1](#footnote1) \/\fR[\fI\,params\/\fR] \fI\,Send command to Bitcoin Core\/\fR +[\fI\,options\/\fR] \fI\, \/\fR[\fI\,params\/\fR] \fI\,Send command to NYC3\/\fR .br .B bitcoin-cli -[\fI\,options\/\fR] \fI\,-named \/\fR[\fI\,name=value\/\fR]... \fI\,Send command to Bitcoin Core (with named arguments)\/\fR +[\fI\,options\/\fR] \fI\,-named \/\fR[\fI\,name=value\/\fR]... \fI\,Send command to NYC3 (with named arguments)\/\fR .br .B bitcoin-cli [\fI\,options\/\fR] \fI\,help List commands\/\fR @@ -15,7 +15,7 @@ bitcoin-cli \- manual page for bitcoin-cli v0.18.0.0 .B bitcoin-cli [\fI\,options\/\fR] \fI\,help Get help for a command\/\fR .SH DESCRIPTION -Bitcoin Core RPC client version v0.18.0.0 +NYC3 RPC client version v0.18.0.0 .SH OPTIONS .HP \-? @@ -106,7 +106,7 @@ Use the test chain .SH COPYRIGHT Copyright (C) 2009-2019 The Bitcoin Core developers -Please contribute if you find Bitcoin Core useful. Visit +Please contribute if you find NYC3 useful. Visit for further information about the software. The source code is available from . diff --git a/doc/man/bitcoin-qt.1 b/doc/man/bitcoin-qt.1 index 7be09126e..ac8bd2985 100644 --- a/doc/man/bitcoin-qt.1 +++ b/doc/man/bitcoin-qt.1 @@ -6,7 +6,7 @@ bitcoin-qt \- manual page for bitcoin-qt v0.18.0.0 .B bitcoin-qt [\fI\,command-line options\/\fR] .SH DESCRIPTION -Bitcoin Core version v0.18.0.0 (64\-bit) +NYC3 version v0.18.0.0 (64\-bit) .SH OPTIONS .HP \-? @@ -628,7 +628,7 @@ Show splash screen on startup (default: 1) .SH COPYRIGHT Copyright (C) 2009-2019 The Bitcoin Core developers -Please contribute if you find Bitcoin Core useful. Visit +Please contribute if you find NYC3 useful. Visit for further information about the software. The source code is available from . diff --git a/doc/man/bitcoin-tx.1 b/doc/man/bitcoin-tx.1 index 5a5abc1e1..dde97b795 100644 --- a/doc/man/bitcoin-tx.1 +++ b/doc/man/bitcoin-tx.1 @@ -9,7 +9,7 @@ bitcoin-tx \- manual page for bitcoin-tx v0.18.0.0 .B bitcoin-tx [\fI\,options\/\fR] \fI\,-create \/\fR[\fI\,commands\/\fR] \fI\,Create hex-encoded bitcoin transaction\/\fR .SH DESCRIPTION -Bitcoin Core bitcoin\-tx utility version v0.18.0.0 +NYC3 bitcoin\-tx utility version v0.18.0.0 .SH OPTIONS .HP \-? @@ -107,7 +107,7 @@ Set register NAME to given JSON\-STRING .SH COPYRIGHT Copyright (C) 2009-2019 The Bitcoin Core developers -Please contribute if you find Bitcoin Core useful. Visit +Please contribute if you find NYC3 useful. Visit for further information about the software. The source code is available from . diff --git a/doc/man/bitcoin-wallet.1 b/doc/man/bitcoin-wallet.1 index 902071ba5..306a03331 100644 --- a/doc/man/bitcoin-wallet.1 +++ b/doc/man/bitcoin-wallet.1 @@ -3,9 +3,9 @@ .SH NAME bitcoin-wallet \- manual page for bitcoin-wallet v0.18.0.0 .SH DESCRIPTION -Bitcoin Core bitcoin\-wallet version v0.18.0.0 +NYC3 bitcoin\-wallet version v0.18.0.0 .PP -wallet\-tool is an offline tool for creating and interacting with Bitcoin Core wallet files. +wallet\-tool is an offline tool for creating and interacting with NYC3 wallet files. By default wallet\-tool will act on wallets in the default mainnet wallet directory in the datadir. To change the target wallet, use the \fB\-datadir\fR, \fB\-wallet\fR and \fB\-testnet\fR/\-regtest arguments. .SS "Usage:" @@ -54,7 +54,7 @@ Get wallet info .SH COPYRIGHT Copyright (C) 2009-2019 The Bitcoin Core developers -Please contribute if you find Bitcoin Core useful. Visit +Please contribute if you find NYC3 useful. Visit for further information about the software. The source code is available from . diff --git a/doc/man/bitcoind.1 b/doc/man/bitcoind.1 index 5aa481784..e743fdcb1 100644 --- a/doc/man/bitcoind.1 +++ b/doc/man/bitcoind.1 @@ -4,9 +4,9 @@ bitcoind \- manual page for bitcoind v0.18.0.0 .SH SYNOPSIS .B bitcoind -[\fI\,options\/\fR] \fI\,Start Bitcoin Core Daemon\/\fR +[\fI\,options\/\fR] \fI\,Start NYC3 Daemon\/\fR .SH DESCRIPTION -Bitcoin Core Daemon version v0.18.0.0 +NYC3 Daemon version v0.18.0.0 .SH OPTIONS .HP \-? @@ -602,7 +602,7 @@ Accept command line and JSON\-RPC commands .SH COPYRIGHT Copyright (C) 2009-2019 The Bitcoin Core developers -Please contribute if you find Bitcoin Core useful. Visit +Please contribute if you find NYC3 useful. Visit for further information about the software. The source code is available from . diff --git a/doc/psbt.md b/doc/psbt.md index 9d85af034..56a49b0b7 100644 --- a/doc/psbt.md +++ b/doc/psbt.md @@ -1,6 +1,6 @@ -# PSBT Howto for Bitcoin Core +# PSBT Howto for NYC3 -Since Bitcoin Core 0.17, an RPC interface exists for Partially Signed Bitcoin +Since NYC3 0.17, an RPC interface exists for Partially Signed Bitcoin Transactions (PSBTs, as specified in [BIP 174](https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki)). @@ -46,7 +46,7 @@ The names above in bold are the names of the roles defined in BIP174. They're useful in understanding the underlying steps, but in practice, software and hardware implementations will typically implement multiple roles simultaneously. -## PSBT in Bitcoin Core +## PSBT in NYC3 ### RPCs @@ -89,10 +89,10 @@ hardware implementations will typically implement multiple roles simultaneously. ### Workflows -#### Multisig with multiple Bitcoin Core instances +#### Multisig with multiple NYC3 instances Alice, Bob, and Carol want to create a 2-of-3 multisig address. They're all using -Bitcoin Core. We assume their wallets only contain the multisig funds. In case +NYC3. We assume their wallets only contain the multisig funds. In case they also have a personal wallet, this can be accomplished through the multiwallet feature - possibly resulting in a need to add `-rpcwallet=name` to the command line in case `bitcoin-cli` is used. diff --git a/doc/reduce-traffic.md b/doc/reduce-traffic.md index dd1469f56..9139076f4 100644 --- a/doc/reduce-traffic.md +++ b/doc/reduce-traffic.md @@ -3,7 +3,7 @@ Reduce Traffic Some node operators need to deal with bandwidth caps imposed by their ISPs. -By default, Bitcoin Core allows up to 125 connections to different peers, 8 of +By default, NYC3 allows up to 125 connections to different peers, 8 of which are outbound. You can therefore, have at most 117 inbound connections. The default settings can result in relatively significant traffic consumption. diff --git a/doc/release-notes.md b/doc/release-notes.md index 9a7547b9e..b583d3245 100644 --- a/doc/release-notes.md +++ b/doc/release-notes.md @@ -1,4 +1,4 @@ -Bitcoin Core version 0.18.x is now available from: +NYC3 version 0.18.x is now available from: @@ -35,16 +35,16 @@ wallet versions are still supported. Compatibility ============== -Bitcoin Core is supported and extensively tested on operating systems +NYC3 is supported and extensively tested on operating systems using the Linux kernel, macOS 10.10+, and Windows 7 and newer. It is not -recommended to use Bitcoin Core on unsupported systems. +recommended to use NYC3 on unsupported systems. -Bitcoin Core should also work on most other Unix-like systems but is not +NYC3 should also work on most other Unix-like systems but is not as frequently tested on them. From 0.17.0 onwards, macOS <10.10 is no longer supported. 0.17.0 is built using Qt 5.9.x, which doesn't support versions of macOS older than -10.10. Additionally, Bitcoin Core does not yet change appearance when +10.10. Additionally, NYC3 does not yet change appearance when macOS "dark mode" is activated. In addition to previously-supported CPU platforms, this release's diff --git a/doc/release-notes/release-notes-0.10.0.md b/doc/release-notes/release-notes-0.10.0.md index 986b8832e..cb6a95bcc 100644 --- a/doc/release-notes/release-notes-0.10.0.md +++ b/doc/release-notes/release-notes-0.10.0.md @@ -1,4 +1,4 @@ -Bitcoin Core version 0.10.0 is now available from: +NYC3 version 0.10.0 is now available from: https://bitcoin.org/bin/0.10.0/ @@ -25,7 +25,7 @@ Downgrading warning Because release 0.10.0 makes use of headers-first synchronization and parallel block download (see further), the block files and databases are not -backwards-compatible with older versions of Bitcoin Core or other software: +backwards-compatible with older versions of NYC3 or other software: * Blocks will be stored on disk out of order (in the order they are received, really), which makes it incompatible with some tools or @@ -50,7 +50,7 @@ Notable changes Faster synchronization ---------------------- -Bitcoin Core now uses 'headers-first synchronization'. This means that we first +NYC3 now uses 'headers-first synchronization'. This means that we first ask peers for block headers (a total of 27 megabytes, as of December 2014) and validate those. In a second stage, when the headers have been discovered, we download the blocks. However, as we already know about the whole chain in @@ -222,7 +222,7 @@ addresses need to added to the wallet before the payment, though. Consensus library ----------------- -Starting from 0.10.0, the Bitcoin Core distribution includes a consensus library. +Starting from 0.10.0, the NYC3 distribution includes a consensus library. The purpose of this library is to make the verification functionality that is critical to Bitcoin's consensus available to other applications, e.g. to language @@ -249,7 +249,7 @@ redemption scripts, allowing applications to make use of any valid script type, such as "n-of-m OR y", hash-locked oracle addresses, etc. While the Bitcoin protocol has always supported these types of script, actually using them on mainnet has been previously inconvenient as -standard Bitcoin Core nodes wouldn't relay them to miners, nor would +standard NYC3 nodes wouldn't relay them to miners, nor would most miners include them in blocks they mined. bitcoin-tx @@ -279,7 +279,7 @@ key and script operations easily accessible via command line. Mining and relay policy enhancements ------------------------------------ -Bitcoin Core's block templates are now for version 3 blocks only, and any mining +NYC3's block templates are now for version 3 blocks only, and any mining software relying on its `getblocktemplate` must be updated in parallel to use libblkmaker either version 0.4.2 or any version from 0.5.1 onward. If you are solo mining, this will affect you the moment you upgrade Bitcoin @@ -292,10 +292,10 @@ achieving its 951/1001 status. The `prioritisetransaction` RPC method has been added to enable miners to manipulate the priority of transactions on an individual basis. -Bitcoin Core now supports BIP 22 long polling, so mining software can be +NYC3 now supports BIP 22 long polling, so mining software can be notified immediately of new templates rather than having to poll periodically. -Support for BIP 23 block proposals is now available in Bitcoin Core's +Support for BIP 23 block proposals is now available in NYC3's `getblocktemplate` method. This enables miners to check the basic validity of their next block before expending work on it, reducing risks of accidental hardforks or mining invalid blocks. @@ -313,7 +313,7 @@ AllowFreeThreshold(), in which case they are relayed subject to the rate limiter BIP 66: strict DER encoding for signatures ------------------------------------------ -Bitcoin Core 0.10 implements BIP 66, which introduces block version 3, and a new +NYC3 0.10 implements BIP 66, which introduces block version 3, and a new consensus rule, which prohibits non-DER signatures. Such transactions have been non-standard since Bitcoin v0.8.0 (released in February 2013), but were technically still permitted inside blocks. @@ -522,7 +522,7 @@ Wallet: GUI: - `c21c74b` osx: Fix missing dock menu with qt5 - `b90711c` Fix Transaction details shows wrong To: -- `516053c` Make links in 'About Bitcoin Core' clickable +- `516053c` Make links in 'About NYC3' clickable - `bdc83e8` Ensure payment request network matches client network - `65f78a1` Add GUI view of peer information - `06a91d9` VerifyDB progress reporting diff --git a/doc/release-notes/release-notes-0.10.1.md b/doc/release-notes/release-notes-0.10.1.md index 8f59f1f68..5872665f6 100644 --- a/doc/release-notes/release-notes-0.10.1.md +++ b/doc/release-notes/release-notes-0.10.1.md @@ -1,4 +1,4 @@ -Bitcoin Core version 0.10.1 is now available from: +NYC3 version 0.10.1 is now available from: @@ -25,7 +25,7 @@ Downgrade warning Because release 0.10.0 and later makes use of headers-first synchronization and parallel block download (see further), the block files and databases are not -backwards-compatible with pre-0.10 versions of Bitcoin Core or other software: +backwards-compatible with pre-0.10 versions of NYC3 or other software: * Blocks will be stored on disk out of order (in the order they are received, really), which makes it incompatible with some tools or diff --git a/doc/release-notes/release-notes-0.10.2.md b/doc/release-notes/release-notes-0.10.2.md index 192ed69d2..9b55becdb 100644 --- a/doc/release-notes/release-notes-0.10.2.md +++ b/doc/release-notes/release-notes-0.10.2.md @@ -1,4 +1,4 @@ -Bitcoin Core version 0.10.2 is now available from: +NYC3 version 0.10.2 is now available from: @@ -25,7 +25,7 @@ Downgrade warning Because release 0.10.0 and later makes use of headers-first synchronization and parallel block download (see further), the block files and databases are not -backwards-compatible with pre-0.10 versions of Bitcoin Core or other software: +backwards-compatible with pre-0.10 versions of NYC3 or other software: * Blocks will be stored on disk out of order (in the order they are received, really), which makes it incompatible with some tools or diff --git a/doc/release-notes/release-notes-0.10.3.md b/doc/release-notes/release-notes-0.10.3.md index 8a110e562..fdc6442b9 100644 --- a/doc/release-notes/release-notes-0.10.3.md +++ b/doc/release-notes/release-notes-0.10.3.md @@ -1,4 +1,4 @@ -Bitcoin Core version 0.10.3 is now available from: +NYC3 version 0.10.3 is now available from: @@ -25,7 +25,7 @@ Downgrade warning Because release 0.10.0 and later makes use of headers-first synchronization and parallel block download (see further), the block files and databases are not -backwards-compatible with pre-0.10 versions of Bitcoin Core or other software: +backwards-compatible with pre-0.10 versions of NYC3 or other software: * Blocks will be stored on disk out of order (in the order they are received, really), which makes it incompatible with some tools or @@ -82,7 +82,7 @@ permitted. Even BIP62 did not propose applying this rule to old version transactions, but conforming implementations have become much more common since BIP62 was initially written. -Bitcoin Core has produced compatible signatures since a28fb70e in +NYC3 has produced compatible signatures since a28fb70e in September 2013, but this didn't make it into a release until 0.9 in March 2014; Bitcoinj has done so for a similar span of time. Bitcoinjs and electrum have been more recently updated. diff --git a/doc/release-notes/release-notes-0.10.4.md b/doc/release-notes/release-notes-0.10.4.md index 38a2c1347..cd0c4a60e 100644 --- a/doc/release-notes/release-notes-0.10.4.md +++ b/doc/release-notes/release-notes-0.10.4.md @@ -1,4 +1,4 @@ -Bitcoin Core version 0.10.4 is now available from: +NYC3 version 0.10.4 is now available from: @@ -26,7 +26,7 @@ Downgrade warning Because release 0.10.0 and later makes use of headers-first synchronization and parallel block download (see further), the block files and databases are not -backwards-compatible with pre-0.10 versions of Bitcoin Core or other software: +backwards-compatible with pre-0.10 versions of NYC3 or other software: * Blocks will be stored on disk out of order (in the order they are received, really), which makes it incompatible with some tools or @@ -79,13 +79,13 @@ found at the URLs below: - Block versions over the last 2,000 blocks showing the days to the earliest possible BIP65 consensus-enforced block: -**Notice to miners:** Bitcoin Core’s block templates are now for +**Notice to miners:** NYC3’s block templates are now for version 4 blocks only, and any mining software relying on its getblocktemplate must be updated in parallel to use libblkmaker either version FIXME or any version from FIXME onward. - If you are solo mining, this will affect you the moment you upgrade - Bitcoin Core, which must be done prior to BIP65 achieving its 951/1001 + NYC3, which must be done prior to BIP65 achieving its 951/1001 status. - If you are mining with the stratum mining protocol: this does not @@ -101,7 +101,7 @@ Windows bug fix for corrupted UTXO database on unclean shutdowns ---------------------------------------------------------------- Several Windows users reported that they often need to reindex the -entire blockchain after an unclean shutdown of Bitcoin Core on Windows +entire blockchain after an unclean shutdown of NYC3 on Windows (or an unclean shutdown of Windows itself). Although unclean shutdowns remain unsafe, this release no longer relies on memory-mapped files for the UTXO database, which significantly reduced the frequency of unclean diff --git a/doc/release-notes/release-notes-0.11.0.md b/doc/release-notes/release-notes-0.11.0.md index 28e49fb7e..b46b8b08e 100644 --- a/doc/release-notes/release-notes-0.11.0.md +++ b/doc/release-notes/release-notes-0.11.0.md @@ -1,4 +1,4 @@ -Bitcoin Core version 0.11.0 is now available from: +NYC3 version 0.11.0 is now available from: @@ -25,7 +25,7 @@ Downgrade warning Because release 0.10.0 and later makes use of headers-first synchronization and parallel block download (see further), the block files and databases are not -backwards-compatible with pre-0.10 versions of Bitcoin Core or other software: +backwards-compatible with pre-0.10 versions of NYC3 or other software: * Blocks will be stored on disk out of order (in the order they are received, really), which makes it incompatible with some tools or @@ -86,7 +86,7 @@ related to the blockchain in the bitcoin system: the raw blocks as received over the network (blk???.dat), the undo data (rev???.dat), the block index and the UTXO set (both LevelDB databases). The databases are built from the raw data. -Block pruning allows Bitcoin Core to delete the raw block and undo data once +Block pruning allows NYC3 to delete the raw block and undo data once it's been validated and used to build the databases. At that point, the raw data is used only to relay blocks to other nodes, to handle reorganizations, to look up old transactions (if -txindex is enabled or via the RPC/REST interfaces), or @@ -95,7 +95,7 @@ all blocks in the blockchain. The user specifies how much space to allot for block & undo files. The minimum allowed is 550MB. Note that this is in addition to whatever is required for the -block index and UTXO databases. The minimum was chosen so that Bitcoin Core will +block index and UTXO databases. The minimum was chosen so that NYC3 will be able to maintain at least 288 blocks on disk (two days worth of blocks at 10 minutes per block). In rare instances it is possible that the amount of space used will exceed the pruning target in order to keep the required last 288 diff --git a/doc/release-notes/release-notes-0.11.1.md b/doc/release-notes/release-notes-0.11.1.md index 799205691..fdcfac720 100644 --- a/doc/release-notes/release-notes-0.11.1.md +++ b/doc/release-notes/release-notes-0.11.1.md @@ -1,4 +1,4 @@ -Bitcoin Core version 0.11.1 is now available from: +NYC3 version 0.11.1 is now available from: @@ -25,7 +25,7 @@ Downgrade warning Because release 0.10.0 and later makes use of headers-first synchronization and parallel block download (see further), the block files and databases are not -backwards-compatible with pre-0.10 versions of Bitcoin Core or other software: +backwards-compatible with pre-0.10 versions of NYC3 or other software: * Blocks will be stored on disk out of order (in the order they are received, really), which makes it incompatible with some tools or @@ -83,7 +83,7 @@ permitted. Even BIP62 did not propose applying this rule to old version transactions, but conforming implementations have become much more common since BIP62 was initially written. -Bitcoin Core has produced compatible signatures since a28fb70e in +NYC3 has produced compatible signatures since a28fb70e in September 2013, but this didn't make it into a release until 0.9 in March 2014; Bitcoinj has done so for a similar span of time. Bitcoinjs and electrum have been more recently updated. diff --git a/doc/release-notes/release-notes-0.11.2.md b/doc/release-notes/release-notes-0.11.2.md index 2351b8065..75a43c93b 100644 --- a/doc/release-notes/release-notes-0.11.2.md +++ b/doc/release-notes/release-notes-0.11.2.md @@ -1,4 +1,4 @@ -Bitcoin Core version 0.11.2 is now available from: +NYC3 version 0.11.2 is now available from: @@ -26,7 +26,7 @@ Downgrade warning Because release 0.10.0 and later makes use of headers-first synchronization and parallel block download (see further), the block files and databases are not -backwards-compatible with pre-0.10 versions of Bitcoin Core or other software: +backwards-compatible with pre-0.10 versions of NYC3 or other software: * Blocks will be stored on disk out of order (in the order they are received, really), which makes it incompatible with some tools or @@ -79,13 +79,13 @@ found at the URLs below: - Block versions over the last 2,000 blocks showing the days to the earliest possible BIP65 consensus-enforced block: -**Notice to miners:** Bitcoin Core’s block templates are now for +**Notice to miners:** NYC3’s block templates are now for version 4 blocks only, and any mining software relying on its getblocktemplate must be updated in parallel to use libblkmaker either version 0.4.3 or any version from 0.5.2 onward. - If you are solo mining, this will affect you the moment you upgrade - Bitcoin Core, which must be done prior to BIP65 achieving its 951/1001 + NYC3, which must be done prior to BIP65 achieving its 951/1001 status. - If you are mining with the stratum mining protocol: this does not @@ -149,7 +149,7 @@ Windows bug fix for corrupted UTXO database on unclean shutdowns ---------------------------------------------------------------- Several Windows users reported that they often need to reindex the -entire blockchain after an unclean shutdown of Bitcoin Core on Windows +entire blockchain after an unclean shutdown of NYC3 on Windows (or an unclean shutdown of Windows itself). Although unclean shutdowns remain unsafe, this release no longer relies on memory-mapped files for the UTXO database, which significantly reduced the frequency of unclean diff --git a/doc/release-notes/release-notes-0.12.0.md b/doc/release-notes/release-notes-0.12.0.md index cf74a1797..5e107bd52 100644 --- a/doc/release-notes/release-notes-0.12.0.md +++ b/doc/release-notes/release-notes-0.12.0.md @@ -1,4 +1,4 @@ -Bitcoin Core version 0.12.0 is now available from: +NYC3 version 0.12.0 is now available from: @@ -26,7 +26,7 @@ Downgrade warning Because release 0.10.0 and later makes use of headers-first synchronization and parallel block download (see further), the block files and databases are not -backwards-compatible with pre-0.10 versions of Bitcoin Core or other software: +backwards-compatible with pre-0.10 versions of NYC3 or other software: * Blocks will be stored on disk out of order (in the order they are received, really), which makes it incompatible with some tools or @@ -48,10 +48,10 @@ This does not affect wallet forward or backward compatibility. Because release 0.12.0 and later will obfuscate the chainstate on every fresh sync or reindex, the chainstate is not backwards-compatible with -pre-0.12 versions of Bitcoin Core or other software. +pre-0.12 versions of NYC3 or other software. If you want to downgrade after you have done a reindex with 0.12.0 or later, -you will need to reindex when you first start Bitcoin Core version 0.11 or +you will need to reindex when you first start NYC3 version 0.11 or earlier. Notable changes @@ -107,15 +107,15 @@ can often prevent an extra roundtrip before the actual block is downloaded. Memory pool limiting -------------------- -Previous versions of Bitcoin Core had their mempool limited by checking +Previous versions of NYC3 had their mempool limited by checking a transaction's fees against the node's minimum relay fee. There was no upper bound on the size of the mempool and attackers could send a large number of transactions paying just slighly more than the default minimum relay fee to crash nodes with relatively low RAM. A temporary workaround -for previous versions of Bitcoin Core was to raise the default minimum +for previous versions of NYC3 was to raise the default minimum relay fee. -Bitcoin Core 0.12 will have a strict maximum size on the mempool. The +NYC3 0.12 will have a strict maximum size on the mempool. The default value is 300 MB and can be configured with the `-maxmempool` parameter. Whenever a transaction would cause the mempool to exceed its maximum size, the transaction that (along with in-mempool descendants) has @@ -124,7 +124,7 @@ minimum relay feerate will be increased to match this feerate plus the initial minimum relay feerate. The initial minimum relay feerate is set to 1000 satoshis per kB. -Bitcoin Core 0.12 also introduces new default policy limits on the length and +NYC3 0.12 also introduces new default policy limits on the length and size of unconfirmed transaction chains that are allowed in the mempool (generally limiting the length of unconfirmed chains to 25 transactions, with a total size of 101 KB). These limits can be overriden using command line @@ -134,7 +134,7 @@ Opt-in Replace-by-fee transactions ---------------------------------- It is now possible to replace transactions in the transaction memory pool of -Bitcoin Core 0.12 nodes. Bitcoin Core will only allow replacement of +NYC3 0.12 nodes. NYC3 will only allow replacement of transactions which have any of their inputs' `nSequence` number set to less than `0xffffffff - 1`. Moreover, a replacement transaction may only be accepted when it pays sufficient fee, as described in [BIP 125] @@ -156,7 +156,7 @@ updated RPC calls `gettransaction` and `listtransactions`, which now have an additional field in the output indicating if a transaction is replaceable under BIP125 ("bip125-replaceable"). -Note that the wallet in Bitcoin Core 0.12 does not yet have support for +Note that the wallet in NYC3 0.12 does not yet have support for creating transactions that would be replaceable under BIP 125. @@ -196,14 +196,14 @@ returned (previously all relevant hashes were returned). Relay and Mining: Priority transactions --------------------------------------- -Bitcoin Core has a heuristic 'priority' based on coin value and age. This +NYC3 has a heuristic 'priority' based on coin value and age. This calculation is used for relaying of transactions which do not pay the minimum relay fee, and can be used as an alternative way of sorting -transactions for mined blocks. Bitcoin Core will relay transactions with +transactions for mined blocks. NYC3 will relay transactions with insufficient fees depending on the setting of `-limitfreerelay=` (default: `r=15` kB per minute) and `-blockprioritysize=`. -In Bitcoin Core 0.12, when mempool limit has been reached a higher minimum +In NYC3 0.12, when mempool limit has been reached a higher minimum relay fee takes effect to limit memory usage. Transactions which do not meet this higher effective minimum relay fee will not be relayed or mined even if they rank highly according to the priority heuristic. @@ -224,7 +224,7 @@ Note, however, that if mining priority transactions is left disabled, the priority delta will be ignored and only the fee metric will be effective. This internal automatic prioritization handling is being considered for removal -entirely in Bitcoin Core 0.13, and it is at this time undecided whether the +entirely in NYC3 0.13, and it is at this time undecided whether the more accurate priority calculation for chained unconfirmed transactions will be restored. Community direction on this topic is particularly requested to help set project priorities. @@ -234,15 +234,15 @@ Automatically use Tor hidden services Starting with Tor version 0.2.7.1 it is possible, through Tor's control socket API, to create and destroy 'ephemeral' hidden services programmatically. -Bitcoin Core has been updated to make use of this. +NYC3 has been updated to make use of this. This means that if Tor is running (and proper authorization is available), -Bitcoin Core automatically creates a hidden service to listen on, without -manual configuration. Bitcoin Core will also use Tor automatically to connect +NYC3 automatically creates a hidden service to listen on, without +manual configuration. NYC3 will also use Tor automatically to connect to other .onion nodes if the control socket can be successfully opened. This will positively affect the number of available .onion nodes and their usage. -This new feature is enabled by default if Bitcoin Core is listening, and +This new feature is enabled by default if NYC3 is listening, and a connection to Tor can be made. It can be configured with the `-listenonion`, `-torcontrol` and `-torpassword` settings. To show verbose debugging information, pass `-debug=tor`. @@ -264,7 +264,7 @@ transaction fees. Users can decide to pay a predefined fee rate by setting `-paytxfee=` (or `settxfee ` rpc during runtime). A value of `n=0` signals Bitcoin -Core to use floating fees. By default, Bitcoin Core will use floating +Core to use floating fees. By default, NYC3 will use floating fees. Based on past transaction data, floating fees approximate the fees @@ -275,9 +275,9 @@ Sometimes, it is not possible to give good estimates, or an estimate at all. Therefore, a fallback value can be set with `-fallbackfee=` (default: `0.0002` BTC/kB). -At all times, Bitcoin Core will cap fees at `-maxtxfee=` (default: +At all times, NYC3 will cap fees at `-maxtxfee=` (default: 0.10) BTC. -Furthermore, Bitcoin Core will never create transactions paying less than +Furthermore, NYC3 will never create transactions paying less than the current minimum relay fee. Finally, a user can set the minimum fee rate for all transactions with `-mintxfee=`, which defaults to 1000 satoshis per kB. diff --git a/doc/release-notes/release-notes-0.12.1.md b/doc/release-notes/release-notes-0.12.1.md index 610cd481d..3a9e6d97f 100644 --- a/doc/release-notes/release-notes-0.12.1.md +++ b/doc/release-notes/release-notes-0.12.1.md @@ -1,4 +1,4 @@ -Bitcoin Core version 0.12.1 is now available from: +NYC3 version 0.12.1 is now available from: @@ -27,10 +27,10 @@ Downgrade warning Because release 0.12.0 and later will obfuscate the chainstate on every fresh sync or reindex, the chainstate is not backwards-compatible with -pre-0.12 versions of Bitcoin Core or other software. +pre-0.12 versions of NYC3 or other software. If you want to downgrade after you have done a reindex with 0.12.0 or later, -you will need to reindex when you first start Bitcoin Core version 0.11 or +you will need to reindex when you first start NYC3 version 0.11 or earlier. Notable changes @@ -84,7 +84,7 @@ For more information about the implementation, see BIP113 locktime enforcement soft fork ------------------------------------- -Bitcoin Core 0.11.2 previously introduced mempool-only locktime +NYC3 0.11.2 previously introduced mempool-only locktime enforcement using GetMedianTimePast(). This release seeks to consensus enforce the rule. diff --git a/doc/release-notes/release-notes-0.13.0.md b/doc/release-notes/release-notes-0.13.0.md index 4c3cb97df..8aabb1d1a 100644 --- a/doc/release-notes/release-notes-0.13.0.md +++ b/doc/release-notes/release-notes-0.13.0.md @@ -1,4 +1,4 @@ -Bitcoin Core version 0.13.0 is now available from: +NYC3 version 0.13.0 is now available from: @@ -21,7 +21,7 @@ an OS initially released in 2001. This means that not even critical security updates will be released anymore. Without security updates, using a bitcoin wallet on a XP machine is irresponsible at least. -In addition to that, with 0.12.x there have been varied reports of Bitcoin Core +In addition to that, with 0.12.x there have been varied reports of NYC3 randomly crashing on Windows XP. It is [not clear](https://github.com/bitcoin/bitcoin/issues/7681#issuecomment-217439891) what the source of these crashes is, but it is likely that upstream libraries such as Qt are no longer being tested on XP. @@ -76,7 +76,7 @@ table by any user on the system. C++11 and Python 3 ------------------ -Various code modernizations have been done. The Bitcoin Core code base has +Various code modernizations have been done. The NYC3 code base has started using C++11. This means that a C++11-capable compiler is now needed for building. Effectively this means GCC 4.7 or higher, or Clang 3.3 or higher. @@ -156,7 +156,7 @@ You can't disable HD key generation once you have created a HD wallet. There is no distinction between internal (change) and external keys. -HD wallets are incompatible with older versions of Bitcoin Core. +HD wallets are incompatible with older versions of NYC3. [Pull request](https://github.com/bitcoin/bitcoin/pull/8035/files), [BIP 32](https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki) @@ -172,7 +172,7 @@ The code preparations for Segregated Witness ("segwit"), as described in [BIP finished and included in this release. However, BIP 141 does not yet specify activation parameters on mainnet, and so this release does not support segwit use on mainnet. Testnet use is supported, and after BIP 141 is updated with -proposed parameters, a future release of Bitcoin Core is expected that +proposed parameters, a future release of NYC3 is expected that implements those parameters for mainnet. Furthermore, because segwit activation is not yet specified for mainnet, diff --git a/doc/release-notes/release-notes-0.13.1.md b/doc/release-notes/release-notes-0.13.1.md index 75c2d61be..7094e6b04 100644 --- a/doc/release-notes/release-notes-0.13.1.md +++ b/doc/release-notes/release-notes-0.13.1.md @@ -1,4 +1,4 @@ -Bitcoin Core version 0.13.1 is now available from: +NYC3 version 0.13.1 is now available from: @@ -22,7 +22,7 @@ an OS initially released in 2001. This means that not even critical security updates will be released anymore. Without security updates, using a bitcoin wallet on a XP machine is irresponsible at least. -In addition to that, with 0.12.x there have been varied reports of Bitcoin Core +In addition to that, with 0.12.x there have been varied reports of NYC3 randomly crashing on Windows XP. It is [not clear](https://github.com/bitcoin/bitcoin/issues/7681#issuecomment-217439891) what the source of these crashes is, but it is likely that upstream libraries such as Qt are no longer being tested on XP. @@ -131,13 +131,13 @@ covered by the txid. This provides several immediate benefits: (specifically, the segregated witnesses) while still ensuring that the node can build an accurate copy of the UTXO set for the block chain with the most proof of work. Segwit enables this capability at the consensus layer, but - note that Bitcoin Core does not provide an option to use this capability as + note that NYC3 does not provide an option to use this capability as of this 0.13.1 release. - **Script versioning:** Segwit makes it easy for future soft forks to allow Bitcoin users to individually opt-in to almost any change in the Bitcoin Script language when those users receive new transactions. Features - currently being researched by Bitcoin Core contributors that may use this + currently being researched by NYC3 contributors that may use this capability include support for Schnorr signatures, which can improve the privacy and efficiency of multisig transactions (or transactions with multiple inputs), and Merklized Abstract Syntax Trees (MAST), which can @@ -183,7 +183,7 @@ a third-party to insert data into other people's transactions, changing the transaction's txid (called transaction malleability) and possibly causing other problems. -Since Bitcoin Core 0.10.0, nodes have defaulted to only relaying and +Since NYC3 0.10.0, nodes have defaulted to only relaying and mining transactions whose dummy element was a null value (0x00, also called OP_0). The null dummy soft fork turns this relay rule into a consensus rule both for non-segwit transactions and segwit transactions, diff --git a/doc/release-notes/release-notes-0.13.2.md b/doc/release-notes/release-notes-0.13.2.md index 45fff5c8b..d1918d5ac 100644 --- a/doc/release-notes/release-notes-0.13.2.md +++ b/doc/release-notes/release-notes-0.13.2.md @@ -1,4 +1,4 @@ -Bitcoin Core version 0.13.2 is now available from: +NYC3 version 0.13.2 is now available from: @@ -21,7 +21,7 @@ an OS initially released in 2001. This means that not even critical security updates will be released anymore. Without security updates, using a bitcoin wallet on a XP machine is irresponsible at least. -In addition to that, with 0.12.x there have been varied reports of Bitcoin Core +In addition to that, with 0.12.x there have been varied reports of NYC3 randomly crashing on Windows XP. It is [not clear](https://github.com/bitcoin/bitcoin/issues/7681#issuecomment-217439891) what the source of these crashes is, but it is likely that upstream libraries such as Qt are no longer being tested on XP. diff --git a/doc/release-notes/release-notes-0.14.0.md b/doc/release-notes/release-notes-0.14.0.md index c41f22979..49ee8cf8f 100644 --- a/doc/release-notes/release-notes-0.14.0.md +++ b/doc/release-notes/release-notes-0.14.0.md @@ -1,4 +1,4 @@ -Bitcoin Core version 0.14.0 is now available from: +NYC3 version 0.14.0 is now available from: @@ -16,7 +16,7 @@ To receive security and update notifications, please subscribe to: Compatibility ============== -Bitcoin Core is extensively tested on multiple operating systems using +NYC3 is extensively tested on multiple operating systems using the Linux kernel, macOS 10.8+, and Windows Vista and later. Microsoft ended support for Windows XP on [April 8th, 2014](https://www.microsoft.com/en-us/WindowsForBusiness/end-of-xp-support), @@ -24,7 +24,7 @@ No attempt is made to prevent installing or running the software on Windows XP, can still do so at your own risk but be aware that there are known instabilities and issues. Please do not report issues about Windows XP to the issue tracker. -Bitcoin Core should also work on most other Unix-like systems but is not +NYC3 should also work on most other Unix-like systems but is not frequently tested on them. Notable changes @@ -55,7 +55,7 @@ improved, leading to much shorter sync and initial block download times. Manual Pruning -------------- -Bitcoin Core has supported automatically pruning the blockchain since 0.11. Pruning +NYC3 has supported automatically pruning the blockchain since 0.11. Pruning the blockchain allows for significant storage space savings as the vast majority of the downloaded data can be discarded after processing so very little of it remains on the disk. @@ -129,7 +129,7 @@ the same thing as the GUI icon. The command takes one boolean parameter, Out-of-sync Modal Info Layer ---------------------------- -When Bitcoin Core is out-of-sync on startup, a semi-transparent information +When NYC3 is out-of-sync on startup, a semi-transparent information layer will be shown over top of the normal display. This layer contains details about the current sync progress and estimates the amount of time remaining to finish syncing. This layer can also be hidden and subsequently @@ -189,7 +189,7 @@ commands such as `prioritisetransaction` so that those changes will not be lost. Final Alert ----------- -The Alert System was [disabled and deprecated](https://bitcoin.org/en/alert/2016-11-01-alert-retirement) in Bitcoin Core 0.12.1 and removed in 0.13.0. +The Alert System was [disabled and deprecated](https://bitcoin.org/en/alert/2016-11-01-alert-retirement) in NYC3 0.12.1 and removed in 0.13.0. The Alert System was retired with a maximum sequence final alert which causes any nodes supporting the Alert System to display a static hard-coded "Alert Key Compromised" message which also prevents any other alerts from overriding it. This final alert is hard-coded into this release @@ -241,7 +241,7 @@ Low-level RPC changes the mempool or if `txindex` is enabled. - A new RPC command `getmemoryinfo` has been added which will return information - about the memory usage of Bitcoin Core. This was added in conjunction with + about the memory usage of NYC3. This was added in conjunction with optimizations to memory management. See [Pull #8753](https://github.com/bitcoin/bitcoin/pull/8753) for more information. diff --git a/doc/release-notes/release-notes-0.14.1.md b/doc/release-notes/release-notes-0.14.1.md index ef072afd4..78f746fd1 100644 --- a/doc/release-notes/release-notes-0.14.1.md +++ b/doc/release-notes/release-notes-0.14.1.md @@ -1,4 +1,4 @@ -Bitcoin Core version 0.14.1 is now available from: +NYC3 version 0.14.1 is now available from: @@ -16,7 +16,7 @@ To receive security and update notifications, please subscribe to: Compatibility ============== -Bitcoin Core is extensively tested on multiple operating systems using +NYC3 is extensively tested on multiple operating systems using the Linux kernel, macOS 10.8+, and Windows Vista and later. Microsoft ended support for Windows XP on [April 8th, 2014](https://www.microsoft.com/en-us/WindowsForBusiness/end-of-xp-support), @@ -24,7 +24,7 @@ No attempt is made to prevent installing or running the software on Windows XP, can still do so at your own risk but be aware that there are known instabilities and issues. Please do not report issues about Windows XP to the issue tracker. -Bitcoin Core should also work on most other Unix-like systems but is not +NYC3 should also work on most other Unix-like systems but is not frequently tested on them. Notable changes diff --git a/doc/release-notes/release-notes-0.14.2.md b/doc/release-notes/release-notes-0.14.2.md index 0ad554b77..ab4d07cc4 100644 --- a/doc/release-notes/release-notes-0.14.2.md +++ b/doc/release-notes/release-notes-0.14.2.md @@ -1,4 +1,4 @@ -Bitcoin Core version 0.14.2 is now available from: +NYC3 version 0.14.2 is now available from: @@ -16,7 +16,7 @@ To receive security and update notifications, please subscribe to: Compatibility ============== -Bitcoin Core is extensively tested on multiple operating systems using +NYC3 is extensively tested on multiple operating systems using the Linux kernel, macOS 10.8+, and Windows Vista and later. Microsoft ended support for Windows XP on [April 8th, 2014](https://www.microsoft.com/en-us/WindowsForBusiness/end-of-xp-support), @@ -24,7 +24,7 @@ No attempt is made to prevent installing or running the software on Windows XP, can still do so at your own risk but be aware that there are known instabilities and issues. Please do not report issues about Windows XP to the issue tracker. -Bitcoin Core should also work on most other Unix-like systems but is not +NYC3 should also work on most other Unix-like systems but is not frequently tested on them. Notable changes @@ -40,7 +40,7 @@ other impact. This only affects users that have explicitly enabled UPnP through the GUI setting or through the `-upnp` option, as since the last UPnP vulnerability -(in Bitcoin Core 0.10.3) it has been disabled by default. +(in NYC3 0.10.3) it has been disabled by default. If you use this option, it is recommended to upgrade to this version as soon as possible. diff --git a/doc/release-notes/release-notes-0.14.3.md b/doc/release-notes/release-notes-0.14.3.md index 8259152f0..002e5609e 100644 --- a/doc/release-notes/release-notes-0.14.3.md +++ b/doc/release-notes/release-notes-0.14.3.md @@ -1,4 +1,4 @@ -Bitcoin Core version *0.14.3* is now available from: +NYC3 version *0.14.3* is now available from: @@ -16,7 +16,7 @@ To receive security and update notifications, please subscribe to: Compatibility ============== -Bitcoin Core is extensively tested on multiple operating systems using +NYC3 is extensively tested on multiple operating systems using the Linux kernel, macOS 10.8+, and Windows Vista and later. Microsoft ended support for Windows XP on [April 8th, 2014](https://www.microsoft.com/en-us/WindowsForBusiness/end-of-xp-support), @@ -24,7 +24,7 @@ No attempt is made to prevent installing or running the software on Windows XP, can still do so at your own risk but be aware that there are known instabilities and issues. Please do not report issues about Windows XP to the issue tracker. -Bitcoin Core should also work on most other Unix-like systems but is not +NYC3 should also work on most other Unix-like systems but is not frequently tested on them. Notable changes @@ -34,7 +34,7 @@ Denial-of-Service vulnerability CVE-2018-17144 ------------------------------- A denial-of-service vulnerability exploitable by miners has been discovered in -Bitcoin Core versions 0.14.0 up to 0.16.2. It is recommended to upgrade any of +NYC3 versions 0.14.0 up to 0.16.2. It is recommended to upgrade any of the vulnerable versions to 0.14.3, 0.15.2 or 0.16.3 as soon as possible. Known Bugs diff --git a/doc/release-notes/release-notes-0.15.0.1.md b/doc/release-notes/release-notes-0.15.0.1.md index 53ab02cbb..b99c2fc3a 100644 --- a/doc/release-notes/release-notes-0.15.0.1.md +++ b/doc/release-notes/release-notes-0.15.0.1.md @@ -1,4 +1,4 @@ -Bitcoin Core version *0.15.0.1* is now available from: +NYC3 version *0.15.0.1* is now available from: @@ -51,10 +51,10 @@ processing the entire blockchain. Compatibility ============== -Bitcoin Core is extensively tested on multiple operating systems using +NYC3 is extensively tested on multiple operating systems using the Linux kernel, macOS 10.8+, and Windows Vista and later. Windows XP is not supported. -Bitcoin Core should also work on most other Unix-like systems but is not +NYC3 should also work on most other Unix-like systems but is not frequently tested on them. Notable changes diff --git a/doc/release-notes/release-notes-0.15.0.md b/doc/release-notes/release-notes-0.15.0.md index 3d000e94d..ad6190ffc 100644 --- a/doc/release-notes/release-notes-0.15.0.md +++ b/doc/release-notes/release-notes-0.15.0.md @@ -1,4 +1,4 @@ -Bitcoin Core version *0.15.0* is now available from: +NYC3 version *0.15.0* is now available from: @@ -48,10 +48,10 @@ processing the entire blockchain. Compatibility ============== -Bitcoin Core is extensively tested on multiple operating systems using +NYC3 is extensively tested on multiple operating systems using the Linux kernel, macOS 10.8+, and Windows Vista and later. Windows XP is not supported. -Bitcoin Core should also work on most other Unix-like systems but is not +NYC3 should also work on most other Unix-like systems but is not frequently tested on them. Notes for 0.15.0 @@ -136,23 +136,23 @@ Fee estimation has been significantly improved in version 0.15, with more accura - The `nblocks` argument has been renamed to `conf_target` (to be consistent with other RPC methods). - An `estimate_mode` argument has been added. This argument takes one of the following strings: `CONSERVATIVE`, `ECONOMICAL` or `UNSET` (which defaults to `CONSERVATIVE`). - The RPC return object now contains an `errors` member, which returns errors encountered during processing. - - If Bitcoin Core has not been running for long enough and has not seen enough blocks or transactions to produce an accurate fee estimation, an error will be returned (previously a value of -1 was used to indicate an error, which could be confused for a feerate). + - If NYC3 has not been running for long enough and has not seen enough blocks or transactions to produce an accurate fee estimation, an error will be returned (previously a value of -1 was used to indicate an error, which could be confused for a feerate). - A new `estimaterawfee` RPC is added to provide raw fee data. External clients can query and use this data in their own fee estimation logic. Multi-wallet support -------------------- -Bitcoin Core now supports loading multiple, separate wallets (See [PR 8694](https://github.com/bitcoin/bitcoin/pull/8694), [PR 10849](https://github.com/bitcoin/bitcoin/pull/10849)). The wallets are completely separated, with individual balances, keys and received transactions. +NYC3 now supports loading multiple, separate wallets (See [PR 8694](https://github.com/bitcoin/bitcoin/pull/8694), [PR 10849](https://github.com/bitcoin/bitcoin/pull/10849)). The wallets are completely separated, with individual balances, keys and received transactions. Multi-wallet is enabled by using more than one `-wallet` argument when starting Bitcoin, either on the command line or in the Bitcoin config file. **In Bitcoin-Qt, only the first wallet will be displayed and accessible for creating and signing transactions.** GUI selectable multiple wallets will be supported in a future version. However, even in 0.15 other loaded wallets will remain synchronized to the node's current tip in the background. This can be useful if running a pruned node, since loading a wallet where the most recent sync is beyond the pruned height results in having to download and revalidate the whole blockchain. Continuing to synchronize all wallets in the background avoids this problem. -Bitcoin Core 0.15.0 contains the following changes to the RPC interface and `bitcoin-cli` for multi-wallet: +NYC3 0.15.0 contains the following changes to the RPC interface and `bitcoin-cli` for multi-wallet: -* When running Bitcoin Core with a single wallet, there are **no** changes to the RPC interface or `bitcoin-cli`. All RPC calls and `bitcoin-cli` commands continue to work as before. -* When running Bitcoin Core with multi-wallet, all *node-level* RPC methods continue to work as before. HTTP RPC requests should be send to the normal `:` endpoint, and `bitcoin-cli` commands should be run as before. A *node-level* RPC method is any method which does not require access to the wallet. -* When running Bitcoin Core with multi-wallet, *wallet-level* RPC methods must specify the wallet for which they're intended in every request. HTTP RPC requests should be send to the `:/wallet/` endpoint, for example `127.0.0.1:8332/wallet/wallet1.dat`. `bitcoin-cli` commands should be run with a `-rpcwallet` option, for example `bitcoin-cli -rpcwallet=wallet1.dat getbalance`. +* When running NYC3 with a single wallet, there are **no** changes to the RPC interface or `bitcoin-cli`. All RPC calls and `bitcoin-cli` commands continue to work as before. +* When running NYC3 with multi-wallet, all *node-level* RPC methods continue to work as before. HTTP RPC requests should be send to the normal `:` endpoint, and `bitcoin-cli` commands should be run as before. A *node-level* RPC method is any method which does not require access to the wallet. +* When running NYC3 with multi-wallet, *wallet-level* RPC methods must specify the wallet for which they're intended in every request. HTTP RPC requests should be send to the `:/wallet/` endpoint, for example `127.0.0.1:8332/wallet/wallet1.dat`. `bitcoin-cli` commands should be run with a `-rpcwallet` option, for example `bitcoin-cli -rpcwallet=wallet1.dat getbalance`. * A new *node-level* `listwallets` RPC method is added to display which wallets are currently loaded. The names returned by this method are the same as those used in the HTTP endpoint and for the `rpcwallet` argument. Note that while multi-wallet is now fully supported, the RPC multi-wallet interface should be considered unstable for version 0.15.0, and there may backwards-incompatible changes in future versions. @@ -160,7 +160,7 @@ Note that while multi-wallet is now fully supported, the RPC multi-wallet interf Replace-by-fee control in the GUI --------------------------------- -Bitcoin Core has supported creating opt-in replace-by-fee (RBF) transactions +NYC3 has supported creating opt-in replace-by-fee (RBF) transactions since version 0.12.0, and since version 0.14.0 has included a `bumpfee` RPC method to replace unconfirmed opt-in RBF transactions with a new transaction that pays a higher fee. @@ -171,7 +171,7 @@ transaction with a higher-fee transaction are both supported in the GUI (See [PR Removal of Coin Age Priority ---------------------------- -In previous versions of Bitcoin Core, a portion of each block could be reserved for transactions based on the age and value of UTXOs they spent. This concept (Coin Age Priority) is a policy choice by miners, and there are no consensus rules around the inclusion of Coin Age Priority transactions in blocks. In practice, only a few miners continue to use Coin Age Priority for transaction selection in blocks. Bitcoin Core 0.15 removes all remaining support for Coin Age Priority (See [PR 9602](https://github.com/bitcoin/bitcoin/pull/9602)). This has the following implications: +In previous versions of NYC3, a portion of each block could be reserved for transactions based on the age and value of UTXOs they spent. This concept (Coin Age Priority) is a policy choice by miners, and there are no consensus rules around the inclusion of Coin Age Priority transactions in blocks. In practice, only a few miners continue to use Coin Age Priority for transaction selection in blocks. NYC3 0.15 removes all remaining support for Coin Age Priority (See [PR 9602](https://github.com/bitcoin/bitcoin/pull/9602)). This has the following implications: - The concept of *free transactions* has been removed. High Coin Age Priority transactions would previously be allowed to be relayed even if they didn't attach a miner fee. This is no longer possible since there is no concept of Coin Age Priority. The `-limitfreerelay` and `-relaypriority` options which controlled relay of free transactions have therefore been removed. - The `-sendfreetransactions` option has been removed, since almost all miners do not include transactions which do not attach a transaction fee. @@ -204,7 +204,7 @@ Version 0.15 introduces several new RPC methods: Low-level RPC changes --------------------- -- When using Bitcoin Core in multi-wallet mode, RPC requests for wallet methods must specify +- When using NYC3 in multi-wallet mode, RPC requests for wallet methods must specify the wallet that they're intended for. See [Multi-wallet support](#multi-wallet-support) for full details. - The new database model no longer stores information about transaction @@ -246,7 +246,7 @@ Low-level RPC changes - The `disconnectnode` RPC can now disconnect a node specified by node ID (as well as by IP address/port). To disconnect a node based on node ID, call the RPC with the new `nodeid` argument (See [PR 10143](https://github.com/bitcoin/bitcoin/pull/10143)). -- The second argument in `prioritisetransaction` has been renamed from `priority_delta` to `dummy` since Bitcoin Core no longer has a concept of coin age priority. The `dummy` argument has no functional effect, but is retained for positional argument compatibility. See [Removal of Coin Age Priority](#removal-of-coin-age-priority). +- The second argument in `prioritisetransaction` has been renamed from `priority_delta` to `dummy` since NYC3 no longer has a concept of coin age priority. The `dummy` argument has no functional effect, but is retained for positional argument compatibility. See [Removal of Coin Age Priority](#removal-of-coin-age-priority). - The `resendwallettransactions` RPC throws an error if the `-walletbroadcast` option is set to false (See [PR 10995](https://github.com/bitcoin/bitcoin/pull/10995)). diff --git a/doc/release-notes/release-notes-0.15.1.md b/doc/release-notes/release-notes-0.15.1.md index 75d2e0971..241da3fde 100644 --- a/doc/release-notes/release-notes-0.15.1.md +++ b/doc/release-notes/release-notes-0.15.1.md @@ -1,4 +1,4 @@ -Bitcoin Core version *0.15.1* is now available from: +NYC3 version *0.15.1* is now available from: @@ -52,10 +52,10 @@ processing the entire blockchain. Compatibility ============== -Bitcoin Core is extensively tested on multiple operating systems using +NYC3 is extensively tested on multiple operating systems using the Linux kernel, macOS 10.8+, and Windows Vista and later. Windows XP is not supported. -Bitcoin Core should also work on most other Unix-like systems but is not +NYC3 should also work on most other Unix-like systems but is not frequently tested on them. @@ -65,7 +65,7 @@ Notable changes Network fork safety enhancements -------------------------------- -A number of changes to the way Bitcoin Core deals with peer connections and invalid blocks +A number of changes to the way NYC3 deals with peer connections and invalid blocks have been made, as a safety precaution against blockchain forks and misbehaving peers. - Unrequested blocks with less work than the minimum-chain-work are now no longer processed even diff --git a/doc/release-notes/release-notes-0.15.2.md b/doc/release-notes/release-notes-0.15.2.md index 1f5827905..7b2a44112 100644 --- a/doc/release-notes/release-notes-0.15.2.md +++ b/doc/release-notes/release-notes-0.15.2.md @@ -1,4 +1,4 @@ -Bitcoin Core version *0.15.2* is now available from: +NYC3 version *0.15.2* is now available from: @@ -48,10 +48,10 @@ processing the entire blockchain. Compatibility ============== -Bitcoin Core is extensively tested on multiple operating systems using +NYC3 is extensively tested on multiple operating systems using the Linux kernel, macOS 10.8+, and Windows Vista and later. Windows XP is not supported. -Bitcoin Core should also work on most other Unix-like systems but is not +NYC3 should also work on most other Unix-like systems but is not frequently tested on them. @@ -62,7 +62,7 @@ Denial-of-Service vulnerability CVE-2018-17144 ------------------------------- A denial-of-service vulnerability exploitable by miners has been discovered in -Bitcoin Core versions 0.14.0 up to 0.16.2. It is recommended to upgrade any of +NYC3 versions 0.14.0 up to 0.16.2. It is recommended to upgrade any of the vulnerable versions to 0.15.2 or 0.16.3 as soon as possible. 0.15.2 Change log diff --git a/doc/release-notes/release-notes-0.16.0.md b/doc/release-notes/release-notes-0.16.0.md index 8f158b348..896010894 100644 --- a/doc/release-notes/release-notes-0.16.0.md +++ b/doc/release-notes/release-notes-0.16.0.md @@ -1,4 +1,4 @@ -Bitcoin Core version 0.16.0 is now available from: +NYC3 version 0.16.0 is now available from: @@ -40,10 +40,10 @@ wallets that were created with older versions are not affected by this. Compatibility ============== -Bitcoin Core is extensively tested on multiple operating systems using +NYC3 is extensively tested on multiple operating systems using the Linux kernel, macOS 10.8+, and Windows Vista and later. Windows XP is not supported. -Bitcoin Core should also work on most other Unix-like systems but is not +NYC3 should also work on most other Unix-like systems but is not frequently tested on them. Notable changes @@ -54,7 +54,7 @@ Wallet changes ### Segwit Wallet -Bitcoin Core 0.16.0 introduces full support for segwit in the wallet and user interfaces. A new `-addresstype` argument has been added, which supports `legacy`, `p2sh-segwit` (default), and `bech32` addresses. It controls what kind of addresses are produced by `getnewaddress`, `getaccountaddress`, and `createmultisigaddress`. A `-changetype` argument has also been added, with the same options, and by default equal to `-addresstype`, to control which kind of change is used. +NYC3 0.16.0 introduces full support for segwit in the wallet and user interfaces. A new `-addresstype` argument has been added, which supports `legacy`, `p2sh-segwit` (default), and `bech32` addresses. It controls what kind of addresses are produced by `getnewaddress`, `getaccountaddress`, and `createmultisigaddress`. A `-changetype` argument has also been added, with the same options, and by default equal to `-addresstype`, to control which kind of change is used. A new `address_type` parameter has been added to the `getnewaddress` and `addmultisigaddress` RPCs to specify which type of address to generate. A `change_type` argument has been added to the `fundrawtransaction` RPC to override the `-changetype` argument for specific transactions. @@ -92,7 +92,7 @@ use the `replaceable` argument for individual transactions. ### Wallets directory configuration (`-walletdir`) -Bitcoin Core now has more flexibility in where the wallets directory can be +NYC3 now has more flexibility in where the wallets directory can be located. Previously wallet database files were stored at the top level of the bitcoin data directory. The behavior is now: @@ -112,7 +112,7 @@ becomes unavailable during operation, funds may be lost. Build: Minimum GCC bumped to 4.8.x ------------------------------------ -The minimum version of the GCC compiler required to compile Bitcoin Core is now 4.8. No effort will be +The minimum version of the GCC compiler required to compile NYC3 is now 4.8. No effort will be made to support older versions of GCC. See discussion in issue #11732 for more information. The minimum version for the Clang compiler is still 3.3. Other minimum dependency versions can be found in `doc/dependencies.md` in the repository. diff --git a/doc/release-notes/release-notes-0.16.1.md b/doc/release-notes/release-notes-0.16.1.md index d99361ae1..482a4e16f 100644 --- a/doc/release-notes/release-notes-0.16.1.md +++ b/doc/release-notes/release-notes-0.16.1.md @@ -1,4 +1,4 @@ -Bitcoin Core version 0.16.1 is now available from: +NYC3 version 0.16.1 is now available from: @@ -40,10 +40,10 @@ wallets that were created with older versions are not affected by this. Compatibility ============== -Bitcoin Core is extensively tested on multiple operating systems using +NYC3 is extensively tested on multiple operating systems using the Linux kernel, macOS 10.8+, and Windows Vista and later. Windows XP is not supported. -Bitcoin Core should also work on most other Unix-like systems but is not +NYC3 should also work on most other Unix-like systems but is not frequently tested on them. Notable changes diff --git a/doc/release-notes/release-notes-0.16.2.md b/doc/release-notes/release-notes-0.16.2.md index d549748d2..3858ff875 100644 --- a/doc/release-notes/release-notes-0.16.2.md +++ b/doc/release-notes/release-notes-0.16.2.md @@ -1,4 +1,4 @@ -Bitcoin Core version 0.16.2 is now available from: +NYC3 version 0.16.2 is now available from: @@ -40,10 +40,10 @@ wallets that were created with older versions are not affected by this. Compatibility ============== -Bitcoin Core is extensively tested on multiple operating systems using +NYC3 is extensively tested on multiple operating systems using the Linux kernel, macOS 10.8+, and Windows Vista and later. Windows XP is not supported. -Bitcoin Core should also work on most other Unix-like systems but is not +NYC3 should also work on most other Unix-like systems but is not frequently tested on them. 0.16.2 change log diff --git a/doc/release-notes/release-notes-0.16.3.md b/doc/release-notes/release-notes-0.16.3.md index 2e52d309c..09ec34ebf 100644 --- a/doc/release-notes/release-notes-0.16.3.md +++ b/doc/release-notes/release-notes-0.16.3.md @@ -1,4 +1,4 @@ -Bitcoin Core version 0.16.3 is now available from: +NYC3 version 0.16.3 is now available from: @@ -39,10 +39,10 @@ wallets that were created with older versions are not affected by this. Compatibility ============== -Bitcoin Core is extensively tested on multiple operating systems using +NYC3 is extensively tested on multiple operating systems using the Linux kernel, macOS 10.8+, and Windows Vista and later. Windows XP is not supported. -Bitcoin Core should also work on most other Unix-like systems but is not +NYC3 should also work on most other Unix-like systems but is not frequently tested on them. Notable changes @@ -52,7 +52,7 @@ Denial-of-Service vulnerability ------------------------------- A denial-of-service vulnerability (CVE-2018-17144) exploitable by miners has -been discovered in Bitcoin Core versions 0.14.0 up to 0.16.2. It is recommended +been discovered in NYC3 versions 0.14.0 up to 0.16.2. It is recommended to upgrade any of the vulnerable versions to 0.16.3 as soon as possible. 0.16.3 change log diff --git a/doc/release-notes/release-notes-0.17.0.1.md b/doc/release-notes/release-notes-0.17.0.1.md index 92db7dac7..b34d6e5e0 100644 --- a/doc/release-notes/release-notes-0.17.0.1.md +++ b/doc/release-notes/release-notes-0.17.0.1.md @@ -1,4 +1,4 @@ -Bitcoin Core version 0.17.0.1 is now available from: +NYC3 version 0.17.0.1 is now available from: diff --git a/doc/release-notes/release-notes-0.17.0.md b/doc/release-notes/release-notes-0.17.0.md index 418d7ba5f..df4c81da4 100644 --- a/doc/release-notes/release-notes-0.17.0.md +++ b/doc/release-notes/release-notes-0.17.0.md @@ -1,4 +1,4 @@ -Bitcoin Core version 0.17.0 is now available from: +NYC3 version 0.17.0 is now available from: @@ -46,10 +46,10 @@ processing the entire blockchain. Compatibility ============== -Bitcoin Core is extensively tested on multiple operating systems using +NYC3 is extensively tested on multiple operating systems using the Linux kernel, macOS 10.10+, and Windows 7 and newer (Windows XP is not supported). -Bitcoin Core should also work on most other Unix-like systems but is not +NYC3 should also work on most other Unix-like systems but is not frequently tested on them. From 0.17.0 onwards macOS <10.10 is no longer supported. 0.17.0 is built using Qt 5.9.x, which doesn't @@ -256,7 +256,7 @@ hardware implementations will typically implement multiple roles simultaneously. Upgrading non-HD wallets to HD wallets -------------------------------------- -Since Bitcoin Core 0.13.0, creating new BIP 32 Hierarchical Deterministic wallets has been supported by Bitcoin Core but old non-HD wallets could not be upgraded to HD. Now non-HD wallets can be upgraded to HD using the `-upgradewallet` command line option. This upgrade will result in the all keys in the keypool being marked as used and a new keypool generated. **A new backup must be made when this upgrade is performed.** +Since NYC3 0.13.0, creating new BIP 32 Hierarchical Deterministic wallets has been supported by NYC3 but old non-HD wallets could not be upgraded to HD. Now non-HD wallets can be upgraded to HD using the `-upgradewallet` command line option. This upgrade will result in the all keys in the keypool being marked as used and a new keypool generated. **A new backup must be made when this upgrade is performed.** Additionally, `-upgradewallet` can be used to upgraded from a non-split HD chain (all keys generated with `m/0'/0'/i'`) to a split HD chain (receiving keys generated with `'m/0'/0'/i'` and change keys generated with `m'/0'/1'/i'`). When this upgrade occurs, all keys already in the keypool will remain in the keypool to be used until all keys from before the upgrade are exhausted. This is to avoid issues with backups and downgrades when some keys may come from the change key keypool. Users can begin using the new split HD chain keypools by using the `newkeypool` RPC to mark all keys in the keypool as used and begin using a new keypool generated from the split HD chain. diff --git a/doc/release-notes/release-notes-0.17.1.md b/doc/release-notes/release-notes-0.17.1.md index b1e50e039..c38bdaa63 100644 --- a/doc/release-notes/release-notes-0.17.1.md +++ b/doc/release-notes/release-notes-0.17.1.md @@ -1,4 +1,4 @@ -Bitcoin Core version 0.17.1 is now available from: +NYC3 version 0.17.1 is now available from: @@ -50,10 +50,10 @@ processing the entire blockchain. Compatibility ============== -Bitcoin Core is extensively tested on multiple operating systems using +NYC3 is extensively tested on multiple operating systems using the Linux kernel, macOS 10.10+, and Windows 7 and newer (Windows XP is not supported). -Bitcoin Core should also work on most other Unix-like systems but is not +NYC3 should also work on most other Unix-like systems but is not frequently tested on them. From 0.17.0 onwards macOS <10.10 is no longer supported. 0.17.0 is built using Qt 5.9.x, which doesn't diff --git a/doc/release-notes/release-notes-0.9.0.md b/doc/release-notes/release-notes-0.9.0.md index 170410ca4..0f14d89e8 100644 --- a/doc/release-notes/release-notes-0.9.0.md +++ b/doc/release-notes/release-notes-0.9.0.md @@ -1,4 +1,4 @@ -Bitcoin Core version 0.9.0 is now available from: +NYC3 version 0.9.0 is now available from: https://bitcoin.org/bin/0.9.0/ @@ -59,11 +59,11 @@ Also, the first time you run a 0.8.x release on a 0.9 wallet it will rescan the blockchain for missing spent coins, which will take a long time (tens of minutes on a typical machine). -Rebranding to Bitcoin Core +Rebranding to NYC3 --------------------------- To reduce confusion between Bitcoin-the-network and Bitcoin-the-software we -have renamed the reference client to Bitcoin Core. +have renamed the reference client to NYC3. OP_RETURN and data in the block chain @@ -295,7 +295,7 @@ GUI: - Add Coin Control Features - Improve receive coins workflow: make the 'Receive' tab into a form to request payments, and move historical address list functionality to File menu. -- Rebrand to `Bitcoin Core` +- Rebrand to `NYC3` - Move initialization/shutdown to a thread. This prevents "Not responding" messages during startup. Also show a window during shutdown. - Don't regenerate autostart link on every client startup diff --git a/doc/release-notes/release-notes-0.9.1.md b/doc/release-notes/release-notes-0.9.1.md index 0552053d2..cb3e3445a 100644 --- a/doc/release-notes/release-notes-0.9.1.md +++ b/doc/release-notes/release-notes-0.9.1.md @@ -1,4 +1,4 @@ -Bitcoin Core version 0.9.1 is now available from: +NYC3 version 0.9.1 is now available from: https://bitcoin.org/bin/0.9.1/ @@ -33,7 +33,7 @@ If you are upgrading from version 0.7.2 or earlier, the first time you run No code changes were made between 0.9.0 and 0.9.1. Only the dependencies were changed. - Upgrade OpenSSL to 1.0.1g. This release fixes the following vulnerabilities which can - affect the Bitcoin Core software: + affect the NYC3 software: - CVE-2014-0160 ("heartbleed") A missing bounds check in the handling of the TLS heartbeat extension can diff --git a/doc/release-notes/release-notes-0.9.2.1.md b/doc/release-notes/release-notes-0.9.2.1.md index 3168ad1a5..a1333948a 100644 --- a/doc/release-notes/release-notes-0.9.2.1.md +++ b/doc/release-notes/release-notes-0.9.2.1.md @@ -1,4 +1,4 @@ -Bitcoin Core version 0.9.2.1 is now available from: +NYC3 version 0.9.2.1 is now available from: https://bitcoin.org/bin/0.9.2.1/ diff --git a/doc/release-notes/release-notes-0.9.2.md b/doc/release-notes/release-notes-0.9.2.md index a2749e549..811dfdf5d 100644 --- a/doc/release-notes/release-notes-0.9.2.md +++ b/doc/release-notes/release-notes-0.9.2.md @@ -1,4 +1,4 @@ -Bitcoin Core version 0.9.2 is now available from: +NYC3 version 0.9.2 is now available from: https://bitcoin.org/bin/0.9.2/ diff --git a/doc/release-notes/release-notes-0.9.3.md b/doc/release-notes/release-notes-0.9.3.md index 0765a360b..b8566bfbd 100644 --- a/doc/release-notes/release-notes-0.9.3.md +++ b/doc/release-notes/release-notes-0.9.3.md @@ -1,4 +1,4 @@ -Bitcoin Core version 0.9.3 is now available from: +NYC3 version 0.9.3 is now available from: https://bitcoin.org/bin/0.9.3/ @@ -70,7 +70,7 @@ GUI: Miscellaneous: - key.cpp: fail with a friendlier message on missing ssl EC support - Remove bignum dependency for scripts -- Upgrade OpenSSL to 1.0.1i (see https://www.openssl.org/news/secadv_20140806.txt - just to be sure, no critical issues for Bitcoin Core) +- Upgrade OpenSSL to 1.0.1i (see https://www.openssl.org/news/secadv_20140806.txt - just to be sure, no critical issues for NYC3) - Upgrade miniupnpc to 1.9.20140701 - Fix boost detection in build system on some platforms diff --git a/doc/release-notes/release-notes-0.9.4.md b/doc/release-notes/release-notes-0.9.4.md index 7ee73246a..bf26e1676 100644 --- a/doc/release-notes/release-notes-0.9.4.md +++ b/doc/release-notes/release-notes-0.9.4.md @@ -1,4 +1,4 @@ -Bitcoin Core version 0.9.4 is now available from: +NYC3 version 0.9.4 is now available from: https://bitcoin.org/bin/0.9.4/ @@ -25,15 +25,15 @@ various operating system maintainers. Review by Gregory Maxwell determined that this update is incompatible with the Bitcoin system and could lead to consensus forks. -Bitcoin Core released binaries from https://bitcoin.org are unaffected, +NYC3 released binaries from https://bitcoin.org are unaffected, as are any built with the gitian deterministic build system. However, if you are running either - The Ubuntu PPA from https://launchpad.net/~bitcoin/+archive/ubuntu/bitcoin -- A third-party or self-compiled Bitcoin Core +- A third-party or self-compiled NYC3 -upgrade to Bitcoin Core 0.9.4, which includes a workaround, **before** updating +upgrade to NYC3 0.9.4, which includes a workaround, **before** updating OpenSSL. The incompatibility is due to the OpenSSL update changing the diff --git a/doc/release-notes/release-notes-0.9.5.md b/doc/release-notes/release-notes-0.9.5.md index bed0af987..b035fc3b3 100644 --- a/doc/release-notes/release-notes-0.9.5.md +++ b/doc/release-notes/release-notes-0.9.5.md @@ -1,4 +1,4 @@ -Bitcoin Core version 0.9.5 is now available from: +NYC3 version 0.9.5 is now available from: https://bitcoin.org/bin/0.9.5/ @@ -24,7 +24,7 @@ Notable changes Mining and relay policy enhancements ------------------------------------ -Bitcoin Core's block templates are now for version 3 blocks only, and any mining +NYC3's block templates are now for version 3 blocks only, and any mining software relying on its `getblocktemplate` must be updated in parallel to use libblkmaker either version 0.4.2 or any version from 0.5.1 onward. If you are solo mining, this will affect you the moment you upgrade Bitcoin diff --git a/doc/release-process.md b/doc/release-process.md index eb1f5ad22..2ac0cc9af 100644 --- a/doc/release-process.md +++ b/doc/release-process.md @@ -114,7 +114,7 @@ NOTE: Offline builds must use the --url flag to ensure Gitian fetches only from The gbuild invocations below DO NOT DO THIS by default. -### Build and sign Bitcoin Core for Linux, Windows, and macOS: +### Build and sign NYC3 for Linux, Windows, and macOS: pushd ./gitian-builder ./bin/gbuild --num-make 2 --memory 3000 --commit bitcoin=v${VERSION} ../bitcoin/contrib/gitian-descriptors/gitian-linux.yml @@ -329,7 +329,7 @@ bitcoin.org (see below for bitcoin.org update instructions). - bitcoin-dev and bitcoin-core-dev mailing list - - Bitcoin Core announcements list https://bitcoincore.org/en/list/announcements/join/ + - NYC3 announcements list https://bitcoincore.org/en/list/announcements/join/ - Update title of #bitcoin on Freenode IRC diff --git a/doc/tor.md b/doc/tor.md index cfb7f1666..6d335a55f 100644 --- a/doc/tor.md +++ b/doc/tor.md @@ -1,14 +1,14 @@ # TOR SUPPORT IN BITCOIN -It is possible to run Bitcoin Core as a Tor hidden service, and connect to such services. +It is possible to run NYC3 as a Tor hidden service, and connect to such services. The following directions assume you have a Tor proxy running on port 9050. Many distributions default to having a SOCKS proxy listening on port 9050, but others may not. In particular, the Tor Browser Bundle defaults to listening on port 9150. See [Tor Project FAQ:TBBSocksPort](https://www.torproject.org/docs/faq.html.en#TBBSocksPort) for how to properly configure Tor. -## 1. Run Bitcoin Core behind a Tor proxy +## 1. Run NYC3 behind a Tor proxy -The first step is running Bitcoin Core behind a Tor proxy. This will already anonymize all +The first step is running NYC3 behind a Tor proxy. This will already anonymize all outgoing connections, but more is possible. -proxy=ip:port Set the proxy server. If SOCKS5 is selected (default), this proxy @@ -37,7 +37,7 @@ In a typical situation, this suffices to run behind a Tor proxy: ./bitcoind -proxy=127.0.0.1:9050 -## 2. Run a Bitcoin Core hidden server +## 2. Run a NYC3 hidden server If you configure your Tor system accordingly, it is possible to make your node also reachable from the Tor network. Add these lines to your /etc/tor/torrc (or equivalent @@ -95,13 +95,13 @@ for normal IPv4/IPv6 communication, use: Starting with Tor version 0.2.7.1 it is possible, through Tor's control socket API, to create and destroy 'ephemeral' hidden services programmatically. -Bitcoin Core has been updated to make use of this. +NYC3 has been updated to make use of this. This means that if Tor is running (and proper authentication has been configured), -Bitcoin Core automatically creates a hidden service to listen on. This will positively +NYC3 automatically creates a hidden service to listen on. This will positively affect the number of available .onion nodes. -This new feature is enabled by default if Bitcoin Core is listening (`-listen`), and +This new feature is enabled by default if NYC3 is listening (`-listen`), and requires a Tor connection to work. It can be explicitly disabled with `-listenonion=0` and, if not disabled, configured using the `-torcontrol` and `-torpassword` settings. To show verbose debugging information, pass `-debug=tor`. @@ -124,7 +124,7 @@ in the tor configuration file. The hashed password can be obtained with the comm ## 4. Privacy recommendations -- Do not add anything but Bitcoin Core ports to the hidden service created in section 2. +- Do not add anything but NYC3 ports to the hidden service created in section 2. If you run a web service too, create a new hidden service for that. Otherwise it is trivial to link them, which may reduce privacy. Hidden services created automatically (as in section 3) always have only one port diff --git a/doc/translation_strings_policy.md b/doc/translation_strings_policy.md index 634aca355..377c1a994 100644 --- a/doc/translation_strings_policy.md +++ b/doc/translation_strings_policy.md @@ -1,7 +1,7 @@ Translation Strings Policy =========================== -This document provides guidelines for internationalization of the Bitcoin Core software. +This document provides guidelines for internationalization of the NYC3 software. How to translate? ------------------ diff --git a/doc/travis-ci.md b/doc/travis-ci.md index 38085cec3..51622aeeb 100644 --- a/doc/travis-ci.md +++ b/doc/travis-ci.md @@ -32,7 +32,7 @@ trigger cache-invalidation and rebuilds as necessary. These caches can be manually removed if necessary. This is one of the very few manual operations that is possible with Travis, and it can be done by the -Bitcoin Core committer via the Travis web interface. +NYC3 committer via the Travis web interface. In some cases, secure strings may be needed for hiding sensitive info such as private keys or URLs. The travis client may be used to create these strings: diff --git a/doc/zmq.md b/doc/zmq.md index 7ffc5623b..44ebd9e2c 100644 --- a/doc/zmq.md +++ b/doc/zmq.md @@ -5,7 +5,7 @@ connections, inter-process communication, and shared-memory, providing various message-oriented semantics such as publish/subscribe, request/reply, and push/pull. -The Bitcoin Core daemon can be configured to act as a trusted "border +The NYC3 daemon can be configured to act as a trusted "border router", implementing the bitcoin wire protocol and relay, making consensus decisions, maintaining the local blockchain database, broadcasting locally generated transactions into the network, and @@ -33,7 +33,7 @@ buffering or reassembly. ## Prerequisites -The ZeroMQ feature in Bitcoin Core requires the ZeroMQ API >= 4.0.0 +The ZeroMQ feature in NYC3 requires the ZeroMQ API >= 4.0.0 [libzmq](https://github.com/zeromq/libzmq/releases). For version information, see [dependencies.md](dependencies.md). Typically, it is packaged by distributions as something like diff --git a/src/init.cpp b/src/init.cpp index d00cf5138..e7b24895a 100644 --- a/src/init.cpp +++ b/src/init.cpp @@ -556,14 +556,12 @@ void SetupServerArgs() std::string LicenseInfo() { - const std::string URL_SOURCE_CODE = ""; - const std::string URL_WEBSITE = ""; + const std::string URL_SOURCE_CODE = ""; return CopyrightHolders(strprintf(_("Copyright (C) %i-%i"), 2009, COPYRIGHT_YEAR) + " ") + "\n" + "\n" + - strprintf(_("Please contribute if you find %s useful. " - "Visit %s for further information about the software."), - PACKAGE_NAME, URL_WEBSITE) + + strprintf(_("Please contribute if you find %s useful. "), + PACKAGE_NAME) + "\n" + strprintf(_("The source code is available from %s."), URL_SOURCE_CODE) + diff --git a/src/nyc3-wallet.cpp b/src/nyc3-wallet.cpp index 32a539aac..515d44d17 100644 --- a/src/nyc3-wallet.cpp +++ b/src/nyc3-wallet.cpp @@ -42,7 +42,7 @@ static bool WalletAppInit(int argc, char* argv[]) } if (argc < 2 || HelpRequested(gArgs)) { std::string usage = strprintf("%s bitcoin-wallet version", PACKAGE_NAME) + " " + FormatFullVersion() + "\n\n" + - "wallet-tool is an offline tool for creating and interacting with Bitcoin Core wallet files.\n" + + "wallet-tool is an offline tool for creating and interacting with NYC3 wallet files.\n" + "By default wallet-tool will act on wallets in the default mainnet wallet directory in the datadir.\n" + "To change the target wallet, use the -datadir, -wallet and -testnet/-regtest arguments.\n\n" + "Usage:\n" + diff --git a/src/protocol.h b/src/protocol.h index a790a0690..43dee2be9 100644 --- a/src/protocol.h +++ b/src/protocol.h @@ -248,14 +248,14 @@ enum ServiceFlags : uint64_t { // Nothing NODE_NONE = 0, // NODE_NETWORK means that the node is capable of serving the complete block chain. It is currently - // set by all Bitcoin Core non pruned nodes, and is unset by SPV clients or other light clients. + // set by all NYC3 non pruned nodes, and is unset by SPV clients or other light clients. NODE_NETWORK = (1 << 0), // NODE_GETUTXO means the node is capable of responding to the getutxo protocol request. - // Bitcoin Core does not support this but a patch set called Bitcoin XT does. + // NYC3 does not support this but a patch set called Bitcoin XT does. // See BIP 64 for details on how this is implemented. NODE_GETUTXO = (1 << 1), // NODE_BLOOM means the node is capable and willing to handle bloom-filtered connections. - // Bitcoin Core nodes used to support this by default, without advertising this bit, + // NYC3 nodes used to support this by default, without advertising this bit, // but no longer do as of protocol version 70011 (= NO_BLOOM_VERSION) NODE_BLOOM = (1 << 2), // NODE_WITNESS indicates that a node can be asked for blocks and transactions including diff --git a/src/qt/addresstablemodel.h b/src/qt/addresstablemodel.h index 035f3e057..94c9dc4f8 100644 --- a/src/qt/addresstablemodel.h +++ b/src/qt/addresstablemodel.h @@ -30,7 +30,7 @@ public: enum ColumnIndex { Label = 0, /**< User specified label */ - Address = 1 /**< Bitcoin address */ + Address = 1 /**< NYC3 address */ }; enum RoleIndex { diff --git a/src/qt/editaddressdialog.cpp b/src/qt/editaddressdialog.cpp index 4711412ac..2fc174be5 100644 --- a/src/qt/editaddressdialog.cpp +++ b/src/qt/editaddressdialog.cpp @@ -108,7 +108,7 @@ void EditAddressDialog::accept() break; case AddressTableModel::INVALID_ADDRESS: QMessageBox::warning(this, windowTitle(), - tr("The entered address \"%1\" is not a valid Bitcoin address.").arg(ui->addressEdit->text()), + tr("The entered address \"%1\" is not a valid NYC3 address.").arg(ui->addressEdit->text()), QMessageBox::Ok, QMessageBox::Ok); break; case AddressTableModel::DUPLICATE_ADDRESS: diff --git a/src/qt/forms/sendcoinsentry.ui b/src/qt/forms/sendcoinsentry.ui index 7ed8f0ac4..6c750c985 100644 --- a/src/qt/forms/sendcoinsentry.ui +++ b/src/qt/forms/sendcoinsentry.ui @@ -57,7 +57,7 @@ - The Bitcoin address to send the payment to + The NYC3 address to send the payment to diff --git a/src/qt/forms/signverifymessagedialog.ui b/src/qt/forms/signverifymessagedialog.ui index c9ddd757c..6a44b25e8 100644 --- a/src/qt/forms/signverifymessagedialog.ui +++ b/src/qt/forms/signverifymessagedialog.ui @@ -48,7 +48,7 @@ - The Bitcoin address to sign the message with + The NYC3 address to sign the message with @@ -152,7 +152,7 @@ - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address Sign &Message @@ -258,7 +258,7 @@ - The Bitcoin address the message was signed with + The NYC3 address the message was signed with @@ -295,7 +295,7 @@ - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address Verify &Message diff --git a/src/qt/guiutil.cpp b/src/qt/guiutil.cpp index 79116c32c..2c355ca29 100644 --- a/src/qt/guiutil.cpp +++ b/src/qt/guiutil.cpp @@ -104,7 +104,7 @@ void setupAddressWidget(QValidatedLineEdit *widget, QWidget *parent) widget->setFont(fixedPitchFont()); // We don't want translators to use own addresses in translations // and this is the only place, where this address is supplied. - widget->setPlaceholderText(QObject::tr("Enter a Bitcoin address (e.g. %1)").arg( + widget->setPlaceholderText(QObject::tr("Enter a NYC3 address (e.g. %1)").arg( QString::fromStdString(DummyAddress(Params())))); widget->setValidator(new BitcoinAddressEntryValidator(parent)); widget->setCheckValidator(new BitcoinAddressCheckValidator(parent)); diff --git a/src/qt/locale/nyc3_af.ts b/src/qt/locale/nyc3_af.ts index 304cb9d63..e95796eee 100644 --- a/src/qt/locale/nyc3_af.ts +++ b/src/qt/locale/nyc3_af.ts @@ -322,7 +322,7 @@ Besig met herindeksering van blokke op hardeskyf... - Send coins to a Bitcoin address + Send coins to a NYC3 address Stuur munte na 'n Bitcoin adres @@ -694,7 +694,7 @@ Wysig stuur adres - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. Die ingevoerde adres "%1" is nie 'n geldige Bitcoin adres nie. @@ -1120,7 +1120,7 @@ Bedrag - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) Voer in 'n Bitcoin adres (bv. %1) @@ -1697,7 +1697,7 @@ transaksievertragingsrisiko. Betalings versoek verstryk. - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address Waarskuwing: Ongeldige Bitcoinadres @@ -1730,7 +1730,7 @@ Is u seker? Hierdie is 'n gewone betaling - The Bitcoin address to send the payment to + The NYC3 address to send the payment to Die Bitcoinadres waarheen die betaling gestuur word @@ -2039,7 +2039,7 @@ word die fooi eweredig verdeel. bitcoin-core - Bitcoin Core + NYC3 Bitcoin Kern diff --git a/src/qt/locale/nyc3_af_ZA.ts b/src/qt/locale/nyc3_af_ZA.ts index 58f04df00..5bb0b0c2e 100644 --- a/src/qt/locale/nyc3_af_ZA.ts +++ b/src/qt/locale/nyc3_af_ZA.ts @@ -326,7 +326,7 @@ Herindekseer blokke op skyf... - Send coins to a Bitcoin address + Send coins to a NYC3 address Stuur muntstukke na 'n Bitcoin adres @@ -718,7 +718,7 @@ Wysig stuurende adres - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. Die ingeskrewe adres "%1" is nie 'n geldige Bitcoin adres nie. diff --git a/src/qt/locale/nyc3_ar.ts b/src/qt/locale/nyc3_ar.ts index 662448993..8fc691234 100644 --- a/src/qt/locale/nyc3_ar.ts +++ b/src/qt/locale/nyc3_ar.ts @@ -334,7 +334,7 @@ إعادة فهرسة الكتل على القرص ... - Send coins to a Bitcoin address + Send coins to a NYC3 address ارسل عملات الى عنوان بيتكوين @@ -744,7 +744,7 @@ تعديل عنوان الارسال - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. العنوان المدخل "%1" ليس عنوان بيت كوين صحيح. @@ -1248,7 +1248,7 @@ عنوان الدفع غير صالح %1 - URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. + URI cannot be parsed! This can be caused by an invalid NYC3 address or malformed URI parameters. لا يمكن تحليل العنوان (URI)! يمكن أن يحدث هذا بسبب عنوان بتكوين غير صالح أو معلمات عنوان (URI) غير صحيحة. @@ -1350,7 +1350,7 @@ مبلغ - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) ادخل عنوان محفطة البتكوين (مثال %1) @@ -2127,7 +2127,7 @@ انتهاء صلاحية طلب الدفع. - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address تحذير: عنوان بتكوين غير صالح @@ -2166,7 +2166,7 @@ هذا دفع اعتيادي - The Bitcoin address to send the payment to + The NYC3 address to send the payment to عنوان البت كوين المرسل اليه الدفع @@ -2259,7 +2259,7 @@ &توقيع الرسالة - The Bitcoin address to sign the message with + The NYC3 address to sign the message with عنوان البتكوين لتوقيع الرسالة به @@ -2291,7 +2291,7 @@ نسخ التوقيع الحالي إلى حافظة النظام - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address وقع الرسالة لتثبت انك تمتلك عنوان البت كوين هذا @@ -2311,11 +2311,11 @@ &تحقق رسالة - The Bitcoin address the message was signed with + The NYC3 address the message was signed with عنوان البتكوين الذي تم توقيع الرسالة به - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address تحقق من الرسالة للتأكد من توقيعها مع عنوان البتكوين المحدد @@ -2911,7 +2911,7 @@ غير قادر على بدء خادم ال HTTP. راجع سجل تصحيح الأخطاء للحصول على التفاصيل. - Bitcoin Core + NYC3 جوهر بيتكوين diff --git a/src/qt/locale/nyc3_be_BY.ts b/src/qt/locale/nyc3_be_BY.ts index 5bbb567a2..c87544eb1 100644 --- a/src/qt/locale/nyc3_be_BY.ts +++ b/src/qt/locale/nyc3_be_BY.ts @@ -290,7 +290,7 @@ Пераіндэксацыя блокаў на дыску... - Send coins to a Bitcoin address + Send coins to a NYC3 address Даслаць манеты на Біткойн-адрас @@ -1209,8 +1209,8 @@ bitcoin-core - Bitcoin Core - Bitcoin Core + NYC3 + NYC3 Do you want to rebuild the block database now? diff --git a/src/qt/locale/nyc3_bg.ts b/src/qt/locale/nyc3_bg.ts index e8739a26a..6948c9b9d 100644 --- a/src/qt/locale/nyc3_bg.ts +++ b/src/qt/locale/nyc3_bg.ts @@ -334,7 +334,7 @@ Повторно индексиране на блоковете на диска... - Send coins to a Bitcoin address + Send coins to a NYC3 address Изпращане към Биткоин адрес @@ -718,7 +718,7 @@ Редактиране на адрес за изпращане - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. "%1" не е валиден Биткоин адрес. @@ -1160,7 +1160,7 @@ Сума - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) Въведете Биткойн адрес (например: %1) @@ -1701,7 +1701,7 @@ Заявката за плащане е изтекла. - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address Внимание: Невалиден Биткойн адрес @@ -1821,7 +1821,7 @@ Копиране на текущия подпис - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address Подпишете съобщение като доказателство, че притежавате определен адрес @@ -1837,7 +1837,7 @@ &Провери - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address Проверете съобщение, за да сте сигурни че е подписано с определен Биткоин адрес @@ -2329,7 +2329,7 @@ bitcoin-core - Bitcoin Core + NYC3 Биткойн ядро diff --git a/src/qt/locale/nyc3_bg_BG.ts b/src/qt/locale/nyc3_bg_BG.ts index 41f4c5cb2..a26ef0ab7 100644 --- a/src/qt/locale/nyc3_bg_BG.ts +++ b/src/qt/locale/nyc3_bg_BG.ts @@ -881,7 +881,7 @@ bitcoin-core - Bitcoin Core + NYC3 Биткойн ядро diff --git a/src/qt/locale/nyc3_ca.ts b/src/qt/locale/nyc3_ca.ts index 830087fe6..dd658438f 100644 --- a/src/qt/locale/nyc3_ca.ts +++ b/src/qt/locale/nyc3_ca.ts @@ -338,7 +338,7 @@ El servidor proxy està <b>activat</b>: %1 - Send coins to a Bitcoin address + Send coins to a NYC3 address Envia monedes a una adreça Bitcoin @@ -744,7 +744,7 @@ Edita l'adreça d'enviament - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. L'adreça introduïda «%1» no és una adreça de Bitcoin vàlida. @@ -1308,7 +1308,7 @@ Adreça de pagament no vàlida %1 - URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. + URI cannot be parsed! This can be caused by an invalid NYC3 address or malformed URI parameters. L'URI no pot ser analitzat! Això pot ser a causa d'una adreça de Bitcoin no vàlida o per paràmetres URI amb mal format. @@ -1410,7 +1410,7 @@ Import - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) Introduïu una adreça de Bitcoin (p. ex. %1) @@ -2231,7 +2231,7 @@ Nota: Com que la comissió es calcula en funció dels bytes, una comissió de "1 La sol·licitud de pagament ha vençut. - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address Avís: adreça Bitcoin no vàlida @@ -2274,7 +2274,7 @@ Nota: Com que la comissió es calcula en funció dels bytes, una comissió de "1 Això és un pagament normal. - The Bitcoin address to send the payment to + The NYC3 address to send the payment to L'adreça Bitcoin on enviar el pagament @@ -2367,7 +2367,7 @@ Nota: Com que la comissió es calcula en funció dels bytes, una comissió de "1 Podeu signar missatges/acords amb les vostres adreces per provar que rebeu les bitcoins que s'hi envien. Aneu amb compte no signar res que sigui vague o aleatori, perquè en alguns atacs de suplantació es pot provar que hi signeu la vostra identitat. Només signeu aquelles declaracions completament detallades en què hi esteu d'acord. - The Bitcoin address to sign the message with + The NYC3 address to sign the message with L'adreça Bitcoin amb què signar el missatge @@ -2399,7 +2399,7 @@ Nota: Com que la comissió es calcula en funció dels bytes, una comissió de "1 Copia la signatura actual al porta-retalls del sistema - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address Signa el missatge per provar que ets propietari d'aquesta adreça Bitcoin @@ -2423,11 +2423,11 @@ Nota: Com que la comissió es calcula en funció dels bytes, una comissió de "1 Introduïu l'adreça del receptor, el missatge (assegureu-vos de copiar els salts de línia, espais, tabuladors, etc. exactament) i signatura de sota per verificar el missatge. Tingueu cura de no llegir més en la signatura del que està al missatge signat, per evitar ser enganyat per un atac d'home-en-el-mig. Tingueu en compte que això només demostra que la part que signa rep amb l'adreça, i no es pot provar l'enviament de qualsevol transacció! - The Bitcoin address the message was signed with + The NYC3 address the message was signed with L'adreça Bitcoin amb què va ser signat el missatge - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address Verificar el missatge per assegurar-se que ha estat signat amb una adreça Bitcoin específica @@ -3059,8 +3059,8 @@ Nota: Com que la comissió es calcula en funció dels bytes, una comissió de "1 No s'ha pogut iniciar el servidor HTTP. Vegeu debug.log per a més detalls. - Bitcoin Core - Bitcoin Core + NYC3 + NYC3 The %s developers diff --git a/src/qt/locale/nyc3_ca@valencia.ts b/src/qt/locale/nyc3_ca@valencia.ts index dfc871fb3..ba833b4f5 100644 --- a/src/qt/locale/nyc3_ca@valencia.ts +++ b/src/qt/locale/nyc3_ca@valencia.ts @@ -290,7 +290,7 @@ S'estan reindexant els blocs al disc... - Send coins to a Bitcoin address + Send coins to a NYC3 address Envia monedes a una adreça Bitcoin @@ -650,7 +650,7 @@ Edita les adreces d'enviament - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. L'adreça introduïda «%1» no és una adreça de Bitcoin vàlida. @@ -1034,7 +1034,7 @@ Adreça de pagament no vàlida %1 - URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. + URI cannot be parsed! This can be caused by an invalid NYC3 address or malformed URI parameters. L'URI no pot ser analitzat! Això pot ser a causa d'una adreça de Bitcoin no vàlida o per paràmetres URI amb mal format. @@ -1128,7 +1128,7 @@ Import - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) Introduïu una adreça de Bitcoin (p. ex. %1) @@ -1737,7 +1737,7 @@ La sol·licitud de pagament ha vençut. - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address Avís: adreça Bitcoin no vàlida @@ -1772,7 +1772,7 @@ Això és un pagament normal. - The Bitcoin address to send the payment to + The NYC3 address to send the payment to L'adreça Bitcoin on enviar el pagament @@ -1861,7 +1861,7 @@ Podeu signar missatges/acords amb les vostres adreces per provar que rebeu les bitcoins que s'hi envien. Aneu amb compte no signar res que siga vague o aleatori, perquè en alguns atacs de suplantació es pot provar que hi signeu la vostra identitat. Només signeu aquelles declaracions completament detallades en què hi esteu d'acord. - The Bitcoin address to sign the message with + The NYC3 address to sign the message with L'adreça Bitcoin amb què signar el missatge @@ -1893,7 +1893,7 @@ Copia la signatura actual al porta-retalls del sistema - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address Signa el missatge per provar que ets propietari d'esta adreça Bitcoin @@ -1917,11 +1917,11 @@ Introduïu l'adreça del receptor, el missatge (assegureu-vos de copiar els salts de línia, espais, tabuladors, etc. exactament) i signatura de sota per verificar el missatge. Tingueu cura de no llegir més en la signatura del que està al missatge signat, per evitar ser enganyat per un atac d'home-en-el-mig. Tingueu en compte que això només demostra que la part que signa rep amb l'adreça, i no es pot provar l'enviament de qualsevol transacció! - The Bitcoin address the message was signed with + The NYC3 address the message was signed with L'adreça Bitcoin amb què va ser signat el missatge - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address Verificar el missatge per assegurar-se que ha estat signat amb una adreça Bitcoin específica @@ -2441,8 +2441,8 @@ S'està podant l'emmagatzemament de blocs... - Bitcoin Core - Bitcoin Core + NYC3 + NYC3 This is a pre-release test build - use at your own risk - do not use for mining or merchant applications diff --git a/src/qt/locale/nyc3_ca_ES.ts b/src/qt/locale/nyc3_ca_ES.ts index 8dbcd6f95..2a3ba06d1 100644 --- a/src/qt/locale/nyc3_ca_ES.ts +++ b/src/qt/locale/nyc3_ca_ES.ts @@ -326,7 +326,7 @@ S'estan reindexant els blocs al disc... - Send coins to a Bitcoin address + Send coins to a NYC3 address Envia monedes a una adreça Bitcoin @@ -722,7 +722,7 @@ Edita l'adreça d'enviament - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. L'adreça introduïda «%1» no és una adreça de Bitcoin vàlida. @@ -1186,7 +1186,7 @@ Adreça de pagament no vàlida %1 - URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. + URI cannot be parsed! This can be caused by an invalid NYC3 address or malformed URI parameters. L'URI no pot ser analitzat! Això pot ser a causa d'una adreça de Bitcoin no vàlida o per paràmetres URI amb mal format. @@ -1280,7 +1280,7 @@ Import - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) Introduïu una adreça de Bitcoin (p. ex. %1) @@ -1969,7 +1969,7 @@ La sol·licitud de pagament ha vençut. - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address Avís: adreça Bitcoin no vàlida @@ -2004,7 +2004,7 @@ Això és un pagament normal. - The Bitcoin address to send the payment to + The NYC3 address to send the payment to L'adreça Bitcoin on enviar el pagament @@ -2093,7 +2093,7 @@ Podeu signar missatges/acords amb les vostres adreces per provar que rebeu les bitcoins que s'hi envien. Aneu amb compte no signar res que sigui vague o aleatori, perquè en alguns atacs de suplantació es pot provar que hi signeu la vostra identitat. Només signeu aquelles declaracions completament detallades en què hi esteu d'acord. - The Bitcoin address to sign the message with + The NYC3 address to sign the message with L'adreça Bitcoin amb què signar el missatge @@ -2125,7 +2125,7 @@ Copia la signatura actual al porta-retalls del sistema - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address Signa el missatge per provar que ets propietari d'aquesta adreça Bitcoin @@ -2149,11 +2149,11 @@ Introduïu l'adreça del receptor, el missatge (assegureu-vos de copiar els salts de línia, espais, tabuladors, etc. exactament) i signatura de sota per verificar el missatge. Tingueu cura de no llegir més en la signatura del que està al missatge signat, per evitar ser enganyat per un atac d'home-en-el-mig. Tingueu en compte que això només demostra que la part que signa rep amb l'adreça, i no es pot provar l'enviament de qualsevol transacció! - The Bitcoin address the message was signed with + The NYC3 address the message was signed with L'adreça Bitcoin amb què va ser signat el missatge - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address Verificar el missatge per assegurar-se que ha estat signat amb una adreça Bitcoin específica @@ -2709,8 +2709,8 @@ No s'ha pogut iniciar el servidor HTTP. Vegeu debug.log per a més detalls. - Bitcoin Core - Bitcoin Core + NYC3 + NYC3 This is a pre-release test build - use at your own risk - do not use for mining or merchant applications diff --git a/src/qt/locale/nyc3_cs.ts b/src/qt/locale/nyc3_cs.ts index afa63f01d..7557636ad 100644 --- a/src/qt/locale/nyc3_cs.ts +++ b/src/qt/locale/nyc3_cs.ts @@ -342,7 +342,7 @@ Proxy je <b>zapnutá</b>: %1 - Send coins to a Bitcoin address + Send coins to a NYC3 address Pošli mince na bitcoinovou adresu @@ -804,7 +804,7 @@ Uprav odesílací adresu - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. Zadaná adresa „%1“ není platná bitcoinová adresa. @@ -1396,7 +1396,7 @@ Neplatná platební adresa %1 - URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. + URI cannot be parsed! This can be caused by an invalid NYC3 address or malformed URI parameters. Nepodařilo se analyzovat URI! Důvodem může být neplatná bitcoinová adresa nebo poškozené parametry URI. @@ -1498,7 +1498,7 @@ Částka - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) Zadej bitcoinovou adresu (např. %1) @@ -2383,7 +2383,7 @@ Poznámka: Jelikož je poplatek počítaný za bajt, poplatek o hodnotě "100 sa Potvrzování by podle odhadu mělo začít během %n bloku.Potvrzování by podle odhadu mělo začít během %n bloků.Potvrzování by podle odhadu mělo začít během %n bloků.Potvrzování by podle odhadu mělo začít během %n bloků. - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address Upozornění: Neplatná bitcoinová adresa @@ -2426,7 +2426,7 @@ Poznámka: Jelikož je poplatek počítaný za bajt, poplatek o hodnotě "100 sa Tohle je normální platba. - The Bitcoin address to send the payment to + The NYC3 address to send the payment to Bitcoinová adresa příjemce @@ -2523,7 +2523,7 @@ Poznámka: Jelikož je poplatek počítaný za bajt, poplatek o hodnotě "100 sa Podepsáním zprávy/smlouvy svými adresami můžeš prokázat, že jsi na ně schopen přijmout bitcoiny. Buď opatrný a nepodepisuj nic vágního nebo náhodného; například při phishingových útocích můžeš být lákán, abys něco takového podepsal. Podepisuj pouze naprosto úplná a detailní prohlášení, se kterými souhlasíš. - The Bitcoin address to sign the message with + The NYC3 address to sign the message with Bitcoinová adresa, kterou se zpráva podepíše @@ -2555,7 +2555,7 @@ Poznámka: Jelikož je poplatek počítaný za bajt, poplatek o hodnotě "100 sa Zkopíruj tento podpis do schránky - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address Podepiš zprávu, čímž prokážeš, že jsi vlastníkem této bitcoinové adresy @@ -2579,11 +2579,11 @@ Poznámka: Jelikož je poplatek počítaný za bajt, poplatek o hodnotě "100 sa K ověření podpisu zprávy zadej adresu příjemce, zprávu (ověř si, že správně kopíruješ zalomení řádků, mezery, tabulátory apod.) a podpis. Dávej pozor na to, abys nezkopíroval do podpisu víc, než co je v samotné podepsané zprávě, abys nebyl napálen man-in-the-middle útokem. Poznamenejme však, že takto lze pouze prokázat, že podepisující je schopný na dané adrese přijmout platbu, ale není možnéprokázat, že odeslal jakoukoli transakci! - The Bitcoin address the message was signed with + The NYC3 address the message was signed with Bitcoinová adresa, kterou je zpráva podepsána - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address Ověř zprávu, aby ses ujistil, že byla podepsána danou bitcoinovou adresou @@ -3251,8 +3251,8 @@ Poznámka: Jelikož je poplatek počítaný za bajt, poplatek o hodnotě "100 sa Nemohu spustit HTTP server. Detaily viz v debug.log. - Bitcoin Core - Bitcoin Core + NYC3 + NYC3 The %s developers diff --git a/src/qt/locale/nyc3_cy.ts b/src/qt/locale/nyc3_cy.ts index bb17bc147..a5023c7e1 100644 --- a/src/qt/locale/nyc3_cy.ts +++ b/src/qt/locale/nyc3_cy.ts @@ -318,7 +318,7 @@ Ailfynegi y blociau ar ddisg... - Send coins to a Bitcoin address + Send coins to a NYC3 address Anfon arian i gyfeiriad Bitcoin @@ -1025,7 +1025,7 @@ bitcoin-core - Bitcoin Core + NYC3 Craidd Bitcoin diff --git a/src/qt/locale/nyc3_da.ts b/src/qt/locale/nyc3_da.ts index 01059e82d..2e90b0c59 100644 --- a/src/qt/locale/nyc3_da.ts +++ b/src/qt/locale/nyc3_da.ts @@ -342,7 +342,7 @@ Proxy er <b>aktiveret</b>: %1 - Send coins to a Bitcoin address + Send coins to a NYC3 address Send bitcoins til en Bitcoin-adresse @@ -780,7 +780,7 @@ Redigér afsendelsesadresse - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. Den indtastede adresse “%1” er ikke en gyldig Bitcoin-adresse. @@ -1368,7 +1368,7 @@ Ugyldig betalingsadresse %1 - URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. + URI cannot be parsed! This can be caused by an invalid NYC3 address or malformed URI parameters. URI kan ikke tolkes! Dette kan skyldes en ugyldig Bitcoin-adresse eller forkert udformede URL-parametre. @@ -1470,7 +1470,7 @@ Beløb - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) Indtast en Bitcoin-adresse (fx %1) @@ -2355,7 +2355,7 @@ Note: Siden gebyret er kalkuleret på en per-byte basis, et gebyr på "100 satos Bekræftelse estimeret til at begynde om %n blok.Bekræftelse estimeret til at begynde om %n blokke. - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address Advarsel: Ugyldig Bitcoin-adresse @@ -2398,7 +2398,7 @@ Note: Siden gebyret er kalkuleret på en per-byte basis, et gebyr på "100 satos Dette er en normal betaling. - The Bitcoin address to send the payment to + The NYC3 address to send the payment to Bitcoin-adresse, som betalingen skal sendes til @@ -2495,7 +2495,7 @@ Note: Siden gebyret er kalkuleret på en per-byte basis, et gebyr på "100 satos Du kan signere beskeder/aftaler med dine adresser for at bevise, at du kan modtage bitcoin, der bliver sendt til adresserne. Vær forsigtig med ikke at signere noget vagt eller tilfældigt, da eventuelle phishing-angreb kan snyde dig til at overlade din identitet til dem. Signér kun fuldt ud detaljerede udsagn, som du er enig i. - The Bitcoin address to sign the message with + The NYC3 address to sign the message with Bitcoin-adresse, som beskeden skal signeres med @@ -2527,7 +2527,7 @@ Note: Siden gebyret er kalkuleret på en per-byte basis, et gebyr på "100 satos Kopiér den nuværende signatur til systemets udklipsholder - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address Signér denne besked for at bevise, at Bitcoin-adressen tilhører dig @@ -2551,11 +2551,11 @@ Note: Siden gebyret er kalkuleret på en per-byte basis, et gebyr på "100 satos Indtast modtagerens adresse, besked (vær sikker på at kopiere linjeskift, mellemrum, tabuleringer, etc. præcist) og signatur herunder for at verificere beskeden. Vær forsigtig med ikke at læse noget ud fra signaturen, som ikke står i selve beskeden, for at undgå at blive snydt af et eventuelt man-in-the-middle-angreb. Bemærk, at dette kun beviser, at den signerende person kan modtage med adressen; det kan ikke bevise hvem der har sendt en given transaktion! - The Bitcoin address the message was signed with + The NYC3 address the message was signed with Bitcoin-adressen, som beskeden blev signeret med - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address Verificér beskeden for at sikre, at den er signeret med den angivne Bitcoin-adresse @@ -3211,8 +3211,8 @@ Note: Siden gebyret er kalkuleret på en per-byte basis, et gebyr på "100 satos Kunne ikke starte HTTP-server. Se fejlretningslog for detaljer. - Bitcoin Core - Bitcoin Core + NYC3 + NYC3 The %s developers diff --git a/src/qt/locale/nyc3_de.ts b/src/qt/locale/nyc3_de.ts index e5346753f..527d320bd 100644 --- a/src/qt/locale/nyc3_de.ts +++ b/src/qt/locale/nyc3_de.ts @@ -342,7 +342,7 @@ Proxy ist <b>aktiviert</b>: %1 - Send coins to a Bitcoin address + Send coins to a NYC3 address Bitcoins an eine Bitcoin-Adresse überweisen @@ -804,7 +804,7 @@ Zahlungsadresse bearbeiten - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. Die eingegebene Adresse "%1" ist keine gültige Bitcoin-Adresse. @@ -1392,7 +1392,7 @@ Ungültige Zahlungsadresse %1 - URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. + URI cannot be parsed! This can be caused by an invalid NYC3 address or malformed URI parameters. URI kann nicht analysiert werden! Dies kann durch eine ungültige Bitcoin-Adresse oder fehlerhafte URI-Parameter verursacht werden. @@ -1494,7 +1494,7 @@ Betrag - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) Bitcoin-Adresse eingeben (z.B. %1) @@ -2379,7 +2379,7 @@ Hinweis: Eine Gebühr von "100 Satoshis pro kB" bei einer Größe der Transaktio Voraussichtlicher Beginn der Bestätigung innerhalb von %n BlockVoraussichtlicher Beginn der Bestätigung innerhalb von %n Blöcken. - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address Warnung: Ungültige Bitcoin-Adresse @@ -2422,7 +2422,7 @@ Hinweis: Eine Gebühr von "100 Satoshis pro kB" bei einer Größe der Transaktio Dies ist eine normale Überweisung. - The Bitcoin address to send the payment to + The NYC3 address to send the payment to Die Zahlungsadresse der Überweisung @@ -2519,7 +2519,7 @@ Hinweis: Eine Gebühr von "100 Satoshis pro kB" bei einer Größe der Transaktio 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. - The Bitcoin address to sign the message with + The NYC3 address to sign the message with Die Bitcoin-Adresse mit der die Nachricht signiert wird @@ -2551,7 +2551,7 @@ Hinweis: Eine Gebühr von "100 Satoshis pro kB" bei einer Größe der Transaktio Aktuelle Signatur in die Zwischenablage kopieren - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address Die Nachricht signieren, um den Besitz dieser Bitcoin-Adresse zu beweisen @@ -2575,11 +2575,11 @@ Hinweis: Eine Gebühr von "100 Satoshis pro kB" bei einer Größe der Transaktio 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. - The Bitcoin address the message was signed with + The NYC3 address the message was signed with Die Bitcoin-Adresse mit der die Nachricht signiert wurde - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address Die Nachricht verifizieren, um sicherzustellen, dass diese mit der angegebenen Bitcoin-Adresse signiert wurde @@ -3247,8 +3247,8 @@ Hinweis: Eine Gebühr von "100 Satoshis pro kB" bei einer Größe der Transaktio Kann HTTP Server nicht starten. Siehe debug log für Details. - Bitcoin Core - Bitcoin Core + NYC3 + NYC3 The %s developers diff --git a/src/qt/locale/nyc3_el_GR.ts b/src/qt/locale/nyc3_el_GR.ts index 7a7b4f5df..4e18dd15e 100644 --- a/src/qt/locale/nyc3_el_GR.ts +++ b/src/qt/locale/nyc3_el_GR.ts @@ -334,7 +334,7 @@ Φόρτωση ευρετηρίου μπλοκ στον σκληρό δίσκο... - Send coins to a Bitcoin address + Send coins to a NYC3 address Στείλε νομίσματα σε μια διεύθυνση bitcoin @@ -676,7 +676,7 @@ Επεξεργασία διεύθυνσης αποστολής - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. Η διεύθυνση "%1" δεν είναι έγκυρη Bitcoin διεύθυνση. @@ -1114,7 +1114,7 @@ Ποσό - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) Εισάγετε μια διεύθυνση Bitcoin (π.χ. %1) @@ -1638,7 +1638,7 @@ Αυτή είναι μια απλή πληρωμή. - The Bitcoin address to send the payment to + The NYC3 address to send the payment to Η διεύθυνση Bitcoin που θα σταλεί η πληρωμή @@ -1699,7 +1699,7 @@ &Υπογραφή Μηνύματος - The Bitcoin address to sign the message with + The NYC3 address to sign the message with Διεύθυνση Bitcoin που θα σταλεί το μήνυμα @@ -1731,7 +1731,7 @@ Αντιγραφή της επιλεγμένης υπογραφής στο πρόχειρο του συστήματος - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address Υπογράψτε το μήνυμα για να αποδείξετε πως σας ανήκει η συγκεκριμένη διεύθυνση Bitcoin @@ -1751,11 +1751,11 @@ &Επιβεβαίωση Mηνύματος - The Bitcoin address the message was signed with + The NYC3 address the message was signed with Διεύθυνση Bitcoin με την οποία έχει υπογραφεί το μήνυμα - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address Επαληθεύστε το μήνυμα για να αποδείξετε πως υπογράφθηκε από τη συγκεκριμένη διεύθυνση Bitcoin @@ -1967,8 +1967,8 @@ bitcoin-core - Bitcoin Core - Bitcoin Core + NYC3 + NYC3 Corrupted block database detected diff --git a/src/qt/locale/nyc3_en.ts b/src/qt/locale/nyc3_en.ts index f1620935d..5bf398612 100644 --- a/src/qt/locale/nyc3_en.ts +++ b/src/qt/locale/nyc3_en.ts @@ -436,8 +436,8 @@ - Send coins to a Bitcoin address - Send coins to a Bitcoin address + Send coins to a NYC3 address + Send coins to a NYC3 address @@ -1011,7 +1011,7 @@ - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. @@ -1775,7 +1775,7 @@ - URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. + URI cannot be parsed! This can be caused by an invalid NYC3 address or malformed URI parameters. @@ -1908,7 +1908,7 @@ - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) @@ -3075,7 +3075,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satos - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address @@ -3130,7 +3130,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satos - The Bitcoin address to send the payment to + The NYC3 address to send the payment to @@ -3254,7 +3254,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satos - The Bitcoin address to sign the message with + The NYC3 address to sign the message with @@ -3296,8 +3296,8 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satos - Sign the message to prove you own this Bitcoin address - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address + Sign the message to prove you own this NYC3 address @@ -3327,13 +3327,13 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satos - The Bitcoin address the message was signed with + The NYC3 address the message was signed with - Verify the message to ensure it was signed with the specified Bitcoin address - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address + Verify the message to ensure it was signed with the specified NYC3 address @@ -4190,8 +4190,8 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satos - Bitcoin Core - Bitcoin Core + NYC3 + NYC3 diff --git a/src/qt/locale/nyc3_en_GB.ts b/src/qt/locale/nyc3_en_GB.ts index 8db107960..b0dfbbfdd 100644 --- a/src/qt/locale/nyc3_en_GB.ts +++ b/src/qt/locale/nyc3_en_GB.ts @@ -342,8 +342,8 @@ Proxy is <b>enabled</b>: %1 - Send coins to a Bitcoin address - Send coins to a Bitcoin address + Send coins to a NYC3 address + Send coins to a NYC3 address Backup wallet to another location @@ -780,8 +780,8 @@ Edit sending address - The entered address "%1" is not a valid Bitcoin address. - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. + The entered address "%1" is not a valid NYC3 address. Address "%1" already exists as a receiving address with label "%2" and so cannot be added as a sending address. @@ -1368,8 +1368,8 @@ Invalid payment address %1 - URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. - URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. + URI cannot be parsed! This can be caused by an invalid NYC3 address or malformed URI parameters. + URI cannot be parsed! This can be caused by an invalid NYC3 address or malformed URI parameters. Payment request file handling @@ -1470,8 +1470,8 @@ Amount - Enter a Bitcoin address (e.g. %1) - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) + Enter a NYC3 address (e.g. %1) %1 d @@ -2355,8 +2355,8 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p Estimated to begin confirmation within %n block.Estimated to begin confirmation within %n blocks. - Warning: Invalid Bitcoin address - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address + Warning: Invalid NYC3 address Warning: Unknown change address @@ -2398,8 +2398,8 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p This is a normal payment. - The Bitcoin address to send the payment to - The Bitcoin address to send the payment to + The NYC3 address to send the payment to + The NYC3 address to send the payment to Alt+A @@ -2495,8 +2495,8 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p 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. - The Bitcoin address to sign the message with - The Bitcoin address to sign the message with + The NYC3 address to sign the message with + The NYC3 address to sign the message with Choose previously used address @@ -2527,8 +2527,8 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p Copy the current signature to the system clipboard - Sign the message to prove you own this Bitcoin address - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address + Sign the message to prove you own this NYC3 address Sign &Message @@ -2551,12 +2551,12 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p Enter the receiver's address, message (ensure you copy line breaks, spaces, tabs, etc. exactly) and signature below to verify the message. Be careful not to read more into the signature than what is in the signed message itself, to avoid being tricked by a man-in-the-middle attack. Note that this only proves the signing party receives with the address, it cannot prove sendership of any transaction! - The Bitcoin address the message was signed with - The Bitcoin address the message was signed with + The NYC3 address the message was signed with + The NYC3 address the message was signed with - Verify the message to ensure it was signed with the specified Bitcoin address - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address + Verify the message to ensure it was signed with the specified NYC3 address Verify &Message @@ -3211,8 +3211,8 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p Unable to start HTTP server. See debug log for details. - Bitcoin Core - Bitcoin Core + NYC3 + NYC3 The %s developers diff --git a/src/qt/locale/nyc3_eo.ts b/src/qt/locale/nyc3_eo.ts index 2ae99b11c..8465b7b2f 100644 --- a/src/qt/locale/nyc3_eo.ts +++ b/src/qt/locale/nyc3_eo.ts @@ -298,7 +298,7 @@ Reindeksado de blokoj sur disko... - Send coins to a Bitcoin address + Send coins to a NYC3 address Sendi monon al Bitmon-adreso @@ -1289,7 +1289,7 @@ Kreo de transakcio fiaskis! - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address Averto: Nevalida Bitmon-adreso @@ -1405,7 +1405,7 @@ Kopii la aktualan subskribon al la tondejo - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address Subskribi la mesaĝon por pravigi, ke vi estas la posedanto de tiu Bitmon-adreso @@ -1425,7 +1425,7 @@ &Kontroli Mesaĝon - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address Kontroli la mesaĝon por pravigi, ke ĝi ja estas subskribita per la specifa Bitmon-adreso @@ -1865,7 +1865,7 @@ bitcoin-core - Bitcoin Core + NYC3 Kerno de Bitmono diff --git a/src/qt/locale/nyc3_es.ts b/src/qt/locale/nyc3_es.ts index f47ce68ca..2f5544ea9 100644 --- a/src/qt/locale/nyc3_es.ts +++ b/src/qt/locale/nyc3_es.ts @@ -338,7 +338,7 @@ Proxy está<b>habilitado</b>: %1 - Send coins to a Bitcoin address + Send coins to a NYC3 address Enviar bitcoins a una dirección Bitcoin @@ -795,7 +795,7 @@ Editar dirección de envío - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. La dirección introducida "%1" no es una dirección Bitcoin válida. @@ -1375,7 +1375,7 @@ Dirección de pago inválida %1 - URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. + URI cannot be parsed! This can be caused by an invalid NYC3 address or malformed URI parameters. URI no puede ser analizado! Esto puede ser causado por una dirección Bitcoin inválida o parametros URI mal formados. @@ -1477,7 +1477,7 @@ Cantidad - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) Introducir una dirección Bitcoin (p. ej. %1) @@ -2342,7 +2342,7 @@ Nota: Dado que la comisión se calcula por byte, una comisión de "100 satoshis Estimado para empezar la confirmación dentro de %n bloque.Estimado para empezar la confirmación dentro de %n bloques. - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address Alerta: dirección Bitcoin inválida @@ -2385,7 +2385,7 @@ Nota: Dado que la comisión se calcula por byte, una comisión de "100 satoshis Esto es un pago ordinario. - The Bitcoin address to send the payment to + The NYC3 address to send the payment to Dirección Bitcoin a la que enviar el pago @@ -2482,7 +2482,7 @@ Nota: Dado que la comisión se calcula por byte, una comisión de "100 satoshis Puede firmar los mensajes con sus direcciones para demostrar que las posee. Tenga cuidado de no firmar cualquier cosa de manera vaga o aleatoria, pues los ataques de phishing pueden tratar de engañarle firmando su identidad a través de ellos. Sólo firme declaraciones totalmente detalladas con las que usted esté de acuerdo. - The Bitcoin address to sign the message with + The NYC3 address to sign the message with Dirección Bitcoin con la que firmar el mensaje @@ -2514,7 +2514,7 @@ Nota: Dado que la comisión se calcula por byte, una comisión de "100 satoshis Copiar la firma actual al portapapeles del sistema - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address Firmar el mensaje para demostrar que se posee esta dirección Bitcoin @@ -2538,11 +2538,11 @@ Nota: Dado que la comisión se calcula por byte, una comisión de "100 satoshis Introduzca la dirección para la firma, el mensaje (asegurándose de copiar tal cual los saltos de línea, espacios, tabulaciones, etc.) y la firma a continuación para verificar el mensaje. Tenga cuidado de no asumir más información de lo que dice el propio mensaje firmado para evitar fraudes basados en ataques de tipo man-in-the-middle. - The Bitcoin address the message was signed with + The NYC3 address the message was signed with La dirección Bitcoin con la que se firmó el mensaje - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address Verificar el mensaje para comprobar que fue firmado con la dirección Bitcoin indicada @@ -3206,8 +3206,8 @@ Nota: Dado que la comisión se calcula por byte, una comisión de "100 satoshis No se ha podido comenzar el servidor HTTP. Ver debug log para detalles. - Bitcoin Core - Bitcoin Core + NYC3 + NYC3 The %s developers diff --git a/src/qt/locale/nyc3_es_CL.ts b/src/qt/locale/nyc3_es_CL.ts index e2c42f735..fdb24e220 100644 --- a/src/qt/locale/nyc3_es_CL.ts +++ b/src/qt/locale/nyc3_es_CL.ts @@ -330,7 +330,7 @@ Cargando el index de bloques... - Send coins to a Bitcoin address + Send coins to a NYC3 address Enviar monedas a una dirección bitcoin @@ -732,7 +732,7 @@ Editar dirección de envio - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. La dirección introducida "%1" no es una dirección Bitcoin valida. @@ -1303,7 +1303,7 @@ Cantidad - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) Ingresa una dirección de Bitcoin (Ejemplo: %1) @@ -2030,7 +2030,7 @@ Solicitud de pago expirada - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address Peligro: Dirección de Bitcoin inválida @@ -2073,7 +2073,7 @@ Este es un pago normal - The Bitcoin address to send the payment to + The NYC3 address to send the payment to Dirección Bitcoin a enviar el pago @@ -2154,7 +2154,7 @@ &Firmar Mensaje - The Bitcoin address to sign the message with + The NYC3 address to sign the message with Dirección Bitcoin con la que firmar el mensaje @@ -2186,7 +2186,7 @@ Copiar la firma actual al portapapeles del sistema - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address Firmar un mensjage para probar que usted es dueño de esta dirección @@ -2206,11 +2206,11 @@ &Firmar Mensaje - The Bitcoin address the message was signed with + The NYC3 address the message was signed with La dirección Bitcoin con la que se firmó el mensaje - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address Verifica el mensaje para asegurar que fue firmado con la dirección de Bitcoin especificada. @@ -2818,7 +2818,7 @@ No se ha podido iniciar el servidor HTTP. Ver debug log para detalles. - Bitcoin Core + NYC3 bitcoin core diff --git a/src/qt/locale/nyc3_es_CO.ts b/src/qt/locale/nyc3_es_CO.ts index 4001af842..769ce5650 100644 --- a/src/qt/locale/nyc3_es_CO.ts +++ b/src/qt/locale/nyc3_es_CO.ts @@ -307,7 +307,7 @@ Exportar los datos en la pestaña actual a un archivo Reindexando bloques en el disco ... - Send coins to a Bitcoin address + Send coins to a NYC3 address Enviando monedas a una dirección de Bitcoin @@ -1109,7 +1109,7 @@ Exportar los datos en la pestaña actual a un archivo Manejo de URI - URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. + URI cannot be parsed! This can be caused by an invalid NYC3 address or malformed URI parameters. ¡URI no puede ser analizado! Esto puede deberse a una dirección de Bitcoin no válida o a parámetros de URI mal formados. @@ -1878,8 +1878,8 @@ Exportar los datos en la pestaña actual a un archivo bitcoin-core - Bitcoin Core - Bitcoin Core + NYC3 + NYC3 This is the transaction fee you may discard if change is smaller than dust at this level diff --git a/src/qt/locale/nyc3_es_DO.ts b/src/qt/locale/nyc3_es_DO.ts index af5553e22..951ee71f1 100644 --- a/src/qt/locale/nyc3_es_DO.ts +++ b/src/qt/locale/nyc3_es_DO.ts @@ -234,7 +234,7 @@ Reindexando bloques en disco... - Send coins to a Bitcoin address + Send coins to a NYC3 address Enviar monedas a una dirección Bitcoin @@ -1111,7 +1111,7 @@ Copiar la firma actual al portapapeles del sistema - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address Firmar el mensaje para demostrar que se posee esta dirección Bitcoin @@ -1131,7 +1131,7 @@ &Verificar mensaje - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address Verificar el mensaje para comprobar que fue firmado con la dirección Bitcoin indicada @@ -1211,7 +1211,7 @@ bitcoin-core - Bitcoin Core + NYC3 Núcleo de Bitcoin diff --git a/src/qt/locale/nyc3_es_ES.ts b/src/qt/locale/nyc3_es_ES.ts index f3a13c059..2ff7df7c3 100644 --- a/src/qt/locale/nyc3_es_ES.ts +++ b/src/qt/locale/nyc3_es_ES.ts @@ -334,7 +334,7 @@ Reindexando bloques en disco... - Send coins to a Bitcoin address + Send coins to a NYC3 address Enviar bitcoins a una dirección Bitcoin @@ -760,7 +760,7 @@ Editar dirección de envío - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. La dirección introducida "%1" no es una dirección Bitcoin válida. @@ -1236,7 +1236,7 @@ Dirección de pago inválida %1 - URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. + URI cannot be parsed! This can be caused by an invalid NYC3 address or malformed URI parameters. URI no puede ser analizado! Esto puede ser causado por una dirección Bitcoin inválida o parametros URI mal formados. @@ -1338,7 +1338,7 @@ Cantidad - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) Introducir una dirección Bitcoin (p. ej. %1) @@ -2075,7 +2075,7 @@ Solicitud de pago caducada. - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address Alerta: dirección Bitcoin inválida @@ -2118,7 +2118,7 @@ Esto es un pago ordinario. - The Bitcoin address to send the payment to + The NYC3 address to send the payment to Dirección Bitcoin a la que enviar el pago @@ -2211,7 +2211,7 @@ Puede firmar los mensajes con sus direcciones para demostrar que las posee. Tenga cuidado de no firmar cualquier cosa de manera vaga o aleatoria, pues los ataques de phishing pueden tratar de engañarle firmando su identidad a través de ellos. Sólo firme declaraciones totalmente detalladas con las que usted esté de acuerdo. - The Bitcoin address to sign the message with + The NYC3 address to sign the message with Dirección Bitcoin con la que firmar el mensaje @@ -2243,7 +2243,7 @@ Copiar la firma actual al portapapeles del sistema - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address Firmar el mensaje para demostrar que se posee esta dirección Bitcoin @@ -2267,11 +2267,11 @@ Introduzca la dirección para la firma, el mensaje (asegurándose de copiar tal cual los saltos de línea, espacios, tabulaciones, etc.) y la firma a continuación para verificar el mensaje. Tenga cuidado de no asumir más información de lo que dice el propio mensaje firmado para evitar fraudes basados en ataques de tipo man-in-the-middle. - The Bitcoin address the message was signed with + The NYC3 address the message was signed with La dirección Bitcoin con la que se firmó el mensaje - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address Verificar el mensaje para comprobar que fue firmado con la dirección Bitcoin indicada @@ -2855,8 +2855,8 @@ No se ha podido comenzar el servidor HTTP. Ver debug log para detalles. - Bitcoin Core - Bitcoin Core + NYC3 + NYC3 The %s developers diff --git a/src/qt/locale/nyc3_es_MX.ts b/src/qt/locale/nyc3_es_MX.ts index d3e9dde09..e728c8fbb 100644 --- a/src/qt/locale/nyc3_es_MX.ts +++ b/src/qt/locale/nyc3_es_MX.ts @@ -186,7 +186,7 @@ Reindexando bloques en el disco... - Send coins to a Bitcoin address + Send coins to a NYC3 address Enviar monedas a una dirección Bitcoin @@ -639,7 +639,7 @@ bitcoin-core - Bitcoin Core + NYC3 nucleo Bitcoin diff --git a/src/qt/locale/nyc3_es_UY.ts b/src/qt/locale/nyc3_es_UY.ts index 4fe7d7d75..edd4fc8bd 100644 --- a/src/qt/locale/nyc3_es_UY.ts +++ b/src/qt/locale/nyc3_es_UY.ts @@ -250,7 +250,7 @@ Cambiar contraseña - Send coins to a Bitcoin address + Send coins to a NYC3 address Enviar monedas a una dirección Bitcoin diff --git a/src/qt/locale/nyc3_es_VE.ts b/src/qt/locale/nyc3_es_VE.ts index f86435384..ddc9d0385 100644 --- a/src/qt/locale/nyc3_es_VE.ts +++ b/src/qt/locale/nyc3_es_VE.ts @@ -208,7 +208,7 @@ Reindexando bloques en el disco... - Send coins to a Bitcoin address + Send coins to a NYC3 address Enviar monedas a una dirección Bitcoin @@ -777,8 +777,8 @@ bitcoin-core - Bitcoin Core - Bitcoin Core + NYC3 + NYC3 Information diff --git a/src/qt/locale/nyc3_et.ts b/src/qt/locale/nyc3_et.ts index 9ca03ddc9..b049809af 100644 --- a/src/qt/locale/nyc3_et.ts +++ b/src/qt/locale/nyc3_et.ts @@ -294,7 +294,7 @@ Kettal olevate blokkide re-indekseerimine... - Send coins to a Bitcoin address + Send coins to a NYC3 address Saada münte Bitcoini aadressile @@ -626,7 +626,7 @@ Muuda saatvat aadressi - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. Sisestatud aadress "%1" ei ole korrektne Bitcoin aadress. @@ -1341,7 +1341,7 @@ Maksepäring aegunud. - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address Hoiatus: Ebakorrektne Bitcoin aadress @@ -1425,7 +1425,7 @@ &Allkirjastamise teade - The Bitcoin address to sign the message with + The NYC3 address to sign the message with Bitcoin aadress millega sõnum allkirjastada @@ -1457,7 +1457,7 @@ Kopeeri praegune signatuur vahemällu - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address Allkirjasta sõnum Bitcoini aadressi sulle kuulumise tõestamiseks @@ -1477,11 +1477,11 @@ &Kinnita Sõnum - The Bitcoin address the message was signed with + The NYC3 address the message was signed with Bitcoin aadress millega sõnum on allkirjastatud - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address Kinnita sõnum tõestamaks selle allkirjastatust määratud Bitcoini aadressiga. @@ -1917,7 +1917,7 @@ bitcoin-core - Bitcoin Core + NYC3 Bitcoini tuumik diff --git a/src/qt/locale/nyc3_et_EE.ts b/src/qt/locale/nyc3_et_EE.ts index 3962f30aa..cad9e86b5 100644 --- a/src/qt/locale/nyc3_et_EE.ts +++ b/src/qt/locale/nyc3_et_EE.ts @@ -755,8 +755,8 @@ bitcoin-core - Bitcoin Core - Bitcoin Core + NYC3 + NYC3 Information diff --git a/src/qt/locale/nyc3_fa.ts b/src/qt/locale/nyc3_fa.ts index b2416e95d..f0b5f5414 100644 --- a/src/qt/locale/nyc3_fa.ts +++ b/src/qt/locale/nyc3_fa.ts @@ -318,7 +318,7 @@ بازنشانی بلوک‌ها روی دیسک... - Send coins to a Bitcoin address + Send coins to a NYC3 address ارسال وجه به نشانی بیت‌کوین @@ -662,7 +662,7 @@ ویرایش آدرس قرستنده - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. نشانی وارد شده "%1" یک نشانی معتبر بیت‌کوین نیست. @@ -1016,7 +1016,7 @@ مبلغ - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) یک آدرس بیت‌کوین وارد کنید (مثلاً %1) @@ -1496,7 +1496,7 @@ این یک پرداخت عادی است - The Bitcoin address to send the payment to + The NYC3 address to send the payment to نشانی بیت‌کوین برای ارسال پرداخت به آن @@ -1549,7 +1549,7 @@ ا&مضای پیام - The Bitcoin address to sign the message with + The NYC3 address to sign the message with نشانی بیت‌کوین برای امضاء پیغام با آن @@ -1581,7 +1581,7 @@ امضای فعلی را به حافظهٔ سیستم کپی کن - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address برای اثبات تعلق این نشانی به شما، پیام را امضا کنید @@ -1601,11 +1601,11 @@ &شناسایی پیام - The Bitcoin address the message was signed with + The NYC3 address the message was signed with نشانی بیت‌کوین که پیغام با آن امضاء شده - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address برای حصول اطمینان از اینکه پیام با نشانی بیت‌کوین مشخص شده امضا است یا خیر، پیام را شناسایی کنید @@ -1849,7 +1849,7 @@ bitcoin-core - Bitcoin Core + NYC3 هسته Bitcoin diff --git a/src/qt/locale/nyc3_fa_IR.ts b/src/qt/locale/nyc3_fa_IR.ts index 50fa7936d..1206e9850 100644 --- a/src/qt/locale/nyc3_fa_IR.ts +++ b/src/qt/locale/nyc3_fa_IR.ts @@ -334,7 +334,7 @@ فهرست‌بندی نمایه بلاک‌ها… - Send coins to a Bitcoin address + Send coins to a NYC3 address ارسال کوین به آدرس بیت کوین @@ -696,7 +696,7 @@ ویرایش آدرس ارسالی - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. آدرس وارد شده "%1" آدرس معتبر بیت کوین نیست. @@ -1692,7 +1692,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p درخواست پرداخت منقضی شد یا تاریخ آن گذشت. - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address هشدار: آدرس بیت کوین نامعتبر @@ -1735,7 +1735,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p این پرداحت,عادی هست. - The Bitcoin address to send the payment to + The NYC3 address to send the payment to آدرس بیت کوین برای ارسال پرداحت به آن @@ -2260,7 +2260,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p bitcoin-core - Bitcoin Core + NYC3 هسته بیت کوین diff --git a/src/qt/locale/nyc3_fi.ts b/src/qt/locale/nyc3_fi.ts index 929fbcf91..2b5838bce 100644 --- a/src/qt/locale/nyc3_fi.ts +++ b/src/qt/locale/nyc3_fi.ts @@ -342,7 +342,7 @@ Välipalvelin on <b>käytössä</b>: %1 - Send coins to a Bitcoin address + Send coins to a NYC3 address Lähetä kolikoita Bitcoin-osoitteeseen @@ -768,7 +768,7 @@ Muokkaa lähettävää osoitetta - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. Antamasi osoite "%1" ei ole kelvollinen Bitcoin-osoite. @@ -1340,7 +1340,7 @@ Virheellinen maksuosoite %1 - URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. + URI cannot be parsed! This can be caused by an invalid NYC3 address or malformed URI parameters. URIa ei voitu jäsentää! Tämä voi johtua virheellisestä Bitcoin-osoitteesta tai väärin muotoilluista URI parametreista. @@ -1442,7 +1442,7 @@ Määrä - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) Syötä Bitcoin-osoite (esim. %1) @@ -2279,7 +2279,7 @@ Vahvistuminen alkaa arviolta %n lohkon sisällä.Vahvistuminen alkaa arviolta %n lohkon sisällä. - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address Varoitus: Virheellinen Bitcoin-osoite @@ -2322,7 +2322,7 @@ Tämä on normaali maksu. - The Bitcoin address to send the payment to + The NYC3 address to send the payment to Bitcoin-osoite johon maksu lähetetään @@ -2419,7 +2419,7 @@ Voit allekirjoittaa viestit / sopimukset omalla osoitteellasi todistaaksesi että voit vastaanottaa siihen lähetetyt bitcoinit. Varo allekirjoittamasta mitään epämääräistä, sillä phishing-hyökkääjät voivat huijata sinua luovuttamaan henkilöllisyytesi allekirjoituksella. Allekirjoita ainoastaan täysin yksityiskohtainen selvitys siitä, mihin olet sitoutumassa. - The Bitcoin address to sign the message with + The NYC3 address to sign the message with Bitcoin-osoite jolla viesti allekirjoitetaan @@ -2451,7 +2451,7 @@ Kopioi tämänhetkinen allekirjoitus leikepöydälle - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address Allekirjoita viesti todistaaksesi, että omistat tämän Bitcoin-osoitteen @@ -2475,11 +2475,11 @@ Syötä vastaanottajan osoite, viesti ja allekirjoitus (varmista että kopioit rivinvaihdot, välilyönnit, sarkaimet yms. täsmälleen) alle vahvistaaksesi viestin. Varo lukemasta allekirjoitukseen enempää kuin mitä viestissä itsessään on välttääksesi man-in-the-middle -hyökkäyksiltä. Huomaa, että tämä todentaa ainoastaan allekirjoittavan vastaanottajan osoitteen, tämä ei voi todentaa minkään tapahtuman lähettäjää! - The Bitcoin address the message was signed with + The NYC3 address the message was signed with Bitcoin-osoite jolla viesti on allekirjoitettu - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address Tarkista viestin allekirjoitus varmistaaksesi, että se allekirjoitettiin tietyllä Bitcoin-osoitteella @@ -3127,7 +3127,7 @@ HTTP-palvelinta ei voitu käynnistää. Katso debug-lokista lisätietoja. - Bitcoin Core + NYC3 Bitcoin-ydin diff --git a/src/qt/locale/nyc3_fr.ts b/src/qt/locale/nyc3_fr.ts index 23d50a962..ac38d85f7 100644 --- a/src/qt/locale/nyc3_fr.ts +++ b/src/qt/locale/nyc3_fr.ts @@ -342,7 +342,7 @@ Le serveur mandataire est <b>activé</b> : %1 - Send coins to a Bitcoin address + Send coins to a NYC3 address Envoyer des pièces à une adresse Bitcoin @@ -804,7 +804,7 @@ Modifier l’adresse d’envoi - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. L’adresse saisie « %1 » n’est pas une adresse Bitcoin valide. @@ -1396,7 +1396,7 @@ Adresse de paiement invalide %1 - URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. + URI cannot be parsed! This can be caused by an invalid NYC3 address or malformed URI parameters. L’URI ne peut pas être analysée ! Cela peut être causé par une adresse Bitcoin invalide ou par des paramètres d’URI mal formés. @@ -1498,7 +1498,7 @@ Montant - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) Saisir une adresse Bitcoin (p. ex. %1) @@ -2383,7 +2383,7 @@ Note : Les frais étant calculés par octet, des frais de « 100 satoshis par Il est estimé que la confirmation commencera dans %n bloc.Il est estimé que la confirmation commencera dans %n blocs. - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address Avertissement : L’adresse Bitcoin est invalide @@ -2426,7 +2426,7 @@ Note : Les frais étant calculés par octet, des frais de « 100 satoshis par Ceci est un paiement normal. - The Bitcoin address to send the payment to + The NYC3 address to send the payment to L’adresse Bitcoin à laquelle envoyer le paiement @@ -2523,7 +2523,7 @@ Note : Les frais étant calculés par octet, des frais de « 100 satoshis par Vous pouvez signer des messages ou des accords avec vos adresses pour prouver que vous pouvez recevoir des bitcoins à ces dernières. Faites attention de ne rien signer de vague ou au hasard, car des attaques d’hameçonnage pourraient essayer de vous faire signer avec votre identité afin de l’usurper. Ne signez que des déclarations entièrement détaillées et avec lesquelles vous êtes d’accord. - The Bitcoin address to sign the message with + The NYC3 address to sign the message with L’adresse Bitcoin avec laquelle signer le message @@ -2555,7 +2555,7 @@ Note : Les frais étant calculés par octet, des frais de « 100 satoshis par Copier la signature actuelle dans le presse-papiers - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address Signer le message afin de prouver que vous détenez cette adresse Bitcoin @@ -2579,11 +2579,11 @@ Note : Les frais étant calculés par octet, des frais de « 100 satoshis par Saisir ci-dessous l’adresse du destinataire, le message (s’assurer de copier fidèlement les retours à la ligne, les espaces, les tabulations, etc.) et la signature pour vérifier le message. Faire attention à ne pas déduire davantage de la signature que ce qui est contenu dans le message signé même, pour éviter d’être trompé par une attaque d’homme du milieu. Prendre en compte que cela ne fait que prouver que le signataire reçoit l’adresse et ne peut pas prouver la provenance d’une transaction ! - The Bitcoin address the message was signed with + The NYC3 address the message was signed with L’adresse Bitcoin avec laquelle le message a été signé - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address Vérifier le message pour s’assurer qu’il a été signé avec l’adresse Bitcoin indiquée @@ -3251,8 +3251,8 @@ Note : Les frais étant calculés par octet, des frais de « 100 satoshis par Impossible de démarrer le serveur HTTP. Voir le journal de débogage pour plus de détails. - Bitcoin Core - Bitcoin Core + NYC3 + NYC3 The %s developers diff --git a/src/qt/locale/nyc3_fr_FR.ts b/src/qt/locale/nyc3_fr_FR.ts index c96a67925..cb489a34c 100644 --- a/src/qt/locale/nyc3_fr_FR.ts +++ b/src/qt/locale/nyc3_fr_FR.ts @@ -338,7 +338,7 @@ Le proxy est <b>activé</b> : %1 - Send coins to a Bitcoin address + Send coins to a NYC3 address Envoyer des pièces à une adresse Bitcoin @@ -744,7 +744,7 @@ Éditer l'adresse d'envoi - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. L'adresse entrée "%1" n'est pas une adresse Bitcoin valide. @@ -1110,7 +1110,7 @@ Montant - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) Entrer une adresse Bitcoin (e.g. %1) @@ -1671,7 +1671,7 @@ Demande de paiement expirée. - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address Attention: Adresse Bitcoin Invalide @@ -2235,8 +2235,8 @@ Impossible de démarrer le serveur HTTP. Voir le journal de débogage pour plus de détails. - Bitcoin Core - Bitcoin Core + NYC3 + NYC3 Importing... diff --git a/src/qt/locale/nyc3_gl.ts b/src/qt/locale/nyc3_gl.ts index cfdfe79a6..211040ba0 100644 --- a/src/qt/locale/nyc3_gl.ts +++ b/src/qt/locale/nyc3_gl.ts @@ -130,7 +130,7 @@ Reindexando bloques no disco... - Send coins to a Bitcoin address + Send coins to a NYC3 address Enviar moedas a unha dirección Bitcoin @@ -919,7 +919,7 @@ Copiar a sinatura actual ao portapapeis do sistema - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address Asina a mensaxe para probar que posees esta dirección Bitcoin @@ -939,7 +939,7 @@ &Verificar Mensaxe - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address Verificar a mensaxe para asegurar que foi asinada coa dirección Bitcoin especificada @@ -999,7 +999,7 @@ bitcoin-core - Bitcoin Core + NYC3 Core de Bitcoin diff --git a/src/qt/locale/nyc3_he.ts b/src/qt/locale/nyc3_he.ts index e53879792..4847684d7 100644 --- a/src/qt/locale/nyc3_he.ts +++ b/src/qt/locale/nyc3_he.ts @@ -338,7 +338,7 @@ שרת הפרוקסי <b>פעיל</b>: %1 - Send coins to a Bitcoin address + Send coins to a NYC3 address שליחת מטבעות לכתובת ביטקוין @@ -744,7 +744,7 @@ עריכת כתובת השליחה - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. הכתובת שהוקלדה „%1” היא אינה כתובת ביטקוין תקנית. @@ -1304,7 +1304,7 @@ כתובת תשלום שגויה %1 - URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. + URI cannot be parsed! This can be caused by an invalid NYC3 address or malformed URI parameters. לא ניתן לנתח את כתובת המשאב! מצב זה יכול לקרות עקב כתובת ביטקוין שגויה או פרמטרים שגויים בכתובת המשאב. @@ -1406,7 +1406,7 @@ כמות - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) נא להזין כתובת ביטקוין (למשל: %1) @@ -2247,7 +2247,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p בקשת התשלום פגה. - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address אזהרה: כתובת ביטקיון שגויה @@ -2290,7 +2290,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p זהו תשלום רגיל. - The Bitcoin address to send the payment to + The NYC3 address to send the payment to כתובת הביטקוין של המוטב @@ -2387,7 +2387,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p באפשרותך לחתום על הודעות/הסכמים באמצעות הכתובות שלך, כדי להוכיח שאתה יכול לקבל את הביטקוינים הנשלחים אליהן. היזהר לא לחתום על תוכן עמום או אקראי, מכיוון שתקיפות פישינג עשויות לנסות לגנוב את הזהות שלך. חתום רק על הצהרות מפורטות שאתה מסכים להן. - The Bitcoin address to sign the message with + The NYC3 address to sign the message with כתובת הביטקוין אתה לחתום אתה את ההודעה @@ -2419,7 +2419,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p העתקת החתימה הנוכחית ללוח הגזירים - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address ניתן לחתום על ההודעה כדי להוכיח שכתובת הביטקוין הזו בבעלותך. @@ -2439,11 +2439,11 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p &אימות הודעה - The Bitcoin address the message was signed with + The NYC3 address the message was signed with כתובת הביטקוין שאתה נחתמה ההודעה - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address ניתן לאמת את ההודעה כדי להבטיח שהיא נחתמה עם כתובת הביטקוין הנתונה @@ -3055,7 +3055,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p שרת ה HTTP לא עלה. ראו את ה debug לוג לפרטים. - Bitcoin Core + NYC3 ליבת ביטקוין diff --git a/src/qt/locale/nyc3_hr.ts b/src/qt/locale/nyc3_hr.ts index 2444f081d..ba56ef8a5 100644 --- a/src/qt/locale/nyc3_hr.ts +++ b/src/qt/locale/nyc3_hr.ts @@ -338,7 +338,7 @@ Proxy je <b>uključen</b>: %1 - Send coins to a Bitcoin address + Send coins to a NYC3 address Pošaljite novac na Bitcoin adresu @@ -747,7 +747,7 @@ Uredi adresu za slanje - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. Upisana adresa "%1" nije valjana Bitcoin adresa. @@ -1315,7 +1315,7 @@ Nevažeća adresa za plaćanje %1 - URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. + URI cannot be parsed! This can be caused by an invalid NYC3 address or malformed URI parameters. Ne može se parsirati URI! Uzrok tomu može biti nevažeća Bitcoin adresa ili neispravni parametri kod URI-a. @@ -1417,7 +1417,7 @@ Iznos - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) Unesite Bitcoin adresu (npr. %1) @@ -2278,7 +2278,7 @@ Napomena: Budući da se naknada računa po bajtu, naknada od "100 satošija po k Procijenjeno je da će početi potvrđivanje unutar %n bloka.Procijenjeno je da će početi potvrđivanje unutar %n bloka.Procijenjeno je da će početi potvrđivanje unutar %n blokova. - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address Upozorenje: Nevažeća Bitcoin adresa @@ -2321,7 +2321,7 @@ Napomena: Budući da se naknada računa po bajtu, naknada od "100 satošija po k Ovo je normalna uplata. - The Bitcoin address to send the payment to + The NYC3 address to send the payment to Bitcoin adresa na koju ćete poslati uplatu @@ -2418,7 +2418,7 @@ Napomena: Budući da se naknada računa po bajtu, naknada od "100 satošija po k Možete potpisati poruke/dogovore svojim adresama kako biste dokazali da možete pristupiti bitcoinima poslanim na te adrese. Budite oprezni da ne potpisujte ništa nejasno ili nasumično, jer napadi phishingom vas mogu prevariti da prepišite svoj identitet njima. Potpisujte samo detaljno objašnjene izjave s kojima se slažete. - The Bitcoin address to sign the message with + The NYC3 address to sign the message with Bitcoin adresa pomoću koje ćete potpisati poruku @@ -2450,7 +2450,7 @@ Napomena: Budući da se naknada računa po bajtu, naknada od "100 satošija po k Kopirajte trenutni potpis u međuspremnik - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address Potpišite poruku kako biste dokazali da posjedujete ovu Bitcoin adresu @@ -2474,11 +2474,11 @@ Napomena: Budući da se naknada računa po bajtu, naknada od "100 satošija po k Unesite primateljevu adresu, poruku (provjerite da kopirate prekide crta, razmake, tabove, itd. točno) i potpis ispod da provjerite poruku. Pazite da ne pridodate veće značenje potpisu nego što je sadržano u samoj poruci kako biste izbjegli napad posrednika (MITM attack). Primijetite da ovo samo dokazuje da stranka koja potpisuje prima na adresu. Ne može dokažati da je neka stranka poslala transakciju! - The Bitcoin address the message was signed with + The NYC3 address the message was signed with Bitcoin adresa kojom je poruka potpisana - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address Provjerite poruku da budete sigurni da je potpisana zadanom Bitcoin adresom @@ -3134,8 +3134,8 @@ Napomena: Budući da se naknada računa po bajtu, naknada od "100 satošija po k Ne može se pokrenuti HTTP server. Vidite debug.log za više detalja. - Bitcoin Core - Bitcoin Core + NYC3 + NYC3 The %s developers diff --git a/src/qt/locale/nyc3_hu.ts b/src/qt/locale/nyc3_hu.ts index 6684aa0ae..8a4904102 100644 --- a/src/qt/locale/nyc3_hu.ts +++ b/src/qt/locale/nyc3_hu.ts @@ -327,7 +327,7 @@ Kérem a kulcsmondatban használjon <b> tíz vagy több véletlenszerű ka Lemezen lévő blokkok újraindexelése... - Send coins to a Bitcoin address + Send coins to a NYC3 address Bitcoin küldése megadott címre @@ -731,7 +731,7 @@ Kérem a kulcsmondatban használjon <b> tíz vagy több véletlenszerű ka Küldő cím szerkesztése - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. A megadott "%1" cím nem egy érvényes Bitcoin-cím. @@ -1255,7 +1255,7 @@ Kérem a kulcsmondatban használjon <b> tíz vagy több véletlenszerű ka Érvénytelen fizetési cím %1 - URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. + URI cannot be parsed! This can be caused by an invalid NYC3 address or malformed URI parameters. Nem sikerült az URI elemzése! Ezt okozhatja érvénytelen Bitcoin cím, vagy rossz URI paraméterezés. @@ -1353,7 +1353,7 @@ Kérem a kulcsmondatban használjon <b> tíz vagy több véletlenszerű ka Összeg - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) Ad meg egy Bitcoin címet (pl: %1) @@ -2142,7 +2142,7 @@ Kérem a kulcsmondatban használjon <b> tíz vagy több véletlenszerű ka A fizetési kérelem lejárt. - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address Figyelmeztetés: Érvénytelen Bitcoin cím @@ -2185,7 +2185,7 @@ Kérem a kulcsmondatban használjon <b> tíz vagy több véletlenszerű ka Ez normál fizetés. - The Bitcoin address to send the payment to + The NYC3 address to send the payment to Erre a Bitcoin címre küldje az összeget @@ -2270,7 +2270,7 @@ Kérem a kulcsmondatban használjon <b> tíz vagy több véletlenszerű ka Üzenet aláírása... - The Bitcoin address to sign the message with + The NYC3 address to sign the message with Bitcoin cím, amivel alá kívánja írni az üzenetet @@ -2302,7 +2302,7 @@ Kérem a kulcsmondatban használjon <b> tíz vagy több véletlenszerű ka A jelenleg kiválasztott aláírás másolása a rendszer-vágólapra - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address Üzenet @@ -2318,11 +2318,11 @@ Kérem a kulcsmondatban használjon <b> tíz vagy több véletlenszerű ka Üzenet ellenőrzése - The Bitcoin address the message was signed with + The NYC3 address the message was signed with Bitcoin cím, amivel aláírta az üzenetet - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address Ellenőrizze az üzenetet, hogy valóban a megjelölt Bitcoin címmel van-e aláírva @@ -2870,8 +2870,8 @@ Kérem a kulcsmondatban használjon <b> tíz vagy több véletlenszerű ka HTTP szerver indítása sikertelen. A részleteket lásd: debug log. - Bitcoin Core - Bitcoin Core + NYC3 + NYC3 The %s developers diff --git a/src/qt/locale/nyc3_id.ts b/src/qt/locale/nyc3_id.ts index 21ff5de15..3d3203616 100644 --- a/src/qt/locale/nyc3_id.ts +++ b/src/qt/locale/nyc3_id.ts @@ -342,7 +342,7 @@ Proxy <b>aktif</b>: %1 - Send coins to a Bitcoin address + Send coins to a NYC3 address Kirim koin ke alamat Bitcoin diff --git a/src/qt/locale/nyc3_id_ID.ts b/src/qt/locale/nyc3_id_ID.ts index 49651e928..e1d34c31e 100644 --- a/src/qt/locale/nyc3_id_ID.ts +++ b/src/qt/locale/nyc3_id_ID.ts @@ -342,7 +342,7 @@ Proxy di <b>aktifkan</b>: %1 - Send coins to a Bitcoin address + Send coins to a NYC3 address Kirim koin ke alamat Bitcoin @@ -776,7 +776,7 @@ Ubah alamat pengirim - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. Alamat yang dimasukkan "%1" bukanlah alamat Bitcoin yang valid. @@ -1348,7 +1348,7 @@ URL permintaan pembayaran tidak valid: %1 - URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. + URI cannot be parsed! This can be caused by an invalid NYC3 address or malformed URI parameters. URI tidak bisa dimengerti! Hal ini bisa disebabkan karena alamat Bitcoin yang tidak sah atau parameter URI yang tidak tepat. @@ -1390,7 +1390,7 @@ Nilai - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) Masukkan alamat Bitcoin (contoh %1) @@ -1921,7 +1921,7 @@ Salin tanda tangan terpilih ke sistem klipboard - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address Tandai pesan untuk menyetujui kamu pemiliki alamat Bitcoin ini @@ -2045,8 +2045,8 @@ bitcoin-core - Bitcoin Core - Bitcoin Core + NYC3 + NYC3 Corrupted block database detected diff --git a/src/qt/locale/nyc3_is.ts b/src/qt/locale/nyc3_is.ts index 06b9beb4b..baa6b9ceb 100644 --- a/src/qt/locale/nyc3_is.ts +++ b/src/qt/locale/nyc3_is.ts @@ -322,7 +322,7 @@ Endurraða blokkum á drifi... - Send coins to a Bitcoin address + Send coins to a NYC3 address Senda mynt í Bitcoin færslugildi @@ -630,7 +630,7 @@ Breyta sendingarfærslugildi - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. Færslugildið sem slegið var inn "%1" er ekki leyfilegt Bitcoin færslugildi. diff --git a/src/qt/locale/nyc3_it.ts b/src/qt/locale/nyc3_it.ts index 779a5379f..5e5410a0c 100644 --- a/src/qt/locale/nyc3_it.ts +++ b/src/qt/locale/nyc3_it.ts @@ -342,7 +342,7 @@ Il Proxy è <b>abilitato</b>:%1 - Send coins to a Bitcoin address + Send coins to a NYC3 address Invia fondi ad un indirizzo Bitcoin @@ -804,7 +804,7 @@ Modifica indirizzo d'invio - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. L'indirizzo inserito "%1" non è un indirizzo bitcoin valido. @@ -1397,7 +1397,7 @@ Per specificare più URL separarli con una barra verticale "|". Indirizzo di pagamento non valido %1 - URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. + URI cannot be parsed! This can be caused by an invalid NYC3 address or malformed URI parameters. Impossibile interpretare l'URI! I parametri dell'URI o l'indirizzo Bitcoin potrebbero non essere corretti. @@ -1499,7 +1499,7 @@ Per specificare più URL separarli con una barra verticale "|". Importo - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) Inserisci un indirizzo Bitcoin (ad es. %1) @@ -2384,7 +2384,7 @@ Nota: poiché la commissione è calcolata su base per byte, una commissione di " Inizio delle conferme stimato entro %n blocchi.Inizio delle conferme stimato entro %n blocchi. - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address Attenzione: Indirizzo Bitcoin non valido @@ -2427,7 +2427,7 @@ Nota: poiché la commissione è calcolata su base per byte, una commissione di " Questo è un normale pagamento. - The Bitcoin address to send the payment to + The NYC3 address to send the payment to L'indirizzo Bitcoin a cui vuoi inviare il pagamento @@ -2524,7 +2524,7 @@ Nota: poiché la commissione è calcolata su base per byte, una commissione di " È possibile firmare messaggi/accordi con i propri indirizzi in modo da dimostrare di poter ricevere bitcoin attraverso di essi. Presta attenzione a non firmare dichiarazioni vaghe o casuali, perché attacchi di phishing potrebbero cercare di indurti ad apporre la firma su di esse. Firma esclusivamente dichiarazioni completamente dettagliate e delle quali condividi in pieno il contenuto. - The Bitcoin address to sign the message with + The NYC3 address to sign the message with Indirizzo Bitcoin da utilizzare per firmare il messaggio @@ -2556,7 +2556,7 @@ Nota: poiché la commissione è calcolata su base per byte, una commissione di " Copia la firma corrente nella clipboard - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address Firma un messaggio per dimostrare di possedere questo indirizzo Bitcoin @@ -2580,11 +2580,11 @@ Nota: poiché la commissione è calcolata su base per byte, una commissione di " Per verificare il messaggio inserire l'indirizzo del firmatario, il messaggio e la firma nei campi sottostanti, assicurandosi di copiare esattamente anche ritorni a capo, spazi, tabulazioni, etc.. Si raccomanda di non lasciarsi fuorviare dalla firma a leggere più di quanto non sia riportato nel testo del messaggio stesso, in modo da evitare di cadere vittima di attacchi di tipo man-in-the-middle. Si ricorda che la verifica della firma dimostra soltanto che il firmatario può ricevere pagamenti con l'indirizzo corrispondente, non prova l'invio di alcuna transazione. - The Bitcoin address the message was signed with + The NYC3 address the message was signed with L'indirizzo Bitcoin con cui è stato contrassegnato il messaggio - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address Verifica il messaggio per accertare che sia stato firmato con l'indirizzo specificato @@ -3244,8 +3244,8 @@ Nota: poiché la commissione è calcolata su base per byte, una commissione di " Impossibile avviare il server HTTP. Dettagli nel log di debug. - Bitcoin Core - Bitcoin Core + NYC3 + NYC3 The %s developers diff --git a/src/qt/locale/nyc3_it_IT.ts b/src/qt/locale/nyc3_it_IT.ts index e1d89a50c..702fa81c4 100644 --- a/src/qt/locale/nyc3_it_IT.ts +++ b/src/qt/locale/nyc3_it_IT.ts @@ -330,7 +330,7 @@ Reindicizzazione dei blocchi sul disco... - Send coins to a Bitcoin address + Send coins to a NYC3 address Invia monete ad un indirizzo Bitcoin... @@ -686,7 +686,7 @@ Modifica l'indirizzo di invio - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. L'indirizzo inserito "%1" non è un indirizzo Bitcoin valido. diff --git a/src/qt/locale/nyc3_ja.ts b/src/qt/locale/nyc3_ja.ts index fe9d7f5bc..6831cd55e 100644 --- a/src/qt/locale/nyc3_ja.ts +++ b/src/qt/locale/nyc3_ja.ts @@ -342,7 +342,7 @@ プロキシは<b>有効</b>: %1 - Send coins to a Bitcoin address + Send coins to a NYC3 address Bitcoin アドレスにコインを送る @@ -804,7 +804,7 @@ 送金先アドレスを編集 - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. 入力されたアドレス "%1" は無効な Bitcoin アドレスです。 @@ -1392,7 +1392,7 @@ 支払い先アドレス「 %1 」は無効です - URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. + URI cannot be parsed! This can be caused by an invalid NYC3 address or malformed URI parameters. URIを解析できませんでした！ Bitcoin アドレスが無効であるか、URIパラメーターが不正な形式である可能性があります。 @@ -1494,7 +1494,7 @@ 金額 - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) Bitcoin アドレスを入力してください (例: %1) @@ -2379,7 +2379,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p 予想される承認開始ブロック: %n ブロック以内 - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address 警告: 無効な Bitcoin アドレス @@ -2422,7 +2422,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p これは通常の支払いです。 - The Bitcoin address to send the payment to + The NYC3 address to send the payment to 支払い先 Bitcoin アドレス @@ -2519,7 +2519,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p あなたが所有しているアドレスでメッセージや契約書に署名をすることで、それらのアドレスへ送られた Bitcoin を受け取ることができることを証明できます。フィッシング攻撃者があなたを騙して、あなたの身分情報に署名させようとしている可能性があるため、よくわからないものやランダムな文字列に対して署名しないでください。あなたが同意した、よく詳細の記された文言にのみ署名するようにしてください。 - The Bitcoin address to sign the message with + The NYC3 address to sign the message with メッセージの署名に使用する Bitcoin アドレス @@ -2551,7 +2551,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p この署名をシステムのクリップボードにコピー - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address メッセージに署名してこの Bitcoin アドレスを所有していることを証明 @@ -2575,11 +2575,11 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p 送金先のアドレスと、メッセージ（改行やスペース、タブなども完全に一致させること）および署名を以下に入力し、メッセージを検証します。中間者攻撃により騙されるのを防ぐため、署名対象のメッセージから書かれていること以上の意味を読み取ろうとしないでください。また、これは署名作成者がこのアドレスで受け取れることを証明するだけであり、取引の送信権限を証明するものではありません！ - The Bitcoin address the message was signed with + The NYC3 address the message was signed with メッセージの署名に使われた Bitcoin アドレス - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address メッセージを検証して指定された Bitcoin アドレスで署名されたことを確認 @@ -3247,7 +3247,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p HTTPサーバを開始できませんでした。詳細は debug.log を参照してください。 - Bitcoin Core + NYC3 Bitcoin コア diff --git a/src/qt/locale/nyc3_ka.ts b/src/qt/locale/nyc3_ka.ts index e3655e365..845670fe1 100644 --- a/src/qt/locale/nyc3_ka.ts +++ b/src/qt/locale/nyc3_ka.ts @@ -310,7 +310,7 @@ დისკზე ბლოკების რეინდექსაცია... - Send coins to a Bitcoin address + Send coins to a NYC3 address მონეტების გაგზავნა Bitcoin-მისამართზე @@ -1391,7 +1391,7 @@ მიმდინარე ხელმოწერის კოპირება კლიპბორდში - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address მოაწერეთ ხელი იმის დასადასტურებლად, რომ ეს მისამართი თქვენია @@ -1411,7 +1411,7 @@ მესიჯის &ვერიფიკაცია - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address შეამოწმეთ, რომ მესიჯი ხელმოწერილია მითითებული Bitcoin-მისამართით @@ -1511,8 +1511,8 @@ bitcoin-core - Bitcoin Core - Bitcoin Core + NYC3 + NYC3 Corrupted block database detected diff --git a/src/qt/locale/nyc3_ko.ts b/src/qt/locale/nyc3_ko.ts index 7c31e1534..80d1dfc31 100644 --- a/src/qt/locale/nyc3_ko.ts +++ b/src/qt/locale/nyc3_ko.ts @@ -314,7 +314,7 @@ 디스크에서 블럭 불러오는 중 - Send coins to a Bitcoin address + Send coins to a NYC3 address 비트코인 주소로 코인 보내기 diff --git a/src/qt/locale/nyc3_ko_KR.ts b/src/qt/locale/nyc3_ko_KR.ts index a854ac630..bf0a733fa 100644 --- a/src/qt/locale/nyc3_ko_KR.ts +++ b/src/qt/locale/nyc3_ko_KR.ts @@ -342,7 +342,7 @@ 프록시가 <b>활성화</b> 되었습니다: %1 - Send coins to a Bitcoin address + Send coins to a NYC3 address 비트코인 주소로 코인을 전송합니다 @@ -804,7 +804,7 @@ 보내는 주소 편집 - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. 입력한 "%1" 주소는 올바른 비트코인 주소가 아닙니다. @@ -1396,7 +1396,7 @@ 잘못된 지불 주소 %1 - URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. + URI cannot be parsed! This can be caused by an invalid NYC3 address or malformed URI parameters. URI의 파싱에 문제가 발생했습니다. 잘못된 비트코인 주소나 URI 파라미터 구성에 오류가 존재할 수 있습니다. @@ -1498,7 +1498,7 @@ 금액 - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) 비트코인 주소를 입력하세요 (예. %1) @@ -2383,7 +2383,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p %n 블록 안에 승인이 시작될 것으로 추정됩니다. - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address 경고: 잘못된 비트코인주소입니다 @@ -2426,7 +2426,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p 이것은 정상적인 지불입니다. - The Bitcoin address to send the payment to + The NYC3 address to send the payment to 이 비트코인 주소로 송금됩니다 @@ -2523,7 +2523,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p 당신이 해당 주소로 비트코인을 받을 수 있다는 것을 증명하기 위해 메시지/합의문을 그 주소로 서명할 수 있습니다. 피싱 공격이 당신을 속일 수 있으므로 임의의 내용이나 모호한 내용에 서명하지 않도록 주의하세요. 당신이 동의하는 명확한 조항들에만 서명하세요. - The Bitcoin address to sign the message with + The NYC3 address to sign the message with 메세지를 서명할 비트코인 주소 @@ -2555,7 +2555,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p 이 서명을 시스템 클립보드로 복사 - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address 당신이 이 비트코인 주소를 소유한다는 증명을 위해 메시지를 서명합니다 @@ -2579,11 +2579,11 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p 메시지를 검증하기 위해 아래 칸에 각각 지갑 주소와 메시지, 서명을 입력하세요 (메시지 원본의 띄어쓰기, 들여쓰기, 행 나눔 등이 정확하게 입력되어야 하므로 원본을 복사해서 입력하세요). 네트워크 침입자의 속임수에 넘어가지 않도록 서명된 메시지 내용 이외의 내용은 참고하지 않도록 유의하세요. 이 기능은 단순히 서명한 쪽에서 해당 주소로 송금을 받을 수 있다는 것을 증명하는 것 뿐이며 그 이상은 어떤 것도 보증하지 않습니다. - The Bitcoin address the message was signed with + The NYC3 address the message was signed with 메세지의 서명에 사용된 비트코인 주소 - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address 입력된 비트코인 주소로 메시지가 서명되었는지 검증합니다 @@ -3251,7 +3251,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p HTTP 서버를 시작할 수 없습니다. 자세한 사항은 디버그 로그를 확인 하세요. - Bitcoin Core + NYC3 비트코인 코어 diff --git a/src/qt/locale/nyc3_la.ts b/src/qt/locale/nyc3_la.ts index 0949c478c..81f0cd58e 100644 --- a/src/qt/locale/nyc3_la.ts +++ b/src/qt/locale/nyc3_la.ts @@ -118,7 +118,7 @@ Recreans indicem frustorum in disco... - Send coins to a Bitcoin address + Send coins to a NYC3 address Mitte nummos ad inscriptionem Bitcoin @@ -679,7 +679,7 @@ Copia signationem in latibulum systematis - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address Signa nuntium ut demonstres hanc inscriptionem Bitcoin a te possessa esse @@ -699,7 +699,7 @@ &Verifica Nuntium - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address Verifica nuntium ut cures signatum esse cum specifica inscriptione Bitcoin @@ -755,7 +755,7 @@ bitcoin-core - Bitcoin Core + NYC3 Bitcoin Nucleus diff --git a/src/qt/locale/nyc3_lt.ts b/src/qt/locale/nyc3_lt.ts index ff0c6637b..c26b80a1d 100644 --- a/src/qt/locale/nyc3_lt.ts +++ b/src/qt/locale/nyc3_lt.ts @@ -330,7 +330,7 @@ Blokai iš naujo indeksuojami... - Send coins to a Bitcoin address + Send coins to a NYC3 address Siųsti monetas Bitcoin adresui @@ -1191,7 +1191,7 @@ Įveskite pranešimą, kurį norite pasirašyti čia - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address Registruotis žinute įrodymuii, kad turite šį adresą @@ -1207,7 +1207,7 @@ &Patikrinti žinutę - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address Patikrinkite žinutę, jog įsitikintumėte, kad ją pasirašė nurodytas Bitcoin adresas @@ -1307,7 +1307,7 @@ bitcoin-core - Bitcoin Core + NYC3 Bitcoin branduolys diff --git a/src/qt/locale/nyc3_lv_LV.ts b/src/qt/locale/nyc3_lv_LV.ts index 573f5af3f..80aa35169 100644 --- a/src/qt/locale/nyc3_lv_LV.ts +++ b/src/qt/locale/nyc3_lv_LV.ts @@ -202,7 +202,7 @@ Bloku reindeksēšana no diska... - Send coins to a Bitcoin address + Send coins to a NYC3 address Nosūtīt bitkoinus uz Bitcoin adresi @@ -1091,7 +1091,7 @@ Kopēt parakstu uz sistēmas starpliktuvi - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address Parakstīt ziņojumu lai pierādītu, ka esi šīs Bitcoin adreses īpašnieks. @@ -1187,8 +1187,8 @@ bitcoin-core - Bitcoin Core - Bitcoin Core + NYC3 + NYC3 Error loading block database diff --git a/src/qt/locale/nyc3_mk_MK.ts b/src/qt/locale/nyc3_mk_MK.ts index 33fc52554..80022c407 100644 --- a/src/qt/locale/nyc3_mk_MK.ts +++ b/src/qt/locale/nyc3_mk_MK.ts @@ -126,7 +126,7 @@ Повторно индексирање на блокови од дискот... - Send coins to a Bitcoin address + Send coins to a NYC3 address Испрати биткоини на Биткоин адреса @@ -577,7 +577,7 @@ bitcoin-core - Bitcoin Core + NYC3 Биткоин Core diff --git a/src/qt/locale/nyc3_ms_MY.ts b/src/qt/locale/nyc3_ms_MY.ts index 13cd10c02..27716e95d 100644 --- a/src/qt/locale/nyc3_ms_MY.ts +++ b/src/qt/locale/nyc3_ms_MY.ts @@ -337,7 +337,7 @@ Alihkan fail data ke dalam tab semasa Reindexi blok pada cakera... - Send coins to a Bitcoin address + Send coins to a NYC3 address Menghantar koin kepada alamat Bitcoin diff --git a/src/qt/locale/nyc3_nb.ts b/src/qt/locale/nyc3_nb.ts index f31533e16..1f7678ea0 100644 --- a/src/qt/locale/nyc3_nb.ts +++ b/src/qt/locale/nyc3_nb.ts @@ -330,7 +330,7 @@ Reindekserer blokker på harddisk... - Send coins to a Bitcoin address + Send coins to a NYC3 address Send til en Bitcoin-adresse @@ -734,7 +734,7 @@ Rediger utsendingsadresse - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. Den angitte adressen "%1" er ikke en gyldig Bitcoin-adresse. @@ -1278,7 +1278,7 @@ Ugyldig betalingsadresse %1 - URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. + URI cannot be parsed! This can be caused by an invalid NYC3 address or malformed URI parameters. URI kan ikke fortolkes! Dette kan være forårsaket av en ugyldig bitcoin-adresse eller feilformede URI-parametre. @@ -1380,7 +1380,7 @@ Beløp - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) Oppgi en Bitcoin-adresse (f.eks. %1) @@ -2193,7 +2193,7 @@ Antatt bekreftelsesbegynnelse innen %n blokk.Antatt bekreftelsesbegynnelse innen %n blokker. - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address Advarsel Ugyldig bitcoin-adresse @@ -2236,7 +2236,7 @@ Dette er en normal betaling. - The Bitcoin address to send the payment to + The NYC3 address to send the payment to Bitcoin-adressen betalingen skal sendes til @@ -2333,7 +2333,7 @@ Du kan signere meldinger/avtaler med adresser for å bevise at du kan motta bitcoins sendt til dem. Vær forsiktig med å signere noe vagt eller tilfeldig, siden phishing-angrep kan prøve å lure deg til å signere din identitet over til dem. Bare signer fullt detaljerte utsagn som du er enig i. - The Bitcoin address to sign the message with + The NYC3 address to sign the message with Bitcoin-adressen meldingen skal signeres med @@ -2365,7 +2365,7 @@ Kopier valgt signatur til utklippstavle - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address Signer meldingen for å bevise at du eier denne Bitcoin-adressen @@ -2389,11 +2389,11 @@ Skriv inn mottakerens adresse, melding (forsikre deg om at du kopier linjeskift, mellomrom, faner osv. nøyaktig) og underskrift nedenfor for å bekrefte meldingen. Vær forsiktig så du ikke leser mer ut av signaturen enn hva som er i den signerte meldingen i seg selv, for å unngå å bli lurt av et man-in-the-middle-angrep. Merk at dette bare beviser at den som signerer kan motta med adressen, dette beviser ikke hvem som har sendt transaksjoner! - The Bitcoin address the message was signed with + The NYC3 address the message was signed with Bitcoin-adressen meldingen ble signert med - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address Verifiser meldingen for å være sikker på at den ble signert av den angitte Bitcoin-adressen @@ -3037,8 +3037,8 @@ Kunne ikke starte HTTP-tjener. Se feilrettingslogg for detaljer. - Bitcoin Core - Bitcoin Core + NYC3 + NYC3 The %s developers diff --git a/src/qt/locale/nyc3_ne.ts b/src/qt/locale/nyc3_ne.ts index cfa36f73c..d141875c6 100644 --- a/src/qt/locale/nyc3_ne.ts +++ b/src/qt/locale/nyc3_ne.ts @@ -171,7 +171,7 @@ डिस्कमा ब्लकलाई पुनः सूचीकरण गरिँदै... - Send coins to a Bitcoin address + Send coins to a NYC3 address बिटकोइन ठेगानामा सिक्का पठाउनुहोस् @@ -296,7 +296,7 @@ रकम - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) कृपया बिटकोइन ठेगाना प्रवेश गर्नुहोस् (उदाहरण %1) diff --git a/src/qt/locale/nyc3_nl.ts b/src/qt/locale/nyc3_nl.ts index c9f3ae7d4..d5253d545 100644 --- a/src/qt/locale/nyc3_nl.ts +++ b/src/qt/locale/nyc3_nl.ts @@ -342,7 +342,7 @@ Proxy is <b>ingeschakeld</b>: %1 - Send coins to a Bitcoin address + Send coins to a NYC3 address Verstuur munten naar een Bitcoinadres @@ -804,7 +804,7 @@ Bewerk verzendadres - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. Het opgegeven adres "%1" is een ongeldig Bitcoinadres. @@ -1396,7 +1396,7 @@ Ongeldig betalingsadres %1 - URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. + URI cannot be parsed! This can be caused by an invalid NYC3 address or malformed URI parameters. URI kan niet verwerkt worden! Dit kan het gevolg zijn van een ongeldig Bitcoin adres of misvormde URI parameters. @@ -1498,7 +1498,7 @@ Bedrag - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) Voer een Bitcoinadres in (bijv. %1) @@ -2383,7 +2383,7 @@ Notitie: Omdat de vergoeding per byte wordt gerekend, zal een vergoeding van "10 Schatting is dat bevestiging begint over %n blok.Schatting is dat bevestiging begint over %n blokken. - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address Waarschuwing: Ongeldig Bitcoinadres @@ -2426,7 +2426,7 @@ Notitie: Omdat de vergoeding per byte wordt gerekend, zal een vergoeding van "10 Dit is een normale betaling. - The Bitcoin address to send the payment to + The NYC3 address to send the payment to Het Bitcoinadres om betaling aan te versturen @@ -2523,7 +2523,7 @@ Notitie: Omdat de vergoeding per byte wordt gerekend, zal een vergoeding van "10 U kunt berichten/overeenkomsten ondertekenen met uw adres om te bewijzen dat u Bitcoins kunt versturen. Wees voorzichtig met het ondertekenen van iets vaags of willekeurigs, omdat phishingaanvallen u kunnen proberen te misleiden tot het ondertekenen van overeenkomsten om uw identiteit aan hen toe te vertrouwen. Onderteken alleen volledig gedetailleerde verklaringen voordat u akkoord gaat. - The Bitcoin address to sign the message with + The NYC3 address to sign the message with Het Bitcoinadres om bericht mee te ondertekenen @@ -2555,7 +2555,7 @@ Notitie: Omdat de vergoeding per byte wordt gerekend, zal een vergoeding van "10 Kopieer de huidige handtekening naar het systeemklembord - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address Onderteken een bericht om te bewijzen dat u een bepaald Bitcoinadres bezit @@ -2579,11 +2579,11 @@ Notitie: Omdat de vergoeding per byte wordt gerekend, zal een vergoeding van "10 Voer het adres van de ontvanger in, bericht (zorg ervoor dat de regeleinden, spaties, tabs etc. precies kloppen) en onderteken onderaan om het bericht te verifiëren. Wees voorzicht om niet meer in de ondertekening te lezen dan in het getekende bericht zelf, om te voorkomen dat je wordt aangevallen met een man-in-the-middle attack. Houd er mee rekening dat dit alleen de ondertekende partij bewijst met het ontvangen adres, er kan niet bewezen worden dat er een transactie heeft plaatsgevonden! - The Bitcoin address the message was signed with + The NYC3 address the message was signed with Het Bitcoinadres waarmee het bericht ondertekend is - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address Controleer een bericht om te verifiëren dat het gespecificeerde Bitcoinadres het bericht heeft ondertekend. @@ -3251,8 +3251,8 @@ Notitie: Omdat de vergoeding per byte wordt gerekend, zal een vergoeding van "10 Niet mogelijk ok HTTP-server te starten. Zie debuglogboek voor details. - Bitcoin Core - Bitcoin Core + NYC3 + NYC3 The %s developers diff --git a/src/qt/locale/nyc3_pam.ts b/src/qt/locale/nyc3_pam.ts index fb41bedeb..7ae615f9e 100644 --- a/src/qt/locale/nyc3_pam.ts +++ b/src/qt/locale/nyc3_pam.ts @@ -122,8 +122,8 @@ &Alilan ing Passphrase... - Send coins to a Bitcoin address - Magpadalang barya king Bitcoin address + Send coins to a NYC3 address + Magpadalang barya king NYC3 address Backup wallet to another location @@ -659,8 +659,8 @@ Kopyan ing kasalungsungan pirma king system clipboard - Sign the message to prove you own this Bitcoin address - Pirman ing mensayi ban patune na keka ya ining Bitcoin address + Sign the message to prove you own this NYC3 address + Pirman ing mensayi ban patune na keka ya ining NYC3 address Sign &Message @@ -679,8 +679,8 @@ &Beripikan ing Mensayi - Verify the message to ensure it was signed with the specified Bitcoin address - Beripikan ing mensayi ban asiguradu a me pirma ya ini gamit ing mepiling Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address + Beripikan ing mensayi ban asiguradu a me pirma ya ini gamit ing mepiling NYC3 address Verify &Message @@ -735,7 +735,7 @@ bitcoin-core - Bitcoin Core + NYC3 Kapilubluban ning Bitcoin diff --git a/src/qt/locale/nyc3_pl.ts b/src/qt/locale/nyc3_pl.ts index 81c462c52..a0d331600 100644 --- a/src/qt/locale/nyc3_pl.ts +++ b/src/qt/locale/nyc3_pl.ts @@ -342,7 +342,7 @@ Proxy jest <b>włączone</b>: %1 - Send coins to a Bitcoin address + Send coins to a NYC3 address Wyślij monety na adres bitcoinowy @@ -780,7 +780,7 @@ Zmień adres wysyłania - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. Wprowadzony adres "%1" nie jest prawidłowym adresem Bitcoin. @@ -1352,7 +1352,7 @@ błędny adres płatności %1 - URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. + URI cannot be parsed! This can be caused by an invalid NYC3 address or malformed URI parameters. Nie można przeanalizować identyfikatora URI! Może to być spowodowane nieważnym adresem Bitcoin lub nieprawidłowymi parametrami URI. @@ -1454,7 +1454,7 @@ Kwota - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) Wprowadź adres bitcoinowy (np. %1) @@ -2320,7 +2320,7 @@ Uwaga: Ponieważ opłata jest naliczana za każdy bajt, opłata "100 satoshi za Przybliżony czas rozpoczęcia zatwierdzenia: %n blok.Przybliżony czas rozpoczęcia zatwierdzenia: %n bloki.Przybliżony czas rozpoczęcia zatwierdzenia: %n bloków.Przybliżony czas rozpoczęcia zatwierdzenia: %n bloków. - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address Ostrzeżenie: nieprawidłowy adres Bitcoin @@ -2363,7 +2363,7 @@ Uwaga: Ponieważ opłata jest naliczana za każdy bajt, opłata "100 satoshi za To jest standardowa płatność - The Bitcoin address to send the payment to + The NYC3 address to send the payment to Adres Bitcoin gdzie wysłać płatność @@ -2460,7 +2460,7 @@ Uwaga: Ponieważ opłata jest naliczana za każdy bajt, opłata "100 satoshi za Możesz podpisywać wiadomości swoimi adresami aby udowodnić, że jesteś ich właścicielem. Uważaj, aby nie podpisywać niczego co wzbudza Twoje podejrzenia, ponieważ ktoś może stosować phishing próbując nakłonić Cię do ich podpisania. Akceptuj i podpisuj tylko w pełni zrozumiałe komunikaty i wiadomości. - The Bitcoin address to sign the message with + The NYC3 address to sign the message with Adres Bitcoin, za pomocą którego podpisać wiadomość @@ -2492,7 +2492,7 @@ Uwaga: Ponieważ opłata jest naliczana za każdy bajt, opłata "100 satoshi za Kopiuje aktualny podpis do schowka systemowego - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address Podpisz wiadomość aby dowieść, że ten adres jest twój @@ -2517,11 +2517,11 @@ Uwaga: Ponieważ opłata jest naliczana za każdy bajt, opłata "100 satoshi za Zwróć uwagę, że poprawnie zweryfikowana wiadomość potwierdza to, że nadawca posiada klucz do adresu, natomiast nie potwierdza to, że poprawne wysłanie jakiejkolwiek transakcji! - The Bitcoin address the message was signed with + The NYC3 address the message was signed with Adres Bitcoin, którym została podpisana wiadomość - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address Zweryfikuj wiadomość, aby upewnić się, że została podpisana odpowiednim adresem Bitcoin. @@ -3177,8 +3177,8 @@ Zwróć uwagę, że poprawnie zweryfikowana wiadomość potwierdza to, że nadaw Uruchomienie serwera HTTP nie powiodło się. Zobacz dziennik debugowania, aby uzyskać więcej szczegółów. - Bitcoin Core - Bitcoin Core + NYC3 + NYC3 The %s developers diff --git a/src/qt/locale/nyc3_pt_BR.ts b/src/qt/locale/nyc3_pt_BR.ts index 1922da96f..02de3211e 100644 --- a/src/qt/locale/nyc3_pt_BR.ts +++ b/src/qt/locale/nyc3_pt_BR.ts @@ -342,7 +342,7 @@ Proxy <b>ativado</b>: %1 - Send coins to a Bitcoin address + Send coins to a NYC3 address Enviar moedas para um endereço bitcoin @@ -804,7 +804,7 @@ Editar endereço de envio - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. O endereço digitado "%1" não é um endereço válido. @@ -1396,7 +1396,7 @@ Endereço de pagamento %1 inválido - URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. + URI cannot be parsed! This can be caused by an invalid NYC3 address or malformed URI parameters. A URI não pode ser analisada! Isto pode ser causado por um endereço inválido ou um parâmetro URI malformado. @@ -1498,7 +1498,7 @@ Quantidade - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) Informe um endereço Bitcoin (ex: %1) @@ -2383,7 +2383,7 @@ Nota: Como a taxa é calculada por byte, uma taxa de "100 satoshis por kB" por Confirmação em %n bloco.Início estimado para confirmação em %n blocos. - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address Aviso: Endereço Bitcoin inválido @@ -2426,7 +2426,7 @@ Nota: Como a taxa é calculada por byte, uma taxa de "100 satoshis por kB" por Este é um pagamento normal. - The Bitcoin address to send the payment to + The NYC3 address to send the payment to O endereço Bitcoin para enviar o pagamento @@ -2523,7 +2523,7 @@ Nota: Como a taxa é calculada por byte, uma taxa de "100 satoshis por kB" por Você pode assinar mensagens com seus endereços para provar que você pode receber bitcoins enviados por alguém. Cuidado para não assinar nada vago ou aleatório, pois ataques phishing podem tentar te enganar para assinar coisas para eles como se fosse você. Somente assine termos bem detalhados que você concorde. - The Bitcoin address to sign the message with + The NYC3 address to sign the message with O endereço Bitcoin que assinará a mensagem @@ -2555,7 +2555,7 @@ Nota: Como a taxa é calculada por byte, uma taxa de "100 satoshis por kB" por Copiar a assinatura para a área de transferência do sistema - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address Assinar mensagem para provar que você é dono deste endereço Bitcoin @@ -2579,11 +2579,11 @@ Nota: Como a taxa é calculada por byte, uma taxa de "100 satoshis por kB" por Coloque o endereço do autor, a mensagem (certifique-se de copiar toda a mensagem, incluindo quebras de linha, espaços, tabulações, etc.) e a assinatura abaixo para verificar a mensagem. Cuidado para não compreender mais da assinatura do que está na mensagem assinada de fato, para evitar ser enganado por um ataque man-in-the-middle. Note que isso somente prova que o signatário recebe com este endereço, não pode provar que é o remetente de nenhuma transação! - The Bitcoin address the message was signed with + The NYC3 address the message was signed with O endereço Bitcoin que foi usado para assinar a mensagem - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address Verificar mensagem para se assegurar que ela foi assinada pelo dono de um endereço Bitcoin específico @@ -3251,8 +3251,8 @@ Nota: Como a taxa é calculada por byte, uma taxa de "100 satoshis por kB" por Não foi possível iniciar o servidor HTTP. Veja o log de depuração para detaihes. - Bitcoin Core - Bitcoin Core + NYC3 + NYC3 The %s developers diff --git a/src/qt/locale/nyc3_pt_PT.ts b/src/qt/locale/nyc3_pt_PT.ts index d3b941c60..8b5e1275b 100644 --- a/src/qt/locale/nyc3_pt_PT.ts +++ b/src/qt/locale/nyc3_pt_PT.ts @@ -342,7 +342,7 @@ Proxy está <b>ativado</b>: %1 - Send coins to a Bitcoin address + Send coins to a NYC3 address Enviar moedas para um endereço Bitcoin @@ -804,7 +804,7 @@ Editar o endereço de envio - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. O endereço introduzido "%1" não é um endereço bitcoin válido. @@ -1393,7 +1393,7 @@ Endereço de pagamento inválido %1 - URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. + URI cannot be parsed! This can be caused by an invalid NYC3 address or malformed URI parameters. URI não foi lido corretamente! Isto pode ser causado por um endereço Bitcoin inválido ou por parâmetros URI malformados. @@ -1495,7 +1495,7 @@ Quantia - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) Introduza um endereço Bitcoin (ex. %1) @@ -2373,7 +2373,7 @@ Nota: como a taxa é calculada por byte, uma taxa de "100 satoshis por kB" por u Pedido de pagamento expirado. - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address Aviso: endereço Bitcoin inválido @@ -2416,7 +2416,7 @@ Nota: como a taxa é calculada por byte, uma taxa de "100 satoshis por kB" por u Este é um pagamento normal. - The Bitcoin address to send the payment to + The NYC3 address to send the payment to O endereço Bitcoin para enviar o pagamento @@ -2513,7 +2513,7 @@ Nota: como a taxa é calculada por byte, uma taxa de "100 satoshis por kB" por u Pode assinar mensagens com os seus endereços para provar que são seus. Tenha atenção ao assinar mensagens ambíguas, pois ataques de phishing podem tentar enganá-lo de modo a assinar a sua identidade para os atacantes. Apenas assine declarações detalhadas com as quais concorde. - The Bitcoin address to sign the message with + The NYC3 address to sign the message with O endereço Bitcoin para designar a mensagem @@ -2545,7 +2545,7 @@ Nota: como a taxa é calculada por byte, uma taxa de "100 satoshis por kB" por u Copiar a assinatura atual para a área de transferência - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address Assine uma mensagem para provar que é dono deste endereço Bitcoin @@ -2569,11 +2569,11 @@ Nota: como a taxa é calculada por byte, uma taxa de "100 satoshis por kB" por u Introduza o endereço de assinatura, mensagem (assegure-se que copia quebras de linha, espaços, tabulações, etc. exatamente) e assinatura abaixo para verificar a mensagem. Tenha atenção para não ler mais na assinatura do que o que estiver na mensagem assinada, para evitar ser enganado por um atacante que se encontre entre si e quem assinou a mensagem. - The Bitcoin address the message was signed with + The NYC3 address the message was signed with O endereço Bitcoin com que a mensagem foi designada - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address Verifique a mensagem para assegurar que foi assinada com o endereço Bitcoin especificado @@ -3225,8 +3225,8 @@ Nota: como a taxa é calculada por byte, uma taxa de "100 satoshis por kB" por u Não é possível iniciar o servidor HTTP. Verifique o debug.log para detalhes. - Bitcoin Core - Bitcoin Core + NYC3 + NYC3 The %s developers diff --git a/src/qt/locale/nyc3_ro.ts b/src/qt/locale/nyc3_ro.ts index 6fe431494..4f47091a1 100644 --- a/src/qt/locale/nyc3_ro.ts +++ b/src/qt/locale/nyc3_ro.ts @@ -298,7 +298,7 @@ Click pentru a permite, din nou, activitate rețelei. - Send coins to a Bitcoin address + Send coins to a NYC3 address Trimite monedele către o adresă Bitcoin @@ -1271,8 +1271,8 @@ bitcoin-core - Bitcoin Core - Bitcoin Core + NYC3 + NYC3 Upgrading UTXO database diff --git a/src/qt/locale/nyc3_ro_RO.ts b/src/qt/locale/nyc3_ro_RO.ts index 2cc2b9668..79169b4f3 100644 --- a/src/qt/locale/nyc3_ro_RO.ts +++ b/src/qt/locale/nyc3_ro_RO.ts @@ -338,7 +338,7 @@ Proxy este<b>activat</b>:%1 - Send coins to a Bitcoin address + Send coins to a NYC3 address Trimite monede către o adresă Bitcoin @@ -748,7 +748,7 @@ Editează adresa de trimitere - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. Adresa introdusă "%1" nu este o adresă Bitcoin validă. @@ -1320,7 +1320,7 @@ Adresă pentru plată invalidă %1 - URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. + URI cannot be parsed! This can be caused by an invalid NYC3 address or malformed URI parameters. URI nu poate fi analizat! Acest lucru poate fi cauzat de o adresă Bitcoin invalidă sau parametri URI deformaţi. @@ -1422,7 +1422,7 @@ Cantitate - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) Introduceţi o adresă Bitcoin (de exemplu %1) @@ -2287,7 +2287,7 @@ Nota: Cum taxa este calculata per byte, o taxa de "100 satoshi per kB" pentru o Se estimeaza inceperea confirmarii in %n bloc.Se estimeaza inceperea confirmarii in %n blocuri.Se estimeaza inceperea confirmarii in %n blocuri. - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address Atenţie: Adresa bitcoin nevalidă! @@ -2330,7 +2330,7 @@ Nota: Cum taxa este calculata per byte, o taxa de "100 satoshi per kB" pentru o Aceasta este o tranzacţie normală. - The Bitcoin address to send the payment to + The NYC3 address to send the payment to Adresa bitcoin către care se face plata @@ -2427,7 +2427,7 @@ Nota: Cum taxa este calculata per byte, o taxa de "100 satoshi per kB" pentru o Puteţi semna mesaje/contracte cu adresele dvs. pentru a demostra ca puteti primi bitcoini trimisi la ele. Aveţi grijă să nu semnaţi nimic vag sau aleator, deoarece atacurile de tip phishing vă pot păcăli să le transferaţi identitatea. Semnaţi numai declaraţiile detaliate cu care sînteti de acord. - The Bitcoin address to sign the message with + The NYC3 address to sign the message with Adresa cu care semnaţi mesajul @@ -2459,7 +2459,7 @@ Nota: Cum taxa este calculata per byte, o taxa de "100 satoshi per kB" pentru o Copiază semnatura curentă în clipboard-ul sistemului - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address Semnează mesajul pentru a dovedi ca deţineţi acestă adresă Bitcoin @@ -2483,11 +2483,11 @@ Nota: Cum taxa este calculata per byte, o taxa de "100 satoshi per kB" pentru o Introduceţi adresa de semnatură, mesajul (asiguraţi-vă că aţi copiat spaţiile, taburile etc. exact) şi semnatura dedesubt pentru a verifica mesajul. Aveţi grijă să nu citiţi mai mult în semnatură decît mesajul în sine, pentru a evita să fiţi păcăliţi de un atac de tip man-in-the-middle. De notat ca aceasta dovedeste doar ca semnatarul primeste odata cu adresa, nu dovedesta insa trimiterea vreunei tranzactii. - The Bitcoin address the message was signed with + The NYC3 address the message was signed with Introduceţi o adresă Bitcoin - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address Verificaţi mesajul pentru a vă asigura că a fost semnat cu adresa Bitcoin specificată @@ -3139,7 +3139,7 @@ Nota: Cum taxa este calculata per byte, o taxa de "100 satoshi per kB" pentru o Imposibil de pornit serverul HTTP. Pentru detalii vezi logul de depanare. - Bitcoin Core + NYC3 Nucleul Bitcoin diff --git a/src/qt/locale/nyc3_ru_RU.ts b/src/qt/locale/nyc3_ru_RU.ts index 6ee597c73..8d647e1f9 100644 --- a/src/qt/locale/nyc3_ru_RU.ts +++ b/src/qt/locale/nyc3_ru_RU.ts @@ -342,7 +342,7 @@ Прокси <b>включен</b>: %1 - Send coins to a Bitcoin address + Send coins to a NYC3 address Послать средства на биткойн адрес @@ -367,7 +367,7 @@ Bitcoin - Bitcoin Core + NYC3 &Send @@ -804,7 +804,7 @@ Изменить адрес отправки - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. Введенный адрес "%1" не является действительным адресом Bitcoin. @@ -902,7 +902,7 @@ Bitcoin - Bitcoin Core + NYC3 At least %1 GB of data will be stored in this directory, and it will grow over time. @@ -1396,7 +1396,7 @@ Неверный адрес %1 - URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. + URI cannot be parsed! This can be caused by an invalid NYC3 address or malformed URI parameters. Не удалось обработать идентификатор! Это может быть связано с неверным Bitcoin-адресом или неправильными параметрами идентификатора. @@ -1498,7 +1498,7 @@ Количество - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) Введите биткоин-адрес (напр. %1) @@ -2375,7 +2375,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p Истекло время ожидания запроса платежа - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address Предупреждение: Неверный Bitcoin адрес @@ -2418,7 +2418,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p Это нормальный платёж. - The Bitcoin address to send the payment to + The NYC3 address to send the payment to Bitcoin-адрес, на который отправить платёж @@ -2515,7 +2515,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p Вы можете подписывать сообщения/соглашения своими адресами, чтобы доказать свою возможность получать биткоины на них. Будьте осторожны, не подписывайте что-то неопределённое или случайное, так как фишинговые атаки могут обманным путём заставить вас подписать нежелательные сообщения. Подписывайте только те сообщения, с которыми вы согласны вплоть до мелочей. - The Bitcoin address to sign the message with + The NYC3 address to sign the message with Bitcoin-адрес, которым подписать сообщение @@ -2547,7 +2547,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p Скопировать текущую подпись в буфер обмена системы - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address Подписать сообщение, чтобы доказать владение Bitcoin-адресом @@ -2571,11 +2571,11 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p Введите ниже адрес получателя, сообщение (убедитесь, что переводы строк, пробелы, табы и т.п. в точности скопированы) и подпись, чтобы проверить сообщение. Убедитесь, что не скопировали лишнего в подпись, по сравнению с самим подписываемым сообщением, чтобы не стать жертвой атаки "man-in-the-middle". Заметьте, что эта операция удостоверяет лишь авторство подписавшего, но не может удостоверить отправителя транзакции. - The Bitcoin address the message was signed with + The NYC3 address the message was signed with Bitcoin-адрес, которым было подписано сообщение - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address Проверить сообщение, чтобы убедиться, что оно было подписано указанным Bitcoin-адресом @@ -3239,8 +3239,8 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p Невозможно запустить HTTP-сервер. Для получения более детальной информации необходимо обратиться к журналу отладки. - Bitcoin Core - Bitcoin Core + NYC3 + NYC3 The %s developers diff --git a/src/qt/locale/nyc3_sk.ts b/src/qt/locale/nyc3_sk.ts index d6c2c19dc..241a90036 100644 --- a/src/qt/locale/nyc3_sk.ts +++ b/src/qt/locale/nyc3_sk.ts @@ -342,7 +342,7 @@ Proxy je <b>zapnuté</b>: %1 - Send coins to a Bitcoin address + Send coins to a NYC3 address Poslať bitcoins na adresu @@ -804,7 +804,7 @@ Upraviť odosielaciu adresu - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. Vložená adresa "%1" nieje platnou adresou Bitcoin. @@ -1396,7 +1396,7 @@ Neplatná adresa platby %1 - URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. + URI cannot be parsed! This can be caused by an invalid NYC3 address or malformed URI parameters. URI sa nedá analyzovať! To môže byť spôsobené neplatnou Bitcoin adresou alebo zle nastavenými vlastnosťami URI. @@ -1498,7 +1498,7 @@ Suma - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) Zadajte bitcoin adresu (napr. %1) @@ -2384,7 +2384,7 @@ Poznámka: Keďže poplatok je počítaný za bajt, poplatok o hodnote "100 sato Odhadovaný začiatok potvrdzovania po %n bloku.Odhadovaný začiatok potvrdzovania po %n blokoch.Odhadovaný začiatok potvrdzovania po %n blokoch.Odhadovaný začiatok potvrdzovania po %n blokoch. - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address Varovanie: Neplatná Bitcoin adresa @@ -2427,7 +2427,7 @@ Poznámka: Keďže poplatok je počítaný za bajt, poplatok o hodnote "100 sato Toto je normálna platba. - The Bitcoin address to send the payment to + The NYC3 address to send the payment to Zvoľte adresu kam poslať platbu @@ -2524,7 +2524,7 @@ Poznámka: Keďže poplatok je počítaný za bajt, poplatok o hodnote "100 sato Môžete podpísať správy svojou adresou a dokázať, že viete prijímať mince zaslané na túto adresu. Buďte však opatrní a podpíšte len podrobné prehlásenia, s ktorými plne súhlasíte, nakoľko útoky typu "phishing" Vás môžu lákať k podpísaniu nejasných alebo príliš všeobecných tvrdení čím prevezmú vašu identitu. - The Bitcoin address to sign the message with + The NYC3 address to sign the message with Bitcoin adresa pre podpísanie správy s @@ -2556,7 +2556,7 @@ Poznámka: Keďže poplatok je počítaný za bajt, poplatok o hodnote "100 sato Kopírovať tento podpis do systémovej schránky - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address Podpíšte správu aby ste dokázali že vlastníte túto adresu @@ -2580,11 +2580,11 @@ Poznámka: Keďže poplatok je počítaný za bajt, poplatok o hodnote "100 sato Vložte adresu príjemcu, správu (uistite sa, že presne kopírujete ukončenia riadkov, medzery, odrážky, atď.) a podpis pre potvrdenie správy. Buďte opatrní a nedomýšľajte si viac než je uvedené v samotnej podpísanej správe a môžete sa tak vyhnúť podvodu MITM útokom. Toto len potvrdzuje, že podpisujúca strana môže prijímať na tejto adrese, nepotvrdzuje to vlastníctvo žiadnej transakcie! - The Bitcoin address the message was signed with + The NYC3 address the message was signed with Adresa Bitcoin, ktorou bola podpísaná správa - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address Overím správy sa uistiť že bola podpísaná označenou Bitcoin adresou @@ -3252,8 +3252,8 @@ Poznámka: Keďže poplatok je počítaný za bajt, poplatok o hodnote "100 sato Nepodarilo sa spustiť HTTP server. Pre viac detailov zobrazte debug log. - Bitcoin Core - Bitcoin Core + NYC3 + NYC3 The %s developers diff --git a/src/qt/locale/nyc3_sl_SI.ts b/src/qt/locale/nyc3_sl_SI.ts index 5f1d6b528..7da4ac73d 100644 --- a/src/qt/locale/nyc3_sl_SI.ts +++ b/src/qt/locale/nyc3_sl_SI.ts @@ -334,7 +334,7 @@ Namestniški strežnik je omogočen</b>: %1 - Send coins to a Bitcoin address + Send coins to a NYC3 address Izvedite plačilo na naslov Bitcoin @@ -1020,7 +1020,7 @@ Znesek - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) Vnesite naslov Bitcoin (npr. %1): @@ -1508,7 +1508,7 @@ Plačilo je navadne vrste. - The Bitcoin address to send the payment to + The NYC3 address to send the payment to Naslov Bitcoin, na katerega bo plačilo poslano @@ -1589,7 +1589,7 @@ S svojimi naslovi lahko podpisujete sporočila ali pogodbe in s tem dokazujete, da na teh naslovih lahko prejemate kovance. Bodite previdni in ne podpisujte ničesar nejasnega ali naključnega, ker vas zlikovci preko ribarjenja (phishing) lahko prelisičijo, da na njih prepišete svojo identiteto. Podpisujte samo podrobno opisane izjave, s katerimi se strinjate. - The Bitcoin address to sign the message with + The NYC3 address to sign the message with Naslov Bitcoin, s katerim podpisujete sporočilo @@ -1621,7 +1621,7 @@ Kopiranje trenutnega podpisa na sistemsko odložišče. - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address Podpišite sporočilo, da dokažete lastništvo nad zgornjim naslovom. @@ -1645,11 +1645,11 @@ Da preverite verodostojnost sporočila, spodaj vnesite: prejemnikov naslov, prejeto sporočilo (pazljivo skopirajte vse prelome vrstic, presledke, tabulatorje ipd.,) in prejeti podpis. Da se izognete napadom tipa man-in-the-middle, vedite, da iz veljavnega podpisa ne sledi nič drugega, kot tisto, kar je navedeno v sporočilu. Podpis samo potrjuje dejstvo, da ima podpisnik v lasti prejemni naslov, ne more pa dokazati vira nobene transakcije! - The Bitcoin address the message was signed with + The NYC3 address the message was signed with Naslov Bitcoin, s katerim je bilo sporočilo podpisano - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address Preverite, ali je bilo sporočilo v resnici podpisano z navedenim naslovom Bitcoin. @@ -1745,8 +1745,8 @@ bitcoin-core - Bitcoin Core - Bitcoin Core + NYC3 + NYC3 Corrupted block database detected diff --git a/src/qt/locale/nyc3_sn.ts b/src/qt/locale/nyc3_sn.ts index f344e0e5e..0cef82631 100644 --- a/src/qt/locale/nyc3_sn.ts +++ b/src/qt/locale/nyc3_sn.ts @@ -182,7 +182,7 @@ Marii - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) Nyora kero ye Bitcoin (sekuti %1) diff --git a/src/qt/locale/nyc3_sq.ts b/src/qt/locale/nyc3_sq.ts index d839c8fc0..97185c93d 100644 --- a/src/qt/locale/nyc3_sq.ts +++ b/src/qt/locale/nyc3_sq.ts @@ -787,7 +787,7 @@ bitcoin-core - Bitcoin Core + NYC3 Berthama Bitcoin diff --git a/src/qt/locale/nyc3_sr.ts b/src/qt/locale/nyc3_sr.ts index 1355bc32d..9d906c2b3 100644 --- a/src/qt/locale/nyc3_sr.ts +++ b/src/qt/locale/nyc3_sr.ts @@ -338,7 +338,7 @@ Прокси је <b>омогућен</b>: %1 - Send coins to a Bitcoin address + Send coins to a NYC3 address Пошаљите новац на Биткоин адресу diff --git a/src/qt/locale/nyc3_sr@latin.ts b/src/qt/locale/nyc3_sr@latin.ts index 57dab56c9..283c91fed 100644 --- a/src/qt/locale/nyc3_sr@latin.ts +++ b/src/qt/locale/nyc3_sr@latin.ts @@ -322,7 +322,7 @@ Ponovo obeležavam blokove na disku... - Send coins to a Bitcoin address + Send coins to a NYC3 address Pošalji novčiće na Bitcoin adresu @@ -677,8 +677,8 @@ bitcoin-core - Bitcoin Core - Bitcoin Core + NYC3 + NYC3 Information diff --git a/src/qt/locale/nyc3_sv.ts b/src/qt/locale/nyc3_sv.ts index e91dbffb6..291924ee4 100644 --- a/src/qt/locale/nyc3_sv.ts +++ b/src/qt/locale/nyc3_sv.ts @@ -343,7 +343,7 @@ Var vänlig och försök igen. Proxy är <b> aktiverad </b>: %1 - Send coins to a Bitcoin address + Send coins to a NYC3 address Skicka bitcoin till en Bitcoin-adress @@ -805,7 +805,7 @@ Var vänlig och försök igen. Redigera avsändaradress - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. Den angivna adressen "%1" är inte en giltig Bitcoin-adress. @@ -1389,7 +1389,7 @@ Var vänlig och försök igen. Ogiltig betalningsadress %1 - URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. + URI cannot be parsed! This can be caused by an invalid NYC3 address or malformed URI parameters. URI kan inte parsas! Detta kan orsakas av en ogiltig Bitcoin-adress eller felaktiga URI-parametrar. @@ -1491,7 +1491,7 @@ Var vänlig och försök igen. Mängd - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) Ange en Bitcoin-adress (t.ex. %1) @@ -2356,7 +2356,7 @@ Notera: Då avgiften beräknas per byte kommer en avgift på 50 satoshi tas ut f Uppskattas till att påbörja bekräftelse inom %n block.Uppskattas till att påbörja bekräftelse inom %n block. - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address Varning: Ogiltig Bitcoin-adress @@ -2399,7 +2399,7 @@ Notera: Då avgiften beräknas per byte kommer en avgift på 50 satoshi tas ut f Detta är en normal betalning. - The Bitcoin address to send the payment to + The NYC3 address to send the payment to Bitcoin-adress att sända betalning till @@ -2496,7 +2496,7 @@ Notera: Då avgiften beräknas per byte kommer en avgift på 50 satoshi tas ut f Du kan signera meddelanden/avtal med dina adresser för att bevisa att du kan ta emot bitcoin som skickats till dem. Var försiktig så du inte signerar något oklart eller konstigt, eftersom phishing-angrepp kan försöka få dig att signera över din identitet till dem. Signera endast väldetaljerade meddelanden som du godkänner. - The Bitcoin address to sign the message with + The NYC3 address to sign the message with Bitcoin-adress att signera meddelandet med @@ -2528,7 +2528,7 @@ Notera: Då avgiften beräknas per byte kommer en avgift på 50 satoshi tas ut f Kopiera signaturen till systemets Urklipp - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address Signera meddelandet för att bevisa att du äger denna Bitcoin-adress @@ -2552,11 +2552,11 @@ Notera: Då avgiften beräknas per byte kommer en avgift på 50 satoshi tas ut f Ange mottagarens adress, meddelande (kopiera radbrytningar, mellanslag, TAB-tecken, osv. exakt) och signatur nedan, för att verifiera meddelandet. Undvik att läsa in mera information i signaturen än vad som stod i själva det signerade meddelandet, för att undvika ett man-in-the-middle-angrepp. Notera att detta endast bevisar att den signerande parten tar emot med adressen, det bevisar inte vem som skickat transaktionen! - The Bitcoin address the message was signed with + The NYC3 address the message was signed with Bitcoin-adress som meddelandet signerades med - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address Verifiera meddelandet för att vara säker på att det signerades med angiven Bitcoin-adress @@ -3220,8 +3220,8 @@ Notera: Då avgiften beräknas per byte kommer en avgift på 50 satoshi tas ut f Kunde inte starta HTTP-server. Se avlusningsloggen för detaljer. - Bitcoin Core - Bitcoin Core + NYC3 + NYC3 The %s developers diff --git a/src/qt/locale/nyc3_szl.ts b/src/qt/locale/nyc3_szl.ts index 550b88b6b..4088ef606 100644 --- a/src/qt/locale/nyc3_szl.ts +++ b/src/qt/locale/nyc3_szl.ts @@ -338,7 +338,7 @@ Proxy je <b>zapuszczone</b>: %1 - Send coins to a Bitcoin address + Send coins to a NYC3 address Poślij mōnety na adresã Bitcoin @@ -748,7 +748,7 @@ Edytuj adresã posyłaniŏ - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. Wkludzōnŏ adresa "%1" niyma nŏleżnōm adresōm Bitcoin. @@ -1218,7 +1218,7 @@ Kwota - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) Wkludź adresã Bitcoin (bp. %1) @@ -1643,7 +1643,7 @@ Utworzynie transakcyje niy podarziło sie! - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address Pozōr: niynŏleżnŏ adresa Bitcoin @@ -1666,7 +1666,7 @@ To je normalny płat. - The Bitcoin address to send the payment to + The NYC3 address to send the payment to Adresa Bitcoin, na kerõ chcesz posłać płat @@ -1955,8 +1955,8 @@ bitcoin-core - Bitcoin Core - Bitcoin Core + NYC3 + NYC3 The %s developers diff --git a/src/qt/locale/nyc3_ta.ts b/src/qt/locale/nyc3_ta.ts index 7474be077..e1b9efccb 100644 --- a/src/qt/locale/nyc3_ta.ts +++ b/src/qt/locale/nyc3_ta.ts @@ -306,7 +306,7 @@ வட்டில் தொகுதிகளை மறுஇயக்குகிறது ... - Send coins to a Bitcoin address + Send coins to a NYC3 address ஒரு விக்கிபீடியா முகவரிக்கு நாணயங்களை அனுப்பவும் @@ -1192,7 +1192,7 @@ கட்டண கோரிக்கையை செயல்படுத்த முடியவில்லை, ஏனெனில் BIP70 ஆதரவு தொகுக்கப்படவில்லை. - URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. + URI cannot be parsed! This can be caused by an invalid NYC3 address or malformed URI parameters. URI அலச முடியாது! தவறான பிட்கின் முகவரி அல்லது தவறான URI அளவுருக்கள் காரணமாக இது ஏற்படலாம். @@ -2131,7 +2131,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p bitcoin-core - Bitcoin Core + NYC3 Bitcoin மையம் diff --git a/src/qt/locale/nyc3_th_TH.ts b/src/qt/locale/nyc3_th_TH.ts index 05775ea50..8bb1c73e9 100644 --- a/src/qt/locale/nyc3_th_TH.ts +++ b/src/qt/locale/nyc3_th_TH.ts @@ -166,7 +166,7 @@ กำลังทำดัชนี ที่เก็บบล็อก ใหม่ ในดิสก์... - Send coins to a Bitcoin address + Send coins to a NYC3 address ส่ง coins ไปยัง ที่เก็บ Bitcoin diff --git a/src/qt/locale/nyc3_tr.ts b/src/qt/locale/nyc3_tr.ts index 280390f8d..b2ddef95b 100644 --- a/src/qt/locale/nyc3_tr.ts +++ b/src/qt/locale/nyc3_tr.ts @@ -338,7 +338,7 @@ Tünelleme <b>etkin</b>: %1 - Send coins to a Bitcoin address + Send coins to a NYC3 address Bir bitcoin adresine bitcoin gönder @@ -752,7 +752,7 @@ Gönderi adresini düzenle - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. Girilen "%1" adresi geçerli bir Bitcoin adresi değildir. @@ -1304,7 +1304,7 @@ %1 ödeme adresi geçersizdir - URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. + URI cannot be parsed! This can be caused by an invalid NYC3 address or malformed URI parameters. URI ayrıştırılamıyor! Bunun nedeni geçersiz bir Bitcoin adresi veya hatalı biçimlendirilmiş URI değişkenleri olabilir. @@ -1406,7 +1406,7 @@ Tutar - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) Bir Bitcoin adresi giriniz (mesela %1) @@ -2235,7 +2235,7 @@ Ödeme talebinin geçerlilik süresi bitti. - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address Uyarı: geçersiz Bitcoin adresi @@ -2278,7 +2278,7 @@ Bu, normal bir ödemedir. - The Bitcoin address to send the payment to + The NYC3 address to send the payment to Ödemenin yollanacağı Bitcoin adresi @@ -2375,7 +2375,7 @@ Adreslerinize yollanan bitcoinleri alabileceğiniz ispatlamak için adreslerinizle iletiler/anlaşmalar imzalayabilirsiniz. Oltalama saldırılarının kimliğinizi imzanızla elde etmeyi deneyebilecekleri için belirsiz ya da rastgele hiçbir şey imzalamamaya dikkat ediniz. Sadece ayrıntılı açıklaması olan ve tümüne katıldığınız ifadeleri imzalayınız. - The Bitcoin address to sign the message with + The NYC3 address to sign the message with İletinin imzalanmasında kullanılacak Bitcoin adresi @@ -2407,7 +2407,7 @@ Güncel imzayı sistem panosuna kopyala - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address Bu Bitcoin adresinin sizin olduğunu ispatlamak için iletiyi imzalayın @@ -2431,11 +2431,11 @@ Alıcının adresini, iletiyi (satır sonları, boşluklar, sekmeler vs. karakterleri tam olarak kopyaladığınızdan emin olunuz) ve imzayı aşağıya giriniz. Bir ortadaki adam saldırısı tarafından kandırılmaya engel olmak için imzadan, imzalı iletinin içeriğini aşan bir anlam çıkarmamaya dikkat ediniz. Bunun sadece imzalayan tarafın adres ile alım yapabildiğini ispatladığını ve herhangi bir işlemin gönderi tarafını kanıtlayamayacağını unutmayınız! - The Bitcoin address the message was signed with + The NYC3 address the message was signed with İletinin imzalanmasında kullanılan Bitcoin adresi - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address Belirtilen Bitcoin adresi ile imzalandığını doğrulamak için iletiyi kontrol et @@ -3079,7 +3079,7 @@ HTTP sunucusu başlatılamadı. Ayrıntılar için debug.log dosyasına bakınız. - Bitcoin Core + NYC3 Bitcoin Çekirdeği diff --git a/src/qt/locale/nyc3_tr_TR.ts b/src/qt/locale/nyc3_tr_TR.ts index 457e83667..fafe65790 100644 --- a/src/qt/locale/nyc3_tr_TR.ts +++ b/src/qt/locale/nyc3_tr_TR.ts @@ -286,7 +286,7 @@ Bloklar disk üzerinde yeniden indeksleniyor... - Send coins to a Bitcoin address + Send coins to a NYC3 address Bitcoin adresine madeni para gönderin @@ -458,7 +458,7 @@ Gönderim adresini düzenleyin - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. Girilen adres "%1" Bitcoin adresiyle eşleşmiyor. @@ -709,7 +709,7 @@ QObject - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) Bitcoin adresinizi girin (örneğin %1) @@ -1094,7 +1094,7 @@ Coin gönderimini onaylayın - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address Uyarı: Hatalı Bitcoin adresi @@ -1390,7 +1390,7 @@ bitcoin-core - Bitcoin Core + NYC3 Bitcoin Çekirdeği diff --git a/src/qt/locale/nyc3_uk.ts b/src/qt/locale/nyc3_uk.ts index ab50b2a35..c902a541b 100644 --- a/src/qt/locale/nyc3_uk.ts +++ b/src/qt/locale/nyc3_uk.ts @@ -342,7 +342,7 @@ Проксі <b>увімкнено</b>: %1 - Send coins to a Bitcoin address + Send coins to a NYC3 address Відправити монети на вказану адресу @@ -776,7 +776,7 @@ Редагувати адресу для відправлення - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. Введена адреса "%1" не є адресою в мережі Bitcoin. @@ -1352,7 +1352,7 @@ Помилка в адресі платежу %1 - URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. + URI cannot be parsed! This can be caused by an invalid NYC3 address or malformed URI parameters. Неможливо обробити URI! Причиною цього може бути некоректна Біткойн-адреса або неправильні параметри URI. @@ -1456,7 +1456,7 @@ Кількість - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) Введіть адресу Bitcoin (наприклад %1) @@ -2341,7 +2341,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p Очікуваний початок підтвердження через %n блок.Очікуваний початок підтвердження протягом %n блоків.Очікуваний початок підтвердження протягом %n блоків.Очікуваний початок підтвердження протягом %n блоків. - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address Увага: Неприпустима Біткойн-адреса. @@ -2384,7 +2384,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p Це звичайний платіж. - The Bitcoin address to send the payment to + The NYC3 address to send the payment to Адреса Bitcoin для відправлення платежу @@ -2481,7 +2481,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p Ви можете підписувати повідомлення/угоди своїми адресами, щоб довести можливість отримання біткоінів, що будуть надіслані на них. Остерігайтеся підписувати будь-що нечітке чи неочікуване, так як за допомогою фішинг-атаки вас можуть спробувати ввести в оману для отримання вашого підпису під чужими словами. Підписуйте лише чіткі твердження, з якими ви повністю згодні. - The Bitcoin address to sign the message with + The NYC3 address to sign the message with Адреса Bitcoin для підпису цього повідомлення @@ -2513,7 +2513,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p Копіювати поточну сигнатуру до системного буферу обміну - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address Підпишіть повідомлення щоб довести, що ви є власником цієї адреси @@ -2537,11 +2537,11 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p Введіть нижче адресу отримувача, повідомлення (впевніться, що ви точно скопіювали символи завершення рядка, табуляцію, пробіли тощо) та підпис для перевірки повідомлення. Впевніться, що в підпис не було додано зайвих символів: це допоможе уникнути атак типу «людина посередині». Зауважте, що це лише засвідчує можливість отримання транзакцій підписувачем, але не в стані підтвердити джерело жодної транзакції! - The Bitcoin address the message was signed with + The NYC3 address the message was signed with Адреса Bitcoin, якою було підписано це повідомлення - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address Перевірте повідомлення для впевненості, що воно підписано вказаною Bitcoin-адресою @@ -3197,8 +3197,8 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p Неможливо запустити HTTP-сервер. Детальніший опис наведено в журналі зневадження. - Bitcoin Core - Bitcoin Core + NYC3 + NYC3 The %s developers diff --git a/src/qt/locale/nyc3_uz@Cyrl.ts b/src/qt/locale/nyc3_uz@Cyrl.ts index a730273ab..f0c5f6749 100644 --- a/src/qt/locale/nyc3_uz@Cyrl.ts +++ b/src/qt/locale/nyc3_uz@Cyrl.ts @@ -138,7 +138,7 @@ Дискдаги блоклар қайта индексланмоқда... - Send coins to a Bitcoin address + Send coins to a NYC3 address Тангаларни Bitcoin манзилига жўнатиш @@ -662,7 +662,7 @@ Миқдори - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) Bitcoin манзилини киритинг (масалан. %1) @@ -1163,8 +1163,8 @@ bitcoin-core - Bitcoin Core - Bitcoin Core + NYC3 + NYC3 Information diff --git a/src/qt/locale/nyc3_vi.ts b/src/qt/locale/nyc3_vi.ts index c311637fd..dc5ea6824 100644 --- a/src/qt/locale/nyc3_vi.ts +++ b/src/qt/locale/nyc3_vi.ts @@ -338,7 +338,7 @@ Proxy là <b> cho phép </b>: %1 - Send coins to a Bitcoin address + Send coins to a NYC3 address Gửi coin đến một địa chỉ Bitcoin @@ -770,8 +770,8 @@ Edit address đang gửi - The entered address "%1" is not a valid Bitcoin address. - Address đã nhập "%1" không valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. + Address đã nhập "%1" không valid NYC3 address. Could not unlock wallet. @@ -1290,8 +1290,8 @@ Invalid payment address %1 - URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. - URI không thể phân tích cú pháp! Đây có thể gây nên bởi invalid Bitcoin address hoặc URI không đúng định dạng tham số. + URI cannot be parsed! This can be caused by an invalid NYC3 address or malformed URI parameters. + URI không thể phân tích cú pháp! Đây có thể gây nên bởi invalid NYC3 address hoặc URI không đúng định dạng tham số. Payment request file handling @@ -1392,8 +1392,8 @@ Số lượng - Enter a Bitcoin address (e.g. %1) - Nhập một Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) + Nhập một NYC3 address (e.g. %1) %1 d @@ -2181,8 +2181,8 @@ Dự kiến bắt đầu xác nhận trong vòng %n blocks. - Warning: Invalid Bitcoin address - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address + Warning: Invalid NYC3 address Warning: Unknown change address @@ -2224,8 +2224,8 @@ Đây là một thông thường payment. - The Bitcoin address to send the payment to - The Bitcoin address để gửi the payment đến + The NYC3 address to send the payment to + The NYC3 address để gửi the payment đến Alt+A @@ -2317,8 +2317,8 @@ Bạn có thể ký/đồng ý với địa chỉ chứng minh bạn có thể receive bitcoins đã gửi đến chúng. Cẩn thận không ký bất cứ không rõ hay random, như các cuộc tấn công lừa đảo có thể cố lừa bạn ký tên vào danh tính của bạn.. Chỉ ký các bản tuyên bố hoàn chỉnh mà bạn đồng ý. - The Bitcoin address to sign the message with - The Bitcoin address để ký với tin nhắn + The NYC3 address to sign the message with + The NYC3 address để ký với tin nhắn Choose previously used address @@ -2349,8 +2349,8 @@ Copy hiện tại signature tới system clipboard - Sign the message to prove you own this Bitcoin address - Ký tin nhắn để chứng minh bạn sở hữu Bitcoin address này + Sign the message to prove you own this NYC3 address + Ký tin nhắn để chứng minh bạn sở hữu NYC3 address này Sign &Message @@ -2373,12 +2373,12 @@ Nhập vào address người nhận, tin nhắn (chắc rằng bạn copy line breaks, khoảng trống, tabs, etc. chính xác) và signature bên dưới verify tin nhắn. Cẩn thận không đọc nhiều hơn từ signature so với cái được ký trong bản thân tin nhắn, để tránh bị lừa bới man-in-the-middle tấn công. Lưu ý rằng điều này chỉ chứng nhận nhóm những người nhân với address, nó không thể chứng minh bên gửi có bất kỳ transaction! - The Bitcoin address the message was signed with - The Bitcoin address tin nhắn đã ký với + The NYC3 address the message was signed with + The NYC3 address tin nhắn đã ký với - Verify the message to ensure it was signed with the specified Bitcoin address - Verify tin nhắn để chắc rằng nó đã được ký với xác định Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address + Verify tin nhắn để chắc rằng nó đã được ký với xác định NYC3 address Verify &Message @@ -3025,8 +3025,8 @@ Unable to start HTTP server. See debug log for details. - Bitcoin Core - Bitcoin Core + NYC3 + NYC3 The %s developers diff --git a/src/qt/locale/nyc3_vi_VN.ts b/src/qt/locale/nyc3_vi_VN.ts index 9c678fd5c..fe3e57001 100644 --- a/src/qt/locale/nyc3_vi_VN.ts +++ b/src/qt/locale/nyc3_vi_VN.ts @@ -319,7 +319,7 @@ Ví của bạn chưa được mã hóa. Đánh chỉ số (indexing) lại các khối (blocks) trên ổ đĩa ... - Send coins to a Bitcoin address + Send coins to a NYC3 address Gửi coins đến tài khoản Bitcoin @@ -1182,8 +1182,8 @@ Ví của bạn chưa được mã hóa. bitcoin-core - Bitcoin Core - Bitcoin Core + NYC3 + NYC3 Information diff --git a/src/qt/locale/nyc3_zh.ts b/src/qt/locale/nyc3_zh.ts index 53a7552bc..7a46fcd18 100644 --- a/src/qt/locale/nyc3_zh.ts +++ b/src/qt/locale/nyc3_zh.ts @@ -258,7 +258,7 @@ 启用代理:%1 - Send coins to a Bitcoin address + Send coins to a NYC3 address 发送比特币到一个比特币地址 @@ -512,7 +512,7 @@ 与此地址列表项关联的地址。只能修改为发送地址。 - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. 输入的地址"%1"不是有效的比特币地址。 @@ -726,7 +726,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p 估计在%n块内确认。 - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address 警告：比特币地址无效 @@ -749,7 +749,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p 这是一个标准的付款方式。 - The Bitcoin address to send the payment to + The NYC3 address to send the payment to 支付到的比特币地址 diff --git a/src/qt/locale/nyc3_zh_CN.ts b/src/qt/locale/nyc3_zh_CN.ts index f1227a521..9b0b0bc74 100644 --- a/src/qt/locale/nyc3_zh_CN.ts +++ b/src/qt/locale/nyc3_zh_CN.ts @@ -342,7 +342,7 @@ 代理已被<b>启用</b>：%1 - Send coins to a Bitcoin address + Send coins to a NYC3 address 向一个比特币地址发送比特币 @@ -803,7 +803,7 @@ 编辑付款地址 - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. 输入的地址 %1 并不是有效的比特币地址。 @@ -1392,7 +1392,7 @@ 无效的付款地址 %1 - URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. + URI cannot be parsed! This can be caused by an invalid NYC3 address or malformed URI parameters. 无法解析 URI 地址！可能是因为比特币地址无效，或是 URI 参数格式错误。 @@ -1490,7 +1490,7 @@ 金额 - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) 请输入一个比特币地址 (例如 %1) @@ -2371,7 +2371,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p 预计在等待 %n 个区块后会有第一个确认。 - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address 警告: 比特币地址无效 @@ -2414,7 +2414,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p 这是笔正常的支付。 - The Bitcoin address to send the payment to + The NYC3 address to send the payment to 付款目的地址 @@ -2511,7 +2511,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p 您可以用你的地址对消息/协议进行签名，以证明您可以接收发送到该地址的比特币。注意不要对任何模棱两可或者随机的消息进行签名，以免遭受钓鱼式攻击。请确保消息内容准确的表达了您的真实意愿。 - The Bitcoin address to sign the message with + The NYC3 address to sign the message with 用来对消息签名的地址 @@ -2543,7 +2543,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p 复制当前签名至剪切板 - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address 签名消息，证明这个地址属于您。 @@ -2567,11 +2567,11 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p 请在下面输入接收者地址、消息（确保换行符、空格符、制表符等完全相同）和签名以验证消息。请仔细核对签名信息，以提防中间人攻击。请注意，这只是证明接收方签名的地址，它不能证明任何交易！ - The Bitcoin address the message was signed with + The NYC3 address the message was signed with 消息使用的签名地址 - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address 验证消息，确保消息是由指定的比特币地址签名过的。 @@ -3239,8 +3239,8 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p 无法启动HTTP服务，查看日志获取更多信息 - Bitcoin Core - Bitcoin Core + NYC3 + NYC3 The %s developers diff --git a/src/qt/locale/nyc3_zh_HK.ts b/src/qt/locale/nyc3_zh_HK.ts index 1165fef74..162016aba 100644 --- a/src/qt/locale/nyc3_zh_HK.ts +++ b/src/qt/locale/nyc3_zh_HK.ts @@ -306,7 +306,7 @@ 正在為磁碟區塊重建索引... - Send coins to a Bitcoin address + Send coins to a NYC3 address 付款至一個 Bitcoin 位址 @@ -448,7 +448,7 @@ QObject - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) 輸入一個 Bitcoin 位址 (例如 %1) diff --git a/src/qt/locale/nyc3_zh_TW.ts b/src/qt/locale/nyc3_zh_TW.ts index a9fe99a87..46985fd6a 100644 --- a/src/qt/locale/nyc3_zh_TW.ts +++ b/src/qt/locale/nyc3_zh_TW.ts @@ -342,7 +342,7 @@ 代理伺服器<b>已經啟用</b>: %1 - Send coins to a Bitcoin address + Send coins to a NYC3 address 付錢給一個 Bitcoin 位址 @@ -788,7 +788,7 @@ 編輯付款位址 - The entered address "%1" is not a valid Bitcoin address. + The entered address "%1" is not a valid NYC3 address. 輸入的位址 %1 並不是有效的 Bitcoin 位址。 @@ -1364,7 +1364,7 @@ 無效的付款位址 %1 - URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters. + URI cannot be parsed! This can be caused by an invalid NYC3 address or malformed URI parameters. 沒辦法解析 URI 位址！可能是因為 Bitcoin 位址無效，或是 URI 參數格式錯誤。 @@ -1466,7 +1466,7 @@ 金額 - Enter a Bitcoin address (e.g. %1) + Enter a NYC3 address (e.g. %1) 輸入 Bitcoin 位址 (比如說 %1) @@ -2331,7 +2331,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p 付款的要求過期了。 - Warning: Invalid Bitcoin address + Warning: Invalid NYC3 address 警告: Bitcoin 位址無效 @@ -2374,7 +2374,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p 這是一筆正常的付款。 - The Bitcoin address to send the payment to + The NYC3 address to send the payment to 接收付款的 Bitcoin 位址 @@ -2471,7 +2471,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p 你可以用自己的位址簽署訊息或合約，來證明你可以從該位址收款。但是請小心，不要簽署語意含糊不清，或隨機產生的內容，因為釣魚式詐騙可能會用騙你簽署的手法來冒充是你。只有在語句中的細節你都同意時才簽署。 - The Bitcoin address to sign the message with + The NYC3 address to sign the message with 用來簽署訊息的 Bitcoin 位址 @@ -2503,7 +2503,7 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p 複製目前的簽章到系統剪貼簿 - Sign the message to prove you own this Bitcoin address + Sign the message to prove you own this NYC3 address 簽署這個訊息來證明這個 Bitcoin 位址是你的 @@ -2527,11 +2527,11 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p 請在下面輸入收款人的位址，訊息(請確定完整複製了所包含的換行，空格，跳位符號等等)，以及簽章，來驗證這個訊息。請小心，除了訊息內容以外，不要對簽章本身過度解讀，以避免被用「中間人攻擊法」詐騙。請注意，通過驗證的簽章只能證明簽章人確實可以從該位址收款，不能證明任何交易中的付款人身份！ - The Bitcoin address the message was signed with + The NYC3 address the message was signed with 簽署這個訊息的 Bitcoin 位址 - Verify the message to ensure it was signed with the specified Bitcoin address + Verify the message to ensure it was signed with the specified NYC3 address 驗證這個訊息來確定是用指定的 Bitcoin 位址簽署的 @@ -3199,8 +3199,8 @@ Note: Since the fee is calculated on a per-byte basis, a fee of "100 satoshis p 無法啟動 HTTP 伺服器。詳情請看除錯紀錄。 - Bitcoin Core - Bitcoin Core + NYC3 + NYC3 The %s developers diff --git a/src/qt/nyc3.h b/src/qt/nyc3.h index 370712d95..9fc9fd75c 100644 --- a/src/qt/nyc3.h +++ b/src/qt/nyc3.h @@ -27,7 +27,7 @@ class Handler; class Node; } // namespace interfaces -/** Class encapsulating Bitcoin Core startup and shutdown. +/** Class encapsulating NYC3 startup and shutdown. * Allows running startup and shutdown in a different thread from the UI thread. */ class BitcoinCore: public QObject diff --git a/src/qt/nyc3addressvalidator.cpp b/src/qt/nyc3addressvalidator.cpp index d78353b06..3ae6414d6 100644 --- a/src/qt/nyc3addressvalidator.cpp +++ b/src/qt/nyc3addressvalidator.cpp @@ -88,7 +88,7 @@ BitcoinAddressCheckValidator::BitcoinAddressCheckValidator(QObject *parent) : QValidator::State BitcoinAddressCheckValidator::validate(QString &input, int &pos) const { Q_UNUSED(pos); - // Validate the passed Bitcoin address + // Validate the passed NYC3 address if (IsValidDestinationString(input.toStdString())) { return QValidator::Acceptable; } diff --git a/src/qt/nyc3addressvalidator.h b/src/qt/nyc3addressvalidator.h index 2a2565803..78f1b3c0d 100644 --- a/src/qt/nyc3addressvalidator.h +++ b/src/qt/nyc3addressvalidator.h @@ -20,7 +20,7 @@ public: State validate(QString &input, int &pos) const; }; -/** Bitcoin address widget validator, checks for a valid bitcoin address. +/** NYC3 address widget validator, checks for a valid bitcoin address. */ class BitcoinAddressCheckValidator : public QValidator { diff --git a/src/qt/nyc3gui.cpp b/src/qt/nyc3gui.cpp index 9675ac4a7..6ba61b584 100644 --- a/src/qt/nyc3gui.cpp +++ b/src/qt/nyc3gui.cpp @@ -245,7 +245,7 @@ void BitcoinGUI::createActions() tabGroup->addAction(overviewAction); sendCoinsAction = new QAction(platformStyle->SingleColorIcon(":/icons/send"), tr("&Send"), this); - sendCoinsAction->setStatusTip(tr("Send coins to a Bitcoin address")); + sendCoinsAction->setStatusTip(tr("Send coins to a NYC3 address")); sendCoinsAction->setToolTip(sendCoinsAction->statusTip()); sendCoinsAction->setCheckable(true); sendCoinsAction->setShortcut(QKeySequence(Qt::ALT + Qt::Key_2)); diff --git a/src/qt/nyc3strings.cpp b/src/qt/nyc3strings.cpp index 6b0e92d93..6cc8f6ddd 100644 --- a/src/qt/nyc3strings.cpp +++ b/src/qt/nyc3strings.cpp @@ -9,7 +9,7 @@ #define UNUSED #endif static const char UNUSED *bitcoin_strings[] = { -QT_TRANSLATE_NOOP("bitcoin-core", "Bitcoin Core"), +QT_TRANSLATE_NOOP("bitcoin-core", "NYC3"), QT_TRANSLATE_NOOP("bitcoin-core", "The %s developers"), QT_TRANSLATE_NOOP("bitcoin-core", "" "-maxtxfee is set very high! Fees this large could be paid on a single " diff --git a/src/qt/paymentserver.cpp b/src/qt/paymentserver.cpp index 48163ebe9..76447a072 100644 --- a/src/qt/paymentserver.cpp +++ b/src/qt/paymentserver.cpp @@ -340,7 +340,7 @@ void PaymentServer::handleURIOrFile(const QString& s) } else Q_EMIT message(tr("URI handling"), - tr("URI cannot be parsed! This can be caused by an invalid Bitcoin address or malformed URI parameters."), + tr("URI cannot be parsed! This can be caused by an invalid NYC3 address or malformed URI parameters."), CClientUIInterface::ICON_WARNING); return; diff --git a/src/qt/sendcoinsdialog.cpp b/src/qt/sendcoinsdialog.cpp index d8627c13f..b7728b1e2 100644 --- a/src/qt/sendcoinsdialog.cpp +++ b/src/qt/sendcoinsdialog.cpp @@ -802,7 +802,7 @@ void SendCoinsDialog::coinControlChangeEdited(const QString& text) } else if (!IsValidDestination(dest)) // Invalid address { - ui->labelCoinControlChangeLabel->setText(tr("Warning: Invalid Bitcoin address")); + ui->labelCoinControlChangeLabel->setText(tr("Warning: Invalid NYC3 address")); } else // Valid address { diff --git a/src/qt/splashscreen.h b/src/qt/splashscreen.h index f99dd0c70..489e2c4ac 100644 --- a/src/qt/splashscreen.h +++ b/src/qt/splashscreen.h @@ -19,7 +19,7 @@ class Wallet; /** Class for the splashscreen with information of the running client. * - * @note this is intentionally not a QSplashScreen. Bitcoin Core initialization + * @note this is intentionally not a QSplashScreen. NYC3 initialization * can take a long time, and in that case a progress window that cannot be * moved around and minimized has turned out to be frustrating to the user. */ diff --git a/src/rpc/rawtransaction.cpp b/src/rpc/rawtransaction.cpp index 71acdbfb9..8cffee71b 100644 --- a/src/rpc/rawtransaction.cpp +++ b/src/rpc/rawtransaction.cpp @@ -443,7 +443,7 @@ CMutableTransaction ConstructTransaction(const UniValue& inputs_in, const UniVal } else { CTxDestination destination = DecodeDestination(name_); if (!IsValidDestination(destination)) { - throw JSONRPCError(RPC_INVALID_ADDRESS_OR_KEY, std::string("Invalid Bitcoin address: ") + name_); + throw JSONRPCError(RPC_INVALID_ADDRESS_OR_KEY, std::string("Invalid NYC3 address: ") + name_); } if (!destinations.insert(destination).second) { @@ -1209,7 +1209,7 @@ UniValue decodepsbt(const JSONRPCRequest& request) " \"asm\" : \"asm\", (string) The asm\n" " \"hex\" : \"hex\", (string) The hex\n" " \"type\" : \"pubkeyhash\", (string) The type, eg 'pubkeyhash'\n" - " \"address\" : \"address\" (string) Bitcoin address if there is one\n" + " \"address\" : \"address\" (string) NYC3 address if there is one\n" " }\n" " },\n" " \"partial_signatures\" : { (json object, optional)\n" diff --git a/src/test/scriptnum10.h b/src/test/scriptnum10.h index e763b6427..5052863c5 100644 --- a/src/test/scriptnum10.h +++ b/src/test/scriptnum10.h @@ -23,7 +23,7 @@ public: class CScriptNum10 { /** - * The ScriptNum implementation from Bitcoin Core 0.10.0, for cross-comparison. + * The ScriptNum implementation from NYC3 0.10.0, for cross-comparison. */ public: diff --git a/src/tinyformat.h b/src/tinyformat.h index 14b7cd302..da34655ef 100644 --- a/src/tinyformat.h +++ b/src/tinyformat.h @@ -1052,7 +1052,7 @@ TINYFORMAT_FOREACH_ARGNUM(TINYFORMAT_MAKE_FORMAT_FUNCS) #endif -// Added for Bitcoin Core +// Added for NYC3 template std::string format(const std::string &fmt, const Args&... args) { diff --git a/src/univalue/include/univalue.h b/src/univalue/include/univalue.h index 91b104e56..6d02e5591 100644 --- a/src/univalue/include/univalue.h +++ b/src/univalue/include/univalue.h @@ -1,5 +1,5 @@ // Copyright 2014 BitPay Inc. -// Copyright 2015 Bitcoin Core Developers +// Copyright 2015 NYC3 Developers // Distributed under the MIT software license, see the accompanying // file COPYING or http://www.opensource.org/licenses/mit-license.php. diff --git a/src/univalue/lib/univalue.cpp b/src/univalue/lib/univalue.cpp index 4c9c15d63..1a8cc2caf 100644 --- a/src/univalue/lib/univalue.cpp +++ b/src/univalue/lib/univalue.cpp @@ -1,5 +1,5 @@ // Copyright 2014 BitPay Inc. -// Copyright 2015 Bitcoin Core Developers +// Copyright 2015 NYC3 Developers // Distributed under the MIT software license, see the accompanying // file COPYING or http://www.opensource.org/licenses/mit-license.php. diff --git a/src/univalue/lib/univalue_get.cpp b/src/univalue/lib/univalue_get.cpp index eabcf2dad..09e87cd9f 100644 --- a/src/univalue/lib/univalue_get.cpp +++ b/src/univalue/lib/univalue_get.cpp @@ -1,5 +1,5 @@ // Copyright 2014 BitPay Inc. -// Copyright 2015 Bitcoin Core Developers +// Copyright 2015 NYC3 Developers // Distributed under the MIT software license, see the accompanying // file COPYING or http://www.opensource.org/licenses/mit-license.php. diff --git a/src/util/system.cpp b/src/util/system.cpp index fe4d89ee1..ccb803b35 100644 --- a/src/util/system.cpp +++ b/src/util/system.cpp @@ -1220,8 +1220,8 @@ std::string CopyrightHolders(const std::string& strPrefix) { std::string strCopyrightHolders = strPrefix + strprintf(_(COPYRIGHT_HOLDERS), _(COPYRIGHT_HOLDERS_SUBSTITUTION)); - // Check for untranslated substitution to make sure Bitcoin Core copyright is not removed by accident - if (strprintf(COPYRIGHT_HOLDERS, COPYRIGHT_HOLDERS_SUBSTITUTION).find("Bitcoin Core") == std::string::npos) { + // Check for untranslated substitution to make sure NYC3 copyright is not removed by accident + if (strprintf(COPYRIGHT_HOLDERS, COPYRIGHT_HOLDERS_SUBSTITUTION).find("NYC3") == std::string::npos) { strCopyrightHolders += "\n" + strPrefix + "The Bitcoin Core developers"; } return strCopyrightHolders; diff --git a/src/wallet/rpcdump.cpp b/src/wallet/rpcdump.cpp index ed9742e6c..c63fdd80f 100644 --- a/src/wallet/rpcdump.cpp +++ b/src/wallet/rpcdump.cpp @@ -287,7 +287,7 @@ UniValue importaddress(const JSONRPCRequest& request) "\nNote: If you import a non-standard raw script in hex form, outputs sending to it will be treated\n" "as change, and not show up in many RPCs.\n", { - {"address", RPCArg::Type::STR, RPCArg::Optional::NO, "The Bitcoin address (or hex-encoded script)"}, + {"address", RPCArg::Type::STR, RPCArg::Optional::NO, "The NYC3 address (or hex-encoded script)"}, {"label", RPCArg::Type::STR, /* default */ "\"\"", "An optional label"}, {"rescan", RPCArg::Type::BOOL, /* default */ "true", "Rescan the wallet for transactions"}, {"p2sh", RPCArg::Type::BOOL, /* default */ "false", "Add the P2SH version of the script as well"}, @@ -340,7 +340,7 @@ UniValue importaddress(const JSONRPCRequest& request) std::vector data(ParseHex(request.params[0].get_str())); ImportScript(pwallet, CScript(data.begin(), data.end()), strLabel, fP2SH); } else { - throw JSONRPCError(RPC_INVALID_ADDRESS_OR_KEY, "Invalid Bitcoin address or script"); + throw JSONRPCError(RPC_INVALID_ADDRESS_OR_KEY, "Invalid NYC3 address or script"); } } if (fRescan) @@ -738,7 +738,7 @@ UniValue dumpprivkey(const JSONRPCRequest& request) std::string strAddress = request.params[0].get_str(); CTxDestination dest = DecodeDestination(strAddress); if (!IsValidDestination(dest)) { - throw JSONRPCError(RPC_INVALID_ADDRESS_OR_KEY, "Invalid Bitcoin address"); + throw JSONRPCError(RPC_INVALID_ADDRESS_OR_KEY, "Invalid NYC3 address"); } auto keyid = GetKeyForDestination(*pwallet, dest); if (keyid.IsNull()) { diff --git a/src/wallet/rpcwallet.cpp b/src/wallet/rpcwallet.cpp index 9393d8657..12c92a54d 100644 --- a/src/wallet/rpcwallet.cpp +++ b/src/wallet/rpcwallet.cpp @@ -157,7 +157,7 @@ static UniValue getnewaddress(const JSONRPCRequest& request) if (request.fHelp || request.params.size() > 2) throw std::runtime_error( RPCHelpMan{"getnewaddress", - "\nReturns a new Bitcoin address for receiving payments.\n" + "\nReturns a new NYC3 address for receiving payments.\n" "If 'label' is specified, it is added to the address book \n" "so payments received with the address will be associated with 'label'.\n", { @@ -220,7 +220,7 @@ static UniValue getrawchangeaddress(const JSONRPCRequest& request) if (request.fHelp || request.params.size() > 1) throw std::runtime_error( RPCHelpMan{"getrawchangeaddress", - "\nReturns a new Bitcoin address, for receiving change.\n" + "\nReturns a new NYC3 address, for receiving change.\n" "This is for use with raw transactions, NOT normal use.\n", { {"address_type", RPCArg::Type::STR, /* default */ "set by -changetype", "The address type to use. Options are \"legacy\", \"p2sh-segwit\", and \"bech32\"."}, @@ -293,7 +293,7 @@ static UniValue setlabel(const JSONRPCRequest& request) CTxDestination dest = DecodeDestination(request.params[0].get_str()); if (!IsValidDestination(dest)) { - throw JSONRPCError(RPC_INVALID_ADDRESS_OR_KEY, "Invalid Bitcoin address"); + throw JSONRPCError(RPC_INVALID_ADDRESS_OR_KEY, "Invalid NYC3 address"); } std::string label = LabelFromValue(request.params[1]); @@ -323,7 +323,7 @@ static CTransactionRef SendMoney(interfaces::Chain::Lock& locked_chain, CWallet throw JSONRPCError(RPC_CLIENT_P2P_DISABLED, "Error: Peer-to-peer functionality missing or disabled"); } - // Parse Bitcoin address + // Parse NYC3 address CScript scriptPubKey = GetScriptForDestination(address); // Create and send the transaction @@ -611,10 +611,10 @@ static UniValue getreceivedbyaddress(const JSONRPCRequest& request) auto locked_chain = pwallet->chain().lock(); LOCK(pwallet->cs_wallet); - // Bitcoin address + // NYC3 address CTxDestination dest = DecodeDestination(request.params[0].get_str()); if (!IsValidDestination(dest)) { - throw JSONRPCError(RPC_INVALID_ADDRESS_OR_KEY, "Invalid Bitcoin address"); + throw JSONRPCError(RPC_INVALID_ADDRESS_OR_KEY, "Invalid NYC3 address"); } CScript scriptPubKey = GetScriptForDestination(dest); if (!IsMine(*pwallet, scriptPubKey)) { @@ -904,7 +904,7 @@ static UniValue sendmany(const JSONRPCRequest& request) for (const std::string& name_ : keys) { CTxDestination dest = DecodeDestination(name_); if (!IsValidDestination(dest)) { - throw JSONRPCError(RPC_INVALID_ADDRESS_OR_KEY, std::string("Invalid Bitcoin address: ") + name_); + throw JSONRPCError(RPC_INVALID_ADDRESS_OR_KEY, std::string("Invalid NYC3 address: ") + name_); } if (destinations.count(dest)) { @@ -970,7 +970,7 @@ static UniValue addmultisigaddress(const JSONRPCRequest& request) std::string msg = RPCHelpMan{"addmultisigaddress", "\nAdd a nrequired-to-sign multisignature address to the wallet. Requires a new wallet backup.\n" - "Each key is a Bitcoin address or hex-encoded public key.\n" + "Each key is a NYC3 address or hex-encoded public key.\n" "This functionality is only intended for use with non-watchonly addresses.\n" "See `importaddress` for watchonly p2sh address support.\n" "If 'label' is specified, assign address to that label.\n", @@ -2799,7 +2799,7 @@ static UniValue listunspent(const JSONRPCRequest& request) const UniValue& input = inputs[idx]; CTxDestination dest = DecodeDestination(input.get_str()); if (!IsValidDestination(dest)) { - throw JSONRPCError(RPC_INVALID_ADDRESS_OR_KEY, std::string("Invalid Bitcoin address: ") + input.get_str()); + throw JSONRPCError(RPC_INVALID_ADDRESS_OR_KEY, std::string("Invalid NYC3 address: ") + input.get_str()); } if (!destinations.insert(dest).second) { throw JSONRPCError(RPC_INVALID_PARAMETER, std::string("Invalid parameter, duplicated address: ") + input.get_str()); diff --git a/test/README.md b/test/README.md index 9d4351b1d..af6279b4e 100644 --- a/test/README.md +++ b/test/README.md @@ -18,7 +18,7 @@ request is opened. All sets of tests can also be run locally. # Running tests locally -Before tests can be run locally, Bitcoin Core must be built. See the [building instructions](/doc#building) for help. +Before tests can be run locally, NYC3 must be built. See the [building instructions](/doc#building) for help. ### Functional tests diff --git a/test/functional/README.md b/test/functional/README.md index 5e3009e6a..3f9074cfb 100644 --- a/test/functional/README.md +++ b/test/functional/README.md @@ -92,7 +92,7 @@ implements the test logic. - `P2PConnection` is the class used to connect to a bitcoind. `P2PInterface` contains the higher level logic for processing P2P payloads and connecting to -the Bitcoin Core node application logic. For custom behaviour, subclass the +the NYC3 node application logic. For custom behaviour, subclass the P2PInterface object and override the callback methods. - Can be used to write tests where specific P2P protocol behavior is tested. diff --git a/test/functional/feature_filelock.py b/test/functional/feature_filelock.py index 9fb0d35a6..22d3b2832 100755 --- a/test/functional/feature_filelock.py +++ b/test/functional/feature_filelock.py @@ -23,7 +23,7 @@ class FilelockTest(BitcoinTestFramework): self.log.info("Using datadir {}".format(datadir)) self.log.info("Check that we can't start a second bitcoind instance using the same datadir") - expected_msg = "Error: Cannot obtain a lock on data directory {}. Bitcoin Core is probably already running.".format(datadir) + expected_msg = "Error: Cannot obtain a lock on data directory {}. NYC3 is probably already running.".format(datadir) self.nodes[1].assert_start_raises_init_error(extra_args=['-datadir={}'.format(self.nodes[0].datadir), '-noserver'], expected_msg=expected_msg) if self.is_wallet_compiled(): diff --git a/test/functional/interface_bitcoin_cli.py b/test/functional/interface_bitcoin_cli.py index aed439339..69120b1f0 100755 --- a/test/functional/interface_bitcoin_cli.py +++ b/test/functional/interface_bitcoin_cli.py @@ -16,7 +16,7 @@ class TestBitcoinCli(BitcoinTestFramework): """Main test logic""" cli_response = self.nodes[0].cli("-version").send_cli() - assert("Bitcoin Core RPC client version" in cli_response) + assert("NYC3 RPC client version" in cli_response) self.log.info("Compare responses from getwalletinfo RPC and `bitcoin-cli getwalletinfo`") if self.is_wallet_compiled(): diff --git a/test/functional/test_framework/mininode.py b/test/functional/test_framework/mininode.py index ac7cc068b..53e53fbfe 100755 --- a/test/functional/test_framework/mininode.py +++ b/test/functional/test_framework/mininode.py @@ -219,7 +219,7 @@ class P2PConnection(asyncio.Protocol): if not self._transport: return # Python <3.4.4 does not have is_closing, so we have to check for - # its existence explicitly as long as Bitcoin Core supports all + # its existence explicitly as long as NYC3 supports all # Python 3.4 versions. if hasattr(self._transport, 'is_closing') and self._transport.is_closing(): return