Remove References to Fisco-bcos from VNext Documentation #1528 (#1533)

* Resolve issue with documentation rendering locally Signed-off-by: Vinayak Raj Ranjan <[email protected]> * Update PSWG whitepaper link in Documentation Signed-off-by: Vinayak Raj Ranjan <[email protected]> * Minor changes in link Signed-off-by: Vinayak Raj Ranjan <[email protected]> * Remove References to Fisco-bcos from VNext Documentation Signed-off-by: Vinayak Raj Ranjan <[email protected]> * remove fisco-bcos reference from other file Signed-off-by: Vinayak Raj Ranjan <[email protected]> --------- Signed-off-by: Vinayak Raj Ranjan <[email protected]>
hyperledger-caliper · Apr 15, 2024 · 2cae2fe · 2cae2fe
1 parent d1d784b
commit 2cae2fe
Show file tree

Hide file tree

Showing 6 changed files with 1 addition and 178 deletions.
diff --git a/docs/vNext/Architecture.md b/docs/vNext/Architecture.md
@@ -41,7 +41,6 @@ The content of the network configuration file is SUT-specific. The file usually
 For the exact structure of the network configuration files, refer to the corresponding SUT connector documentations (we will discuss connectors a bit later on this page):
 * [Hyperledger Besu & Ethereum](./Ethereum_Configuration.md)
 * [Hyperledger Fabric](./Fabric_Configuration.md)
-* [FISCO BCOS](./FISCO_BCOS_Configuration.md)
 
 ### Workload modules
 

diff --git a/docs/vNext/CONTRIBUTING.md b/docs/vNext/CONTRIBUTING.md
@@ -75,7 +75,6 @@ The following platform tests (i.e., valid `BENCHMARK` values) are available:
 * besu
 * ethereum
 * fabric
-* fisco-bcos
 
 A PR must pass all unit and integration tests.
 
@@ -201,7 +200,6 @@ Each `caliper-<adapter>` is a separate package that contains a distinct adapter
 
 - caliper-ethereum
 - caliper-fabric
-- caliper-fisco-bcos
 
 Each adapter extends the `ConnectorBase` from the core package, as well as exports a `ConnectorFactory` function.
 

diff --git a/docs/vNext/Caliper_FAQ.md b/docs/vNext/Caliper_FAQ.md
@@ -23,7 +23,7 @@ There is another configuration file, namely `./config/default.yaml`, containing
 ### III. Testing a Blockchain Network
 
 **Q:** What kind of networks does Caliper support currently?
-**A:** Now you can use Caliper to test Besu, Ethereum, Fabric, and FISCO-SCOS networks.
+**A:** Now you can use Caliper to test Besu, Ethereum and Fabric.
 
 **Q:** How can I test a blockchain system that Caliper does not support currently？
 **A:** If you want to test the blockchain system that Caliper does not support now, you must write your own blockchain adapter that Caliper can use to inferface with the backend network. For details, you can refer to the [Writing Adapters](./Writing_Adapters.md) page. The Caliper-specific configurations remain unchanged. Take a look at the provided adapter implementations and example networks to gather some best-practices.

diff --git a/docs/vNext/FISCO_BCOS_Configuration.md b/docs/vNext/FISCO_BCOS_Configuration.md
diff --git a/docs/vNext/Getting_Started.md b/docs/vNext/Getting_Started.md
@@ -21,7 +21,6 @@ Caliper is a blockchain performance benchmark framework, which allows users to t
 * [Hyperledger Besu](https://github.com/hyperledger/besu)
 * [Ethereum](https://github.com/ethereum/)
 * [Hyperledger Fabric](https://github.com/hyperledger/fabric)
-* [FISCO BCOS](https://github.com/FISCO-BCOS/FISCO-BCOS)
 
 ### Supported performance metrics
 

diff --git a/docs/vNext/Installing_Caliper.md b/docs/vNext/Installing_Caliper.md
@@ -110,8 +110,6 @@ The following SUT name and SDK version combinations are supported:
 * **besu**: `1.3.2`, `1.3`, `1.4`
 * **ethereum**: `1.2.1`, `1.3`
 * **fabric**: `1.4`, `2.2`, `2.4`
-* **fisco-bcos**: `2.0.0`
-
 > __Note:__ Ensure that the SDK you are binding is compatible with the the SUT version that you intend to target.
 
 The `bind` command is useful when you plan to run multiple benchmarks against the same SUT version. Bind once, then run different benchmarks without the need to bind again. As you will see in the next sections, the launcher commands for the manager and worker processes can also perform the binding step if the required parameter is present.