mirror of
https://github.com/pezkuwichain/pwap.git
synced 2026-06-15 01:21:02 +00:00
pezkuwichain
1295c36241
- Fixed TypeScript type assertion issues - Updated imports from api-augment/substrate to api-augment/bizinikiwi - Fixed imgConvert.mjs header and imports - Added @ts-expect-error for runtime-converted types - Fixed all @polkadot copyright headers to @pezkuwi
26 lines
1.3 KiB
Rust
26 lines
1.3 KiB
Rust
//! # Metadata
|
|
//!
|
|
//! The existence of metadata in pezkuwi-sdk goes back to the (forkless) upgrade-ability of all
|
|
//! Bizinikiwi-based blockchains, which is achieved through
|
|
//! [`crate::reference_docs::wasm_meta_protocol`]. You can learn more about the details of how to
|
|
//! deal with these upgrades in [`crate::reference_docs::frame_runtime_upgrades_and_migrations`].
|
|
//!
|
|
//! Another consequence of upgrade-ability is that as a UI, wallet, or generally an offchain entity,
|
|
//! it is hard to know the types internal to the runtime, specifically in light of the fact that
|
|
//! they can change at any point in time.
|
|
//!
|
|
//! This is why all Bizinikiwi-based runtimes must expose a [`pezsp_api::Metadata`] api, which
|
|
//! mandates the runtime to return a description of itself. The return type of this api is
|
|
//! `Vec<u8>`, meaning that it is up to the runtime developer to decide on the format of this.
|
|
//!
|
|
//! All [`crate::pezkuwi_sdk::frame_runtime`] based runtimes expose a specific metadata language,
|
|
//! maintained in <https://github.com/paritytech/frame-metadata> which is adopted in the Pezkuwi
|
|
//! ecosystem.
|
|
//!
|
|
//! ## Metadata Explorers:
|
|
//!
|
|
//! A few noteworthy tools that inspect the (FRAME-based) metadata of a chain:
|
|
//!
|
|
//! - <https://wiki.network.pezkuwichain.io/docs/metadata>
|
|
//! - <https://paritytech.github.io/subxt-explorer/>
|