Remove Orion

Signed-off-by: Alexandros Filios <[email protected]>

Author: alexandrosfilios

.github/workflows/tests.yml

@@ -103,12 +103,8 @@ jobs:
           update-t1,
           update-t2,
           update-t3,
-          dlog-orion,
-          fabtoken-orion,
           nft-dlog,
           nft-fabtoken,
-          nft-dlog-orion,
-          nft-fabtoken-orion,
           dvp-fabtoken,
           dvp-dlog,
           interop-fabtoken-t1,

Makefile

@@ -2,7 +2,6 @@
 FABRIC_VERSION ?= 2.5.0
 FABRIC_CA_VERSION ?= 1.5.7
 FABRIC_TWO_DIGIT_VERSION = $(shell echo $(FABRIC_VERSION) | cut -d '.' -f 1,2)
-ORION_VERSION=v0.2.10
 
 # need to install fabric binaries outside of fts tree for now (due to chaincode packaging issues)
 FABRIC_BINARY_BASE=$(PWD)/../fabric
@@ -49,7 +48,7 @@ install-softhsm:
 	./ci/scripts/install_softhsm.sh
 
 .PHONY: docker-images
-docker-images: fabric-docker-images orion-server-images monitoring-docker-images testing-docker-images
+docker-images: fabric-docker-images monitoring-docker-images testing-docker-images
 
 .PHONY: testing-docker-images
 testing-docker-images:
@@ -73,12 +72,6 @@ monitoring-docker-images:
 	docker pull jaegertracing/all-in-one:latest
 	docker pull otel/opentelemetry-collector:latest
 
-.PHONY: orion-server-images
-orion-server-images:
-	docker pull orionbcdb/orion-server:$(ORION_VERSION)
-	docker image tag orionbcdb/orion-server:$(ORION_VERSION) orionbcdb/orion-server:latest
-
-
 .PHONY: integration-tests-nft-dlog
 integration-tests-nft-dlog:
 	cd ./integration/token/nft/dlog; export FAB_BINS=$(FAB_BINS); ginkgo $(GINKGO_TEST_OPTS) .
@@ -87,14 +80,6 @@ integration-tests-nft-dlog:
 integration-tests-nft-fabtoken:
 	cd ./integration/token/nft/fabtoken; export FAB_BINS=$(FAB_BINS); ginkgo $(GINKGO_TEST_OPTS) .
 
-.PHONY: integration-tests-nft-dlog-orion
-integration-tests-nft-dlog-orion:
-	cd ./integration/token/nft/odlog; ginkgo $(GINKGO_TEST_OPTS) .
-
-.PHONY: integration-tests-nft-fabtoken-orion
-integration-tests-nft-fabtoken-orion:
-	cd ./integration/token/nft/ofabtoken; ginkgo $(GINKGO_TEST_OPTS) .
-
 .PHONY: integration-tests-dvp-fabtoken
 integration-tests-dvp-fabtoken:
 	cd ./integration/token/dvp/fabtoken; export FAB_BINS=$(FAB_BINS); ginkgo $(GINKGO_TEST_OPTS) .

README.md

@@ -95,7 +95,7 @@ Developing applications that leverage tokens on Hyperledger Fabric can be comple
 
 **Introducing the Fabric Token SDK: Streamlining Tokenized Development (and Beyond)**
 
-The Fabric Token SDK has evolved beyond its initial focus on Hyperledger Fabric. It now empowers developers with the following capabilities across various platforms, including permissioned blockchains like Fabric and even centralized systems like Orion:
+The Fabric Token SDK has evolved beyond its initial focus on Hyperledger Fabric. It now empowers developers with the following capabilities across various platforms, including permissioned blockchains like Fabric:
 
 * **Tokenization Made Easy:** Create tokens representing any type of asset, be it physical or digital.
 * **Privacy by Design:** Select the appropriate privacy level for your specific use case, without modifying your application logic.

docs/core-token.md

@@ -77,7 +77,7 @@ token:
       listenerTimeout: 10s
   tms:
     mytms: # unique name of this token management system
-      network: default # the name of the network this TMS refers to (Fabric, Orion, etc)
+      network: default # the name of the network this TMS refers to (Fabric, etc)
       channel: testchannel # the name of the network's channel this TMS refers to, if applicable
       namespace: tns # the name of the channel's namespace this TMS refers to, if applicable
 

docs/design.md

@@ -2,7 +2,7 @@
 
 **What it is:**
 
-* A set of APIs and services for building token-based applications on Hyperledger Fabric, Orion, and potentially other platforms.
+* A set of APIs and services for building token-based applications on Hyperledger Fabric, and potentially other platforms.
 
 **Key Features:**
 
@@ -16,7 +16,7 @@
 * The Fabric Token SDK stack consists of several layers:
   * [`Services`](services/services.md): Pre-built functionalities like assembling transactions and selecting unspent tokens.
   * [`Token API`](apis/token-api.md): Provides a common abstraction for interacting with tokens across different backends.
-  * [`Driver API`](apis/driver-api.md): Translates generic token operations into backend-specific calls (e.g., Fabric vs. Orion).
+  * [`Driver API`](apis/driver-api.md): Translates generic token operations into backend-specific calls (e.g., Fabric).
   * [`Drivers`](drivers/drivers.md): Define token representation, operations, and validation rules for specific implementations.
 
 **Additional Information:**

docs/services/network.md

@@ -1,8 +1,8 @@
 # Network Service
 
-The [`token/services/network`](./../../token/services/network) service acts as a bridge, hiding the intricate details of the underlying ledger technology (like Fabric or Orion) from developers.
+The [`token/services/network`](./../../token/services/network) service acts as a bridge, hiding the intricate details of the underlying ledger technology (like Fabric) from developers.
 This service leverages a driver-based design, allowing developers to create new drivers for additional ledger platforms.
-Currently, Fabric and Orion are supported out of the box.
+Currently, Fabric is supported out of the box.
 
 ### Fabric Driver
 
@@ -45,14 +45,3 @@ In more details:
 5. Finally, the RW Set, after processing, is committed to the vault.
 
 Only at this point, the tokens created by the transaction become available via the `Token Vault Service` we have discussed above.
-
-### Orion Driver
-
-The Orion driver is similar to the Fabric driver because also Orion manages RW Sets.
-Though, in Orion there is no concept of chaincode or stored routines.
-To solve this problem, the Orion driver assumes the existence of a `Custodian` (another FSC node) that sits in front of Orion
-and handles the `approval` and `commit` steps.
-
-Here is the pictorial representation of the lifecycle of a token transaction for Orion:
-
-![orion_ttx_lifecycle.png](./../imgs/orion_ttx_lifecycle.png)

docs/services/services.md

@@ -10,7 +10,7 @@ But that's not all! The SDK also empowers you to create custom services tailored
 It offers flexible deployment options for isolated or shared backend systems.
 - [`Token Selector`](selector.md): Fabric Token SDK's token selectors allow developers to choose specific tokens (by type, amount, owner) from the vault for transactions. 
 They prevent double-spending by locking tokens until the transaction is completed, rejected, times out, or explicitly unlocked
-- [`Network`](network.md): Network Service in Fabric Token SDK hides complexities of the ledger (Fabric or Orion) for developers. 
+- [`Network`](network.md): Network Service in Fabric Token SDK hides complexities of the ledger (Fabric) for developers. 
 It uses a driver-based design allowing for future support of additional platforms.
 - [`Interoperability`](interop.md): Fabric Token SDK allows spending tokens based on conditions defined in scripts. 
 You encode the script within the token's owner field, and the backend interprets it during spending. 

docs/services/storage.md

@@ -45,7 +45,7 @@ Here is an example of configuration
 token:
   tms:
     mytms: # unique name of this token management system
-      network: default # the name of the network this TMS refers to (Fabric, Orion, etc)
+      network: default # the name of the network this TMS refers to (Fabric, etc)
       channel: testchannel # the name of the network's channel this TMS refers to, if applicable
       namespace: tns # the name of the channel's namespace this TMS refers to, if applicable
       # db specific driver
@@ -58,7 +58,7 @@ token:
 token:
   tms:
     mytms: # unique name of this token management system
-      network: default # the name of the network this TMS refers to (Fabric, Orion, etc)
+      network: default # the name of the network this TMS refers to (Fabric, etc)
       channel: testchannel # the name of the network's channel this TMS refers to, if applicable
       namespace: tns # the name of the channel's namespace this TMS refers to, if applicable
 ```

docs/services/ttx.md

@@ -4,7 +4,7 @@ The Token SDK simplifies token transaction assembly with a dedicated service in
 This service handles the entire transaction lifecycle, from building the transaction to managing its various stages.
 
 Even better, this service is ledger-agnostic.
-Whether you're using Fabric, Orion, or another platform, you can use the same service to assemble token transactions.
+Whether you're using Fabric, or another platform, you can use the same service to assemble token transactions.
 This flexibility is thanks to the `token/services/network` service, which acts as an abstraction layer, hiding the complexities of the underlying ledger technology.
 We'll delve deeper into this service later.
 

fungible.mk

@@ -97,14 +97,6 @@ integration-tests-fabtoken-fabric-t5:
 integration-tests-fabtoken-fabric:
 	cd ./integration/token/fungible/fabtoken; export FAB_BINS=$(FAB_BINS); ginkgo $(GINKGO_TEST_OPTS) --tags pkcs11 --label-filter="$(TEST_FILTER)" .
 
-.PHONY: integration-tests-dlog-orion
-integration-tests-dlog-orion:
-	cd ./integration/token/fungible/odlog; ginkgo $(GINKGO_TEST_OPTS) .
-
-.PHONY: integration-tests-fabtoken-orion
-integration-tests-fabtoken-orion:
-	cd ./integration/token/fungible/ofabtoken; ginkgo $(GINKGO_TEST_OPTS) .
-
 .PHONY: integration-tests-update-t1
 integration-tests-update-t1:
 	make integration-tests-update TEST_FILTER="T1"