feat: Rebrand Kurdistan SDK to PezkuwiChain

This commit is contained in:
2025-12-14 01:11:30 +03:00
parent e65c951214
commit 5520d491a5
49 changed files with 93 additions and 96 deletions
+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,
}
+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
@@ -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
+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.
+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.
//!
@@ -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;
+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
+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