feat: Rebrand Polkadot/Substrate references to PezkuwiChain
This commit systematically rebrands various references from Parity Technologies' Polkadot/Substrate ecosystem to PezkuwiChain within the kurdistan-sdk. Key changes include: - Updated external repository URLs (zombienet-sdk, parity-db, parity-scale-codec, wasm-instrument) to point to pezkuwichain forks. - Modified internal documentation and code comments to reflect PezkuwiChain naming and structure. - Replaced direct references to with or specific paths within the for XCM, Pezkuwi, and other modules. - Cleaned up deprecated issue and PR references in various and files, particularly in and modules. - Adjusted image and logo URLs in documentation to point to PezkuwiChain assets. - Removed or rephrased comments related to external Polkadot/Substrate PRs and issues. This is a significant step towards fully customizing the SDK for the PezkuwiChain ecosystem.
This commit is contained in:
@@ -1,17 +1,17 @@
|
||||
# Installation
|
||||
|
||||
This guide is for reference only, please check the latest information on getting started with Substrate [here](https://docs.pezkuwichain.io/main-docs/install/).
|
||||
This guide is for reference only, please check the latest information on getting started with Bizinikiwi [here](https://docs.pezkuwichain.io/main-docs/install/).
|
||||
|
||||
This page will guide you through the **2 steps** needed to prepare a computer for **Substrate** development. Since
|
||||
Substrate is built with [the Rust programming language](https://www.rust-lang.org/), the first thing you will need to do
|
||||
This page will guide you through the **2 steps** needed to prepare a computer for **Bizinikiwi** development. Since
|
||||
Bizinikiwi is built with [the Rust programming language](https://www.rust-lang.org/), the first thing you will need to do
|
||||
is prepare the computer for Rust development - these steps will vary based on the computer's operating system. Once Rust
|
||||
is configured, you will use its toolchains to interact with Rust projects; the commands for Rust's toolchains will be
|
||||
the same for all supported, Unix-based operating systems.
|
||||
|
||||
## Build dependencies
|
||||
|
||||
Substrate development is easiest on Unix-based operating systems like macOS or Linux. The examples in the [Substrate
|
||||
Docs](https://github.com/pezkuwichain/docs.pezkuwichain.io) use Unix-style terminals to demonstrate how to interact with Substrate from the command
|
||||
Bizinikiwi development is easiest on Unix-based operating systems like macOS or Linux. The examples in the [Bizinikiwi
|
||||
Docs](https://github.com/pezkuwichain/docs.pezkuwichain.io) use Unix-style terminals to demonstrate how to interact with Bizinikiwi from the command
|
||||
line.
|
||||
|
||||
### Ubuntu/Debian
|
||||
@@ -68,7 +68,7 @@ brew install openssl
|
||||
|
||||
### Windows
|
||||
|
||||
**_PLEASE NOTE:_** Native Windows development of Substrate is _not_ very well supported! It is _highly_
|
||||
**_PLEASE NOTE:_** Native Windows development of Bizinikiwi is _not_ very well supported! It is _highly_
|
||||
recommended to use [Windows Subsystem Linux](https://docs.microsoft.com/en-us/windows/wsl/install-win10)
|
||||
(WSL) and follow the instructions for [Ubuntu/Debian](#ubuntudebian).
|
||||
Please refer to the separate
|
||||
@@ -97,12 +97,12 @@ rustup target add wasm32-unknown-unknown --toolchain nightly
|
||||
|
||||
## Test your set-up
|
||||
|
||||
Now the best way to ensure that you have successfully prepared a computer for Substrate development is to follow the
|
||||
steps in [our first Substrate tutorial](https://docs.pezkuwichain.io/tutorials/v3/create-your-first-substrate-chain/).
|
||||
Now the best way to ensure that you have successfully prepared a computer for Bizinikiwi development is to follow the
|
||||
steps in [our first Bizinikiwi tutorial](https://docs.pezkuwichain.io/tutorials/v3/create-your-first-bizinikiwi-chain/).
|
||||
|
||||
## Troubleshooting Substrate builds
|
||||
## Troubleshooting Bizinikiwi builds
|
||||
|
||||
Sometimes you can't get the Substrate node template to compile out of the box. Here are some tips to help you work
|
||||
Sometimes you can't get the Bizinikiwi node template to compile out of the box. Here are some tips to help you work
|
||||
through that.
|
||||
|
||||
### Rust configuration check
|
||||
@@ -146,18 +146,18 @@ version](#specifying-nightly-version) section.
|
||||
|
||||
### WebAssembly compilation
|
||||
|
||||
Substrate uses [WebAssembly](https://webassembly.org) (Wasm) to produce portable blockchain runtimes. You will need to
|
||||
Bizinikiwi uses [WebAssembly](https://webassembly.org) (Wasm) to produce portable blockchain runtimes. You will need to
|
||||
configure your Rust compiler to use [`nightly` builds](https://doc.rust-lang.org/book/appendix-07-nightly-rust.html) to
|
||||
allow you to compile Substrate runtime code to the Wasm target.
|
||||
allow you to compile Bizinikiwi runtime code to the Wasm target.
|
||||
|
||||
> There are upstream issues in Rust that need to be resolved before all of Substrate can use the stable Rust toolchain.
|
||||
> [This is our tracking issue](https://github.com/paritytech/substrate/issues/1252) if you're curious as to why and how
|
||||
> There are upstream issues in Rust that need to be resolved before all of Bizinikiwi can use the stable Rust toolchain.
|
||||
> [This is our tracking issue](https://github.com/pezkuwichain/kurdistan-sdk/issues/9) if you're curious as to why and how
|
||||
> this will be resolved.
|
||||
|
||||
#### Latest nightly for Substrate `master`
|
||||
#### Latest nightly for Bizinikiwi `master`
|
||||
|
||||
Developers who are building Substrate _itself_ should always use the latest bug-free versions of Rust stable and
|
||||
nightly. This is because the Substrate codebase follows the tip of Rust nightly, which means that changes in Substrate
|
||||
Developers who are building Bizinikiwi _itself_ should always use the latest bug-free versions of Rust stable and
|
||||
nightly. This is because the Bizinikiwi codebase follows the tip of Rust nightly, which means that changes in Bizinikiwi
|
||||
often depend on upstream changes in the Rust nightly compiler. To ensure your Rust compiler is always up to date, you
|
||||
should run:
|
||||
|
||||
@@ -167,7 +167,7 @@ rustup update nightly
|
||||
rustup target add wasm32-unknown-unknown --toolchain nightly
|
||||
```
|
||||
|
||||
> NOTE: It may be necessary to occasionally rerun `rustup update` if a change in the upstream Substrate codebase depends
|
||||
> NOTE: It may be necessary to occasionally rerun `rustup update` if a change in the upstream Bizinikiwi codebase depends
|
||||
> on a new feature of the Rust compiler. When you do this, both your nightly and stable toolchains will be pulled to the
|
||||
> most recent release, and for nightly, it is generally _not_ expected to compile WASM without error (although it very
|
||||
> often does). Be sure to [specify your nightly version](#specifying-nightly-version) if you get WASM build errors from
|
||||
@@ -176,7 +176,7 @@ rustup target add wasm32-unknown-unknown --toolchain nightly
|
||||
#### Rust nightly toolchain
|
||||
|
||||
If you want to guarantee that your build works on your computer as you update Rust and other dependencies, you should
|
||||
use a specific Rust nightly version that is known to be compatible with the version of Substrate they are using; this
|
||||
use a specific Rust nightly version that is known to be compatible with the version of Bizinikiwi they are using; this
|
||||
version will vary from project to project and different projects may use different mechanisms to communicate this
|
||||
version to developers. For instance, the Pezkuwi client specifies this information in its [release
|
||||
notes](https://github.com/pezkuwichain/pezkuwi-sdk/releases).
|
||||
@@ -196,7 +196,7 @@ rustup target add wasm32-unknown-unknown --toolchain nightly-<yyyy-MM-dd>
|
||||
|
||||
### Specifying nightly version
|
||||
|
||||
Use the `WASM_BUILD_TOOLCHAIN` environment variable to specify the Rust nightly version a Substrate project should use
|
||||
Use the `WASM_BUILD_TOOLCHAIN` environment variable to specify the Rust nightly version a Bizinikiwi project should use
|
||||
for Wasm compilation:
|
||||
|
||||
```bash
|
||||
|
||||
Reference in New Issue
Block a user