SatoshiQaziMuhammed
eb00e49a52
light-client/zagros.json and light-client/people-zagros.json are what the wallet's embedded light client starts from. The full specifications carry the raw genesis storage, about 3 MB each. These carry only the genesis state root, which identifies the chain: - The relay specification adds a checkpoint (lightSyncState) exported by the relay node through sync_state_genSyncSpec. It is 7.3 KB. - People has no checkpoint, because the relay chain's finality covers it. It is 732 bytes. Boot nodes put the /wss addresses on 443 first and keep the plain TCP ones. scripts/light_client_specs.py writes both files. It checks every state root by rebuilding the genesis header and comparing its hash with the chain's genesis hash. A root with one byte changed is refused. The checkpoint is a trust anchor: a client that starts from a false one can follow a false chain. It reaches the wallet inside the APK or through signed/targets.json, never from peers. Targets are re-signed (version 3, 689 files). The secret scan lets through the four public chain-data keys these files carry: stateRootHash, finalizedBlockHeader, babeEpochChanges and grandpaAuthoritySet.
Pezkuwi Wallet Utils
Configuration repository for Pezkuwi Wallet - next generation mobile wallet for Pezkuwichain and the Polkadot ecosystem.
Overview
This repository contains chain configurations, staking metadata, dApp listings, and other utility files used by Pezkuwi Wallet applications.
Structure
pezkuwi-wallet-utils/
├── chains/ # Chain configurations for all supported networks
│ ├── pezkuwichain/ # Pezkuwichain (Relay + Asset Hub + People Chain)
│ ├── polkadot/ # Polkadot ecosystem chains
│ ├── kusama/ # Kusama ecosystem chains
│ └── ... # Other ecosystem chains
├── staking/ # Staking metadata (validators, pools, etc.)
├── dapps/ # DApp configurations and metadata
├── xcm/ # XCM (Cross-Chain Messaging) configurations
├── governance/ # Governance dApps and proposals
├── banners/ # Promotional banners and announcements
├── migrations/ # Chain migration configurations
├── assets/ # Asset metadata and icons
├── icons/ # Chain and network icons
└── global/ # Global configuration files
Native Tokens
| Token | Network | Description |
|---|---|---|
| HEZ | Pezkuwi Relay Chain | Native token for fees and staking |
| PEZ | Asset Hub | Governance token |
| USDT | Asset Hub | Tether USD stablecoin |
Supported Networks
Pezkuwichain Ecosystem
- Pezkuwi Relay Chain - Main relay chain with HEZ token
- Asset Hub - System teyrchain for assets (PEZ, USDT, wHEZ)
- People Chain - Identity and people management
Polkadot Ecosystem
Full support for Polkadot and all major parachains.
Kusama Ecosystem
Full support for Kusama and all major parachains.
Usage
These configurations are fetched by Pezkuwi Wallet at runtime from GitHub raw URLs:
https://raw.githubusercontent.com/pezkuwichain/pezkuwi-wallet-utils/master/chains/{network}/chains.json
Signed config
signed/targets.json gives the sha256 of every JSON file the wallet may fetch, signed with the targets
key; signed/root.json names that key and the three root keys, two of which can replace it. The wallet
carries the first root and refuses a file whose hash the signed list does not give, so a change to any
served JSON file is re-signed in the same pull request:
python3 scripts/signed_config.py sign --key <targets seed>
Code Quality refuses a tree whose files do not match the signed list, and its weekly run fails a month before a signature expires.
Contributing
- Fork this repository
- Create your feature branch
- Commit your changes
- Push to the branch
- Create a Pull Request
Related Projects
License
Apache 2.0
Resources
- Website: https://pezkuwichain.io
- Documentation: https://docs.pezkuwichain.io
- Telegram: https://t.me/pezkuwichain
- Twitter: https://twitter.com/pezkuwichain
Based on Nova Utils - Extended with Pezkuwichain support
© Dijital Kurdistan Tech Institute 2026