feat: Rebrand Kurdistan SDK to PezkuwiChain

bridges/README.md

@@ -31,14 +31,14 @@ rustup target add wasm32-unknown-unknown --toolchain nightly
 Once this is configured you can build and test the repo as follows:
 
 ```
-git clone https://github.com/paritytech/parity-bridges-common.git
+git clone https://github.com/pezkuwichain/kurdistan-sdk/tree/main/bridges
 cd parity-bridges-common
 cargo build --all
 cargo test --all
 ```
 
 Also you can build the repo with [Parity CI Docker
-image](https://github.com/paritytech/scripts/tree/master/dockerfiles/ci-unified):
+image](https://github.com/pezkuwichain/scripts/tree/master/dockerfiles/ci-unified):
 
 ```bash
 docker pull paritytech/ci-unified:latest
@@ -54,7 +54,7 @@ docker run --rm -it -w /shellhere/parity-bridges-common \
 ```
 
 If you want to reproduce other steps of CI process you can use the following
-[guide](https://github.com/paritytech/scripts#reproduce-ci-locally).
+[guide](https://github.com/pezkuwichain/scripts#reproduce-ci-locally).
 
 If you need more information about setting up your development environment [Bizinikiwi's Installation
 page](https://docs.pezkuwichain.io/main-docs/install/) is a good resource.

bridges/modules/grandpa/README.md

@@ -9,7 +9,7 @@ It is used by the teyrchains light client (bridge teyrchains pallet) and by mess
 
 ## A Brief Introduction into GRANDPA Finality
 
-You can find detailed information on GRANDPA, by exploring its [repository](https://github.com/paritytech/finality-grandpa).
+You can find detailed information on GRANDPA, by exploring its [repository](https://github.com/pezkuwichain/finality-grandpa).
 Here is the minimal required GRANDPA information to understand how pallet works.
 
 Any Bizinikiwi chain may use different block authorship algorithms (like BABE or Aura) to determine block producers and

bridges/relays/finality/README.md

@@ -4,7 +4,7 @@ The finality relay is able to work with different finality engines. In the moder
 and BEEFY. Let's talk about GRANDPA here, because BEEFY relay and bridge BEEFY pallet are in development.
 
 In general, the relay works as follows: it connects to the source and target chain. The source chain must have the
-[GRANDPA gadget](https://github.com/paritytech/finality-grandpa) running (so it can't be a teyrchain). The target
+[GRANDPA gadget](https://github.com/pezkuwichain/finality-grandpa) running (so it can't be a teyrchain). The target
 chain must have the [bridge GRANDPA pallet](../../modules/grandpa/) deployed at its runtime. The relay subscribes
 to the GRANDPA finality notifications at the source chain and when the new justification is received, it is submitted
 to the pallet at the target chain.
@@ -59,4 +59,4 @@ chains, simply change chain names. So the metrics are:
   this shall not happen and the metric will have `0` value.
 
 If relay operates properly, you should see that the `pezkuwichain_to_BridgeHubzagros_Sync_best_source_at_target_block_number`
-tries to reach the `pezkuwichain_to_BridgeHubzagros_Sync_best_source_block_number`. And the latter one always increases.
+tries to reach the `pezkuwichain_to_BridgeHubzagros_Sync_best_source_block_number`. And the latter one always increases.

bridges/snowbridge/primitives/inbound-queue/src/v1.rs

@@ -73,7 +73,7 @@ pub enum Destination {
 	AccountId32 { id: [u8; 32] },
 	/// The funds will deposited into the sovereign account of destination teyrchain `para_id` on
 	/// AssetHub, Account `id` on the destination teyrchain will receive the funds via a
-	/// reserve-backed transfer. See <https://github.com/paritytech/xcm-format#depositreserveasset>
+	/// reserve-backed transfer. See <https://github.com/pezkuwichain/xcm-format#depositreserveasset>
 	ForeignAccountId32 {
 		para_id: u32,
 		id: [u8; 32],
@@ -82,7 +82,7 @@ pub enum Destination {
 	},
 	/// The funds will deposited into the sovereign account of destination teyrchain `para_id` on
 	/// AssetHub, Account `id` on the destination teyrchain will receive the funds via a
-	/// reserve-backed transfer. See <https://github.com/paritytech/xcm-format#depositreserveasset>
+	/// reserve-backed transfer. See <https://github.com/pezkuwichain/xcm-format#depositreserveasset>
 	ForeignAccountId20 {
 		para_id: u32,
 		id: [u8; 20],

bridges/testing/README.md

@@ -1,11 +1,11 @@
 # Bridges Tests for Local pezkuwichain <> zagros Bridge
 
-This folder contains [zombienet](https://github.com/paritytech/zombienet/) based integration tests for both
+This folder contains [zombienet](https://github.com/pezkuwichain/zombienet-sdk/) based integration tests for both
 onchain and offchain bridges code.
 
 Prerequisites for running the tests locally:
 
-- download latest [zombienet release](https://github.com/paritytech/zombienet/releases) and place it at
+- download latest [zombienet release](https://github.com/pezkuwichain/zombienet-sdk/releases) and place it at
 `~/local_bridge_testing/bin/zombienet`;
 
 - build PezkuwiChain binary by running `cargo build -p pezkuwi --release  --features fast-runtime` command in the
@@ -18,7 +18,7 @@ Prerequisites for running the tests locally:
   `pezkuwi/api-cli` package. Use `yarn global add @pezkuwi/api-cli` to install it.
 
 - build Bizinikiwi relay by running `cargo build -p bizinikiwi-relay --release` command in the
-  [`parity-bridges-common`](https://github.com/paritytech/parity-bridges-common) repository clone;
+  [`pezkuwichain/kurdistan-sdk`](https://github.com/pezkuwichain/kurdistan-sdk/tree/main/bridges) repository clone;
 
 - copy the `bizinikiwi-relay` binary, built in the previous step, to `~/local_bridge_testing/bin/bizinikiwi-relay`;