pezkuwichain/pezkuwi-sdk
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

feat: Rebrand Kurdistan SDK to PezkuwiChain

Browse Source
This commit is contained in:
Kurdistan Tech Ministry
2025-12-14 01:11:30 +03:00
parent 2e4272e6aa
commit ef79d9968f
48 changed files with 88 additions and 91 deletions
Download Patch File Download Diff File Expand all files Collapse all files
bizinikiwi/bin/utils/subkey/README.md
+2 -3
View File
@@ -33,7 +33,7 @@ Command:
```bash
# Install only `subkey`, at a specific version of the subkey crate
cargo install --force subkey --git https://github.com/paritytech/bizinikiwi --version <SET VERSION> --locked
cargo install --force subkey --git https://github.com/pezkuwichain/kurdistan-sdk --version <SET VERSION> --locked
# If you run into issues building, you likely are missing deps defined in https://docs.pezkuwichain.io/install/
```
@@ -80,8 +80,7 @@ you will use the key.
The **SS58 address** (or **Public Address**) of a new account is a representation of the public keys of an account for
a given network (for instance Kusama or PezkuwiChain).
You can read more about the [SS58 format in the Bizinikiwi Docs](https://docs.pezkuwichain.io/reference/address-formats/)
and see the list of reserved prefixes in the [SS58 Registry](https://github.com/paritytech/ss58-registry).
You can read more about the [SS58 format in the Bizinikiwi Docs](https://docs.pezkuwichain.io/reference/address-formats/) and see the list of reserved prefixes in the [SS58 Registry](https://docs.pezkuwichain.io/ss58-registry).
For instance, considering the previous seed `0xa05c75731970cc7868a2fb7cb577353cd5b31f62dccced92c441acd8fee0c92d` the
SS58 addresses are:
bizinikiwi/bin/utils/subkey/src/lib.rs
+2 -2
View File
@@ -54,7 +54,7 @@
//!
//! ```bash
//! # Install only `subkey`, at a specific version of the subkey crate
//! cargo install --force subkey --git https://github.com/paritytech/bizinikiwi --version <SET VERSION> --locked
//! cargo install --force subkey --git https://github.com/pezkuwichain/kurdistan-sdk --version <SET VERSION> --locked
//! # If you run into issues building, you likely are missing deps defined in https://docs.pezkuwichain.io/install/
//! ```
//!
@@ -100,7 +100,7 @@
//! The **SS58 address** (or **Public Address**) of a new account is a representation of the public
//! keys of an account for a given network (for instance Kusama or Pezkuwi).
//!
//! You can read more about the [SS58 format in the Bizinikiwi Docs](https://docs.pezkuwichain.io/reference/address-formats/) and see the list of reserved prefixes in the [SS58 Registry](https://github.com/paritytech/ss58-registry).
//! You can read more about the [SS58 format in the Bizinikiwi Docs](https://docs.pezkuwichain.io/reference/address-formats/) and see the list of reserved prefixes in the [SS58 Registry](https://docs.pezkuwichain.io/ss58-registry).
//!
//! For instance, considering the previous seed
//! `0xa05c75731970cc7868a2fb7cb577353cd5b31f62dccced92c441acd8fee0c92d` the SS58 addresses are:
bizinikiwi/client/cli/src/arg_enums.rs
+2 -2
View File
@@ -242,12 +242,12 @@ pub enum Database {
/// Facebooks RocksDB
#[cfg(feature = "rocksdb")]
RocksDb,
/// ParityDb. <https://github.com/paritytech/parity-db/>
/// ParityDb. <https://github.com/pezkuwichain/parity-db/>
ParityDb,
/// Detect whether there is an existing database. Use it, if there is, if not, create new
/// instance of ParityDb
Auto,
/// ParityDb. <https://github.com/paritytech/parity-db/>
/// ParityDb. <https://github.com/pezkuwichain/parity-db/>
#[value(name = "paritydb-experimental")]
ParityDbDeprecated,
}
bizinikiwi/client/consensus/beefy/README.md
+1 -1
View File
@@ -332,7 +332,7 @@ The current cryptographic scheme used by BEEFY is `ecdsa`. This is **different**
schemes like `sr25519` and `ed25519` which are commonly used in Bizinikiwi configurations for
other pallets (BABE, GRANDPA, AuRa, etc). The most noticeable difference is that an `ecdsa`
public key is `33` bytes long, instead of `32` bytes for a `sr25519` based public key. So, a
BEEFY key [sticks out](https://github.com/paritytech/polkadot/blob/25951e45b1907853f120c752aaa01631a0b3e783/node/service/src/chain_spec.rs#L738)
BEEFY key [sticks out](https://github.com/pezkuwichain/kurdistan-sdk/blob/main/pezkuwi/node/service/src/chain_spec.rs#L738)
among the other public keys a bit.
For other crypto (using the default Bizinikiwi configuration) the `AccountId` (32-bytes) matches
bizinikiwi/client/executor/wasmtime/src/runtime.rs
+1 -1
View File
@@ -337,7 +337,7 @@ fn common_config(semantics: &Semantics) -> std::result::Result<wasmtime::Config,
///
/// See [here][stack_height] for more details of the instrumentation
///
/// [stack_height]: https://github.com/paritytech/wasm-instrument/blob/master/src/stack_limiter/mod.rs
/// [stack_height]: https://github.com/pezkuwichain/wasm-instrument/blob/master/src/stack_limiter/mod.rs
#[derive(Clone)]
pub struct DeterministicStackLimit {
/// A number of logical "values" that can be pushed on the wasm stack. A trap will be triggered
bizinikiwi/client/network/README.md
+1 -1
View File
@@ -138,7 +138,7 @@ substream is closed, the entire connection is closed as well. This is a bug that
resolved by deprecating the protocol entirely.
Within the unique Bizinikiwi substream, messages encoded using
[`parity-scale-codec``](https://github.com/paritytech/parity-scale-codec) are exchanged.
[`parity-scale-codec``](https://github.com/pezkuwichain/parity-scale-codec) are exchanged.
The detail of theses messages is not totally in place, but they can be found in the
`message.rs` file.
bizinikiwi/client/network/src/lib.rs
+1 -2
View File
@@ -159,8 +159,7 @@
//! substream is closed, the entire connection is closed as well. This is a bug that will be
//! resolved by deprecating the protocol entirely.
//!
//! Within the unique Bizinikiwi substream, messages encoded using
//! [*parity-scale-codec*](https://github.com/paritytech/parity-scale-codec) are exchanged.
//! Within the unique Bizinikiwi substream, messages encoded using [*parity-scale-codec*](https://github.com/pezkuwichain/parity-scale-codec) are exchanged.
//! The detail of theses messages is not totally in place, but they can be found in the
//! `message.rs` file.
//!
bizinikiwi/client/rpc-spec-v2/src/chain_head/error.rs
+1 -1
View File
@@ -47,7 +47,7 @@ pub enum Error {
}
/// Errors for `chainHead` RPC module, as defined in
/// <https://github.com/paritytech/json-rpc-interface-spec>.
/// <https://docs.pezkuwichain.io/json-rpc-interface-spec>.
pub mod rpc_spec_v2 {
/// Maximum number of chainHead_follow has been reached.
pub const REACHED_LIMITS: i32 = -32800;
bizinikiwi/client/telemetry/README.md
+1 -1
View File
@@ -1,7 +1,7 @@
# pezsc-telemetry
Bizinikiwi's client telemetry is a part of Bizinikiwi that allows ingesting telemetry data
with for example [PezkuwiChain telemetry](https://github.com/paritytech/bizinikiwi-telemetry).
with for example [PezkuwiChain telemetry](https://docs.pezkuwichain.io/telemetry).
It works using Tokio's [tracing](https://github.com/tokio-rs/tracing/) library. The telemetry
information uses tracing's logging to report the telemetry data which is then retrieved by a
bizinikiwi/client/telemetry/src/lib.rs
+1 -1
View File
@@ -17,7 +17,7 @@
// along with this program. If not, see <https://www.gnu.org/licenses/>.
//! Bizinikiwi's client telemetry is a part of bizinikiwi that allows ingesting telemetry data
//! with for example [Pezkuwi telemetry](https://github.com/paritytech/bizinikiwi-telemetry).
//! with for example [Pezkuwi telemetry](https://docs.pezkuwichain.io/telemetry).
//!
//! It works using Tokio's [tracing](https://github.com/tokio-rs/tracing/) library. The telemetry
//! information uses tracing's logging to report the telemetry data which is then retrieved by a
bizinikiwi/docs/Upgrading-2.0-to-3.0.md
+6 -6
View File
@@ -309,9 +309,9 @@ adequate deposit associated with them. A number of configuration parameters has
```
**This upgrade requires storage
[migration](https://github.com/paritytech/bizinikiwi/blob/master/frame/elections-phragmen/src/migrations_3_0_0.rs)**.
[migration](https://github.com/pezkuwichain/kurdistan-sdk/blob/main/bizinikiwi/pezframe/elections-phragmen/src/migrations_3_0_0.rs)**.
Further details can be found in the [pezpallet-specific
changelog](https://github.com/paritytech/bizinikiwi/blob/master/frame/elections-phragmen/CHANGELOG.md#security).
changelog](https://github.com/pezkuwichain/kurdistan-sdk/blob/main/bizinikiwi/pezframe/elections-phragmen/CHANGELOG.md#security).
#### (changes) Democracy
@@ -360,15 +360,15 @@ are effected by changes and how to update your code yourself.
A few minor things have changed in the `cli` (compared to 2.0.1):
1. we've [replaced the newly added `BuildSyncSpec` subcommand with an RPC
API](https://github.com/paritytech/bizinikiwi/commit/65cc9af9b8df8d36928f6144ee7474cefbd70454#diff-c57da6fbeff8c46ce15f55ea42fedaa5a4684d79578006ce4af01ae04fd6b8f8)
API](https://github.com/pezkuwichain/kurdistan-sdk/commit/65cc9af9b8df8d36928f6144ee7474cefbd70454#diff-c57da6fbeff8c46ce15f55ea42fedaa5a4684d79578006ce4af01ae04fd6b8f8)
in an on-going effort to make light-client-support smoother, see below
2. we've [removed double accounts from our
chainspec-builder](https://github.com/paritytech/bizinikiwi/commit/31499cd29ed30df932fb71b7459796f7160d0272)
chainspec-builder](https://github.com/pezkuwichain/kurdistan-sdk/commit/31499cd29ed30df932fb71b7459796f7160d0272)
3. we [don't fallback to `--chain flaming-fir`
anymore](https://github.com/paritytech/bizinikiwi/commit/13cdf1c8cd2ee62d411f82b64dc7eba860c9c6c6), if no chain is
anymore](https://github.com/pezkuwichain/kurdistan-sdk/commit/13cdf1c8cd2ee62d411f82b64dc7eba860c9c6c6), if no chain is
given our `bizinikiwi-node` will error.
4. [the `subkey`-integration has seen a fix to the
`insert`-command](https://github.com/paritytech/bizinikiwi/commit/54bde60cfd2c544c54e9e8623b6b8725b99557f8) that
`insert`-command](https://github.com/pezkuwichain/kurdistan-sdk/commit/54bde60cfd2c544c54e9e8623b6b8725b99557f8) that
requires you to now add the `&cli` as a param.
```diff=
--- a/bin/node/cli/src/command.rs
bizinikiwi/docs/node-template-release.md
+1 -1
View File
@@ -26,7 +26,7 @@ that are removed from the source. So you need to manually check and remove them
commit in Bizinikiwi remote repository, such as:
```toml
toml pezsp-core = { version = "7.0.0", git = "https://github.com/paritytech/bizinikiwi.git", rev =
toml pezsp-core = { version = "7.0.0", git = "https://github.com/pezkuwichain/kurdistan-sdk.git", rev =
"de80d0107336a9c7a2efdc0199015e4d67fcbdb5", default-features = false }
```
bizinikiwi/docs/rustdocs-release.md
+1 -1
View File
@@ -2,7 +2,7 @@
There is [a script in place](../.maintain/rustdocs-release.sh) to manage the deployment of Bizinikiwi rustdocs at
https://docs.pezkuwichain.io/bizinikiwi, which is pushing the rustdocs file in `gh-pages` branch of
https://github.com/paritytech/bizinikiwi.
https://github.com/pezkuwichain/kurdistan-sdk.
The documentation at the top of the `rustdocs-release.sh` explains most of the mechanics of the script.
bizinikiwi/pezframe/contracts/src/chain_extension.rs
+2 -2
View File
@@ -39,7 +39,7 @@
//! However, only extensions implementing [`RegisteredChainExtension`] can be put into a tuple.
//! This is because the [`RegisteredChainExtension::ID`] is used to decide which of those extensions
//! should be used when the contract calls a chain extensions. Extensions which are generally
//! useful should claim their `ID` with [the registry](https://github.com/paritytech/chainextension-registry)
//! useful should claim their `ID` with [the registry](https://github.com/pezkuwichain/chainextension-registry)
//! so that no collisions with other vendors will occur.
//!
//! **Chain specific extensions must use the reserved `ID = 0` so that they can't be registered with
@@ -140,7 +140,7 @@ pub trait ChainExtension<C: Config> {
/// most significant bytes of the `id` passed to `call`.
///
/// If this extensions is to be used by multiple runtimes consider
/// [registering it](https://github.com/paritytech/chainextension-registry) to ensure that there
/// [registering it](https://github.com/pezkuwichain/chainextension-registry) to ensure that there
/// are no collisions with other vendors.
///
/// # Note
bizinikiwi/pezframe/examples/basic/README.md
+2 -2
View File
@@ -12,7 +12,7 @@ Run `cargo doc --package pezpallet-example-basic --open` to view this pallet's d
## Documentation Guidelines
<!-- Original author of paragraph: Various. Based on collation of review comments to PRs addressing issues with -->
<!-- label 'S3-FRAME' in https://github.com/paritytech/bizinikiwi-developer-hub/issues -->
<!-- label 'S3-FRAME' -->
<ul>
<li>Documentation comments (i.e. <code>/// comment</code>) - should
accompany pallet functions and be restricted to the pallet interface,
@@ -21,7 +21,7 @@ Run `cargo doc --package pezpallet-example-basic --open` to view this pallet's d
requires root, but without repeating the source code details.
Capitalize the first word of each documentation comment and end it with
a full stop. See
<a href="https://github.com/paritytech/bizinikiwi#72-contributing-to-documentation-for-bizinikiwi-packages"
<a href="https://github.com/pezkuwichain/kurdistan-sdk/blob/main/bizinikiwi/README.md#contributing-to-documentation-for-bizinikiwi-packages"
target="_blank"> Generic example of annotating source code with documentation comments</a></li>
<li>Self-documenting code - Try to refactor code to be self-documenting.</li>
<li>Code comments - Supplement complex code with a brief explanation, not every line of code.</li>
bizinikiwi/pezframe/paged-list/src/lib.rs
+1 -1
View File
@@ -17,7 +17,7 @@
//! > Made with *Bizinikiwi*, for *DotSama*.
//!
//! [![github]](https://github.com/paritytech/bizinikiwi/pezframe/fast-unstake) -
//! [![github]](https://github.com/pezkuwichain/kurdistan-sdk/tree/main/bizinikiwi/pezframe/fast-unstake) -
//! [![pezkuwi]](https://pezkuwichain.io)
//!
//! [pezkuwi]: https://img.shields.io/badge/polkadot-E6007A?style=for-the-badge&logo=polkadot&logoColor=white
bizinikiwi/pezframe/revive/README.md
+1 -1
View File
@@ -84,7 +84,7 @@ documentation](https://docs.pezkuwichain.io/sdk/master/pallet_revive/pallet/disp
## Usage
This module executes PolkaVM smart contracts. These can potentially be written in any language that compiles to
RISC-V. For now, the only officially supported languages are Solidity (via [`revive`](https://github.com/xermicus/revive))
RISC-V. For now, the only officially supported languages are Solidity (via [`revive`](https://github.com/pezkuwichain/revive))
and Rust (check the `fixtures` directory for Rust examples).
## Host function tracing
bizinikiwi/pezframe/staking-async/runtimes/teyrchain/src/lib.rs
+1 -1
View File
@@ -253,7 +253,7 @@ parameter_types! {
pub const ApprovalDeposit: Balance = EXISTENTIAL_DEPOSIT;
pub const AssetsStringLimit: u32 = 50;
/// Key = 32 bytes, Value = 36 bytes (32+1+1+1+1)
// https://github.com/paritytech/bizinikiwi/blob/069917b/frame/assets/src/lib.rs#L257L271
// https://github.com/pezkuwichain/kurdistan-sdk/blob/main/bizinikiwi/pezframe/assets/src/lib.rs#L257L271
pub const MetadataDepositBase: Balance = deposit(1, 68);
pub const MetadataDepositPerByte: Balance = deposit(0, 1);
}
bizinikiwi/pezframe/staking/src/migrations.rs
+1 -1
View File
@@ -203,7 +203,7 @@ pub mod v15 {
}
/// Migration of era exposure storage items to paged exposures.
/// Changelog: [v14.](https://github.com/paritytech/bizinikiwi/blob/ankan/paged-rewards-rebased2/frame/staking/CHANGELOG.md#14)
/// Changelog: [v14.](https://github.com/pezkuwichain/kurdistan-sdk/blob/main/bizinikiwi/pezframe/staking/CHANGELOG.md#14)
pub mod v14 {
use super::*;
bizinikiwi/primitives/crypto/ec-utils/src/lib.rs
+1 -1
View File
@@ -21,7 +21,7 @@
//! The implementation has been primarily designed to be used in slow hosted
//! targets (e.g. wasm32) and offloads the most computationally expensive
//! operations to the host by leveraging the
//! [arkworks-extensions](https://github.com/paritytech/arkworks-extensions)
//! [arkworks-extensions](https://github.com/pezkuwichain/arkworks-extensions)
//! library and Bizinikiwi's host functions.
//!
//! The exported types are organized and named in a way that mirrors the structure
bizinikiwi/utils/pezframe/benchmarking-cli/src/overhead/README.md
+5 -5
View File
@@ -109,9 +109,9 @@ cargo run --profile=production -- benchmark overhead --chain=pezkuwi-dev --wasm-
```
This will overwrite the
[block_weights.rs](https://github.com/paritytech/polkadot/blob/c254e5975711a6497af256f6831e9a6c752d28f5/runtime/polkadot/constants/src/weights/block_weights.rs)
[block_weights.rs](https://github.com/pezkuwichain/kurdistan-sdk/blob/main/pezkuwi/runtime/pezkuwichain/constants/src/weights/block_weights.rs)
and
[extrinsic_weights.rs](https://github.com/paritytech/polkadot/blob/c254e5975711a6497af256f6831e9a6c752d28f5/runtime/polkadot/constants/src/weights/extrinsic_weights.rs)
[extrinsic_weights.rs](https://github.com/pezkuwichain/kurdistan-sdk/blob/main/pezkuwi/runtime/pezkuwichain/constants/src/weights/extrinsic_weights.rs)
files in the PezkuwiChain runtime directory. You can try the same for *pezkuwichain* and to see that the results slightly differ.
👉 It is paramount to use `--profile=production` and `--wasm-execution=compiled` as the results are otherwise useless.
@@ -138,9 +138,9 @@ License: Apache-2.0
<!-- LINKS -->
[`ExtrinsicBaseWeight`]:
https://github.com/paritytech/bizinikiwi/blob/580ebae17fa30082604f1c9720f6f4a1cfe95b50/frame/support/src/weights/extrinsic_weights.rs#L26
https://github.com/pezkuwichain/kurdistan-sdk/blob/main/bizinikiwi/pezframe/support/src/weights/extrinsic_weights.rs#L26
[`BlockExecutionWeight`]:
https://github.com/paritytech/bizinikiwi/blob/580ebae17fa30082604f1c9720f6f4a1cfe95b50/frame/support/src/weights/block_weights.rs#L26
https://github.com/pezkuwichain/kurdistan-sdk/blob/main/bizinikiwi/pezframe/support/src/weights/block_weights.rs#L26
[System::Remark]:
https://github.com/paritytech/bizinikiwi/blob/580ebae17fa30082604f1c9720f6f4a1cfe95b50/frame/system/src/lib.rs#L382
https://github.com/pezkuwichain/kurdistan-sdk/blob/main/bizinikiwi/pezframe/system/src/lib.rs#L382
bizinikiwi/utils/wasm-builder/src/prerequisites.rs
+1 -1
View File
@@ -64,7 +64,7 @@ pub(crate) fn check(target: RuntimeTarget) -> Result<CargoCommandVersioned, Stri
if !cargo_command.supports_bizinikiwi_runtime_env(target) {
return Err(colorize_error_message(
"Cannot compile a RISC-V runtime: no compatible Rust compiler found!\n\
Install a toolchain from here and try again: https://github.com/paritytech/rustc-rv32e-toolchain/",
Install a toolchain from here and try again: https://github.com/pezkuwichain/rustc-rv32e-toolchain/",
));
}
bizinikiwi/utils/wasm-builder/src/wasm_project.rs
+1 -1
View File
@@ -528,7 +528,7 @@ fn create_project_cargo_toml(
// TODO: Remove this once a new version of `bitvec` (which uses a new version of `radium`
// which doesn't have this problem) is released on crates.io.
let radium_patch = toml::toml! {
radium = { git = "https://github.com/paritytech/radium-0.7-fork.git", rev = "a5da15a15c90fd169d661d206cf0db592487f52b" }
radium = { git = "https://github.com/pezkuwichain/radium-0.7-fork.git", rev = "a5da15a15c90fd169d661d206cf0db592487f52b" }
};
let mut patch = wasm_workspace_toml
bridges/README.md
+3 -3
View File
@@ -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
+1 -1
View File
@@ -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
+2 -2
View File
@@ -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
+2 -2
View File
@@ -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
+3 -3
View File
@@ -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`;
docs/RELEASE.md
+4 -4
View File
@@ -25,8 +25,8 @@ The outputs of a stable release are:
# Timeline
`Stable` releases are scheduled on a quarterly basis, usually by the end of the last month of each quarter. The exact
schedule can be found on the [Release Registry](https://github.com/paritytech/release-registry/).It is possible to
subscribe to a [calendar link](https://raw.githubusercontent.com/paritytech/release-registry/main/releases-v1.ics)
schedule can be found on the [Release Registry](https://github.com/pezkuwichain/release-registry/).It is possible to
subscribe to a [calendar link](https://raw.githubusercontent.com/pezkuwichain/release-registry/main/releases-v1.ics)
to have it in your personal calendar.
Each stable release is supported for a period of one year from its first release. For example, `Pezkuwi stable2412`
@@ -175,8 +175,8 @@ to have it as a final rc on the S3
From the main Pezkuwi-sdk repository in the paritytech org:
1. Synchronize templates using [Synchronize templates](/.github/workflows/misc-sync-templates.yml)
2. Update the [Release Registry](https://github.com/paritytech/release-registry/)
follwoing the [instructions](https://github.com/paritytech/release-registry?tab=readme-ov-file#maintenance)
2. Update the [Release Registry](https://github.com/pezkuwichain/release-registry/)
follwoing the [instructions](https://github.com/pezkuwichain/release-registry?tab=readme-ov-file#maintenance)
in the repo with the actual release dates.
## Patch release for the latest stable version
docs/contributor/container.md
+1 -1
View File
@@ -16,7 +16,7 @@ Parity builds and publishes a container image that can be found as `docker.io/pa
## Parity CI image
Parity maintains and uses internally a generic "CI" image that can be used as a base to build binaries: [Parity CI
container image](https://github.com/paritytech/dockerfiles/tree/main/ci-unified):
container image](https://github.com/pezkuwichain/dockerfiles/tree/main/ci-unified):
The command below allows building a Linux binary without having to even install Rust or any dependency locally:
docs/contributor/prdoc.md
+3 -4
View File
@@ -1,6 +1,6 @@
# PRDoc
A [prdoc](https://github.com/paritytech/prdoc) is like a changelog but for a Pull Request. We use
A [prdoc](https://github.com/pezkuwichain/prdoc) is like a changelog but for a Pull Request. We use
this approach to record changes on a crate level. This information is then processed by the release
team to apply the correct crate version bumps and to generate the CHANGELOG of the next release.
@@ -53,12 +53,11 @@ Options:
A `.prdoc` file is a YAML file with a defined structure (ie JSON Schema). Please follow these steps
to generate one:
1. Install the [`prdoc` CLI](https://github.com/paritytech/prdoc) by running `cargo install
parity-prdoc`.
1. Install the [`prdoc` CLI](https://github.com/pezkuwichain/prdoc) by running `cargo install`
1. Open a Pull Request and get the PR number.
1. Generate the file with `prdoc generate <PR_NUMBER>`. The output filename will be printed.
1. Optional: Install the `prdoc/schema_user.json` schema in your editor, for example
[VsCode](https://github.com/paritytech/prdoc?tab=readme-ov-file#schemas).
[VsCode](https://github.com/pezkuwichain/prdoc?tab=readme-ov-file#schemas).
1. Edit your `.prdoc` file according to the [Audience](#pick-an-audience) and
[SemVer](#record-semver-changes) sections.
1. Check your prdoc with `prdoc check -n <PR_NUMBER>`. This is optional since the CI will also check
docs/sdk/src/pezkuwi_sdk/bizinikiwi.rs
+1 -1
View File
@@ -88,7 +88,7 @@
//! build their WASM files as a part of normal build command (e.g. `cargo build`). Once built, the
//! wasm file is placed in `./target/{debug|release}/wbuild/{runtime_name}/{runtime_name}.wasm`.
//!
//! In order to ensure that the WASM build is **deterministic**, the [Bizinikiwi Runtime Toolbox (srtool)](https://github.com/paritytech/srtool) can be used.
//! In order to ensure that the WASM build is **deterministic**, the [Bizinikiwi Runtime Toolbox (srtool)](https://github.com/pezkuwichain/srtool) can be used.
//!
//! ### Anatomy of a Binary Crate
//!
docs/sdk/src/pezkuwi_sdk/mod.rs
+8 -8
View File
@@ -58,18 +58,18 @@
//!
//! #### XCM
//!
//! [![XCM-license](https://img.shields.io/badge/License-GPL3-blue)](https://github.com/paritytech/polkadot-sdk/blob/master/polkadot/LICENSE)
//! [![XCM-license](https://img.shields.io/badge/License-GPL3-blue)](https://github.com/pezkuwichain/pezkuwi-sdk/blob/master/pezkuwi/LICENSE)
//! [![GitHub
//! Repo](https://img.shields.io/badge/github-XCM-e6007a?logo=polkadot)](https://github.com/paritytech/polkadot-sdk/blob/master/polkadot/xcm)
//! Repo](https://img.shields.io/badge/github-XCM-e6007a?logo=polkadot)](https://github.com/pezkuwichain/pezkuwi-sdk/blob/master/pezkuwi/xcm)
//!
//! [`xcm`], short for "cross consensus message", is the primary format that is used for
//! communication between teyrchains, but is intended to be extensible to other use cases as well.
//!
//! #### Pezkuwi
//!
//! [![Pezkuwi-license](https://img.shields.io/badge/License-GPL3-blue)](https://github.com/paritytech/polkadot-sdk/blob/master/polkadot/LICENSE)
//! [![Pezkuwi-license](https://img.shields.io/badge/License-GPL3-blue)](https://github.com/pezkuwichain/pezkuwi-sdk/blob/master/pezkuwi/LICENSE)
//! [![GitHub
//! Repo](https://img.shields.io/badge/github-polkadot-e6007a?logo=polkadot)](https://github.com/paritytech/polkadot-sdk/blob/master/polkadot)
//! Repo](https://img.shields.io/badge/github-polkadot-e6007a?logo=polkadot)](https://github.com/pezkuwichain/pezkuwi-sdk/blob/master/pezkuwi)
//!
//! [`pezkuwi`] is an implementation of a Pezkuwi node in Rust, by `@paritytech`. The Pezkuwi
//! runtimes are located under the
@@ -116,10 +116,10 @@
//!
//! ## Notable Upstream Crates
//!
//! - [`parity-scale-codec`](https://github.com/paritytech/parity-scale-codec)
//! - [`parity-db`](https://github.com/paritytech/parity-db)
//! - [`trie`](https://github.com/paritytech/trie)
//! - [`parity-common`](https://github.com/paritytech/parity-common)
//! - [`parity-scale-codec`](https://github.com/pezkuwichain/parity-scale-codec)
//! - [`parity-db`](https://github.com/pezkuwichain/parity-db)
//! - [`trie`](https://github.com/pezkuwichain/trie)
//! - [`parity-common`](https://github.com/pezkuwichain/parity-common)
//!
//! ## Trophy Section: Notable Downstream Projects
//!
docs/sdk/src/pezkuwi_sdk/xcm.rs
+2 -2
View File
@@ -5,7 +5,7 @@
//!
//! ## Overview
//!
//! XCM is a standard, specification of which lives in the [xcm format repo](https://github.com/paritytech/xcm-format).
//! XCM is a standard, specification of which lives in the [xcm format repo](https://github.com/pezkuwichain/xcm-format).
//! It's agnostic both in programming language and blockchain platform, which means it could be used
//! in Rust in Pezkuwi, or in Go or C++ in any other platform like Cosmos or Ethereum.
//!
@@ -30,7 +30,7 @@
//!
//! ## Implementation
//!
//! A ready-to-use Rust implementation lives in the [pezkuwi-sdk repo](https://github.com/paritytech/polkadot-sdk/tree/master/polkadot/xcm),
//! A ready-to-use Rust implementation lives in the [pezkuwi-sdk repo](https://github.com/pezkuwichain/kurdistan-sdk/tree/main/pezkuwi/xcm),
//! but will be moved to its own repo in the future.
//!
//! Its main components are:
docs/sdk/src/reference_docs/frame_runtime_upgrades_and_migrations.rs
+3 -3
View File
@@ -87,8 +87,8 @@
//! - Touching too many storage keys and resulting in an excessively large PoV.
//! - Taking too long to execute.
//!
//! [`try-runtime-cli`](https://github.com/paritytech/try-runtime-cli) has a sub-command
//! [`on-runtime-upgrade`](https://paritytech.github.io/try-runtime-cli/try_runtime_core/commands/enum.Action.html#variant.OnRuntimeUpgrade)
//! [`try-runtime-cli`](https://github.com/pezkuwichain/try-runtime-cli) has a sub-command
//! [`on-runtime-upgrade`](https://pezkuwichain.github.io/try-runtime-cli/try_runtime_core/commands/enum.Action.html#variant.OnRuntimeUpgrade)
//! which is designed to help with exactly this.
//!
//! Developers MUST run this command before deploying migrations to ensure they will not
@@ -100,7 +100,7 @@
//!
//! ### Note on the Manipulability of PoV Size and Execution Time
//!
//! While [`try-runtime-cli`](https://github.com/paritytech/try-runtime-cli) can help ensure with
//! While [`try-runtime-cli`](https://github.com/pezkuwichain/try-runtime-cli) can help ensure with
//! very high certainty that a migration will succeed given **existing** on-chain state, it cannot
//! prevent a malicious actor from manipulating state in a way that will cause the migration to take
//! longer or produce a PoV much larger than previously measured.
pezcumulus/teyrchains/runtimes/assets/asset-hub-pezkuwichain/src/lib.rs
+1 -1
View File
@@ -257,7 +257,7 @@ parameter_types! {
pub const ApprovalDeposit: Balance = EXISTENTIAL_DEPOSIT;
pub const AssetsStringLimit: u32 = 50;
/// Key = 32 bytes, Value = 36 bytes (32+1+1+1+1)
// https://github.com/paritytech/bizinikiwi/blob/069917b/frame/assets/src/lib.rs#L257L271
// https://github.com/pezkuwichain/kurdistan-sdk/blob/main/bizinikiwi/pezframe/assets/src/lib.rs#L257L271
pub const MetadataDepositBase: Balance = deposit(1, 68);
pub const MetadataDepositPerByte: Balance = deposit(0, 1);
}
pezcumulus/teyrchains/runtimes/assets/asset-hub-zagros/src/lib.rs
+1 -1
View File
@@ -281,7 +281,7 @@ parameter_types! {
pub const ApprovalDeposit: Balance = EXISTENTIAL_DEPOSIT;
pub const AssetsStringLimit: u32 = 50;
/// Key = 32 bytes, Value = 36 bytes (32+1+1+1+1)
// https://github.com/paritytech/bizinikiwi/blob/069917b/frame/assets/src/lib.rs#L257L271
// https://github.com/pezkuwichain/kurdistan-sdk/blob/main/bizinikiwi/pezframe/assets/src/lib.rs#L257L271
pub const MetadataDepositBase: Balance = deposit(1, 68);
pub const MetadataDepositPerByte: Balance = deposit(0, 1);
}
pezkuwi/README.md
+2 -2
View File
@@ -230,7 +230,7 @@ that we currently maintain.
### Shell Completion
[Shell Completion](https://github.com/paritytech/polkadot-sdk/blob/master/polkadot/doc/shell-completion.md)
[Shell Completion](https://github.com/pezkuwichain/pezkuwi-sdk/blob/master/pezkuwi/doc/shell-completion.md)
## Contributing
@@ -244,4 +244,4 @@ that we currently maintain.
## License
Pezkuwi is [GPL 3.0 licensed](https://github.com/paritytech/polkadot-sdk/blob/master/polkadot/LICENSE).
Pezkuwi is [GPL 3.0 licensed](https://github.com/pezkuwichain/pezkuwi-sdk/blob/master/pezkuwi/LICENSE).
pezkuwi/node/core/pvf/README.md
+1 -1
View File
@@ -43,5 +43,5 @@ another popular persistent shell, mosh, it allows scrollback.
[impl-guide]: https://docs.pezkuwichain.io/sdk/book/pvf-prechecking.html#summary
[glossary]: https://docs.pezkuwichain.io/sdk/book/glossary.html
[testing]: https://github.com/paritytech/polkadot-sdk/blob/master/polkadot/doc/testing.md
[testing]: https://github.com/pezkuwichain/kurdistan-sdk/blob/main/pezkuwi/doc/testing.md
[et]: https://github.com/MisterTea/EternalTerminal
pezkuwi/node/malus/README.md
+1 -1
View File
@@ -56,4 +56,4 @@ podman build -t paritypr/malus:v1 -f Containerfile ../../..
```
[zombienet]: https://github.com/paritytech/zombienet
[gke]: (https://github.com/paritytech/gurke/blob/main/docs/How-to-setup-access-to-gke-k8s-cluster.md)
[gke]: (https://github.com/pezkuwichain/gurke/blob/main/docs/How-to-setup-access-to-gke-k8s-cluster.md)
pezkuwi/roadmap/implementers-guide/src/messaging.md
+1 -1
View File
@@ -91,7 +91,7 @@ are required to be processed by the receiver's candidate, only the processed mes
rest are provided as hashes.
Further details can be found at the official repository for the [Cross-Consensus Message Format
(XCM)](https://github.com/paritytech/xcm-format/blob/master/README.md), as well as at the [W3F research
(XCM)](https://github.com/pezkuwichain/xcm-format/blob/master/README.md), as well as at the [W3F research
website](https://research.web3.foundation/en/latest/polkadot/XCMP.html) and [this
blogpost](https://medium.com/web3foundation/polkadots-messaging-scheme-b1ec560908b7).
pezkuwi/roadmap/implementers-guide/src/runtime/session_info.md
+3 -3
View File
@@ -14,7 +14,7 @@ struct SessionInfo {
///
/// NOTE: There might be more authorities in the current session, than `validators` participating
/// in teyrchain consensus. See
/// [`max_validators`](https://github.com/paritytech/polkadot/blob/a52dca2be7840b23c19c153cf7e110b1e3e475f8/runtime/parachains/src/configuration.rs#L148).
/// [`max_validators`](https://github.com/pezkuwichain/kurdistan-sdk/blob/main/pezkuwi/runtime/teyrchains/src/configuration.rs#L148)..
///
/// `SessionInfo::validators` will be limited to `max_validators` when set.
validators: Vec<ValidatorId>,
@@ -23,14 +23,14 @@ struct SessionInfo {
/// NOTE: The first `validators.len()` entries will match the corresponding validators in
/// `validators`, afterwards any remaining authorities can be found. This is any authorities not
/// participating in teyrchain consensus - see
/// [`max_validators`](https://github.com/paritytech/polkadot/blob/a52dca2be7840b23c19c153cf7e110b1e3e475f8/runtime/parachains/src/configuration.rs#L148)
/// [`max_validators`](https://github.com/pezkuwichain/kurdistan-sdk/blob/main/pezkuwi/runtime/teyrchains/src/configuration.rs#L148).
#[cfg_attr(feature = "std", ignore_malloc_size_of = "outside type")]
discovery_keys: Vec<AuthorityDiscoveryId>,
/// The assignment keys for validators.
///
/// NOTE: There might be more authorities in the current session, than validators participating
/// in teyrchain consensus. See
/// [`max_validators`](https://github.com/paritytech/polkadot/blob/a52dca2be7840b23c19c153cf7e110b1e3e475f8/runtime/parachains/src/configuration.rs#L148).
/// [`max_validators`](https://github.com/pezkuwichain/kurdistan-sdk/blob/main/pezkuwi/runtime/teyrchains/src/configuration.rs#L148)..
///
/// Therefore:
/// ```ignore
pezkuwi/roadmap/implementers-guide/src/types/runtime.md
+2 -2
View File
@@ -7,7 +7,7 @@ Types used within the runtime exclusively and pervasively.
The internal-to-runtime configuration of the teyrchain host is kept in `struct HostConfiguration`. This is expected to
be altered only by governance procedures or via migrations from the Pezkuwi-SDK codebase. The latest definition of
`HostConfiguration` can be found in the project repo
[here](https://github.com/paritytech/polkadot-sdk/blob/master/polkadot/runtime/parachains/src/configuration.rs). Each
[here](https://github.com/pezkuwichain/kurdistan-sdk/blob/main/pezkuwi/runtime/teyrchains/src/configuration.rs). Each
parameter has got a doc comment so for any details please refer to the code.
Some related parameters in `HostConfiguration` are grouped together so that they can be managed easily. These are:
@@ -20,7 +20,7 @@ Check the definitions of these structs for further details.
### Configuration migrations
Modifying `HostConfiguration` requires a storage migration. These migrations are located in the
[`migrations`](https://github.com/paritytech/polkadot-sdk/blob/master/polkadot/runtime/parachains/src/configuration.rs)
[`migrations`](https://github.com/pezkuwichain/kurdistan-sdk/blob/main/pezkuwi/runtime/teyrchains/src/configuration.rs)
subfolder of Pezkuwi-SDK repo.
## ParaInherentData
prdoc/schema_user.json
+1 -1
View File
@@ -1,6 +1,6 @@
{
"$schema": "https://json-schema.org/draft/2020-12/schema#",
"$id": "https://raw.githubusercontent.com/paritytech/prdoc/master/prdoc_schema_user.json",
"$id": "https://raw.githubusercontent.com/pezkuwichain/prdoc/master/prdoc_schema_user.json",
"version": {
"major": 1,
"minor": 1,
scripts/release/build-changelogs.sh
+2 -2
View File
@@ -27,12 +27,12 @@ OUTPUT="${TMP}/changelogs/$PRODUCT/$VERSION"
echo -e "OUTPUT: \t\t$OUTPUT"
mkdir -p $OUTPUT
$ENGINE run --rm -v ${PROJECT_ROOT}:/repo paritytech/prdoc load -d "prdoc/$VERSION" --json > $DATA_JSON
$ENGINE run --rm -v ${PROJECT_ROOT}:/repo pezkuwichain/prdoc load -d "prdoc/$VERSION" --json > $DATA_JSON
cat $DATA_JSON | jq ' { "prdoc" : .}' > $CONTEXT_JSON
# Fetch the list of valid audiences and their descriptions
SCHEMA_URL=https://raw.githubusercontent.com/paritytech/polkadot-sdk/master/prdoc/schema_user.json
SCHEMA_URL=https://raw.githubusercontent.com/pezkuwichain/kurdistan-sdk/master/prdoc/schema_user.json
SCHEMA=$(curl -s $SCHEMA_URL | sed 's|^//.*||')
aud_desc_array=()
while IFS= read -r line; do
scripts/release/templates/runtimes.md.tera
+1 -1
View File
@@ -8,7 +8,7 @@
{% set rtm = srtool[0] -%}
The information about the runtimes included in this release can be found below.
The runtimes have been built using [{{ rtm.data.gen }}](https://github.com/paritytech/srtool) and `{{ rtm.data.rustc }}`.
The runtimes have been built using [{{ rtm.data.gen }}](https://github.com/pezkuwichain/srtool) and `{{ rtm.data.rustc }}`.
{%- for runtime in srtool | sort(attribute="name") %}
{%- set HIDE_VAR = "HIDE_SRTOOL_" ~ runtime.name | upper %}
umbrella/README.md
+1 -1
View File
@@ -63,7 +63,7 @@ with-tracing = ["pezkuwi-sdk/with-tracing"]
cargo build --features "runtime-benchmarks,with-tracing"
```
Bizinikiwi's [try-runtime](https://paritytech.github.io/try-runtime-cli/try_runtime/) is an essential
Bizinikiwi's [try-runtime](https://pezkuwichain.github.io/try-runtime-cli/try_runtime/) is an essential
tool for testing runtime protocol upgrades locally, which can be enabled with the `try-runtime`
feature.
vendor/zombienet-configuration/Cargo.toml
Vendored
+1 -1
View File
@@ -26,7 +26,7 @@ description = "Zombienet sdk config builder, allow to build a network configurat
readme = false
keywords = ["configuration", "sdk", "zombienet"]
license = "Apache-2.0 OR GPL-3.0"
repository = "https://github.com/paritytech/zombienet-sdk"
repository = "https://github.com/pezkuwichain/zombienet-sdk"
[lib]
name = "zombienet_configuration"