xazab

.github/ISSUE_TEMPLATE.md

@@ -1,10 +1,10 @@
 <!--- Remove sections that do not apply -->
 
-This issue tracker is only for technical issues related to Dash Core.
+This issue tracker is only for technical issues related to Xazab Core.
 
-General Dash questions and/or support requests and are best directed to the [Dashpay Reddit](https://www.reddit.com/r/dashpay/).
+General Xazab questions and/or support requests and are best directed to the [Xazabpay Reddit](https://www.reddit.com/r/xazab/).
 
-To report critical security issues, email infosec@dash.org and/or see the DASH bug bounty program on [Bugcrowd](https://bugcrowd.com/dashdigitalcash) instead of creating Github issues.
+To report critical security issues, email infosec@xazab.org and/or see the XAZAB bug bounty program on [Bugcrowd](https://bugcrowd.com/xazabdigitalcash) instead of creating Github issues.
 
 ### Describe the issue
 
@@ -23,7 +23,7 @@ Tell us what happens instead
 ### Screenshots.
 If the issue is related to the GUI, screenshots can be added to this issue via drag & drop.
 
-### What version of Dash Core are you using?
+### What version of Xazab Core are you using?
 List the version number/commit ID, and if it is an official binary, self compiled or a distribution package such as PPA.
 
 ### Machine specs:

.gitignore

@@ -6,15 +6,15 @@ reset-files.bash
 *.tar.gz
 
 *.exe
-src/dash
-src/dashd
-src/dash-cli
-src/dash-tx
-src/test/test_dash
-src/test/test_dash_fuzzy
-src/qt/test/test_dash-qt
+src/xazab
+src/xazabd
+src/xazab-cli
+src/xazab-tx
+src/test/test_xazab
+src/test/test_xazab_fuzzy
+src/qt/test/test_xazab-qt
 src/qt/res/css/colors/*
-src/bench/bench_dash
+src/bench/bench_xazab
 
 # autoreconf
 Makefile.in
@@ -37,8 +37,8 @@ config.log
 config.status
 configure
 libtool
-src/config/dash-config.h
-src/config/dash-config.h.in
+src/config/xazab-config.h
+src/config/xazab-config.h.in
 src/config/stamp-h1
 share/setup.nsi
 share/qt/Info.plist
@@ -83,14 +83,14 @@ libconftest.dylib*
 # Compilation and Qt preprocessor part
 *.qm
 Makefile
-dash-qt
-Dash-Qt.app
+xazab-qt
+Xazab-Qt.app
 background.tiff*
 !/depends/Makefile
 
 # Unit-tests
 Makefile.test
-dash-qt_test
+xazab-qt_test
 
 # Resources cpp
 qrc_*.cpp
@@ -103,7 +103,7 @@ build
 *.gcno
 *.gcda
 /*.info
-test_dash.coverage/
+test_xazab.coverage/
 total.coverage/
 coverage_percent.txt
 
@@ -121,15 +121,15 @@ test/cache/*
 .autotools
 /doc/doxygen/
 
-libdashconsensus.pc
+libxazabconsensus.pc
 contrib/devtools/split-debug.sh
-src/qt/dash-qt.bash
+src/qt/xazab-qt.bash
 qa/pull-tester/tests-config.sh
 
 #development symlinks
-dash-cli
-dashd
-dash-qt
+xazab-cli
+xazabd
+xazab-qt
 make
 
 /docker/bin

.travis.yml

@@ -54,7 +54,7 @@ builddocker: &builddocker
  stage: build docker
  script:
  # no need to run tests again here
- - if [ "$DOCKER_BUILD" = "true" ]; then $DOCKER_RUN_IN_BUILDER ./ci/build_depends.sh && $DOCKER_RUN_IN_BUILDER ./ci/build_src.sh && BUILD_DIR=build-ci/dashcore-$BUILD_TARGET ./docker/build-docker.sh; fi
+ - if [ "$DOCKER_BUILD" = "true" ]; then $DOCKER_RUN_IN_BUILDER ./ci/build_depends.sh && $DOCKER_RUN_IN_BUILDER ./ci/build_src.sh && BUILD_DIR=build-ci/xazabcore-$BUILD_TARGET ./docker/build-docker.sh; fi
 
 jobs:
  include:
@@ -111,7 +111,7 @@ jobs:
 
 before_cache:
  # Save builder image
- - docker save dash-builder-$BUILD_TARGET-$TRAVIS_JOB_NUMBER $(docker history -q dash-builder-$BUILD_TARGET-$TRAVIS_JOB_NUMBER | grep -v \<missing\>) | gzip -2 > $HOME/cache/docker/dash-builder-$BUILD_TARGET.tar.gz
+ - docker save xazab-builder-$BUILD_TARGET-$TRAVIS_JOB_NUMBER $(docker history -q xazab-builder-$BUILD_TARGET-$TRAVIS_JOB_NUMBER | grep -v \<missing\>) | gzip -2 > $HOME/cache/docker/xazab-builder-$BUILD_TARGET.tar.gz
 
 install:
  # Fix annoying Travis bug: a branch with a single commit has an empty TRAVIS_COMMIT_RANGE sometimes
@@ -129,15 +129,15 @@ install:
  # Keep this as it makes caching related debugging easier
  - ls -lah $HOST_CACHE_DIR && ls -lah $HOST_CACHE_DIR/depends && ls -lah $HOST_CACHE_DIR/ccache && ls -lah $HOST_CACHE_DIR/docker
  # Load cached builder image
- - if [ -f $HOST_CACHE_DIR/docker/dash-builder-$BUILD_TARGET.tar.gz ]; then zcat $HOST_CACHE_DIR/docker/dash-builder-$BUILD_TARGET.tar.gz | docker load || true; fi
+ - if [ -f $HOST_CACHE_DIR/docker/xazab-builder-$BUILD_TARGET.tar.gz ]; then zcat $HOST_CACHE_DIR/docker/xazab-builder-$BUILD_TARGET.tar.gz | docker load || true; fi
  - travis_retry docker pull ubuntu:bionic
  - travis_retry docker build -t $BUILDER_IMAGE_NAME --build-arg=USER_ID=$UID --build-arg=GROUP_ID=$UID --build-arg=BUILD_TARGET=$BUILD_TARGET -f ci/Dockerfile.builder ci
 before_script:
  # Make sure stdout is in blocking mode. Otherwise builds will fail due to large writes to stdout
  # See https://github.com/travis-ci/travis-ci/issues/4704. If this gets fixed, this line can also be removed.
  - python3 -c 'import os,sys,fcntl; flags = fcntl.fcntl(sys.stdout, fcntl.F_GETFL); fcntl.fcntl(sys.stdout, fcntl.F_SETFL, flags&~os.O_NONBLOCK);'
  # Build docker image only for develop branch of the main repo
- - if [ "$TRAVIS_REPO_SLUG" != "dashpay/dash" -o "$TRAVIS_BRANCH" != "develop" -o "$TRAVIS_PULL_REQUEST" != "false" ]; then export DOCKER_BUILD="false"; echo DOCKER_BUILD=$DOCKER_BUILD; fi
+ - if [ "$TRAVIS_REPO_SLUG" != "xazab/xazab" -o "$TRAVIS_BRANCH" != "develop" -o "$TRAVIS_PULL_REQUEST" != "false" ]; then export DOCKER_BUILD="false"; echo DOCKER_BUILD=$DOCKER_BUILD; fi
 after_script:
  - echo $TRAVIS_COMMIT_RANGE
  - echo $TRAVIS_COMMIT_LOG

.tx/config

@@ -1,7 +1,7 @@
 [main]
 host = https://www.transifex.com
 
-[dash.qt-translation-012x]
-file_filter = src/qt/locale/dash_<lang>.ts
-source_file = src/qt/locale/dash_en.ts
+[xazab.qt-translation-012x]
+file_filter = src/qt/locale/xazab_<lang>.ts
+source_file = src/qt/locale/xazab_en.ts
 source_lang = en

CMakeLists.txt

@@ -6,7 +6,7 @@
 # You'll also have to manually change the executable in the configuration to the correct path of the already built executable
 
 cmake_minimum_required(VERSION 3.7)
-project(dash)
+project(xazab)
 
 set(CMAKE_CXX_STANDARD 14)
 
@@ -87,4 +87,4 @@ file(GLOB SOURCE_FILES
  src/zmq/*.h
  )
 
-add_executable(dash ${SOURCE_FILES})
+add_executable(xazab ${SOURCE_FILES})

CONTRIBUTING.md

@@ -1,7 +1,7 @@
-Contributing to Dash Core
+Contributing to Xazab Core
 ============================
 
-The Dash Core project operates an open contributor model where anyone is
+The Xazab Core project operates an open contributor model where anyone is
 welcome to contribute towards development in the form of peer review, testing
 and patches. This document explains the practical process and guidelines for
 contributing.
@@ -57,7 +57,7 @@ the pull request affects. Valid areas as:
 
  - *Consensus* for changes to consensus critical code
  - *Docs* for changes to the documentation
- - *Qt* for changes to dash-qt
+ - *Qt* for changes to xazab-qt
  - *Mining* for changes to the mining code
  - *Net* or *P2P* for changes to the peer-to-peer network code
  - *RPC/REST/ZMQ* for changes to the RPC, REST or ZMQ APIs
@@ -82,7 +82,7 @@ Examples:
  Trivial: Fix typo in init.cpp
 
 Note that translations should not be submitted as pull requests, please see
-[Translation Process](https://github.com/dashpay/dash/blob/master/doc/translation_process.md) 
+[Translation Process](https://github.com/xazab/xazab/blob/master/doc/translation_process.md) 
 for more information on helping with translations.
 
 If a pull request is not to be considered for merging (yet), please
@@ -161,11 +161,11 @@ where possible keep them short, uncomplex and easy to verify.
 "Decision Making" Process
 -------------------------
 
-The following applies to code changes to the Dash Core project (and related
-projects such as libsecp256k1), and is not to be confused with overall Dash
+The following applies to code changes to the Xazab Core project (and related
+projects such as libsecp256k1), and is not to be confused with overall Xazab
 Network Protocol consensus changes.
 
-Whether a pull request is merged into Dash Core rests with the project merge
+Whether a pull request is merged into Xazab Core rests with the project merge
 maintainers and ultimately the project lead.
 
 Maintainers will take into consideration if a patch is in line with the general
@@ -183,7 +183,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 Dash consensus rules are considerably more involved than
+Patches that change Xazab 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
@@ -224,7 +224,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 Dash consensus, it must have been
+Where a patch set proposes to change the Xazab 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.
@@ -250,7 +250,7 @@ function gfd() {
 
 ### Finding Reviewers
 
-The review process is normally fairly responsive on the Dash Core repository, however
+The review process is normally fairly responsive on the Xazab Core repository, however
 this might not always be the case. If you find that you've been waiting
 for a pull request to be given attention for several months, there may be a number
 of reasons for this, some of which you can do something about:
@@ -282,7 +282,7 @@ of reasons for this, some of which you can do something about:
 Release Policy
 --------------
 
-The project leader is the release manager for each Dash Core release.
+The project leader is the release manager for each Xazab Core release.
 
 Copyright
 ---------

COPYING

@@ -2,7 +2,7 @@ The MIT License (MIT)
 
 Copyright (c) 2009-2020 The Bitcoin Core developers
 Copyright (c) 2009-2020 Bitcoin Developers
-Copyright (c) 2014-2020 The Dash Core developers
+Copyright (c) 2014-2020 The Xazab Core developers
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

INSTALL.md

@@ -1,5 +1,5 @@
-Building Dash
+Building Xazab
 =============
 
 See doc/build-*.md for instructions on building the various
-elements of the Dash Core reference implementation of Dash.
+elements of the Xazab Core reference implementation of Xazab.