Refactoring Checkpoint: (WIP)

bridges/primitives/relayers/src/extension.rs

@@ -17,9 +17,9 @@
 //! All runtime calls, supported by `pezpallet-bridge-relayers` when it acts as a signed
 //! extension.
 
-use bp_header_chain::SubmitFinalityProofInfo;
+use bp_header_pez_chain::SubmitFinalityProofInfo;
 use bp_messages::MessagesCallInfo;
-use bp_runtime::StaticStrProvider;
+use pezbp_runtime::StaticStrProvider;
 use bp_teyrchains::SubmitTeyrchainHeadsInfo;
 use codec::{Decode, Encode};
 use pezframe_support::{

bridges/primitives/relayers/src/lib.rs

@@ -25,7 +25,7 @@ pub use extension::{
 };
 pub use registration::{ExplicitOrAccountParams, Registration, StakeAndSlash};
 
-use bp_runtime::{ChainId, StorageDoubleMapKeyProvider};
+use pezbp_runtime::{ChainId, StorageDoubleMapKeyProvider};
 use pezframe_support::{traits::tokens::Preservation, Blake2_128Concat, Identity};
 use scale_info::TypeInfo;
 use pezsp_runtime::{

bridges/primitives/relayers/src/registration.rs

@@ -21,7 +21,7 @@
 //! required finality proofs). This extension boosts priority of message delivery
 //! transactions, based on the number of bundled messages. So transaction with more
 //! messages has larger priority than the transaction with less messages.
-//! See `bridge_runtime_common::extensions::priority_calculator` for details;
+//! See `pezbridge_runtime_common::extensions::priority_calculator` for details;
 //!
 //! This encourages relayers to include more messages to their delivery transactions.
 //! At the same time, we are not verifying storage proofs before boosting