repair copyright headers across codebase

change URI referencing bitcoin to nyc3
include quicker blake2b routines
2019-06-15 17:49:59 +08:00 · 2019-06-15 17:23:22 +08:00 · 2019-06-13 12:38:58 +08:00 · 2019-06-13 10:15:08 +08:00 · 2019-06-13 05:12:24 +08:00 · 2019-06-13 05:09:48 +08:00
618 changed files with 13319 additions and 6721 deletions
@@ -1,6 +1,6 @@
-<!-- This issue tracker is only for technical issues related to Bitcoin Core.
+<!-- This issue tracker is only for technical issues related to NYC3 Core.

-General bitcoin questions and/or support requests are best directed to the Bitcoin StackExchange at https://bitcoin.stackexchange.com.
+General bitcoin questions and/or support requests are best directed to the NYC3 StackExchange at https://bitcoin.stackexchange.com.

 For reporting security issues, please read instructions at https://bitcoincore.org/en/contact/.

@@ -13,7 +13,7 @@ If the node is "stuck" during sync or giving "block checksum mismatch" errors, p

 <!--- How reliably can you reproduce the issue, what are the steps to do so? -->

-<!-- What version of Bitcoin Core are you using, where did you get it (website, self-compiled, etc)? -->
+<!-- What version of NYC3 Core are you using, where did you get it (website, self-compiled, etc)? -->

 <!-- What type of machine are you observing the error on (OS/CPU and disk type)? -->

@@ -2,7 +2,7 @@ Pull requests without a rationale and clear improvement may be closed
 immediately.

 Please provide clear motivation for your patch and explain how it improves
-Bitcoin Core user experience or Bitcoin Core developer experience
+NYC3 Core user experience or NYC3 Core developer experience
 significantly.

 * Any test improvements or new tests that improve coverage are always welcome.
@@ -15,7 +15,7 @@ significantly.
  was fixed.
 * Features are welcome, but might be rejected due to design or scope issues.
  If a feature is based on a lot of dependencies, contributors should first
-  consider building the system outside of Bitcoin Core, if possible.
+  consider building the system outside of NYC3 Core, if possible.
 * Refactoring changes are only accepted if they are required for a feature or
  bug fix or otherwise improve developer experience significantly. For example,
  most "code style" refactoring changes require a thorough explanation why they
@@ -25,7 +25,7 @@ significantly.
  preferred in the [developer notes](/doc/developer-notes.md), stylistic code
  changes are usually rejected.

-Bitcoin Core has a thorough review process and even the most trivial change
+NYC3 Core has a thorough review process and even the most trivial change
 needs to pass a lot of eyes and requires non-zero or even substantial time
 effort to review. There is a huge lack of active reviewers on the project, so
 patches often sit for a long time.
@@ -83,7 +83,7 @@ src/qt/bitcoin-qt.includes
 *.qm
 Makefile
 bitcoin-qt
-Bitcoin-Qt.app
+NYC3-Qt.app
 background.tiff*

 # Unit-tests
@@ -1,6 +1,6 @@
 #!/usr/bin/env bash
 #
-# Copyright (c) 2018 The Bitcoin Core developers
+# Copyright (c) 2018 The NYC3 Core developers
 # Distributed under the MIT software license, see the accompanying
 # file COPYING or http://www.opensource.org/licenses/mit-license.php.

@@ -1,6 +1,6 @@
 #!/usr/bin/env bash
 #
-# Copyright (c) 2018 The Bitcoin Core developers
+# Copyright (c) 2018 The NYC3 Core developers
 # Distributed under the MIT software license, see the accompanying
 # file COPYING or http://www.opensource.org/licenses/mit-license.php.

@@ -1,6 +1,6 @@
 #!/usr/bin/env bash
 #
-# Copyright (c) 2018 The Bitcoin Core developers
+# Copyright (c) 2018 The NYC3 Core developers
 # Distributed under the MIT software license, see the accompanying
 # file COPYING or http://www.opensource.org/licenses/mit-license.php.

@@ -1,6 +1,6 @@
 #!/usr/bin/env bash
 #
-# Copyright (c) 2018 The Bitcoin Core developers
+# Copyright (c) 2018 The NYC3 Core developers
 # Distributed under the MIT software license, see the accompanying
 # file COPYING or http://www.opensource.org/licenses/mit-license.php.

@@ -1,6 +1,6 @@
 #!/usr/bin/env bash
 #
-# Copyright (c) 2018 The Bitcoin Core developers
+# Copyright (c) 2018 The NYC3 Core developers
 # Distributed under the MIT software license, see the accompanying
 # file COPYING or http://www.opensource.org/licenses/mit-license.php.

@@ -1,6 +1,6 @@
 #!/usr/bin/env bash
 #
-# Copyright (c) 2018 The Bitcoin Core developers
+# Copyright (c) 2018 The NYC3 Core developers
 # Distributed under the MIT software license, see the accompanying
 # file COPYING or http://www.opensource.org/licenses/mit-license.php.

@@ -1,6 +1,6 @@
 #!/usr/bin/env bash
 #
-# Copyright (c) 2018 The Bitcoin Core developers
+# Copyright (c) 2018 The NYC3 Core developers
 # Distributed under the MIT software license, see the accompanying
 # file COPYING or http://www.opensource.org/licenses/mit-license.php.

@@ -1,6 +1,6 @@
 #!/usr/bin/env bash
 #
-# Copyright (c) 2018 The Bitcoin Core developers
+# Copyright (c) 2018 The NYC3 Core developers
 # Distributed under the MIT software license, see the accompanying
 # file COPYING or http://www.opensource.org/licenses/mit-license.php.

@@ -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
-projects such as libsecp256k1), and is not to be confused with overall Bitcoin
+The following applies to code changes to the NYC3 project (and related
+projects such as libsecp256k1), and is not to be confused with overall NYC3
 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
@@ -221,7 +221,7 @@ In general, all pull requests must:
  - Where bugs are fixed, where possible, there should be unit tests
    demonstrating the bug and also proving the fix. This helps prevent regression.

-Patches that change Bitcoin consensus rules are considerably more involved than
+Patches that change NYC3 consensus rules are considerably more involved than
 normal because they affect the entire ecosystem and so must be preceded by
 extensive mailing list discussions and have a numbered BIP. While each case will
 be different, one should be prepared to expend more time and effort than for
@@ -262,7 +262,7 @@ higher in terms of discussion and peer review requirements, keeping in mind that
 mistakes could be very costly to the wider community. This includes refactoring
 of consensus critical code.

-Where a patch set proposes to change the Bitcoin consensus, it must have been
+Where a patch set proposes to change the NYC3 consensus, it must have been
 discussed extensively on the mailing list and IRC, be accompanied by a widely
 discussed BIP and have a generally widely perceived technical consensus of being
 a worthwhile change based on the judgement of the maintainers.
@@ -302,7 +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
 ---------
@@ -1,7 +1,7 @@
 The MIT License (MIT)

-Copyright (c) 2009-2019 The Bitcoin Core developers
-Copyright (c) 2009-2019 Bitcoin Developers
+Copyright (c) 2009-2019 The NYC3 Core developers
+Copyright (c) 2009-2019 NYC3 Developers

 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal
@@ -1,5 +1,5 @@
-Building Bitcoin
+Building NYC3
 ================

 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 NYC3.
@@ -1,4 +1,4 @@
-# Copyright (c) 2013-2016 The Bitcoin Core developers
+# Copyright (c) 2013-2016 The NYC3 Core developers
 # Distributed under the MIT software license, see the accompanying
 # file COPYING or http://www.opensource.org/licenses/mit-license.php.

@@ -26,7 +26,7 @@ BITCOIN_WIN_INSTALLER=$(PACKAGE)-$(PACKAGE_VERSION)-win$(WINDOWS_BITS)-setup$(EX
 empty :=
 space := $(empty) $(empty)

-OSX_APP=Bitcoin-Qt.app
+OSX_APP=NYC3-Qt.app
 OSX_VOLNAME = $(subst $(space),-,$(PACKAGE_NAME))
 OSX_DMG = $(OSX_VOLNAME).dmg
 OSX_BACKGROUND_SVG=background.svg
@@ -35,7 +35,7 @@ OSX_BACKGROUND_IMAGE_DPIS=36 72
 OSX_DSSTORE_GEN=$(top_srcdir)/contrib/macdeploy/custom_dsstore.py
 OSX_DEPLOY_SCRIPT=$(top_srcdir)/contrib/macdeploy/macdeployqtplus
 OSX_FANCY_PLIST=$(top_srcdir)/contrib/macdeploy/fancy.plist
-OSX_INSTALLER_ICONS=$(top_srcdir)/src/qt/res/icons/bitcoin.icns
+OSX_INSTALLER_ICONS=$(top_srcdir)/src/qt/res/icons/nyc3.icns
 OSX_PLIST=$(top_builddir)/share/qt/Info.plist #not installed
 OSX_QT_TRANSLATIONS = da,de,es,hu,ru,uk,zh_CN,zh_TW

@@ -94,11 +94,11 @@ $(OSX_APP)/Contents/Info.plist: $(OSX_PLIST)
 	$(MKDIR_P) $(@D)
 	$(INSTALL_DATA) $< $@

-$(OSX_APP)/Contents/Resources/bitcoin.icns: $(OSX_INSTALLER_ICONS)
+$(OSX_APP)/Contents/Resources/nyc3.icns: $(OSX_INSTALLER_ICONS)
 	$(MKDIR_P) $(@D)
 	$(INSTALL_DATA) $< $@

-$(OSX_APP)/Contents/MacOS/Bitcoin-Qt: all-recursive
+$(OSX_APP)/Contents/MacOS/NYC3-Qt: all-recursive
 	$(MKDIR_P) $(@D)
 	STRIPPROG="$(STRIP)" $(INSTALL_STRIP_PROGRAM)  $(BITCOIN_QT_BIN) $@

@@ -107,8 +107,8 @@ $(OSX_APP)/Contents/Resources/Base.lproj/InfoPlist.strings:
 	echo '{	CFBundleDisplayName = "$(PACKAGE_NAME)"; CFBundleName = "$(PACKAGE_NAME)"; }' > $@

 OSX_APP_BUILT=$(OSX_APP)/Contents/PkgInfo $(OSX_APP)/Contents/Resources/empty.lproj \
-  $(OSX_APP)/Contents/Resources/bitcoin.icns $(OSX_APP)/Contents/Info.plist \
-  $(OSX_APP)/Contents/MacOS/Bitcoin-Qt $(OSX_APP)/Contents/Resources/Base.lproj/InfoPlist.strings
+  $(OSX_APP)/Contents/Resources/nyc3.icns $(OSX_APP)/Contents/Info.plist \
+  $(OSX_APP)/Contents/MacOS/NYC3-Qt $(OSX_APP)/Contents/Resources/Base.lproj/InfoPlist.strings

 osx_volname:
 	echo $(OSX_VOLNAME) >$@
@@ -133,7 +133,7 @@ $(APP_DIST_DIR)/Applications:
 	@rm -f $@
 	@cd $(@D); $(LN_S) /Applications $(@F)

-$(APP_DIST_EXTRAS): $(APP_DIST_DIR)/$(OSX_APP)/Contents/MacOS/Bitcoin-Qt
+$(APP_DIST_EXTRAS): $(APP_DIST_DIR)/$(OSX_APP)/Contents/MacOS/NYC3-Qt

 $(OSX_DMG): $(APP_DIST_EXTRAS)
 	$(GENISOIMAGE) -no-cache-inodes -D -l -probe -V "$(OSX_VOLNAME)" -no-pad -r -dir-mode 0755 -apple -o $@ dist
@@ -148,7 +148,7 @@ $(APP_DIST_DIR)/.background/$(OSX_BACKGROUND_IMAGE): $(OSX_BACKGROUND_IMAGE_DPIF
 $(APP_DIST_DIR)/.DS_Store: $(OSX_DSSTORE_GEN)
 	$(PYTHON) $< "$@" "$(OSX_VOLNAME)"

-$(APP_DIST_DIR)/$(OSX_APP)/Contents/MacOS/Bitcoin-Qt: $(OSX_APP_BUILT) $(OSX_PACKAGING)
+$(APP_DIST_DIR)/$(OSX_APP)/Contents/MacOS/NYC3-Qt: $(OSX_APP_BUILT) $(OSX_PACKAGING)
 	INSTALLNAMETOOL=$(INSTALLNAMETOOL)  OTOOL=$(OTOOL) STRIP=$(STRIP) $(PYTHON) $(OSX_DEPLOY_SCRIPT) $(OSX_APP) -translations-dir=$(QT_TRANSLATION_DIR) -add-qt-tr $(OSX_QT_TRANSLATIONS) -verbose 2

 deploydir: $(APP_DIST_EXTRAS)
@@ -1,35 +1,22 @@
-Bitcoin Core integration/staging tree
-=====================================
+NYC3 (NewYorkCoin3) integration/staging tree
+============================================

-[![Build Status](https://travis-ci.org/bitcoin/bitcoin.svg?branch=master)](https://travis-ci.org/bitcoin/bitcoin)

-https://bitcoincore.org
+Built upon Bitcoin Core 0.18; NYC3 offers a blocktime of 10 seconds, consensus operates using a modified version of the Argon2 password hashing algorithm (http://github.com/barrystyle/argon2s) in a POW configuration and uses LWMA3 to regulate block-spacing.

-What is Bitcoin?
----------------
-
-Bitcoin is an experimental digital currency that enables instant payments to
-anyone, anywhere in the world. Bitcoin uses peer-to-peer technology to operate
-with no central authority: managing transactions and issuing money are carried
-out collectively by the network. Bitcoin Core is the name of open source
-software which enables the use of this currency.
-
-For more information, as well as an immediately useable, binary version of
-the Bitcoin Core software, see https://bitcoincore.org/en/download/, or read the
-[original whitepaper](https://bitcoincore.org/bitcoin.pdf).

 License
 -------

-Bitcoin Core is released under the terms of the MIT license. See [COPYING](COPYING) for more
+NYC3 is released under the terms of the MIT license. See [COPYING](COPYING) for more
 information or see https://opensource.org/licenses/MIT.

 Development Process
 -------------------

 The `master` branch is regularly built and tested, but is not guaranteed to be
-completely stable. [Tags](https://github.com/bitcoin/bitcoin/tags) are created
-regularly to indicate new official, stable release versions of Bitcoin Core.
+completely stable. [Tags](https://github.com/nyc3coin/nyc3/tags) are created
+regularly to indicate new official, stable release versions of NYC3.

 The contribution workflow is described in [CONTRIBUTING.md](CONTRIBUTING.md)
 and useful hints for developers can be found in [doc/developer-notes.md](doc/developer-notes.md).
@@ -61,17 +48,3 @@ Changes should be tested by somebody other than the developer who wrote the
 code. This is especially important for large or high-risk changes. It is useful
 to add a test plan to the pull request description if testing the changes is
 not straightforward.
-
-Translations
------------
-
-Changes to translations as well as new translations can be submitted to
-[Bitcoin Core's Transifex page](https://www.transifex.com/projects/p/bitcoin/).
-
-Translations are periodically pulled from Transifex and merged into the git repository. See the
-[translation process](doc/translation_process.md) for details on how this works.
-
-**Important**: We do not accept translation changes as GitHub pull requests because the next
-pull from Transifex would automatically overwrite them again.
-
-Translators should also subscribe to the [mailing list](https://groups.google.com/forum/#!forum/bitcoin-translators).
@@ -1,5 +1,5 @@
 #!/bin/sh
-# Copyright (c) 2013-2016 The Bitcoin Core developers
+# Copyright (c) 2013-2016 The NYC3 Core developers
 # Distributed under the MIT software license, see the accompanying
 # file COPYING or http://www.opensource.org/licenses/mit-license.php.

@@ -14,3 +14,5 @@ fi
 which autoreconf >/dev/null || \
  (echo "configuration failed, please install autoconf first" && exit 1)
 autoreconf --install --force --warnings=all
+
+git submodule update --init
@@ -1,4 +1,4 @@
-dnl Copyright (c) 2013-2015 The Bitcoin Core developers
+dnl Copyright (c) 2013-2015 The NYC3 Core developers
 dnl Distributed under the MIT software license, see the accompanying
 dnl file COPYING or http://www.opensource.org/licenses/mit-license.php.

@@ -1,4 +1,4 @@
-dnl Copyright (c) 2013-2016 The Bitcoin Core developers
+dnl Copyright (c) 2013-2016 The NYC3 Core developers
 dnl Distributed under the MIT software license, see the accompanying
 dnl file COPYING or http://www.opensource.org/licenses/mit-license.php.

@@ -1,4 +1,4 @@
-dnl Copyright (c) 2013-2014 The Bitcoin Core developers
+dnl Copyright (c) 2013-2014 The NYC3 Core developers
 dnl Distributed under the MIT software license, see the accompanying
 dnl file COPYING or http://www.opensource.org/licenses/mit-license.php.

@@ -1,15 +1,15 @@
-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).

 Dependencies
 ---------------------
-A number of [open source libraries](https://github.com/bitcoin/bitcoin/blob/master/doc/dependencies.md) are required in order to be able to build Bitcoin.
+A number of [open source libraries](https://github.com/bitcoin/bitcoin/blob/master/doc/dependencies.md) are required in order to be able to build NYC3.

 Options for installing the dependencies in a Visual Studio compatible manner are:

@@ -23,10 +23,10 @@
 #define COPYRIGHT_HOLDERS "The %s developers"

 /* Copyright holder(s) */
-#define COPYRIGHT_HOLDERS_FINAL "The Bitcoin Core developers"
+#define COPYRIGHT_HOLDERS_FINAL "The NYC3 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"
@@ -1,25 +1,25 @@
 dnl require autoconf 2.60 (AS_ECHO/AS_ECHO_N)
 AC_PREREQ([2.60])
-define(_CLIENT_VERSION_MAJOR, 0)
-define(_CLIENT_VERSION_MINOR, 18)
+define(_CLIENT_VERSION_MAJOR, 1)
+define(_CLIENT_VERSION_MINOR, 1)
 define(_CLIENT_VERSION_REVISION, 0)
 define(_CLIENT_VERSION_BUILD, 0)
 define(_CLIENT_VERSION_RC, 0)
 define(_CLIENT_VERSION_IS_RELEASE, true)
 define(_COPYRIGHT_YEAR, 2019)
 define(_COPYRIGHT_HOLDERS,[The %s developers])
-define(_COPYRIGHT_HOLDERS_SUBSTITUTION,[[Bitcoin Core]])
-AC_INIT([Bitcoin Core],m4_join([.], _CLIENT_VERSION_MAJOR, _CLIENT_VERSION_MINOR, _CLIENT_VERSION_REVISION, m4_if(_CLIENT_VERSION_BUILD, [0], [], _CLIENT_VERSION_BUILD))m4_if(_CLIENT_VERSION_RC, [0], [], [rc]_CLIENT_VERSION_RC),[https://github.com/bitcoin/bitcoin/issues],[bitcoin],[https://bitcoincore.org/])
+define(_COPYRIGHT_HOLDERS_SUBSTITUTION,[[nyc3]])
+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])
 AC_CONFIG_MACRO_DIR([build-aux/m4])

-BITCOIN_DAEMON_NAME=bitcoind
-BITCOIN_GUI_NAME=bitcoin-qt
-BITCOIN_CLI_NAME=bitcoin-cli
-BITCOIN_TX_NAME=bitcoin-tx
-BITCOIN_WALLET_TOOL_NAME=bitcoin-wallet
+BITCOIN_DAEMON_NAME=nyc3d
+BITCOIN_GUI_NAME=nyc3-qt
+BITCOIN_CLI_NAME=nyc3-cli
+BITCOIN_TX_NAME=nyc3-tx
+BITCOIN_WALLET_TOOL_NAME=nyc3-wallet

 dnl Unless the user specified ARFLAGS, force it to be cr
 AC_ARG_VAR(ARFLAGS, [Flags for the archiver, defaults to <cr> if not set])
@@ -221,6 +221,12 @@ AC_ARG_ENABLE([bip70],
  [enable_bip70=$enableval],
  [enable_bip70=auto])

+AC_ARG_ENABLE([sse2],
+    [AS_HELP_STRING([--enable-sse2],
+    [enable SSE2 instructions in the scrypt library. (default is disabled)])],
+    [use_sse2=$enableval],
+    [use_sse2=no])
+
 AC_ARG_WITH([protoc-bindir],[AS_HELP_STRING([--with-protoc-bindir=BIN_DIR],[specify protoc bin path])], [protoc_bin_path=$withval], [])

 AC_ARG_ENABLE(man,
@@ -1393,6 +1399,16 @@ else
  BUILD_TEST=""
 fi

+AC_MSG_CHECKING([whether to enable sse2 instructions])
+if test x$use_sse2 != xno; then
+  AC_MSG_RESULT(yes)
+  AC_DEFINE([USE_SSE2],[1],[Define if SSE2 support should be compiled in])
+  use_sse2=yes
+  CPPFLAGS="$CPPFLAGS -DUSE_SSE2=1"
+else
+  AC_MSG_RESULT(no)
+fi
+
 AC_MSG_CHECKING([whether to reduce exports])
 if test x$use_reduce_exports = xyes; then
  AC_MSG_RESULT([yes])
@@ -1415,6 +1431,7 @@ AM_CONDITIONAL([ENABLE_QT_TESTS],[test x$BUILD_TEST_QT = xyes])
 AM_CONDITIONAL([ENABLE_BIP70],[test x$enable_bip70 = xyes])
 AM_CONDITIONAL([ENABLE_BENCH],[test x$use_bench = xyes])
 AM_CONDITIONAL([USE_QRCODE], [test x$use_qr = xyes])
+AM_CONDITIONAL([USE_SSE2], [test x$use_sse2 = xyes])
 AM_CONDITIONAL([USE_LCOV],[test x$use_lcov = xyes])
 AM_CONDITIONAL([GLIBC_BACK_COMPAT],[test x$use_glibc_compat = xyes])
 AM_CONDITIONAL([HARDEN],[test x$use_hardening = xyes])
@@ -1472,6 +1489,7 @@ AC_SUBST(SHANI_CXXFLAGS)
 AC_SUBST(LIBTOOL_APP_LDFLAGS)
 AC_SUBST(USE_UPNP)
 AC_SUBST(USE_QRCODE)
+AC_SUBST(USE_SSE2)
 AC_SUBST(BOOST_LIBS)
 AC_SUBST(TESTDEFS)
 AC_SUBST(LEVELDB_TARGET_FLAGS)
@@ -13,7 +13,7 @@ Construct a linear, no-fork, best version of the blockchain.

 ### [Qos](/contrib/qos) ###

-A Linux bash script that will set up traffic control (tc) to limit the outgoing bandwidth for connections to the Bitcoin network. This means one can have an always-on bitcoind instance running, and another local bitcoind/bitcoin-qt instance which connects to this node and receives blocks from it.
+A Linux bash script that will set up traffic control (tc) to limit the outgoing bandwidth for connections to the NYC3 network. This means one can have an always-on bitcoind instance running, and another local bitcoind/bitcoin-qt instance which connects to this node and receives blocks from it.

 ### [Seeds](/contrib/seeds) ###
 Utility to generate the pnSeed[] array that is compiled into the client.
@@ -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. 
@@ -42,7 +42,7 @@ Test and Verify Tools
 ---------------------

 ### [TestGen](/contrib/testgen) ###
-Utilities to generate test vectors for the data-driven Bitcoin tests.
+Utilities to generate test vectors for the data-driven NYC3 tests.

 ### [Verify Binaries](/contrib/verifybinaries) ###
 This script attempts to download and verify the signature file SHA256SUMS.asc from bitcoin.org.
@@ -1,5 +1,5 @@
 # bash programmable completion for bitcoin-cli(1)
-# Copyright (c) 2012-2016 The Bitcoin Core developers
+# Copyright (c) 2012-2016 The NYC3 Core developers
 # Distributed under the MIT software license, see the accompanying
 # file COPYING or http://www.opensource.org/licenses/mit-license.php.

@@ -1,5 +1,5 @@
 # bash programmable completion for bitcoin-tx(1)
-# Copyright (c) 2016 The Bitcoin Core developers
+# Copyright (c) 2016 The NYC3 Core developers
 # Distributed under the MIT software license, see the accompanying
 # file COPYING or http://www.opensource.org/licenses/mit-license.php.

@@ -1,5 +1,5 @@
 # bash programmable completion for bitcoind(1) and bitcoin-qt(1)
-# Copyright (c) 2012-2016 The Bitcoin Core developers
+# Copyright (c) 2012-2016 The NYC3 Core developers
 # Distributed under the MIT software license, see the accompanying
 # file COPYING or http://www.opensource.org/licenses/mit-license.php.

@@ -1,13 +1,13 @@
 Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
-Upstream-Name: Bitcoin
+Upstream-Name: NYC3
 Upstream-Contact: Satoshi Nakamoto <satoshin@gmx.com>
 irc://#bitcoin@freenode.net
 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/*
@@ -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:

 ```
@@ -36,31 +36,31 @@ Specifying `verbose` will list the full filenames of files of each category.

 copyright\_header.py update \<base\_directory\> [verbose]
 ---------------------------------------------------------
-Updates all the copyright headers of `The Bitcoin Core developers` which were
+Updates all the copyright headers of `The NYC3 Core developers` which were
 changed in a year more recent than is listed. For example:
 ```
-// Copyright (c) <firstYear>-<lastYear> The Bitcoin Core developers
+// Copyright (c) <firstYear>-<lastYear> The NYC3 Core developers
 ```
 will be updated to:
 ```
-// Copyright (c) <firstYear>-<lastModifiedYear> The Bitcoin Core developers
+// Copyright (c) <firstYear>-<lastModifiedYear> The NYC3 Core developers
 ```
 where `<lastModifiedYear>` is obtained from the `git log` history.

 This subcommand also handles copyright headers that have only a single year. In
 those cases:
 ```
-// Copyright (c) <year> The Bitcoin Core developers
+// Copyright (c) <year> The NYC3 Core developers
 ```
 will be updated to:
 ```
-// Copyright (c) <year>-<lastModifiedYear> The Bitcoin Core developers
+// Copyright (c) <year>-<lastModifiedYear> The NYC3 Core developers
 ```
 where the update is appropriate.

 copyright\_header.py insert \<file\>
 ------------------------------------
-Inserts a copyright header for `The Bitcoin Core developers` at the top of the
+Inserts a copyright header for `The NYC3 Core developers` at the top of the
 file in either Python or C++ style as determined by the file extension. If the
 file is a Python file and it has  `#!` starting the first line, the header is
 inserted in the line below it.
@@ -70,7 +70,7 @@ The copyright dates will be set to be `<year_introduced>-<current_year>` where
 `<year_introduced>` is equal to `<current_year>`, it will be set as a single
 year rather than two hyphenated years.

-If the file already has a copyright for `The Bitcoin Core developers`, the
+If the file already has a copyright for `The NYC3 Core developers`, the
 script will exit.

 gen-manpages.sh
@@ -1,5 +1,5 @@
 #!/usr/bin/env python3
-# Copyright (c) 2016-2018 The Bitcoin Core developers
+# Copyright (c) 2016-2018 The NYC3 Core developers
 # Distributed under the MIT software license, see the accompanying
 # file COPYING or http://www.opensource.org/licenses/mit-license.php.

@@ -89,8 +89,8 @@ def compile_copyright_regex(copyright_style, year_style, name):

 EXPECTED_HOLDER_NAMES = [
    "Satoshi Nakamoto\n",
-    "The Bitcoin Core developers\n",
-    "Bitcoin Core Developers\n",
+    "The NYC3 Core developers\n",
+    "NYC3 Developers\n",
    "BitPay Inc\.\n",
    "University of Illinois at Urbana-Champaign\.\n",
    "Pieter Wuille\n",
@@ -334,7 +334,7 @@ def write_file_lines(filename, file_lines):
 COPYRIGHT = 'Copyright \(c\)'
 YEAR = "20[0-9][0-9]"
 YEAR_RANGE = '(%s)(-%s)?' % (YEAR, YEAR)
-HOLDER = 'The Bitcoin Core developers'
+HOLDER = 'The NYC3 Core developers'
 UPDATEABLE_LINE_COMPILED = re.compile(' '.join([COPYRIGHT, YEAR_RANGE, HOLDER]))

 def get_updatable_copyright_line(file_lines):
@@ -399,24 +399,24 @@ def exec_update_header_year(base_directory):
 ################################################################################

 UPDATE_USAGE = """
-Updates all the copyright headers of "The Bitcoin Core developers" which were
+Updates all the copyright headers of "The NYC3 Core developers" which were
 changed in a year more recent than is listed. For example:

-// Copyright (c) <firstYear>-<lastYear> The Bitcoin Core developers
+// Copyright (c) <firstYear>-<lastYear> The NYC3 Core developers

 will be updated to:

-// Copyright (c) <firstYear>-<lastModifiedYear> The Bitcoin Core developers
+// Copyright (c) <firstYear>-<lastModifiedYear> The NYC3 Core developers

 where <lastModifiedYear> is obtained from the 'git log' history.

 This subcommand also handles copyright headers that have only a single year. In those cases:

-// Copyright (c) <year> The Bitcoin Core developers
+// Copyright (c) <year> The NYC3 Core developers

 will be updated to:

-// Copyright (c) <year>-<lastModifiedYear> The Bitcoin Core developers
+// Copyright (c) <year>-<lastModifiedYear> The NYC3 Core developers

 where the update is appropriate.

@@ -449,7 +449,7 @@ def get_header_lines(header, start_year, end_year):
    return [line + '\n' for line in lines]

 CPP_HEADER = '''
-// Copyright (c) %s The Bitcoin Core developers
+// Copyright (c) %s The NYC3 Core developers
 // Distributed under the MIT software license, see the accompanying
 // file COPYING or http://www.opensource.org/licenses/mit-license.php.
 '''
@@ -458,7 +458,7 @@ def get_cpp_header_lines_to_insert(start_year, end_year):
    return reversed(get_header_lines(CPP_HEADER, start_year, end_year))

 PYTHON_HEADER = '''
-# Copyright (c) %s The Bitcoin Core developers
+# Copyright (c) %s The NYC3 Core developers
 # Distributed under the MIT software license, see the accompanying
 # file COPYING or http://www.opensource.org/licenses/mit-license.php.
 '''
@@ -512,7 +512,7 @@ def insert_cpp_header(filename, file_lines, start_year, end_year):
 def exec_insert_header(filename, style):
    file_lines = read_file_lines(filename)
    if file_already_has_core_copyright(file_lines):
-        sys.exit('*** %s already has a copyright by The Bitcoin Core developers'
+        sys.exit('*** %s already has a copyright by The NYC3 Core developers'
                 % (filename))
    start_year, end_year = get_git_change_year_range(filename)
    if style == 'python':
@@ -525,7 +525,7 @@ def exec_insert_header(filename, style):
 ################################################################################

 INSERT_USAGE = """
-Inserts a copyright header for "The Bitcoin Core developers" at the top of the
+Inserts a copyright header for "The NYC3 Core developers" at the top of the
 file in either Python or C++ style as determined by the file extension. If the
 file is a Python file and it has a '#!' starting the first line, the header is
 inserted in the line below it.
@@ -539,7 +539,7 @@ where <year_introduced> is according to the 'git log' history. If

 "<current_year>"

-If the file already has a copyright for "The Bitcoin Core developers", the
+If the file already has a copyright for "The NYC3 Core developers", the
 script will exit.

 Usage:
@@ -571,7 +571,7 @@ def insert_cmd(argv):
 ################################################################################

 USAGE = """
-copyright_header.py - utilities for managing copyright headers of 'The Bitcoin
+copyright_header.py - utilities for managing copyright headers of 'The NYC3
 Core developers' in repository source files.

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

@@ -1,5 +1,5 @@
 #!/usr/bin/env python3
-# Copyright (c) 2014-2018 The Bitcoin Core developers
+# Copyright (c) 2014-2018 The NYC3 Core developers
 # Distributed under the MIT software license, see the accompanying
 # file COPYING or http://www.opensource.org/licenses/mit-license.php.
 '''
@@ -1,5 +1,5 @@
 #!/usr/bin/env python3
-# Copyright (c) 2015-2018 The Bitcoin Core developers
+# Copyright (c) 2015-2018 The NYC3 Core developers
 # Distributed under the MIT software license, see the accompanying
 # file COPYING or http://www.opensource.org/licenses/mit-license.php.
 '''
@@ -1,5 +1,5 @@
 #!/usr/bin/env python3
-# Copyright (c) 2015-2018 The Bitcoin Core developers
+# Copyright (c) 2015-2018 The NYC3 Core developers
 # Distributed under the MIT software license, see the accompanying
 # file COPYING or http://www.opensource.org/licenses/mit-license.php.
 '''
@@ -30,7 +30,7 @@ SOURCE_LANG = 'bitcoin_en.ts'
 LOCALE_DIR = 'src/qt/locale'
 # Minimum number of messages for translation to be considered at all
 MIN_NUM_MESSAGES = 10
-# Regexp to check for Bitcoin addresses
+# Regexp to check for NYC3 addresses
 ADDRESS_REGEXP = re.compile('([13]|bc1)[a-zA-Z0-9]{30,}')

 def check_at_repository_root():
@@ -29,7 +29,7 @@ def setup():
    if not os.path.isdir('gitian-builder'):
        subprocess.check_call(['git', 'clone', 'https://github.com/devrandom/gitian-builder.git'])
    if not os.path.isdir('bitcoin'):
-        subprocess.check_call(['git', 'clone', 'https://github.com/bitcoin/bitcoin.git'])
+        subprocess.check_call(['git', 'clone', 'https://github.com/nyc3coin/nyc3'])
    os.chdir('gitian-builder')
    make_image_prog = ['bin/make-base-vm', '--suite', 'bionic', '--arch', 'amd64']
    if args.docker:
@@ -1,5 +1,5 @@
 ---
-name: "bitcoin-linux-0.18"
+name: "nyc3-linux-0.18"
 enable_cache: true
 suites:
 - "bionic"
@@ -32,12 +32,15 @@ packages:
 - "ca-certificates"
 - "python"
 remotes:
- "url": "https://github.com/bitcoin/bitcoin.git"
-  "dir": "bitcoin"
+- "url": "https://github.com/nyc3coin/nyc3"
+  "dir": "nyc3"
+- "url": "https://github.com/barrystyle/argon2s.git"
+  "dir": "argon2s"
 files: []
 script: |
  set -e -o pipefail
-
+#this is a hack since gitian has no natural support for submodules
+  cp -r argon2s/* nyc3/src/argon2s
  WRAP_DIR=$HOME/wrapped
  HOSTS="i686-pc-linux-gnu x86_64-linux-gnu arm-linux-gnueabihf aarch64-linux-gnu riscv64-linux-gnu"
  CONFIGFLAGS="--enable-glibc-back-compat --enable-reduce-exports --disable-bench --disable-gui-tests"
@@ -122,7 +125,7 @@ script: |
  chmod +x ${WRAP_DIR}/${prog}
  done

-  cd bitcoin
+  cd nyc3
  BASEPREFIX=`pwd`/depends
  # Build dependencies for each host
  for i in $HOSTS; do
@@ -144,13 +147,13 @@ script: |
  ./autogen.sh
  CONFIG_SITE=${BASEPREFIX}/`echo "${HOSTS}" | awk '{print $1;}'`/share/config.site ./configure --prefix=/
  make dist
-  SOURCEDIST=`echo bitcoin-*.tar.gz`
+  SOURCEDIST=`echo nyc3-*.tar.gz`
  DISTNAME=`echo ${SOURCEDIST} | sed 's/.tar.*//'`
  # Correct tar file order
  mkdir -p temp
  pushd temp
  tar xf ../$SOURCEDIST
-  find bitcoin-* | sort | tar --no-recursion --mode='u+rw,go+r-w,a+X' --owner=0 --group=0 -c -T - | gzip -9n > ../$SOURCEDIST
+  find nyc3-* | sort | tar --no-recursion --mode='u+rw,go+r-w,a+X' --owner=0 --group=0 -c -T - | gzip -9n > ../$SOURCEDIST
  popd

  # Workaround for tarball not building with the bare tag version (prep)
@@ -1,5 +1,5 @@
 ---
-name: "bitcoin-dmg-signer"
+name: "nyc3-dmg-signer"
 suites:
 - "bionic"
 architectures:
@@ -1,5 +1,5 @@
 ---
-name: "bitcoin-osx-0.18"
+name: "nyc3-osx-0.18"
 enable_cache: true
 suites:
 - "bionic"
@@ -28,13 +28,17 @@ packages:
 - "python-setuptools"
 - "fonts-tuffy"
 remotes:
- "url": "https://github.com/bitcoin/bitcoin.git"
-  "dir": "bitcoin"
+- "url": "https://github.com/nyc3coin/nyc3"
+  "dir": "nyc3"
+- "url": "https://github.com/barrystyle/argon2s.git"
+  "dir": "argon2s"
 files:
 - "MacOSX10.11.sdk.tar.gz"
 script: |
  set -e -o pipefail
-
+#this is a hack since gitian has no natural support for submodules
+  cp -r argon2s/* nyc3/src/argon2s
+  #make sure this file exists... 
  WRAP_DIR=$HOME/wrapped
  HOSTS="x86_64-apple-darwin14"
  CONFIGFLAGS="--enable-reduce-exports --disable-bench --disable-gui-tests GENISOIMAGE=$WRAP_DIR/genisoimage"
@@ -86,7 +90,7 @@ script: |
  create_per-host_faketime_wrappers "2000-01-01 12:00:00"
  export PATH=${WRAP_DIR}:${PATH}

-  cd bitcoin
+  cd nyc3
  BASEPREFIX=`pwd`/depends

  mkdir -p ${BASEPREFIX}/SDKs
@@ -107,14 +111,14 @@ script: |
  ./autogen.sh
  CONFIG_SITE=${BASEPREFIX}/`echo "${HOSTS}" | awk '{print $1;}'`/share/config.site ./configure --prefix=/
  make dist
-  SOURCEDIST=`echo bitcoin-*.tar.gz`
+  SOURCEDIST=`echo nyc3-*.tar.gz`
  DISTNAME=`echo ${SOURCEDIST} | sed 's/.tar.*//'`

  # Correct tar file order
  mkdir -p temp
  pushd temp
  tar xf ../$SOURCEDIST
-  find bitcoin-* | sort | tar --no-recursion --mode='u+rw,go+r-w,a+X' --owner=0 --group=0 -c -T - | gzip -9n > ../$SOURCEDIST
+  find nyc3-* | sort | tar --no-recursion --mode='u+rw,go+r-w,a+X' --owner=0 --group=0 -c -T - | gzip -9n > ../$SOURCEDIST
  popd

  # Workaround for tarball not building with the bare tag version (prep)
@@ -1,5 +1,5 @@
 ---
-name: "bitcoin-win-signer"
+name: "nyc3-win-signer"
 suites:
 - "bionic"
 architectures:
@@ -1,5 +1,5 @@
 ---
-name: "bitcoin-win-0.18"
+name: "nyc3-win-0.18"
 enable_cache: true
 suites:
 - "bionic"
@@ -23,12 +23,15 @@ packages:
 - "python"
 - "rename"
 remotes:
- "url": "https://github.com/bitcoin/bitcoin.git"
-  "dir": "bitcoin"
+- "url": "https://github.com/nyc3coin/nyc3"
+  "dir": "nyc3"
+- "url": "https://github.com/barrystyle/argon2s.git"
+  "dir": "argon2s"
 files: []
 script: |
  set -e -o pipefail
-
+#this is a hack since gitian has no natural support for submodules
+  cp -r argon2s/* nyc3/src/argon2s
  WRAP_DIR=$HOME/wrapped
  HOSTS="i686-w64-mingw32 x86_64-w64-mingw32"
  CONFIGFLAGS="--enable-reduce-exports --disable-bench --disable-gui-tests"
@@ -76,7 +79,7 @@ script: |

  function create_per-host_linker_wrapper {
  # This is only needed for trusty, as the mingw linker leaks a few bytes of
-  # heap, causing non-determinism. See discussion in https://github.com/bitcoin/bitcoin/pull/6900
+  # heap, causing non-determinism. See discussion in https://github.com/nyc3/nyc3/pull/6900
  for i in $HOSTS; do
    mkdir -p ${WRAP_DIR}/${i}
    for prog in collect2; do
@@ -105,7 +108,7 @@ script: |
  create_per-host_linker_wrapper "2000-01-01 12:00:00"
  export PATH=${WRAP_DIR}:${PATH}

-  cd bitcoin
+  cd nyc3
  BASEPREFIX=`pwd`/depends
  # Build dependencies for each host
  for i in $HOSTS; do
@@ -123,14 +126,14 @@ script: |
  ./autogen.sh
  CONFIG_SITE=${BASEPREFIX}/`echo "${HOSTS}" | awk '{print $1;}'`/share/config.site ./configure --prefix=/
  make dist
-  SOURCEDIST=`echo bitcoin-*.tar.gz`
+  SOURCEDIST=`echo nyc3-*.tar.gz`
  DISTNAME=`echo ${SOURCEDIST} | sed 's/.tar.*//'`

  # Correct tar file order
  mkdir -p temp
  pushd temp
  tar xf ../$SOURCEDIST
-  find bitcoin-* | sort | tar --no-recursion --mode='u+rw,go+r-w,a+X' --owner=0 --group=0 -c -T - | gzip -9n > ../$SOURCEDIST
+  find nyc3-* | sort | tar --no-recursion --mode='u+rw,go+r-w,a+X' --owner=0 --group=0 -c -T - | gzip -9n > ../$SOURCEDIST
  mkdir -p $OUTDIR/src
  cp ../$SOURCEDIST $OUTDIR/src
  popd
@@ -159,7 +162,7 @@ script: |
    make deploy
    make install DESTDIR=${INSTALLPATH}
    rename 's/-setup\.exe$/-setup-unsigned.exe/' *-setup.exe
-    cp -f bitcoin-*setup*.exe $OUTDIR/
+    cp -f nyc3-*setup*.exe $OUTDIR/
    cd installed
    mv ${DISTNAME}/bin/*.dll ${DISTNAME}/lib/
    find . -name "lib*.la" -delete
@@ -175,7 +178,7 @@ script: |
  cp -rf contrib/windeploy $BUILD_DIR
  cd $BUILD_DIR/windeploy
  mkdir unsigned
-  cp $OUTDIR/bitcoin-*setup-unsigned.exe unsigned/
+  cp $OUTDIR/nyc3-*setup-unsigned.exe unsigned/
  find . | sort | tar --no-recursion --mode='u+rw,go+r-w,a+X' --owner=0 --group=0 -c -T - | gzip -9n > ${OUTDIR}/${DISTNAME}-win-unsigned.tar.gz
  mv ${OUTDIR}/${DISTNAME}-x86_64-*-debug.zip ${OUTDIR}/${DISTNAME}-win64-debug.zip
  mv ${OUTDIR}/${DISTNAME}-i686-*-debug.zip ${OUTDIR}/${DISTNAME}-win32-debug.zip
@@ -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.
@@ -1,4 +1,4 @@
-description "Bitcoin Core Daemon"
+description "NYC3 Daemon"

 start on runlevel [2345]
 stop on starting rc RUNLEVEL=[016]
@@ -38,7 +38,7 @@ pre-start script
        echo "It is recommended that you also set alertnotify so you are "
        echo "notified of problems:"
        echo
-        echo "ie: alertnotify=echo %%s | mail -s \"Bitcoin Alert\"" \
+        echo "ie: alertnotify=echo %%s | mail -s \"NYC3 Alert\"" \
            "admin@foo.com"
        echo
        exit 1
@@ -18,8 +18,8 @@ BITCOIND_BIN=${BITCOIND_BIN:-/usr/bin/bitcoind}
 BITCOIND_NICE=${BITCOIND_NICE:-${NICELEVEL:-0}}
 BITCOIND_OPTS="${BITCOIND_OPTS:-${BITCOIN_OPTS}}"

-name="Bitcoin Core Daemon"
-description="Bitcoin cryptocurrency P2P network daemon"
+name="NYC3 Daemon"
+description="NYC3 cryptocurrency P2P network daemon"

 command="/usr/bin/bitcoind"
 command_args="-pid=\"${BITCOIND_PIDFILE}\" \
@@ -84,7 +84,7 @@ checkconfig()
 		eerror "It is recommended that you also set alertnotify so you are "
 		eerror "notified of problems:"
 		eerror ""
-		eerror "ie: alertnotify=echo %%s | mail -s \"Bitcoin Alert\"" \
+		eerror "ie: alertnotify=echo %%s | mail -s \"NYC3 Alert\"" \
 			"admin@foo.com"
 		eerror ""
 		return 1
@@ -9,7 +9,7 @@
 # in ExecStart=

 [Unit]
-Description=Bitcoin daemon
+Description=NYC3 daemon
 After=network.target

 [Service]
@@ -1,5 +1,5 @@
 # Linearize
-Construct a linear, no-fork, best version of the Bitcoin blockchain. The scripts
+Construct a linear, no-fork, best version of the NYC3 blockchain. The scripts
 run using Python 3 but are compatible with Python 2.

 ## Step 1: Download hash list
@@ -2,7 +2,7 @@
 #
 # linearize-data.py: Construct a linear, no-fork version of the chain.
 #
-# Copyright (c) 2013-2018 The Bitcoin Core developers
+# Copyright (c) 2013-2018 The NYC3 Core developers
 # Distributed under the MIT software license, see the accompanying
 # file COPYING or http://www.opensource.org/licenses/mit-license.php.
 #
@@ -2,7 +2,7 @@
 #
 # linearize-hashes.py:  List blocks in a linear, no-fork version of the chain.
 #
-# Copyright (c) 2013-2018 The Bitcoin Core developers
+# Copyright (c) 2013-2018 The NYC3 Core developers
 # Distributed under the MIT software license, see the accompanying
 # file COPYING or http://www.opensource.org/licenses/mit-license.php.
 #
@@ -22,7 +22,7 @@ def hex_switchEndian(s):
    pairList = [s[i:i+2].encode() for i in range(0, len(s), 2)]
    return b''.join(pairList[::-1]).decode()

-class BitcoinRPC:
+class NYC3RPC:
    def __init__(self, host, port, username, password):
        authpair = "%s:%s" % (username, password)
        authpair = authpair.encode('utf-8')
@@ -64,7 +64,7 @@ class BitcoinRPC:
        return 'error' in resp_obj and resp_obj['error'] is not None

 def get_block_hashes(settings, max_blocks_per_call=10000):
-    rpc = BitcoinRPC(settings['host'], settings['port'],
+    rpc = NYC3RPC(settings['host'], settings['port'],
             settings['rpcuser'], settings['rpcpassword'])

    height = settings['min_height']
@@ -11,5 +11,5 @@ This script should not be run manually, instead, after building as usual:
 During the process, the disk image window will pop up briefly where the fancy
 settings are applied. This is normal, please do not interfere.

-When finished, it will produce `Bitcoin-Core.dmg`.
+When finished, it will produce `NYC3-Core.dmg`.

@@ -3,7 +3,7 @@
 "http://www.w3.org/TR/2001/REC-SVG-20010904/DTD/svg10.dtd">
 <svg version="1.0" xmlns="http://www.w3.org/2000/svg" width="1000pt" height="640pt" viewBox="0 0 1000 640" preserveAspectRatio="xMidYMid meet">
 	<!-- kate: space-indent off;
-	Copyright (c) 2015 The Bitcoin Core developers
+	Copyright (c) 2015 The NYC3 Core developers
 	Distributed under the MIT software license, see the accompanying
 	file COPYING or http://www.opensource.org/licenses/mit-license.php.
 	-->
@@ -1,5 +1,5 @@
 #!/usr/bin/env python3
-# Copyright (c) 2013-2018 The Bitcoin Core developers
+# Copyright (c) 2013-2018 The NYC3 Core developers
 # Distributed under the MIT software license, see the accompanying
 # file COPYING or http://www.opensource.org/licenses/mit-license.php.
 import biplist
@@ -53,7 +53,7 @@ ds['.']['icvp'] = icvp
 ds['.']['vSrn'] = ('long', 1)

 ds['Applications']['Iloc'] = (370, 156)
-ds['Bitcoin-Qt.app']['Iloc'] = (128, 156)
+ds['NYC3-Qt.app']['Iloc'] = (128, 156)

 ds.flush()
 ds.close()
@@ -1,5 +1,5 @@
 #!/bin/sh
-# Copyright (c) 2014-2015 The Bitcoin Core developers
+# Copyright (c) 2014-2015 The NYC3 Core developers
 # Distributed under the MIT software license, see the accompanying
 # file COPYING or http://www.opensource.org/licenses/mit-license.php.

@@ -1,5 +1,5 @@
 #!/bin/sh
-# Copyright (c) 2014-2015 The Bitcoin Core developers
+# Copyright (c) 2014-2015 The NYC3 Core developers
 # Distributed under the MIT software license, see the accompanying
 # file COPYING or http://www.opensource.org/licenses/mit-license.php.

@@ -7,7 +7,7 @@ export LC_ALL=C
 set -e

 ROOTDIR=dist
-BUNDLE="${ROOTDIR}/Bitcoin-Qt.app"
+BUNDLE="${ROOTDIR}/NYC3-Qt.app"
 CODESIGN=codesign
 TEMPDIR=sign.temp
 TEMPLIST=${TEMPDIR}/signatures.txt
@@ -1,5 +1,5 @@
 #!/usr/bin/env bash
-# Copyright (c) 2016 The Bitcoin Core developers
+# Copyright (c) 2016 The NYC3 Core developers
 # Distributed under the MIT software license, see the accompanying
 # file COPYING or http://www.opensource.org/licenses/mit-license.php.

@@ -154,7 +154,7 @@ class FrameworkInfo(object):
 class ApplicationBundleInfo(object):
    def __init__(self, path):
        self.path = path
-        appName = "Bitcoin-Qt"
+        appName = "NYC3-Qt"
        self.binaryPath = os.path.join(path, "Contents", "MacOS", appName)
        if not os.path.exists(self.binaryPath):
            raise RuntimeError("Could not find bundle binary for " + path)
@@ -596,7 +596,7 @@ else:

 # ------------------------------------------------

-target = os.path.join("dist", "Bitcoin-Qt.app")
+target = os.path.join("dist", "NYC3-Qt.app")

 if verbose >= 2:
    print("+ Copying source bundle +")
@@ -1,5 +1,5 @@
 ### QoS (Quality of service) ###

-This is a Linux bash script that will set up tc to limit the outgoing bandwidth for connections to the Bitcoin network. It limits outbound TCP traffic with a source or destination port of 8333, but not if the destination IP is within a LAN.
+This is a Linux bash script that will set up tc to limit the outgoing bandwidth for connections to the NYC3 network. It limits outbound TCP traffic with a source or destination port of 8333, but not if the destination IP is within a LAN.

 This means one can have an always-on bitcoind instance running, and another local bitcoind/bitcoin-qt instance which connects to this node and receives blocks from it.
@@ -1,6 +1,6 @@
 #!/usr/bin/env bash
 #
-# Copyright (c) 2017 The Bitcoin Core developers
+# Copyright (c) 2017 The NYC3 Core developers
 # Distributed under the MIT software license, see the accompanying
 # file COPYING or http://www.opensource.org/licenses/mit-license.php.

@@ -9,7 +9,7 @@ export LC_ALL=C
 IF="eth0"
 #limit of the network interface in question
 LINKCEIL="1gbit"
-#limit outbound Bitcoin protocol traffic to this rate
+#limit outbound NYC3 protocol traffic to this rate
 LIMIT="160kbit"
 #defines the IPv4 address space for which you wish to disable rate limiting
 LOCALNET_V4="192.168.0.0/16"
@@ -1,5 +1,5 @@
 #!/usr/bin/env python3
-# Copyright (c) 2013-2018 The Bitcoin Core developers
+# Copyright (c) 2013-2018 The NYC3 Core developers
 # Distributed under the MIT software license, see the accompanying
 # file COPYING or http://www.opensource.org/licenses/mit-license.php.
 #
@@ -1,6 +1,6 @@
 ### TestGen ###

-Utilities to generate test vectors for the data-driven Bitcoin tests.
+Utilities to generate test vectors for the data-driven NYC3 tests.

 Usage: 

@@ -1,8 +1,8 @@
-# Copyright (c) 2012-2018 The Bitcoin Core developers
+# Copyright (c) 2012-2018 The NYC3 Core developers
 # Distributed under the MIT software license, see the accompanying
 # file COPYING or http://www.opensource.org/licenses/mit-license.php.
 '''
-Bitcoin base58 encoding and decoding.
+NYC3 base58 encoding and decoding.

 Based on https://bitcointalk.org/index.php?topic=1026.0 (public domain)
 '''
@@ -39,7 +39,7 @@ def b58encode(v):
        long_value = div
    result = __b58chars[long_value] + result

-    # Bitcoin does a little leading-zero-compression:
+    # NYC3 does a little leading-zero-compression:
    # leading 0-bytes in the input become leading-1s
    nPad = 0
    for c in v:
@@ -1,5 +1,5 @@
 #!/usr/bin/env python3
-# Copyright (c) 2012-2018 The Bitcoin Core developers
+# Copyright (c) 2012-2018 The NYC3 Core developers
 # Distributed under the MIT software license, see the accompanying
 # file COPYING or http://www.opensource.org/licenses/mit-license.php.
 '''
@@ -1,4 +1,4 @@
-# Valgrind suppressions file for Bitcoin.
+# Valgrind suppressions file for NYC3.
 #
 # Includes known Valgrind warnings in our dependencies that cannot be fixed
 # in-tree.
@@ -1,5 +1,5 @@
 #!/bin/sh
-# Copyright (c) 2014-2016 The Bitcoin Core developers
+# Copyright (c) 2014-2016 The NYC3 Core developers
 # Distributed under the MIT software license, see the accompanying
 # file COPYING or http://www.opensource.org/licenses/mit-license.php.

@@ -1,5 +1,5 @@
 #!/usr/bin/env bash
-# Copyright (c) 2014-2015 The Bitcoin Core developers
+# Copyright (c) 2014-2015 The NYC3 Core developers
 # Distributed under the MIT software license, see the accompanying
 # file COPYING or http://www.opensource.org/licenses/mit-license.php.

@@ -1,5 +1,5 @@
 #!/usr/bin/env python3
-# Copyright (c) 2018 The Bitcoin Core developers
+# Copyright (c) 2018 The NYC3 Core developers
 # Distributed under the MIT software license, see the accompanying
 # file COPYING or http://www.opensource.org/licenses/mit-license.php.
 """Verify commits against a trusted keys list."""
@@ -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) <laanwj@gmail.com>
+uid                  Wladimir J. van der Laan (NYC3 binary release signing key) <laanwj@gmail.com>
 ```

 #### Usage:
@@ -1,5 +1,5 @@
 #!/usr/bin/env bash
-# Copyright (c) 2016 The Bitcoin Core developers
+# Copyright (c) 2016 The NYC3 Core developers
 # Distributed under the MIT software license, see the accompanying
 # file COPYING or http://www.opensource.org/licenses/mit-license.php.

@@ -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:"
@@ -1,5 +1,5 @@
 #!/bin/sh
-# Copyright (c) 2014-2015 The Bitcoin Core developers
+# Copyright (c) 2014-2015 The NYC3 Core developers
 # Distributed under the MIT software license, see the accompanying
 # file COPYING or http://www.opensource.org/licenses/mit-license.php.

@@ -1,12 +1,12 @@
 #!/usr/bin/env python3
-# Copyright (c) 2014-2018 The Bitcoin Core developers
+# Copyright (c) 2014-2018 The NYC3 Core developers
 # Distributed under the MIT software license, see the accompanying
 # file COPYING or http://www.opensource.org/licenses/mit-license.php.

 """
    ZMQ example using python3's asyncio

-    Bitcoin should be started with the command line arguments:
+    NYC3 should be started with the command line arguments:
        bitcoind -testnet -daemon \
                -zmqpubrawtx=tcp://127.0.0.1:28332 \
                -zmqpubrawblock=tcp://127.0.0.1:28332 \
@@ -1,12 +1,12 @@
 #!/usr/bin/env python3
-# Copyright (c) 2014-2018 The Bitcoin Core developers
+# Copyright (c) 2014-2018 The NYC3 Core developers
 # Distributed under the MIT software license, see the accompanying
 # file COPYING or http://www.opensource.org/licenses/mit-license.php.

 """
    ZMQ example using python3's asyncio

-    Bitcoin should be started with the command line arguments:
+    NYC3 should be started with the command line arguments:
        bitcoind -testnet -daemon \
                -zmqpubrawtx=tcp://127.0.0.1:28332 \
                -zmqpubrawblock=tcp://127.0.0.1:28332 \
@@ -12,9 +12,9 @@ For example:

    make HOST=x86_64-w64-mingw32 -j4

-A prefix will be generated that's suitable for plugging into Bitcoin's
+A prefix will be generated that's suitable for plugging into NYC3's
 configure. In the above example, a dir named x86_64-w64-mingw32 will be
-created. To use it for Bitcoin:
+created. To use it for NYC3:

    ./configure --prefix=`pwd`/depends/x86_64-w64-mingw32

@@ -1,4 +1,4 @@
-This is a system of building and caching dependencies necessary for building Bitcoin. 
+This is a system of building and caching dependencies necessary for building NYC3. 
 There are several features that make it different from most similar systems:

 ### It is designed to be builder and host agnostic
@@ -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
@@ -1265,7 +1265,7 @@ DOCSET_FEEDNAME        = "Doxygen generated docs"
 # The default value is: org.doxygen.Project.
 # This tag requires that the tag GENERATE_DOCSET is set to YES.

-DOCSET_BUNDLE_ID       = org.bitcoin.Bitcoin-Core
+DOCSET_BUNDLE_ID       = org.bitcoin.NYC3-Core

 # The DOCSET_PUBLISHER_ID tag specifies a string that should uniquely identify
 # the documentation publisher. This should be a reverse domain-name style
@@ -1273,7 +1273,7 @@ DOCSET_BUNDLE_ID       = org.bitcoin.Bitcoin-Core
 # The default value is: org.doxygen.Publisher.
 # This tag requires that the tag GENERATE_DOCSET is set to YES.

-DOCSET_PUBLISHER_ID    = org.bitcoin.Bitcoin-Core
+DOCSET_PUBLISHER_ID    = org.bitcoin.NYC3-Core

 # The DOCSET_PUBLISHER_NAME tag identifies the documentation publisher.
 # The default value is: Publisher.
@@ -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
@@ -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 NYC3 client and it builds the backbone of the network. It downloads and, by default, stores the entire history of NYC3 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,18 +24,18 @@ 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?

-* See the documentation at the [Bitcoin Wiki](https://en.bitcoin.it/wiki/Main_Page)
+* See the documentation at the [NYC3 Wiki](https://en.bitcoin.it/wiki/Main_Page)
 for help and more information.
 * Ask for help on [#bitcoin](http://webchat.freenode.net?channels=bitcoin) on Freenode. If you don't have an IRC client, use [webchat here](http://webchat.freenode.net?channels=bitcoin).
-* Ask for help on the [BitcoinTalk](https://bitcointalk.org/) forums, in the [Technical Support board](https://bitcointalk.org/index.php?board=4.0).
+* Ask for help on the [NYC3Talk](https://bitcointalk.org/) forums, in the [Technical Support board](https://bitcointalk.org/index.php?board=4.0).

 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)
@@ -48,7 +48,7 @@ The following are developer notes on how to build Bitcoin Core on your native pl

 Development
 ---------------------
-The Bitcoin repo's [root README](/README.md) contains relevant information on the development process and automated testing.
+The NYC3 repo's [root README](/README.md) contains relevant information on the development process and automated testing.

 - [Developer Notes](developer-notes.md)
 - [Productivity Notes](productivity.md)
@@ -66,9 +66,9 @@ The Bitcoin repo's [root README](/README.md) contains relevant information on th
 - [Benchmarking](benchmarking.md)

 ### Resources
-* Discuss on the [BitcoinTalk](https://bitcointalk.org/) forums, in the [Development & Technical Discussion board](https://bitcointalk.org/index.php?board=6.0).
+* Discuss on the [NYC3Talk](https://bitcointalk.org/) forums, in the [Development & Technical Discussion board](https://bitcointalk.org/index.php?board=6.0).
 * Discuss project-specific development on #bitcoin-core-dev on Freenode. If you don't have an IRC client, use [webchat here](http://webchat.freenode.net/?channels=bitcoin-core-dev).
-* Discuss general Bitcoin development on #bitcoin-dev on Freenode. If you don't have an IRC client, use [webchat here](http://webchat.freenode.net/?channels=bitcoin-dev).
+* Discuss general NYC3 development on #bitcoin-dev on Freenode. If you don't have an IRC client, use [webchat here](http://webchat.freenode.net/?channels=bitcoin-dev).

 ### Miscellaneous
 - [Assets Attribution](assets-attribution.md)
@@ -1,9 +1,9 @@
-Bitcoin Core
+NYC3
 =============

 Intro
 -----
-Bitcoin is a free open source peer-to-peer electronic cash system that is
+NYC3 is a free open source peer-to-peer electronic cash system that is
 completely decentralized, without the need for a central server or trusted
 parties.  Users hold the crypto keys to their own money and transact directly
 with each other, with the help of a P2P network to check for double-spending.
@@ -13,8 +13,8 @@ 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.
-However, it downloads and stores the entire history of Bitcoin transactions;
+NYC3 is the original NYC3 client and it builds the backbone of the network.
+However, it downloads and stores the entire history of NYC3 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.

@@ -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
@@ -1,11 +1,11 @@
-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)).
 * [`BIP 13`](https://github.com/bitcoin/bips/blob/master/bip-0013.mediawiki): The address format for P2SH addresses has been implemented since **v0.6.0** ([PR #669](https://github.com/bitcoin/bitcoin/pull/669)).
 * [`BIP 14`](https://github.com/bitcoin/bips/blob/master/bip-0014.mediawiki): The subversion string is being used as User Agent since **v0.6.0** ([PR #669](https://github.com/bitcoin/bitcoin/pull/669)).
 * [`BIP 16`](https://github.com/bitcoin/bips/blob/master/bip-0016.mediawiki): The pay-to-script-hash evaluation rules have been implemented since **v0.6.0**, and took effect on *April 1st 2012* ([PR #748](https://github.com/bitcoin/bitcoin/pull/748)).
-* [`BIP 21`](https://github.com/bitcoin/bips/blob/master/bip-0021.mediawiki): The URI format for Bitcoin payments has been implemented since **v0.6.0** ([PR #176](https://github.com/bitcoin/bitcoin/pull/176)).
+* [`BIP 21`](https://github.com/bitcoin/bips/blob/master/bip-0021.mediawiki): The URI format for NYC3 payments has been implemented since **v0.6.0** ([PR #176](https://github.com/bitcoin/bitcoin/pull/176)).
 * [`BIP 22`](https://github.com/bitcoin/bips/blob/master/bip-0022.mediawiki): The 'getblocktemplate' (GBT) RPC protocol for mining has been implemented since **v0.7.0** ([PR #936](https://github.com/bitcoin/bitcoin/pull/936)).
 * [`BIP 23`](https://github.com/bitcoin/bips/blob/master/bip-0023.mediawiki): Some extensions to GBT have been implemented since **v0.10.0rc1**, including longpolling and block proposals ([PR #1816](https://github.com/bitcoin/bitcoin/pull/1816)).
 * [`BIP 30`](https://github.com/bitcoin/bips/blob/master/bip-0030.mediawiki): The evaluation rules to forbid creating new transactions with the same txid as previous not-fully-spent transactions were implemented since **v0.6.0**, and the rule took effect on *March 15th 2012* ([PR #915](https://github.com/bitcoin/bitcoin/pull/915)).
@@ -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*.
@@ -35,5 +35,5 @@ BIPs that are implemented by Bitcoin Core (up-to-date up to **v0.18.0**):
 * [`BIP 152`](https://github.com/bitcoin/bips/blob/master/bip-0152.mediawiki): Compact block transfer and related optimizations are used as of **v0.13.0** ([PR 8068](https://github.com/bitcoin/bitcoin/pull/8068)).
 * [`BIP 159`](https://github.com/bitcoin/bips/blob/master/bip-0159.mediawiki): The NODE_NETWORK_LIMITED service bit is signalled as of **v0.16.0** ([PR 11740](https://github.com/bitcoin/bitcoin/pull/11740)), and such nodes are connected to as of **v0.17.0** ([PR 10387](https://github.com/bitcoin/bitcoin/pull/10387)).
 * [`BIP 173`](https://github.com/bitcoin/bips/blob/master/bip-0173.mediawiki): Bech32 addresses for native Segregated Witness outputs are supported as of **v0.16.0** ([PR 11167](https://github.com/bitcoin/bitcoin/pull/11167)).
-* [`BIP 174`](https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki): RPCs to operate on Partially Signed Bitcoin Transactions (PSBT) are present as of **v0.17.0** ([PR 13557](https://github.com/bitcoin/bitcoin/pull/13557)).
+* [`BIP 174`](https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki): RPCs to operate on Partially Signed NYC3 Transactions (PSBT) are present as of **v0.17.0** ([PR 13557](https://github.com/bitcoin/bitcoin/pull/13557)).
 * [`BIP 176`](https://github.com/bitcoin/bips/blob/master/bip-0176.mediawiki): Bits Denomination [QT only] is supported as of **v0.16.0** ([PR 12035](https://github.com/bitcoin/bitcoin/pull/12035)).
@@ -32,6 +32,6 @@ Network specific options can be:

 ## Configuration File Path

-The configuration file is not automatically created; you can create it using your favorite text editor. By default, the configuration file name is `bitcoin.conf` and it is located in the Bitcoin data directory, but both the Bitcoin data directory and the configuration file path may be changed using the `-datadir` and `-conf` command-line options.
+The configuration file is not automatically created; you can create it using your favorite text editor. By default, the configuration file name is `bitcoin.conf` and it is located in the NYC3 data directory, but both the NYC3 data directory and the configuration file path may be changed using the `-datadir` and `-conf` command-line options.

 The `includeconf=<file>` option in the `bitcoin.conf` file can be used to include additional configuration files.
@@ -13,7 +13,7 @@ You will need the following dependencies, which can be installed as root via pkg
 ```shell
 pkg install autoconf automake boost-libs git gmake libevent libtool openssl pkgconf

-git clone https://github.com/bitcoin/bitcoin.git
+git clone https://github.com/nyc3coin/nyc3
 ```

 In order to run the test suite (recommended), you will need to have Python 3 installed:
@@ -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):

@@ -22,7 +22,7 @@ libtool
 pkg-config
 python37

-git clone https://github.com/bitcoin/bitcoin.git
+git clone https://github.com/nyc3coin/nyc3
 ```

 See [dependencies.md](dependencies.md) for a complete overview.
@@ -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).

@@ -17,7 +17,7 @@ pkg_add autoconf # (select highest version, e.g. 2.69)
 pkg_add automake # (select highest version, e.g. 1.16)
 pkg_add python # (select highest version, e.g. 3.6)

-git clone https://github.com/bitcoin/bitcoin.git
+git clone https://github.com/nyc3coin/nyc3
 ```

 See [dependencies.md](dependencies.md) for a complete overview.
@@ -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.

@@ -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,21 +78,21 @@ 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:

-    mkdir -p "/Users/${USER}/Library/Application Support/Bitcoin"
+    mkdir -p "/Users/${USER}/Library/Application Support/NYC3"

-    touch "/Users/${USER}/Library/Application Support/Bitcoin/bitcoin.conf"
+    touch "/Users/${USER}/Library/Application Support/NYC3/bitcoin.conf"

-    chmod 600 "/Users/${USER}/Library/Application Support/Bitcoin/bitcoin.conf"
+    chmod 600 "/Users/${USER}/Library/Application Support/NYC3/bitcoin.conf"

 The first time you run bitcoind, it will start downloading the blockchain. This process could take many hours, or even days on slower than average systems.

 You can monitor the download process by looking at the debug.log file:

-    tail -f $HOME/Library/Application\ Support/Bitcoin/debug.log
+    tail -f $HOME/Library/Application\ Support/NYC3/debug.log

 Other commands:
 -------
@@ -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
@@ -244,7 +244,7 @@ Setup and Build Example: Arch Linux
 This example lists the steps necessary to setup and build a command line only, non-wallet distribution of the latest changes on Arch Linux:

    pacman -S git base-devel boost libevent python
-    git clone https://github.com/bitcoin/bitcoin.git
+    git clone https://github.com/nyc3coin/nyc3
    cd bitcoin/
    ./autogen.sh
    ./configure --disable-wallet --without-gui --without-miniupnpc
@@ -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.


@@ -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,13 +83,13 @@ Ubuntu Bionic 18.04 <sup>[1](#footnote1)</sup>:

 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.

 Acquire the source in the usual way:

-    git clone https://github.com/bitcoin/bitcoin.git
+    git clone https://github.com/nyc3coin/nyc3

 Once the source code is ready the build steps are below:

@@ -111,13 +111,13 @@ For Ubuntu Bionic 18.04 and Windows Subsystem for Linux <sup>[1](#footnote1)</su

    sudo update-alternatives --config i686-w64-mingw32-g++  # Set the default mingw32 g++ compiler option to posix.

-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 located directly on the host Windows file system to perform the build.

 Acquire the source in the usual way:

-    git clone https://github.com/bitcoin/bitcoin.git
+    git clone https://github.com/nyc3coin/nyc3

 Then build using:

@@ -154,5 +154,5 @@ Footnotes
 compiler options to allow a choice between either posix or win32 threads. The default option is win32 threads which is the more
 efficient since it will result in binary code that links directly with the Windows kernel32.lib. Unfortunately, the headers
 required to support win32 threads conflict with some of the classes in the C++11 standard library, in particular std::mutex.
-It's not possible to build the Bitcoin Core code using the win32 version of the Mingw-w64 cross compilers (at least not without
-modifying headers in the Bitcoin Core source code).
+It's not possible to build the NYC3 code using the win32 version of the Mingw-w64 cross compilers (at least not without
+modifying headers in the NYC3 source code).
@@ -1,7 +1,7 @@
 Dependencies
 ============

-These are the dependencies currently used by Bitcoin Core. You can find instructions for installing them in the `build-*.md` file for your platform.
+These are the dependencies currently used by NYC3. You can find instructions for installing them in the `build-*.md` file for your platform.

 | Dependency | Version used | Minimum required | CVEs | Shared | [Bundled Qt library](https://doc.qt.io/qt-5/configure-options.html#third-party-libraries) |
 | --- | --- | --- | --- | --- | --- |
@@ -1,6 +1,6 @@
-# Support for Output Descriptors in Bitcoin Core
+# Support for Output Descriptors in NYC3

-Since Bitcoin Core v0.17, there is support for Output Descriptors. This is a
+Since NYC3 v0.17, there is support for Output Descriptors. This is a
 simple language which can be used to describe collections of output scripts.
 Supporting RPCs are:
 - `scantxoutset` takes as input descriptors to scan for, and also reports
@@ -100,7 +100,7 @@ not contain "p2" for brevity.
 ### Multisig

 Several pieces of software use multi-signature (multisig) scripts based
-on Bitcoin's OP_CHECKMULTISIG opcode. To support these, we introduce the
+on NYC3's OP_CHECKMULTISIG opcode. To support these, we introduce the
 `multi(k,key_1,key_2,...,key_n)` function. It represents a *k-of-n*
 multisig policy, where any *k* out of the *n* provided `KEY` expressions must
 sign.
@@ -172,7 +172,7 @@ steps, or for dumping wallet descriptors including private key material.
 ### Compatibility with old wallets

 In order to easily represent the sets of scripts currently supported by
-existing Bitcoin Core wallets, a convenience function `combo` is
+existing NYC3 wallets, a convenience function `combo` is
 provided, which takes as input a public key, and describes a set of P2PK,
 P2PKH, P2WPKH, and P2SH-P2WPH scripts for that key. In case the key is
 uncompressed, the set only includes P2PK and P2PKH scripts.
@@ -189,7 +189,7 @@ be detected in descriptors up to 501 characters, and up to 3 errors in longer
 ones. For larger numbers of errors, or other types of errors, there is a
 roughly 1 in a trillion chance of not detecting the errors.

-All RPCs in Bitcoin Core will include the checksum in their output. Only
+All RPCs in NYC3 will include the checksum in their output. Only
 certain RPCs require checksums on input, including `deriveaddress` and
 `importmulti`. The checksum for a descriptor without one can be computed
 using the `getdescriptorinfo` RPC.
@@ -22,7 +22,7 @@ Developer Notes
    - [Threads](#threads)
    - [Ignoring IDE/editor files](#ignoring-ideeditor-files)
 - [Development guidelines](#development-guidelines)
-    - [General Bitcoin Core](#general-bitcoin-core)
+    - [General NYC3](#general-bitcoin-core)
    - [Wallet](#wallet)
    - [General C++](#general-c)
    - [C++ data structures](#c-data-structures)
@@ -130,7 +130,7 @@ Refer to [/test/functional/README.md#style-guidelines](/test/functional/README.m
 Coding Style (Doxygen-compatible comments)
 ------------------------------------------

-Bitcoin Core uses [Doxygen](http://www.doxygen.nl/) to generate its official documentation.
+NYC3 uses [Doxygen](http://www.doxygen.nl/) to generate its official documentation.

 Use Doxygen-compatible comment blocks for functions, methods, and fields.

@@ -229,7 +229,7 @@ that run in `-regtest` mode.

 ### DEBUG_LOCKORDER

-Bitcoin Core is a multi-threaded application, and deadlocks or other
+NYC3 is a multi-threaded application, and deadlocks or other
 multi-threading bugs can be very difficult to track down. The `--enable-debug`
 configure option adds `-DDEBUG_LOCKORDER` to the compiler flags. This inserts
 run-time checks to keep track of which locks are held, and adds warnings to the
@@ -313,7 +313,7 @@ See the functional test documentation for how to invoke perf within tests.

 **Sanitizers**

-Bitcoin Core can be compiled with various "sanitizers" enabled, which add
+NYC3 can be compiled with various "sanitizers" enabled, which add
 instrumentation for issues regarding things like memory safety, thread race
 conditions, or undefined behavior. This is controlled with the
 `--with-sanitizers` configure flag, which should be a comma separated list of
@@ -412,7 +412,7 @@ Ignoring IDE/editor files
 In closed-source environments in which everyone uses the same IDE it is common
 to add temporary files it produces to the project-wide `.gitignore` file.

-However, in open source software such as Bitcoin Core, where everyone uses
+However, in open source software such as NYC3, where everyone uses
 their own editors/IDE/tools, it is less common. Only you know what files your
 editor produces and this may change from version to version. The canonical way
 to do this is thus to create your local gitignore. Add this to `~/.gitconfig`:
@@ -442,9 +442,9 @@ Development guidelines
 ============================

 A few non-style-related recommendations for developers, as well as points to
-pay attention to for reviewers of Bitcoin Core code.
+pay attention to for reviewers of NYC3 code.

-General Bitcoin Core
+General NYC3
 ----------------------

 - New features should be exposed on RPC first, then can be made available in the GUI
@@ -602,7 +602,7 @@ Strings and formatting

 - For `strprintf`, `LogPrint`, `LogPrintf` formatting characters don't need size specifiers

-  - *Rationale*: Bitcoin Core uses tinyformat, which is type safe. Leave them out to avoid confusion
+  - *Rationale*: NYC3 uses tinyformat, which is type safe. Leave them out to avoid confusion

 Variable names
 --------------
@@ -769,12 +769,12 @@ Subtrees

 Several parts of the repository are subtrees of software maintained elsewhere.

-Some of these are maintained by active developers of Bitcoin Core, in which case changes should probably go
+Some of these are maintained by active developers of NYC3, in which case changes should probably go
 directly upstream without being PRed directly against the project.  They will be merged back in the next
 subtree merge.

 Others are external projects without a tight relationship with our project.  Changes to these should also
-be sent upstream but bugfixes may also be prudent to PR against Bitcoin Core so that they can be integrated
+be sent upstream but bugfixes may also be prudent to PR against NYC3 so that they can be integrated
 quickly.  Cosmetic changes should be purely taken upstream.

 There is a tool in `test/lint/git-subtree-check.sh` to check a subtree directory for consistency with
@@ -807,7 +807,7 @@ you must be aware of.

 In most configurations we use the default LevelDB value for `max_open_files`,
 which is 1000 at the time of this writing. If LevelDB actually uses this many
-file descriptors it will cause problems with Bitcoin's `select()` loop, because
+file descriptors it will cause problems with NYC3's `select()` loop, because
 it may cause new sockets to be created where the fd value is >= 1024. For this
 reason, on 64-bit Unix systems we rely on an internal LevelDB optimization that
 uses `mmap()` + `close()` to open table files without actually retaining
@@ -833,14 +833,14 @@ details.
 ### Consensus Compatibility

 It is possible for LevelDB changes to inadvertently change consensus
-compatibility between nodes. This happened in Bitcoin 0.8 (when LevelDB was
+compatibility between nodes. This happened in NYC3 0.8 (when LevelDB was
 first introduced). When upgrading LevelDB you should review the upstream changes
 to check for issues affecting consensus compatibility.

 For example, if LevelDB had a bug that accidentally prevented a key from being
 returned in an edge case, and that bug was fixed upstream, the bug "fix" would
 be an incompatible consensus change. In this situation the correct behavior
-would be to revert the upstream fix before applying the updates to Bitcoin's
+would be to revert the upstream fix before applying the updates to NYC3's
 copy of LevelDB. In general you should be wary of any upstream changes affecting
 what data is returned from LevelDB queries.

@@ -969,7 +969,7 @@ A few guidelines for introducing and reviewing new RPC interfaces:
  RPCs whose behavior does *not* depend on the current chainstate may omit this
  call.

-  - *Rationale*: In previous versions of Bitcoin Core, the wallet was always
+  - *Rationale*: In previous versions of NYC3, the wallet was always
    in-sync with the chainstate (by virtue of them all being updated in the
    same cs_main lock). In order to maintain the behavior that wallet RPCs
    return results as of at least the highest best-known block an RPC
@@ -1,12 +1,12 @@
 Expectations for DNS Seed operators
 ====================================

-Bitcoin Core attempts to minimize the level of trust in DNS seeds,
+NYC3 attempts to minimize the level of trust in DNS seeds,
 but DNS seeds still pose a small amount of risk for the network.
 As such, DNS seeds must be run by entities which have some minimum
-level of trust within the Bitcoin community.
+level of trust within the NYC3 community.

-Other implementations of Bitcoin software may also use the same
+Other implementations of NYC3 software may also use the same
 seeds and may be more exposed. In light of this exposure, this
 document establishes some basic expectations for operating dnsseeds.

@@ -16,7 +16,7 @@ and not sell or transfer control of the DNS seed. Any hosting services
 contracted by the operator are equally expected to uphold these expectations.

 1. The DNS seed results must consist exclusively of fairly selected and
-functioning Bitcoin nodes from the public network to the best of the
+functioning NYC3 nodes from the public network to the best of the
 operator's understanding and capability.

 2. For the avoidance of doubt, the results may be randomized but must not
@@ -26,7 +26,7 @@ urgent technical necessity and disclosed.
 3. The results may not be served with a DNS TTL of less than one minute.

 4. Any logging of DNS queries should be only that which is necessary
-for the operation of the service or urgent health of the Bitcoin
+for the operation of the service or urgent health of the NYC3
 network and must not be retained longer than necessary nor disclosed
 to any third party.

@@ -42,7 +42,7 @@ details of their operating practices.
 related to the DNS seed operation.

 If these expectations cannot be satisfied the operator should
-discontinue providing services and contact the active Bitcoin
+discontinue providing services and contact the active NYC3
 Core development team as well as posting on
 [bitcoin-dev](https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev).

@@ -1,4 +1,4 @@
-Fuzz-testing Bitcoin Core
+Fuzz-testing NYC3
 ==========================

 A special test harness in `src/test/fuzz/` is provided for each fuzz target to
@@ -43,7 +43,7 @@ export AFLPATH=$PWD

 ### Instrumentation

-To build Bitcoin Core using AFL instrumentation (this assumes that the
+To build NYC3 using AFL instrumentation (this assumes that the
 `AFLPATH` was set as above):
 ```
 ./configure --disable-ccache --disable-shared --enable-tests --enable-fuzz --disable-wallet --disable-bench --with-utils=no --with-daemon=no --with-libs=no --with-gui=no CC=${AFLPATH}/afl-gcc CXX=${AFLPATH}/afl-g++
@@ -1,4 +1,4 @@
 Gitian building
 ================

-This file was moved to [the Bitcoin Core documentation repository](https://github.com/bitcoin-core/docs/blob/master/gitian-building.md) at [https://github.com/bitcoin-core/docs](https://github.com/bitcoin-core/docs).
+This file was moved to [the NYC3 documentation repository](https://github.com/bitcoin-core/docs/blob/master/gitian-building.md) at [https://github.com/bitcoin-core/docs](https://github.com/bitcoin-core/docs).
@@ -84,9 +84,9 @@ OpenRC).
 ### macOS

 Binary:              `/usr/local/bin/bitcoind`  
-Configuration file:  `~/Library/Application Support/Bitcoin/bitcoin.conf`  
-Data directory:      `~/Library/Application Support/Bitcoin`  
-Lock file:           `~/Library/Application Support/Bitcoin/.lock`  
+Configuration file:  `~/Library/Application Support/NYC3/bitcoin.conf`  
+Data directory:      `~/Library/Application Support/NYC3`  
+Lock file:           `~/Library/Application Support/NYC3/.lock`  

 Installing Service Configuration
 -----------------------------------
@@ -4,10 +4,10 @@
 bitcoin-cli \- manual page for bitcoin-cli v0.18.0.0
 .SH SYNOPSIS
 .B bitcoin-cli
-[\fI\,options\/\fR] \fI\,<command> \/\fR[\fI\,params\/\fR]  \fI\,Send command to Bitcoin Core\/\fR
+[\fI\,options\/\fR] \fI\,<command> \/\fR[\fI\,params\/\fR]  \fI\,Send command to NYC3\/\fR
 .br
 .B bitcoin-cli
-[\fI\,options\/\fR] \fI\,-named <command> \/\fR[\fI\,name=value\/\fR]...  \fI\,Send command to Bitcoin Core (with named arguments)\/\fR
+[\fI\,options\/\fR] \fI\,-named <command> \/\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 <command>      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
 \-?
@@ -104,9 +104,9 @@ Chain selection options:
 .IP
 Use the test chain
 .SH COPYRIGHT
-Copyright (C) 2009-2019 The Bitcoin Core developers
+Copyright (C) 2009-2019 The NYC3 Core developers

-Please contribute if you find Bitcoin Core useful. Visit
+Please contribute if you find NYC3 useful. Visit
 <https://bitcoincore.org> for further information about the software.
 The source code is available from <https://github.com/bitcoin/bitcoin>.

@@ -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
 \-?
@@ -626,9 +626,9 @@ Set SSL root certificates for payment request (default: \fB\-system\-\fR)
 .IP
 Show splash screen on startup (default: 1)
 .SH COPYRIGHT
-Copyright (C) 2009-2019 The Bitcoin Core developers
+Copyright (C) 2009-2019 The NYC3 Core developers

-Please contribute if you find Bitcoin Core useful. Visit
+Please contribute if you find NYC3 useful. Visit
 <https://bitcoincore.org> for further information about the software.
 The source code is available from <https://github.com/bitcoin/bitcoin>.

@@ -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
 \-?
@@ -105,9 +105,9 @@ set=NAME:JSON\-STRING
 .IP
 Set register NAME to given JSON\-STRING
 .SH COPYRIGHT
-Copyright (C) 2009-2019 The Bitcoin Core developers
+Copyright (C) 2009-2019 The NYC3 Core developers

-Please contribute if you find Bitcoin Core useful. Visit
+Please contribute if you find NYC3 useful. Visit
 <https://bitcoincore.org> for further information about the software.
 The source code is available from <https://github.com/bitcoin/bitcoin>.

@@ -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:"
@@ -52,9 +52,9 @@ info
 .IP
 Get wallet info
 .SH COPYRIGHT
-Copyright (C) 2009-2019 The Bitcoin Core developers
+Copyright (C) 2009-2019 The NYC3 Core developers

-Please contribute if you find Bitcoin Core useful. Visit
+Please contribute if you find NYC3 useful. Visit
 <https://bitcoincore.org> for further information about the software.
 The source code is available from <https://github.com/bitcoin/bitcoin>.

@@ -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
 \-?
@@ -600,9 +600,9 @@ Username for JSON\-RPC connections
 .IP
 Accept command line and JSON\-RPC commands
 .SH COPYRIGHT
-Copyright (C) 2009-2019 The Bitcoin Core developers
+Copyright (C) 2009-2019 The NYC3 Core developers

-Please contribute if you find Bitcoin Core useful. Visit
+Please contribute if you find NYC3 useful. Visit
 <https://bitcoincore.org> for further information about the software.
 The source code is available from <https://github.com/bitcoin/bitcoin>.

@@ -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 NYC3
 Transactions (PSBTs, as specified in
 [BIP 174](https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki)).

@@ -10,7 +10,7 @@ scenarios.

 ## PSBT in general

-PSBT is an interchange format for Bitcoin transactions that are not fully signed
+PSBT is an interchange format for NYC3 transactions that are not fully signed
 yet, together with relevant metadata to help entities work towards signing it.
 It is intended to simplify workflows where multiple parties need to cooperate to
 produce a transaction. Examples include hardware wallets, multisig setups, and
@@ -18,7 +18,7 @@ produce a transaction. Examples include hardware wallets, multisig setups, and

 ### Overall workflow

-Overall, the construction of a fully signed Bitcoin transaction goes through the
+Overall, the construction of a fully signed NYC3 transaction goes through the
 following steps:

 - A **Creator** proposes a particular transaction to be created. They construct
@@ -32,7 +32,7 @@ following steps:
  partial signature for the inputs for which they have relevant key(s).
 - A **Finalizer** is run for each input to convert the partial signatures and
  possibly script information into a final `scriptSig` and/or `scriptWitness`.
- An **Extractor** produces a valid Bitcoin transaction (in network format)
+- An **Extractor** produces a valid NYC3 transaction (in network format)
  from a PSBT for which all inputs are finalized.

 Generally, each of the above (excluding Creator and Extractor) will simply
@@ -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.
@@ -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.
@@ -1,4 +1,4 @@
-Bitcoin Core version 0.18.x is now available from:
+NYC3 version 0.18.x is now available from:

  <https://bitcoincore.org/bin/bitcoin-core-0.18.x/>

@@ -19,7 +19,7 @@ How to Upgrade
 If you are running an older version, shut it down. Wait until it has
 completely shut down (which might take a few minutes for older
 versions), then run the installer (on Windows) or just copy over
-`/Applications/Bitcoin-Qt` (on Mac) or `bitcoind`/`bitcoin-qt` (on
+`/Applications/NYC3-Qt` (on Mac) or `bitcoind`/`bitcoin-qt` (on
 Linux).

 The first time you run version 0.15.0 or newer, your chainstate database
@@ -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
--- a/Show More
+++ b/Show More
Author	SHA1	Message	Date
barrystyle	43a15d192e	repair copyright headers across codebase	2019-06-15 17:49:59 +08:00
barrystyle	44bb626396	change URI referencing bitcoin to nyc3	2019-06-15 17:23:22 +08:00
barrystyle	1a633d08c1	include quicker blake2b routines	2019-06-13 12:38:58 +08:00
barrystyle	8e2967a843	revert bech32 address change	2019-06-13 10:15:08 +08:00
nyc3coin	04da911127	Merge pull request #4 from barrystyle/master misc work	2019-06-13 05:12:24 +08:00
barrystyle	744a4e0259	remove some unused vars from splashscreen	2019-06-13 05:09:48 +08:00
barrystyle	8e8108ff2f	make argon2s native to the repo, allowing for clean builds	2019-06-13 05:09:06 +08:00
barrystyle	dd684bdabe	make bech32 the defaultaddress format	2019-06-13 04:55:41 +08:00
nyc3coin	1739b485fd	Merge pull request #1 from akshaynexus/master [Build] Update version , Bitcoin to NYC3 , Gitian descriptors update	2019-06-11 06:12:10 +08:00
Akshay	f7f7c5c1bf	update splashes	2019-06-11 00:49:17 +03:00
Akshay	2aced5a86c	change splash screen	2019-06-11 00:13:19 +03:00
Akshay	403583dcbf	Update icons	2019-06-10 23:53:08 +03:00
nyc3coin	c6c7351beb	Merge pull request #2 from barrystyle/master Add nodes, speed up sync	2019-06-10 05:55:55 +08:00
barrystyle	bce608fdbb	disable rbf125 by default	2019-06-10 05:50:08 +08:00
barrystyle	4b2cf9258c	speed up sync, add more default seeds	2019-06-10 05:45:12 +08:00
Akshay	6a4a654545	Fix icns error	2019-06-09 23:07:43 +03:00
Akshay	516a7bafec	Bitcoin to NYC3 and update gitian compile code	2019-06-09 12:22:49 +03:00
Akshay	d8192b664c	[Build] Update gitian descriptors	2019-06-08 17:56:08 +03:00
Akshay	eca8a7d78f	Bitcoin to NYC3	2019-06-08 17:47:53 +03:00
Akshay CM	433253cb83	update to v1.1	2019-06-08 01:24:54 +03:00
barrystyle	1077300b05	correct files for win64 build	2019-06-05 21:00:20 +00:00
barrystyle	23c3b7ed32	Merge branch 'rebrand'	2019-06-06 04:14:39 +08:00
barrystyle	14c5e6c59a	final rebranding to NYC3	2019-06-06 01:36:37 +08:00
barrystyle	80c2180cec	Merge branch 'develop'	2019-06-06 01:04:34 +08:00
barrystyle	89d7a9cd6b	dissatisfied with algorithm, changed out for argon2s	2019-06-06 01:03:38 +08:00
barrystyle	6eaecb1553	adjust icons for windows build	2019-05-30 18:16:40 +08:00
barrystyle	cd956d4aed	final alterations for mainnet	2019-05-30 17:48:04 +08:00
barrystyle	c81599d338	Merge branch 'develop'	2019-05-30 17:41:57 +08:00
barrystyle	688431bdba	preseed rand so a random image is selected on launch	2019-05-30 17:40:27 +08:00
barrystyle	1431c5cd1a	commit first node address and finalize genesis	2019-05-30 17:35:33 +08:00
barrystyle	4c526e65fa	final units, path and images	2019-05-30 06:45:03 +08:00
barrystyle	3d953055b0	rebrand codebase	2019-05-30 05:51:29 +08:00
barrystyle	2d24a1c6c5	implement parallel pow hash algorithm, along with genesis block	2019-05-29 18:07:04 +08:00
barrystyle	eed5784acb	retrofit setgenerate function for solomining	2019-05-29 06:29:01 +08:00
barrystyle	a09a38567a	set chain up for 10s blocktime, prevent possible future problems	2019-05-29 05:52:38 +08:00
barrystyle	532eaf649f	cherrypick d531cf36 from litecoin-project/litecoin	2019-05-29 04:35:28 +08:00