Remove Litmus from runtime

.github/runtime.json

@@ -5,12 +5,6 @@
       "path": "runtime/rococo",
       "uri": "wss://rpc.rococo-parachain.litentry.io:443"
     },
-    {
-      "name": "litmus",
-      "package": "litmus-parachain-runtime",
-      "path": "runtime/litmus",
-      "uri": "wss://rpc.litmus-parachain.litentry.io:443"
-    },
     {
       "name": "litentry",
       "package": "litentry-parachain-runtime",

.github/workflows/benchmark-machine.yml

@@ -62,7 +62,7 @@ jobs:
           chmod 600 ./benchmark-server-key.pem
           ssh -o StrictHostKeyChecking=no -i ./benchmark-server-key.pem "${{ env.BENCHMARK_SSH_USER }}@${{ steps.start_instance.outputs.remote_ip }}" \
             "docker pull litentry/litentry-parachain:${{ github.event.inputs.docker_tag }} && \
-            docker run --rm litentry/litentry-parachain:${{ github.event.inputs.docker_tag }} benchmark machine --allow-fail --chain=litmus-dev"
+            docker run --rm litentry/litentry-parachain:${{ github.event.inputs.docker_tag }} benchmark machine --allow-fail --chain=litentry-dev"
           rm -f ./benchmark-server-key.pem
 
       - name: Stop remote instance

.github/workflows/benchmark-runtime-weights.yml

@@ -14,11 +14,6 @@ on:
         description: litentry
         required: true
         default: true
-      litmus:
-        type: boolean
-        description: litmus
-        required: true
-        default: true
       rococo:
         type: boolean
         description: rococo
@@ -83,9 +78,6 @@ jobs:
       - name: Set env
         run: |
           chain=""
-          if [ "${{ github.event.inputs.litmus }}" = "true" ]; then
-            chain="$chain litmus"
-          fi
           if [ "${{ github.event.inputs.litentry }}" = "true" ]; then
             chain="$chain litentry"
           fi

.github/workflows/build-wasm.yml

@@ -7,7 +7,6 @@ on:
         type: choice
         description: The chain whose runtime-wasm is built
         options:
-          - litmus
           - litentry
           - rococo
       ref:

.github/workflows/ci.yml

@@ -597,7 +597,6 @@ jobs:
     strategy:
       matrix:
         chain:
-          - litmus
           - litentry
           - rococo
     name: ${{ matrix.chain }}
@@ -727,9 +726,6 @@ jobs:
           echo "::group::rococo runtime test"
           cargo test --locked -p rococo-parachain-runtime --lib
           echo "::endgroup::"
-          echo "::group::litmus runtime test"
-          cargo test --locked -p litmus-parachain-runtime --lib
-          echo "::endgroup::"
           echo "::group::litentry runtime test"
           cargo test --locked -p litentry-parachain-runtime --lib
           echo "::endgroup::"

.github/workflows/create-release-draft.yml

@@ -35,7 +35,6 @@ on:
         description: If any of the genesis artefacts should be released alongside
         options:
           - none
-          - litmus
           - rococo
           - litentry
 
@@ -76,7 +75,6 @@ jobs:
     strategy:
       matrix:
         chain:
-          - litmus
           - rococo
           - litentry
     name: ${{ matrix.chain }}
@@ -305,7 +303,6 @@ jobs:
     strategy:
       matrix:
         chain:
-          - litmus
           - litentry
     name: ${{ matrix.chain }}
     steps:

.github/workflows/release-bot.yml

@@ -25,21 +25,6 @@ jobs:
             🚀 A new client release has been built: https://github.com/litentry/litentry-parachain/releases/tag/${{ github.event.release.tag_name }}
             ✨ Please update the client using the docker image litentry/litentry-parachain:$DOCKER_TAG
 
-      - name: Update litmus image version
-        uses: "OnFinality-io/action-onf-release@v1"
-        continue-on-error: true
-        with:
-          # These keys should be in your GitHub secrets
-          # https://documentation.onfinality.io/support/onfinality-cli-tool-and-access-keys
-          onf-access-key: ${{ secrets.ONF_ACCESS_KEY }}
-          onf-secret-key: ${{ secrets.ONF_SECRET_KEY }}
-          onf-workspace-id: ${{ secrets.ONF_WORKSPACE_ID }}
-          onf-network-key: litmus-onfinality-key
-          # Add a new image version to network spec
-          onf-sub-command: image
-          onf-action: add
-          image-version: $DOCKER_TAG
-
       - name: Update litentry image version
         uses: "OnFinality-io/action-onf-release@v1"
         continue-on-error: true

Cargo.toml

@@ -23,7 +23,6 @@ members = [
     'primitives/core/macros',
     'primitives/hex',
     'runtime/litentry',
-    'runtime/litmus',
     'runtime/rococo',
     'runtime/common',
 ]
@@ -250,7 +249,6 @@ litentry-proc-macros = { path = "primitives/core/proc-macros" }
 litentry-hex-utils = { path = "primitives/hex", default-features = false }
 runtime-common = { path = "runtime/common", default-features = false }
 litentry-parachain-runtime = { path = "runtime/litentry", default-features = false }
-litmus-parachain-runtime = { path = "runtime/litmus", default-features = false }
 rococo-parachain-runtime = { path = "runtime/rococo", default-features = false }
 pallet-account-fix = { path = "pallets/account-fix", default-features = false }
 pallet-asset-manager = { path = "pallets/xcm-asset-manager", default-features = false }

Makefile

@@ -38,10 +38,6 @@ build-node:
 build-runtime-litentry:
 	cargo build --locked -p $(call pkgid, litentry-parachain-runtime) --release
 
-.PHONY: build-runtime-litmus ## Build litmus release runtime
-build-runtime-litmus:
-	cargo build --locked -p $(call pkgid, litmus-parachain-runtime) --release
-
 .PHONY: build-runtime-rococo ## Build rococo release runtime
 build-runtime-rococo:
 	cargo build --locked -p $(call pkgid, rococo-parachain-runtime) --release
@@ -50,10 +46,6 @@ build-runtime-rococo:
 srtool-build-wasm-litentry:
 	@./scripts/build-wasm.sh litentry
 
-.PHONY: srtool-build-wasm-litmus ## Build litmus wasm with srtools
-srtool-build-wasm-litmus:
-	@./scripts/build-wasm.sh litmus
-
 .PHONY: srtool-build-wasm-rococo ## Build rococo wasm with srtools
 srtool-build-wasm-rococo:
 	@./scripts/build-wasm.sh rococo
@@ -88,10 +80,6 @@ launch-docker-bridge:
 launch-docker-litentry: generate-docker-compose-litentry
 	@./scripts/launch-local-docker.sh litentry
 
-.PHONY: launch-docker-litmus ## Launch a local litmus-parachain network with docker
-launch-docker-litmus: generate-docker-compose-litmus
-	@./scripts/launch-local-docker.sh litmus
-
 .PHONY: launch-docker-rococo ## Launch a local rococo-parachain network with docker
 launch-docker-rococo: generate-docker-compose-rococo
 	@./scripts/launch-local-docker.sh rococo
@@ -100,10 +88,6 @@ launch-docker-rococo: generate-docker-compose-rococo
 launch-binary-litentry:
 	@./scripts/launch-local-binary.sh litentry
 
-.PHONY: launch-binary-litmus ## Launch a local litmus-parachain network with binaries
-launch-binary-litmus:
-	@./scripts/launch-local-binary.sh litmus
-
 .PHONY: launch-binary-rococo ## Launch a local rococo-parachain network with binaries
 launch-binary-rococo:
 	@./scripts/launch-local-binary.sh rococo
@@ -126,10 +110,6 @@ test-cargo-all-benchmarks:
 test-ts-docker-litentry: launch-docker-litentry launch-docker-bridge
 	@./scripts/run-ts-test.sh litentry bridge evm
 
-.PHONY: test-ts-docker-litmus ## Run litmus ts tests with docker without clean-up
-test-ts-docker-litmus: launch-docker-litmus launch-docker-bridge
-	@./scripts/run-ts-test.sh litmus bridge no_evm
-
 .PHONY: test-ts-docker-rococo ## Run rococo ts tests with docker without clean-up
 test-ts-docker-rococo: launch-docker-rococo launch-docker-bridge
 	@./scripts/run-ts-test.sh rococo bridge evm
@@ -138,10 +118,6 @@ test-ts-docker-rococo: launch-docker-rococo launch-docker-bridge
 test-ts-binary-litentry: launch-binary-litentry
 	@./scripts/run-ts-test.sh litentry no_bridge evm
 
-.PHONY: test-ts-binary-litmus ## Run litmus ts tests with binary without clean-up
-test-ts-binary-litmus: launch-binary-litmus
-	@./scripts/run-ts-test.sh litmus no_bridge no_evm
-
 .PHONY: test-ts-binary-rococo ## Run rococo ts tests with binary without clean-up
 test-ts-binary-rococo: launch-binary-rococo
 	@./scripts/run-ts-test.sh rococo no_bridge evm
@@ -152,10 +128,6 @@ test-ts-binary-rococo: launch-binary-rococo
 clean-docker-litentry:
 	@./scripts/clean-local-docker.sh litentry
 
-.PHONY: clean-docker-litmus ## Clean up litmus docker images, containers, volumes, etc
-clean-docker-litmus:
-	@./scripts/clean-local-docker.sh litmus
-
 .PHONY: clean-docker-rococo ## Clean up rococo docker images, containers, volumes, etc
 clean-docker-rococo:
 	@./scripts/clean-local-docker.sh rococo
@@ -170,10 +142,6 @@ clean-binary:
 generate-docker-compose-litentry:
 	@./scripts/generate-docker-files.sh litentry
 
-.PHONY: generate-docker-compose-litmus ## Generate docker-compose files for litmus local network
-generate-docker-compose-litmus:
-	@./scripts/generate-docker-files.sh litmus
-
 .PHONY: generate-docker-compose-rococo ## Generate docker-compose files for rococo local network
 generate-docker-compose-rococo:
 	@./scripts/generate-docker-files.sh rococo

README.md

@@ -11,12 +11,11 @@ Basically, parachains are layer-1 blockchains that connect to the relaychains (P
 
 To achieve identity aggregation, Litentry has a requirement to store sensitive user data, like web3 addresses, computed credit scores, and VCs in the trusted execution environment (TEE). Litentry builds a TEE side chain for this purpose and it is composed of multiple TEE-equipped nodes, to guarantee the security of data storage and data processing without exposing users' private data. A core component of this is the Litentry TEE worker which is based on Integritee's worker. It executes functions with specified inputs and resource limits in response to TEE calls and operations to ensure a sufficient level of scaling.
 
-Overall, our architecture is made of up Relaychains ( Polkadot and Kusama), Parachains (Litentry and Litmus), and the TEE sidechain which is supported by  and enables the runtime to execute in an SGX secure run environment.
+Overall, our architecture is made of up Relaychains (Polkadot and Kusama), Parachains (Litentry and rococo), and the TEE sidechain which is supported by  and enables the runtime to execute in an SGX secure run environment.
 
 To serve as the backbone platform for various Litentry products and achieve a transparent and decentralized user experience, we have different chain-specs/runtimes compiled into one single binary. They are:
 
 - litentry-parachain-runtime (on polkadot)
-- litmus-parachain-runtime (on kusama)
 - rococo-parachain-runtime (on rococo testnet)
 
 Therefore, when building node binary or docker image, no distinction is required. But when building runtime/starting binary/running tests, the chain type must be explicitly given. See the examples below.
@@ -57,7 +56,7 @@ make build-runtime-litentry
 
 The wasms should be located under `target/release/wbuild/litentry-parachain-runtime/`
 
-Similarly, use `make build-runtime-litmus` and `make build-runtime-rococo` to build the litmus-parachain-runtime and rococo-parachain-runtime, respectively.
+Similarly, use `make build-runtime-rococo` to build the rococo-parachain-runtime.
 
 ## Launch parachain
 ### Launch a full parachain network with relay chains

docker/entrypoint.sh

@@ -11,7 +11,7 @@ check(){
         export CHAIN="rococo"
     fi
 
-    ALLOWED_VALUES=("rococo" "litmus" "litentry")
+    ALLOWED_VALUES=("rococo" "litentry")
 
     if [[ " ${ALLOWED_VALUES[@]} " =~ " ${CHAIN} " ]]; then
         echo "CHAIN is set to a valid value: $CHAIN"