# pezkuwi.rs - source
Source of the Rust file `docs/sdk/src/pezkuwi_sdk/pezkuwi.rs`.

#
pezkuwi_sdk_docs/pezkuwi_sdk/
pezkuwi.rs

    1//! # Pezkuwi
    2//!
    3//! Implementation of the Pezkuwi node/host in Rust.
    4//!
    5//! ## Learn More and Get Involved
    6//!
    7//! - [Pezkuwi Forum](https://forum.network.pezkuwichain.io/)
    8//! - [Pezkuwi Teyrchains](https://teyrchains.info/)
    9//! - [Pezkuwi (multi-chain) Explorer: Subscan](https://subscan.io/)
    10//! - Pezkuwi Fellowship
    11//!     - [Manifesto](https://github.com/pezkuwichain/pezkuwi-fellows/tree/main/manifesto/blob/main/manifesto.pdf)
    12//!     - [Runtimes](https://github.com/pezkuwichain/pezkuwi-fellows/tree/main/runtimes)
    13//!     - [RFCs](https://github.com/pezkuwichain/pezkuwi-fellows/tree/main/rfcs)
    14//! 	- [Dashboard](https://pezkuwi-fellows.github.io/dashboard/)
    15//! - [Pezkuwi Specs](http://spec.pezkuwi.network)
    16//! - [The Pezkuwi Teyrchain Host Implementers' Guide](https://docs.pezkuwichain.io/sdk/book/)
    17//! - [Pezkuwi papers](https://pezkuwichain.io/papers/)
    18//! - [JAM Graypaper](https://graypaper.com)
    19//!
    20//! ## Alternative Node Implementations 🌈
    21//!
    22//! - [Smoldot](https://docs.rs/crate/smoldot-light/latest). Pezkuwi light node/client.
    23//! - [KAGOME](https://github.com/qdrvm/kagome). C++ implementation of the Pezkuwi host.
    24//! - [Gossamer](https://github.com/ChainSafe/gossamer). Golang implementation of the Pezkuwi host.
    25//!
    26//! ## Platform
    27//!
    28//! In this section, we examine what platform Pezkuwi exactly provides to developers.
    29//!
    30//! ### Pezkuwi White Paper
    31//!
    32//! The original vision of Pezkuwi (everything in the whitepaper, which was eventually called
    33//! **Pezkuwi 1.0**) revolves around the following arguments:
    34//!
    35//! * Future is multi-chain, because we need different chains with different specialization to
    36//!   achieve widespread goals.
    37//! * In other words, no single chain is good enough to achieve all goals.
    38//! * A multi-chain future will inadvertently suffer from fragmentation of economic security.
    39//!   * This stake fragmentation will make communication over consensus system with varying security
    40//!     levels inherently unsafe.
    41//!
    42//! Pezkuwi's answer to the above is:
    43//!
    44//! > The chains of the future must have a way to share their economic security, whilst maintaining
    45//! > their execution and governance sovereignty. These chains are called "Teyrchains".
    46//!
    47//! * Shared Security: The idea of shared economic security sits at the core of Pezkuwi. Pezkuwi
    48//!   enables different teyrchains to pool their economic security from Pezkuwi (i.e. "*Relay
    49//!   Chain*").
    50//! * (heterogenous) Sharded Execution: Yet, each teyrchain is free to have its own execution logic
    51//!   (runtime), which also encompasses governance and sovereignty. Moreover, Pezkuwi ensures the
    52//!   correct execution of all teyrchains, without having all of its validators re-execute all
    53//!   teyrchain blocks. When seen from this perspective, Pezkuwi achieves the ability to verify
    54//!   the validity of the block execution of multiple teyrchains using the same set of validators as
    55//!   the Relay Chain. In practice, this means that the shards (teyrchains) share the same economic
    56//!   security as the Relay Chain.
    57//!   Learn about this process called [Approval Checking](https://pezkuwichain.io/blog/pezkuwi-v1-0-sharding-and-economic-security#approval-checking-and-finality).
    58//! * A framework to build blockchains: In order to materialize the ecosystem of teyrchains, an easy
    59//!   blockchain framework must exist. This is [Bizinikiwi](crate::pezkuwi_sdk::bizinikiwi),
    60//!   [FRAME](crate::pezkuwi_sdk::frame_runtime) and [Pezcumulus](crate::pezkuwi_sdk::pezcumulus).
    61//! * A communication language between blockchains: In order for these blockchains to communicate,
    62//!   they need a shared language. [XCM](crate::pezkuwi_sdk::xcm) is one such language, and the one
    63//!   that is most endorsed in the Pezkuwi ecosystem.
    64//!
    65//! > Note that the interoperability promised by Pezkuwi is unparalleled in that any two teyrchains
    66//! > connected to Pezkuwi have the same security and can have much better guarantees about the
    67//! > security of the recipient of any message.
    68//! > Bridges enable transaction and information flow between different consensus systems, crucial
    69//! > for Pezkuwi's multi-chain architecture. However, they can become the network's most
    70//! > vulnerable points. If a bridge's security measures are weaker than those of the connected
    71//! > blockchains, it poses a significant risk. Attackers might exploit these weaknesses to launch
    72//! > attacks such as theft or disruption of services.
    73//!
    74//! Pezkuwi delivers the above vision, alongside a flexible means for teyrchains to schedule
    75//! themselves with the Relay Chain. To achieve this, Pezkuwi has been developed with an
    76//! architecture similar to that of a computer. Pezkuwi Relay Chain has a number of "cores". Each
    77//! core is (in simple terms) capable of progressing 1 teyrchain at a time. For example, a teyrchain
    78//! can schedule itself on a single core for 5 relay chain blocks.
    79//!
    80//! Within the scope of Pezkuwi 1.x, two main scheduling ways have been considered:
    81//!
    82//! * Long term Teyrchains, obtained through locking a sum of HEZ in an auction system.
    83//! * On-demand Teyrchains, purchased through paying HEZ to the relay-chain whenever needed.
    84//!
    85//! ### The Future
    86//!
    87//! After delivering Pezkuwi 1.x, the future of Pezkuwi as a protocol and platform is in the hands
    88//! of the community and the fellowship. This is happening most notable through the RFC process.
    89//! Some of the RFCs that do alter Pezkuwi as a platform and have already passed are as follows:
    90//!
    91//! - RFC#1: [Agile-coretime](https://github.com/pezkuwichain/pezkuwi-fellows/RFCs/blob/main/text/0001-agile-coretime.md):
    92//!   Agile periodic-sale-based model for assigning Coretime on the Pezkuwi Ubiquitous Computer.
    93//! - RFC#5: [Coretime-interface](https://github.com/pezkuwichain/pezkuwi-fellows/RFCs/blob/main/text/0005-coretime-interface.md):
    94//!   Interface for manipulating the usage of cores on the Pezkuwi Ubiquitous Computer.
    95//!
    96//! Learn more about [Pezkuwi as a Computational Resource](https://wiki.network.pezkuwichain.io/docs/pezkuwi-direction#pezkuwi-as-a-computational-resource).