Raptoreum -> Theta

Raptoreum -> Theta
raptoreum -> theta
RTM -> FITA

.github/ISSUE_TEMPLATE.md

@@ -1,8 +1,8 @@
 <!--- Remove sections that do not apply -->
 
-This issue tracker is only for technical issues related to Raptoreum Core.
+This issue tracker is only for technical issues related to Theta Core.
 
-General Raptoreum questions and/or support requests and are best directed to the [Raptoreum Discord](https://discord.com/invite/2T8xG7e).
+General Theta questions and/or support requests and are best directed to the [Theta Discord](https://discord.com/invite/2T8xG7e).
 
 To report critical security issues, DM the Core or Developer Teams instead of creating Github issues.
 
@@ -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 Raptoreum Core are you using?
+### What version of Theta 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:

.github/workflows/build.yaml

@@ -1,5 +1,5 @@
 ---
-name: Raptoreum Build
+name: Theta Build
 on:
   push:
     branches:
@@ -11,9 +11,9 @@ on:
     branches:
       - develop
 env:
-  COIN_NAME: raptoreum
-  BUILD_DIR: raptoreum-build
-  COMPRESS_DIR: raptoreum-compress
+  COIN_NAME: theta
+  BUILD_DIR: theta-build
+  COMPRESS_DIR: theta-compress
   TEST_LOG_ARTIFACT_DIR: test-logs
 jobs:
   checking-build-version:
@@ -96,7 +96,7 @@ jobs:
         run: |
           make -j$(nproc)
           mkdir -p $BUILD_DIR
-          mv src/{raptoreum-cli,raptoreum-tx,raptoreumd,qt/raptoreum-qt} $BUILD_DIR/
+          mv src/{theta-cli,theta-tx,thetad,qt/theta-qt} $BUILD_DIR/
           strip $BUILD_DIR/*
       - name: generate checksum and compress
         run: |
@@ -155,7 +155,7 @@ jobs:
         run: |
           make -j$(nproc)
           mkdir -p $BUILD_DIR
-          mv src/{raptoreum-cli,raptoreum-tx,raptoreumd,qt/raptoreum-qt} $BUILD_DIR/
+          mv src/{theta-cli,theta-tx,thetad,qt/theta-qt} $BUILD_DIR/
           strip $BUILD_DIR/*
       - name: generate checksum and compress
         run: |
@@ -213,7 +213,7 @@ jobs:
         run: |
           make -j8
           mkdir -p $BUILD_DIR
-          mv src/{raptoreum-cli,raptoreum-tx,raptoreumd,qt/raptoreum-qt} $BUILD_DIR/
+          mv src/{theta-cli,theta-tx,thetad,qt/theta-qt} $BUILD_DIR/
           strip $BUILD_DIR/*
       - name: generate checksum and compress
         run: |
@@ -245,10 +245,10 @@ jobs:
         run: |
           make deploy
           mkdir -p macos-dmg
-          mv Raptoreum-Qt.dmg macos-dmg/
+          mv Theta-Qt.dmg macos-dmg/
           cd macos-dmg
-          echo "sha256: `shasum Raptoreum-Qt.dmg`" >> checksums.txt
-          echo "openssl-sha256: `openssl sha256 Raptoreum-Qt.dmg`" >> checksums.txt
+          echo "sha256: `shasum Theta-Qt.dmg`" >> checksums.txt
+          echo "openssl-sha256: `openssl sha256 Theta-Qt.dmg`" >> checksums.txt
           cd ..
       - name: Upload dmg file
         uses: actions/upload-artifact@v3
@@ -286,7 +286,7 @@ jobs:
         run: |
           make -j$(nproc)
           mkdir -p $BUILD_DIR
-          mv src/{raptoreum-cli,raptoreum-tx,raptoreumd,qt/raptoreum-qt} $BUILD_DIR/
+          mv src/{theta-cli,theta-tx,thetad,qt/theta-qt} $BUILD_DIR/
       - name: generate checksum and compress binary
         run: |
           echo "buildng $BUILD_VERSION version"
@@ -344,7 +344,7 @@ jobs:
         run: |
           make -j$(nproc)
           mkdir -p $BUILD_DIR
-          mv src/{raptoreum-cli,raptoreum-tx,raptoreumd,qt/raptoreum-qt} $BUILD_DIR/
+          mv src/{theta-cli,theta-tx,thetad,qt/theta-qt} $BUILD_DIR/
       - name: generate checksum and compress binary
         run: |
           echo "buildng $BUILD_VERSION version"
@@ -405,7 +405,7 @@ jobs:
         run: |
           make -j$(nproc)
           mkdir -p $BUILD_DIR
-          mv src/{raptoreum-cli.exe,raptoreum-tx.exe,raptoreumd.exe,qt/raptoreum-qt.exe} $BUILD_DIR/
+          mv src/{theta-cli.exe,theta-tx.exe,thetad.exe,qt/theta-qt.exe} $BUILD_DIR/
           strip $BUILD_DIR/*
       - name: generate checksum and compress binary
         run: |

.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/raptoreumcore-$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/thetacore-$BUILD_TARGET ./docker/build-docker.sh; fi
 
 jobs:
   include:
@@ -142,7 +142,7 @@ jobs:
 
 before_cache:
   # Save builder image
-  - docker save raptoreum-builder-$BUILD_TARGET-$TRAVIS_JOB_NUMBER $(docker history -q raptoreum-builder-$BUILD_TARGET-$TRAVIS_JOB_NUMBER | grep -v \<missing\>) | gzip -2 > $HOME/cache/docker/raptoreum-builder-$BUILD_TARGET.tar.gz
+  - docker save theta-builder-$BUILD_TARGET-$TRAVIS_JOB_NUMBER $(docker history -q theta-builder-$BUILD_TARGET-$TRAVIS_JOB_NUMBER | grep -v \<missing\>) | gzip -2 > $HOME/cache/docker/theta-builder-$BUILD_TARGET.tar.gz
 
 install:
     # Fix annoying Travis bug: a branch with a single commit has an empty TRAVIS_COMMIT_RANGE sometimes
@@ -159,15 +159,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/raptoreum-builder-$BUILD_TARGET.tar.gz ]; then zcat $HOST_CACHE_DIR/docker/raptoreum-builder-$BUILD_TARGET.tar.gz | docker load || true; fi
+    - if [ -f $HOST_CACHE_DIR/docker/theta-builder-$BUILD_TARGET.tar.gz ]; then zcat $HOST_CACHE_DIR/docker/theta-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" != "raptoreum/raptoreum" -o "$TRAVIS_BRANCH" != "develop" -o "$TRAVIS_PULL_REQUEST" != "false" ]; then export DOCKER_BUILD="false"; echo DOCKER_BUILD=$DOCKER_BUILD; fi
+    - if [ "$TRAVIS_REPO_SLUG" != "theta/theta" -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
 
-[raptoreum.qt-translation-012x]
-file_filter = src/qt/locale/raptoreum_<lang>.ts
-source_file = src/qt/locale/raptoreum_en.ts
+[theta.qt-translation-012x]
+file_filter = src/qt/locale/theta_<lang>.ts
+source_file = src/qt/locale/theta_en.ts
 source_lang = en

CMakeLists.txt

@@ -8,7 +8,7 @@
 cmake_minimum_required(VERSION 3.7)
 
 set(PROJECT_NAME
-    raptoreum)
+    theta)
 
 project(${PROJECT_NAME}
   LANGUAGES CXX C)

CONTRIBUTING.md

@@ -1,7 +1,7 @@
-Contributing to Raptoreum Core
+Contributing to Theta Core
 ============================
 
-The Raptoreum Core project operates an open contributor model where anyone is
+The Theta 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 raptoreum-qt
+  - *Qt* for changes to theta-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/Raptor3um/raptoreum/blob/master/doc/translation_process.md) 
+[Translation Process](https://github.com/Raptor3um/theta/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 Raptoreum Core project (and related
-projects such as libsecp256k1), and is not to be confused with overall Raptoreum
+The following applies to code changes to the Theta Core project (and related
+projects such as libsecp256k1), and is not to be confused with overall Theta
 Network Protocol consensus changes.
 
-Whether a pull request is merged into Raptoreum Core rests with the project merge
+Whether a pull request is merged into Theta 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 Raptoreum consensus rules are considerably more involved than
+Patches that change Theta 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 Raptoreum consensus, it must have been
+Where a patch set proposes to change the Theta 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 Raptoreum Core repository, however
+The review process is normally fairly responsive on the Theta 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 Raptoreum Core release.
+The project leader is the release manager for each Theta Core release.
 
 Copyright
 ---------

INSTALL.md

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