Files
pezkuwi-sdk/bizinikiwi/pezframe/src/README.md
T
pezkuwichain 3139ffa25e 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

1.9 KiB

SDK Logo SDK Logo

pezkuwi-sdk-frame

StackExchange

pezkuwi-sdk-frame is an umbrella crate for the FRAME framework. It simplifies building FRAME pallets and runtimes by re-exporting all the necessary components for pezpallet development.

Outside the Pezkuwi SDK, pezkuwi-sdk-frame should be imported through the main Pezkuwi SDK umbrella crate.

💻 Usage

The main intended use of this crate is through Preludes, which re-export most of the components needed for pezpallet development. The available preludes are:

  • prelude: main prelude for pezpallet development, containing essential types and traits
  • testing_prelude: testing utilities and helpers for writing pezpallet tests
  • runtime::prelude: runtime-specific components for building blockchain runtimes
  • benchmarking::prelude: benchmarking components for performance testing
  • weights_prelude: components for the auto-generated weight.rs files

If you need specific dependencies that aren't included in the preludes, you can use the deps module to access all FRAME and Bizinikiwi dependencies directly. However, we strongly recommend checking the preludes and domain-specific modules first, as they provide a more organized and maintainable way to access these dependencies.

📚 Documentation

For more detailed documentation and examples, see pezkuwi_sdk_frame.