Pezkuwi SDK — Sovereign Blockchain Infrastructure

Developed and maintained by Kurdistan Tech Institute

Pezkuwi SDK is a fully independent blockchain development framework, providing all the tools needed to build sovereign, interoperable blockchain networks for stateless nations and distributed communities.

Origin

Pezkuwi SDK originated as a fork of Polkadot SDK (stable2512). It has since been completely rebranded and restructured as an independent project under Kurdistan Tech Institute stewardship. All crate names, dependencies, and documentation have been updated to reflect this independence.

Architecture

┌─────────────────────────────────────────────────────────────┐
│                    Pezkuwi SDK Ecosystem                    │
├─────────────────────────────────────────────────────────────┤
│                                                              │
│   ┌─────────────────────┐    ┌─────────────────────────┐    │
│   │   Bizinikiwi        │    │      PezCumulus         │    │
│   │   (Core Framework)  │    │     (TeyrChain SDK)     │    │
│   │                     │    │                         │    │
│   │  • Runtime Engine   │    │  • Collator Framework   │    │
│   │  • Consensus        │    │  • XCM Integration      │    │
│   │  • Networking       │    │  • Relay Chain Bridge   │    │
│   └─────────────────────┘    └─────────────────────────┘    │
│              │                          │                    │
│              └──────────┬───────────────┘                    │
│                         │                                    │
│              ┌──────────▼───────────┐                        │
│              │   PezkuwiChain       │                        │
│              │   (Reference Impl)   │                        │
│              │   • TeyrChain        │                        │
│              │   • Zagros Runtime   │                        │
│              └──────────────────────┘                        │
└─────────────────────────────────────────────────────────────┘

Crate Naming Convention

Pezkuwi SDK uses a distinct naming scheme to ensure complete independence:

PezkuwiChain — Reference Implementation

PezkuwiChain is the flagship blockchain built on Pezkuwi SDK, designed for Kurdish digital sovereignty.

Token Economics

HEZ — Native Gas Token

• Purpose: Transaction fees, staking, network security
• Model: Inflationary with staking rewards
• Distribution: 85% staking rewards, 15% treasury

PEZ — Governance Token

• Total Supply: 5,000,000,000 PEZ
• Model: Fixed supply with halving cycles
• Access: Citizenship-gated rewards

Custom Pallets

TNPoS Consensus

Trust-enhanced Nominated Proof-of-Stake combines:

• Economic Stake (HEZ)
• Social Trust metrics
• Performance scoring

TNPoS Consensus — World's First Trust-Augmented PoS

Trust-enhanced Nominated Proof-of-Stake combines:

• Economic Stake: Traditional staking (HEZ)
• Social Trust: Peer endorsements, citizenship level, governance participation
• Performance Metrics: Uptime, finality participation, historical behavior

Key Innovations:

• First implementation of social trust in consensus (academic contribution)
• Parliamentary NFT System: 201 non-transferable governance seats
• Sybil-resistant via citizenship verification (Tiki pallet)
• Multi-dimensional validator scoring

Cross-Chain Integration (XCM v5)

Polkadot Asset Hub (USDT)
         │
         │ XCM Reserve Transfer
         ▼
TeyrChain (Parachain)
         │
         ├─► Presale contributions
         ├─► DEX trading (future)
         └─► Withdraw back to Asset Hub

• Full XCM v5 implementation
• Reserve-backed wUSDT bridge
• HRMP channels for system teyrchains
• Future bridges: wETH, wBTC, Ethereum, Tron, BSC

Network Roadmap

Multi-Nation Platform Vision

PezkuwiChain is designed to host multiple digital nations simultaneously:

Shared Infrastructure: All nations use HEZ for transactions Nation-Specific Tokens: Each group issues citizenship-gated tokens (PEZ model) Interoperable Governance: Cross-nation commerce, diplomacy on single blockchain

Use Cases

1. Digital Governance — Parliamentary NFTs, on-chain voting, treasury management
2. Token Launches — Compliant multi-round presales with vesting
3. Education — Blockchain-verified certificates (Perwerde)
4. Identity — Self-sovereign KYC and citizenship verification
5. Cross-Chain Finance — wUSDT bridge, DeFi primitives
6. Cultural Preservation — Language, heritage, oral tradition on-chain
7. Remittance — Low-cost diaspora→homeland transfers ($20B+ Kurdish annual flows)

Quick Start

# Clone repository
git clone https://github.com/pezkuwichain/pezkuwi-sdk.git
cd pezkuwi-sdk

# Build release
cargo build --release

# Build with benchmarks
cargo build --release --features runtime-benchmarks

# Run local testnet
./target/release/pezkuwi-node --dev

Links

Community

Quickstart

If you want to get an example node running quickly you can execute the following getting started script:

curl --proto '=https' --tlsv1.2 -sSf https://raw.githubusercontent.com/pezkuwichain/pezkuwi-sdk/master/scripts/getting-started.sh | bash

Building

In order to build this project you need to install some dependencies, follow the instructions in this guide.

Documentation

• Pezkuwi Documentation Portal
• rust-docs: Where we keep track of the API docs of our Rust crates. Includes:
  • Introduction to each component of the Pezkuwi SDK: Bizinikiwi, FRAME, PezCumulus, and XCM
  • Guides, namely how to build your first FRAME pallet
  • Templates for starting a new project.
  • External Resources
• Have a question? You can ask in the Pezkuwi SDK Developers Chat.
  • Telegram
  • Matrix
  • Discord
  • Pezkuwi StackExchange

Releases

The Pezkuwi SDK is released every three months as a Pezkuwi stableYYMM release. Each stable release is supported for one year with patches. See the next upcoming versions in the Release Registry and more docs in RELEASE.md.

You can use psvm to update all dependencies to a specific version without needing to manually select the correct version for each crate.

Tooling

Pezkuwi SDK Version Manager: A simple tool to manage and update the Pezkuwi SDK dependencies in any Cargo.toml file. It will automatically update the Pezkuwi SDK dependencies to their correct crates.io version.

Security

The security policy and procedures can be found in docs/contributor/SECURITY.md.

Contributing & Code of Conduct

Ensure you follow our contribution guidelines. In every interaction and contribution, this project adheres to the Contributor Covenant Code of Conduct.

Ready to Contribute?

Take a look at the issues labeled with mentor (or alternatively this page, created by one of the maintainers) label to get started! We always recognize valuable contributions by proposing an on-chain tip to the PezkuwiChain network as a token of our appreciation.

Pezkuwi Fellowship

Development in this repo usually goes hand in hand with the fellowship organization. In short, this repository provides all the SDK pieces needed to build both PezkuwiChain and its teyrchains. But, the actual PezkuwiChain runtime lives in the fellowship/runtimes repository. Read more about the fellowship, this separation, and the RFC process in the Pezkuwi Fellows repository.

History

This repository is the amalgamation of 3 separate repositories that used to make up Pezkuwi SDK, namely Bizinikiwi, Pezkuwi and PezCumulus. Read more about the SDK in the Pezkuwi SDK Documentation.

License

Pezkuwi SDK is licensed under Apache 2.0. See LICENSE for details.

lib.rs:

Supporting pezpallet for the statement store.

• Pezpallet

Overview

The Statement pezpallet provides means to create and validate statements for the statement store.

For each statement validation function calculates the following three values based on the statement author balance: max_count: Maximum number of statements allowed for the author (signer) of this statement. max_size: Maximum total size of statements allowed for the author (signer) of this statement.

This pezpallet also contains an offchain worker that turns on-chain statement events into statements. These statements are placed in the store and propagated over the network.