fix: Complete snowbridge pezpallet rebrand and critical bug fixes

- snowbridge-pezpallet-* → pezsnowbridge-pezpallet-* (201 refs) - pallet/ directories → pezpallet/ (4 locations) - Fixed pezpallet.rs self-include recursion bug - Fixed sc-chain-spec hardcoded crate name in derive macro - Reverted .pezpallet_by_name() to .pallet_by_name() (subxt API) - Added BizinikiwiConfig type alias for zombienet tests - Deleted obsolete session state files Verified: pezsnowbridge-pezpallet-*, pezpallet-staking, pezpallet-staking-async, pezframe-benchmarking-cli all pass cargo check
2025-12-16 09:57:23 +03:00
parent eea003e14d
commit 3139ffa25e
3022 changed files with 42157 additions and 23579 deletions
@@ -13,17 +13,17 @@
  - [Messaging Overview](messaging.md)
  - [PVF Pre-checking](pvf-prechecking.md)
 - [Runtime Architecture](runtime/README.md)
-  - [`Initializer` Pallet](runtime/initializer.md)
-  - [`Configuration` Pallet](runtime/configuration.md)
-  - [`Shared` Pallet](runtime/shared.md)
-  - [`Disputes` Pallet](runtime/disputes.md)
-  - [`Paras` Pallet](runtime/paras.md)
-  - [`Scheduler` Pallet](runtime/scheduler.md)
-  - [`Inclusion` Pallet](runtime/inclusion.md)
-  - [`ParaInherent` Pallet](runtime/parainherent.md)
-  - [`DMP` Pallet](runtime/dmp.md)
-  - [`HRMP` Pallet](runtime/hrmp.md)
-  - [`Session Info` Pallet](runtime/session_info.md)
+  - [`Initializer` Pezpallet](runtime/initializer.md)
+  - [`Configuration` Pezpallet](runtime/configuration.md)
+  - [`Shared` Pezpallet](runtime/shared.md)
+  - [`Disputes` Pezpallet](runtime/disputes.md)
+  - [`Paras` Pezpallet](runtime/paras.md)
+  - [`Scheduler` Pezpallet](runtime/scheduler.md)
+  - [`Inclusion` Pezpallet](runtime/inclusion.md)
+  - [`ParaInherent` Pezpallet](runtime/parainherent.md)
+  - [`DMP` Pezpallet](runtime/dmp.md)
+  - [`HRMP` Pezpallet](runtime/hrmp.md)
+  - [`Session Info` Pezpallet](runtime/session_info.md)
 - [Runtime APIs](runtime-api/README.md)
  - [Validators](runtime-api/validators.md)
  - [Validator Groups](runtime-api/validator-groups.md)
@@ -268,7 +268,7 @@ the set by slashes. ([**Point 6.**](#system-overview))
 ## Forcing New Era

 Previous implementation of disabling had some limited mechanisms allowing for validators disablement and if too many
-were disabled forcing a new era (new election). Frame staking pallet offered the ability to force a new era but it was
+were disabled forcing a new era (new election). Frame staking pezpallet offered the ability to force a new era but it was
 also deemed unsafe as it could be abused and compromised the security of the network for instance by weakening the
 randomness used throughout the protocol.

@@ -1,4 +1,4 @@
-# Configuration Pallet
+# Configuration Pezpallet

 This module is responsible for managing all configuration of the teyrchain host in-flight. It provides a central point
 for configuration updates to prevent races between configuration changes and teyrchain-processing logic. Configuration
@@ -1,4 +1,4 @@
-# Disputes Pallet
+# Disputes Pezpallet

 After a backed candidate is made available, it is included and proceeds into an acceptance period during which
 validators are randomly selected to do (secondary) approval checks of the parablock. Any reports disputing the validity
@@ -134,7 +134,7 @@ means persisted in the runtime storage. The filtering has got two purposes:
 * Limit the amount of data saved onchain.
 * Prevent persisting malicious dispute data onchain.

-*Implementation note*: Filtering is performed in function `filter_dispute_data` from `Disputes` pallet.
+*Implementation note*: Filtering is performed in function `filter_dispute_data` from `Disputes` pezpallet.

 The filtering is performed on the whole statement set which is about to be imported onchain. The following filters are
 applied:
@@ -164,4 +164,4 @@ inconclusive disputes are not slashed. Thanks to the applied filtering (describe
 confident that there are no spam disputes in the runtime. So if a validator is not voting it is due to another reason
 (e.g. being under DoS attack). There is no reason to punish such validators with a slash.

-*Implementation note*: Slashing is performed in `process_checked_dispute_data` from `Disputes` pallet.
+*Implementation note*: Slashing is performed in `process_checked_dispute_data` from `Disputes` pezpallet.
@@ -1,4 +1,4 @@
-# DMP Pallet
+# DMP Pezpallet

 A module responsible for Downward Message Processing (DMP). See [Messaging Overview](../messaging.md) for more details.

@@ -1,4 +1,4 @@
-# HRMP Pallet
+# HRMP Pezpallet

 A module responsible for Horizontally Relay-routed Message Passing (HRMP). See [Messaging Overview](../messaging.md) for
 more details.
@@ -1,4 +1,4 @@
-# Inclusion Pallet
+# Inclusion Pezpallet

 > NOTE: This module has suffered changes for the elastic scaling implementation. As a result, parts of this document may
 be out of date and will be updated at a later time. Issue tracking the update:
@@ -44,7 +44,7 @@ PendingAvailabilityCommitments: map ParaId => CandidateCommitments;

 * `MessageQueue`: The message queue provides general queueing and processing functionality. Currently it replaces the
  old `UMP` dispatch queue. Other use-cases can be implemented as well by adding new variants to
-  `AggregateMessageOrigin`. Normally it should be set to an instance of the `MessageQueue` pallet.
+  `AggregateMessageOrigin`. Normally it should be set to an instance of the `MessageQueue` pezpallet.

 ## Session Change

@@ -57,7 +57,7 @@ Optional:

 ## Initialization

-No initialization routine runs for this module. However, the initialization of the `MessageQueue` pallet will attempt to
+No initialization routine runs for this module. However, the initialization of the `MessageQueue` pezpallet will attempt to
 process any pending UMP messages.


@@ -166,7 +166,7 @@ All failed checks should lead to an unrecoverable error making the block invalid
  the candidate hash is one of the disputed candidates, then clean up the corresponding storage for that candidate and
  the commitments. Return a vector of cleaned-up core IDs.

-These functions were formerly part of the UMP pallet:
+These functions were formerly part of the UMP pezpallet:

 * `check_upward_messages(P: ParaId, Vec<UpwardMessage>)`:
    1. Checks that the teyrchain is not currently offboarding and error otherwise.
@@ -1,4 +1,4 @@
-# Initializer Pallet
+# Initializer Pezpallet

 This module is responsible for initializing the other modules in a deterministic order. It also has one other purpose as
 described in the overview of the runtime: accepting and forwarding session change notifications.
@@ -93,6 +93,6 @@ Backed candidates sanitization removes malformed ones, candidates which have got
 or candidates produced by unassigned cores. Furthermore any backing votes from disabled validators for a candidate are
 dropped. This is part of the validator disabling strategy. After filtering the statements from disabled validators a
 backed candidate may end up with votes count less than `minimum_backing_votes` (a parameter from `HostConfiguration`).
-In this case the whole candidate is dropped otherwise it will be rejected by `process_candidates` from pallet inclusion.
+In this case the whole candidate is dropped otherwise it will be rejected by `process_candidates` from pezpallet inclusion.
 All checks related to backed candidates are implemented in `sanitize_backed_candidates` and
 `filter_backed_statements_from_disabled_validators`.
@@ -1,4 +1,4 @@
-# Paras Pallet
+# Paras Pezpallet

 The Paras module is responsible for storing information on teyrchains. Registered teyrchains cannot change except at
 session boundaries and after at least a full session has passed. This is primarily to ensure that the number and meaning
@@ -1,4 +1,4 @@
-# Scheduler Pallet
+# Scheduler Pezpallet

 > TODO: this section is still heavily under construction. key questions about availability cores and validator
 > assignment are still open and the flow of the section may be contradictory or inconsistent
@@ -1,4 +1,4 @@
-# Shared Pallet
+# Shared Pezpallet

 This module is responsible for managing shared storage and configuration for other modules.