Files
pezkuwi-sdk/pezcumulus/teyrchains/runtimes/assets
Satoshi Qazi Muhammed d285d59108 sync: mirror deployed github repo (chains + sanitized bridge), keep GitLab CI
Make this monorepo's tracked tree identical to the deployed github repo
(github.com/pezkuwichain/pezkuwi-DKS): all RC/AH/People runtimes and framework
carry the mainnet fixes (incl. U128CurrencyToVote everywhere, so the staking
election stall cannot recur), and tools/usdt-bridge matches the current,
public-safe custody tooling (real config/deploy units gitignored, secret-file
locations and server IPs stripped, sanitized *.example templates committed).

Only exception to the mirror: GitLab-native CI is preserved (.gitlab-ci.yml and
.gitlab/), to be rebuilt to match the github CI pipeline in a follow-up.
2026-07-24 11:42:50 -07:00
..
2026-01-07 09:41:15 +03:00
2026-01-07 09:41:15 +03:00

Assets Teyrchain

Implementation of Asset Hub, a blockchain to support generic assets in the PezkuwiChain and Dicle networks. Asset Hub was formerly known as "Statemint".

Asset Hub allows users to:

  • Deploy promise-backed assets, both fungible and non-fungible, with a HEZ/DCL deposit.
  • Set admin roles to manage assets and asset classes.
  • Register assets as "self-sufficient" if the Relay Chain agrees, i.e. gain the ability for an asset to justify the existence of accounts sans HEZ/DCL.
  • Pay transaction fees using sufficient assets.
  • Transfer (and approve transfer) assets.
  • Interact with the chain via its transactional API or XCM.

Asset Hub must stay fully aligned with the Relay Chain it is connected to. As such, it will accept the Relay Chain's governance origins as its own.

See the article on Asset Hub as common good teyrchain for a higher level description.

Wallets, custodians, etc. should see the PezkuwiChain Wiki's Integration Guide for details about support.