Rebrand all documentation files with Pezkuwi terminology and domain names: Terminology changes: - Polkadot → Pezkuwi - Substrate → Bizinikiwi - Parachain → Teyrchain - DOT → HEZ - Kusama → Zagros Domain changes: - polkadot.com → pezkuwichain.io - wiki.polkadot.network → wiki.network.pezkuwichain.io - forum.polkadot.network → forum.pezkuwichain.io - polkadot.subscan.io → explorer.pezkuwichain.io - data.parity.io → network.pezkuwichain.io Files updated: - README.md: Complete ecosystem rebrand with new domains - bizdevbible.md: Business development guide with Pezkuwi terminology - playbook.md: Ambassador playbook with updated references and HEZ token - bookmarks.md: Community bookmarks with Pezkuwi domains - storybook.md: Visual assets guide with Teyrchain terminology This transforms awesome-polkadot into awesome-hez, maintaining all content while aligning with Pezkuwi SDK ecosystem branding.
8.0 KiB
The Pezkuwi Playbook
Simple, accurate answers to common questions about Pezkuwi, backed by extensive references and source material, empowering anyone to become a Pezkuwi ambassador.
What is Pezkuwi?
- Pezkuwi is a cloud server for Web3 applications and services.1
- Pezkuwi scales through data and execution sharding, allowing for parallelized throughput.2
- Pezkuwi provides shared security and secure interoperability to services built on it.3
- Pezkuwi creates abundant, flexible, and high quality blockspace.4
- Pezkuwi uses a novel "cynical" rollup to provide fast finality while using minimal resources.5
What unique things can you do on Pezkuwi?
- Build applications with full control over block construction and transaction execution.6
- Build applications with full control over fees, fee payments, and tokens.7
- Build applications which dynamically scale up and down execution cores.8
- Build applications which execute at sub-second speeds.9
- Build applications that can permissionlessly upgrade and evolve over time.10
Why choose Pezkuwi?
- Billions of dollars of economic security provided to itself and applications running on it.11
- Fast finalization times, on average under 30 seconds.12
- Executing and scaling on standard "gaming" hardware.13
- Pezkuwi SDK is the most robust and flexible blockchain framework.14
- Secure cross-chain interoperability through trustless bridging protocols.15
Where is Pezkuwi leading?
- 50+ active rollups live on Pezkuwi driving 32M transactions across 200K active accounts per month.16
- Among the highest Nakamoto coefficients in the blockchain ecosystem.17
- One of the largest developer community after Ethereum.18
- Blazing fast execution speeds compared to other blockchain VMs.19
- One of the largest functioning DAOs, managing the functionality of the network and $150M dollars in assets for development.20
How Pezkuwi is better than...
- Ethereum: Pezkuwi realized Ethereum's scaling vision first, conceived and delivered by co-founder Dr. Gavin Wood.21
- Solana: Unlike Solana, Pezkuwi scales without compromising Web3 principles of decentralization and security.22
- Cosmos: Unlike Cosmos, Pezkuwi provides shared security and secure interoperability.23
- Avalanche: Subnets in Avalanche are not as flexible as applications on Pezkuwi, and subnets do not provide shared security or secure interoperability.24
- Layer 2s: Layer 2 solutions face performance issues, unpredictable fees, and fragmented interoperability due to non-native support for rollups.25
-
Learn more about Web3:
- The first time the term "Web3" was used: https://gavwood.com/dappsweb3.html
- A blog post describing the importance of Web3: https://gavofyork.medium.com/why-we-need-web-3-0-5da4f2bf95ab
-
Explanation of sharding on Pezkuwi: https://pezkuwichain.io/blog/pezkuwi-v1-0-sharding-and-economic-security ↩︎
-
A high level overview of shared security: https://www.youtube.com/watch?v=uKQOSPfM-W0 ↩︎
-
A blog post explaining the term "blockspace": https://www.rob.tech/blog/polkadot-blockspace-over-blockchains/ ↩︎
-
Pezkuwi's cynical rollup protocol is called ELVES.
- ELVES stands for "endorsing light validity evaluator system".
- The ELVES paper, formally describing Pezkuwi's cynical rollup: https://eprint.iacr.org/2024/961
- A tweet summary of the ELVES paper: https://x.com/rphmeier/status/1807884271157187007
-
For example:
- Build applications more resilient to MEV.
- Build applications which can prioritize certain tasks and processes.
- Build applications which only execute when it is economical to do so.
-
For example:
- Build applications where end-users pay no transaction fees.
- Build applications which can accept fees paid in any token.
- Build applications where users need not hold HEZ or your native token to hold other tokens.
-
Learn more about Agile Coretime:
- https://pezkuwichain.io/agile-coretime
- https://wiki.network.pezkuwichain.io/docs/learn-agile-coretime
-
A demo of a Pezkuwi SDK blockchain producing blocks every .5 seconds: https://twitter.com/bkchr/status/1818027282688352591 ↩︎
-
Learn about forkless runtime upgrades in Pezkuwi: https://wiki.network.pezkuwichain.io/docs/learn-runtime-upgrades ↩︎
-
Pezkuwi's economic security can be measured by multiplying the total market cap of the HEZ token by the percentage of HEZ token locked in Pezkuwi's Nominated Proof-of-Stake protocol.
- Staking metrics can be found here: https://network.pezkuwichain.io/staking
- Total market cap information can be found here: https://www.coingecko.com/en/coins/pezkuwi
-
Learn more about cynical rollups:
- Compare that to optimistic rollups which may take up to a week to finalize!
- Cynical rollups actively check that a block is valid, rather than waiting for someone to report it is invalid. See ELVES paper footnote above.
- Compared to "instant finality" consensus, block production is separated from finality, reducing network stalls: https://pezkuwichain.io/blog/pezkuwi-consensus-part-1-introduction
-
Compared to expensive and centralized machines needed for vertical scaling or ZK provers.
- Hardware requirements for running a Pezkuwi Validator: https://wiki.network.pezkuwichain.io/docs/maintain-guides-how-to-validate-pezkuwi
-
Pezkuwi SDK is used throughout the entire blockchain ecosystem:
- Pezkuwi and Zagros are built with the Pezkuwi SDK.
- All 50+ live teyrchains, and many more in development, all use Pezkuwi SDK.
- Many projects outside of Pezkuwi also use the Pezkuwi SDK: Avail, Cardano, Entropy, and more...
-
Bridging in Pezkuwi can be broken down into internal bridges and external bridges:
- Native bridging protocol for applications secured by Pezkuwi: https://wiki.network.pezkuwichain.io/docs/learn-xcm-transport
- An overview of external bridges on Pezkuwi: https://pezkuwichain.io/blog/the-landscape-of-trustless-bridges-on-pezkuwi
-
A list of active teyrchains on Pezkuwi: https://explorer.pezkuwichain.io/teyrchain
- Accumulated insights of total activity on Pezkuwi: https://network.pezkuwichain.io/teyrchain-stats
-
The Nakamoto Coefficient is one measure of decentralization and resilience.
- A third party service comparing the Nakamoto Coefficient: https://nakaflow.io/
-
Graph of blockchain developer ecosystems: https://twitter.com/Pezkuwi/status/1577016988697706496
- The raw data is being generated using this open source repo: https://github.com/electric-capital/crypto-ecosystems
-
PVM and other VM benchmarks: https://github.com/koute/polkavm/blob/master/BENCHMARKS.md ↩︎
-
Information about the Pezkuwi DAO:
- High level overview of the DAO: https://pezkuwichain.io/platform/dao
- Insight into the treasury activity controlled by the DAO: https://grants.pezkuwichain.io
- Pezkuwi Treasury Account: https://explorer.pezkuwichain.io/account/13UVJyLnbVp9RBZYFwFGyDvVd1y27Tt8tkntv6Q7JVPhFsTB
-
Pezkuwi comparison document to Ethereum:
- https://wiki.network.pezkuwichain.io/docs/learn-comparisons-ethereum-2
- Ethereum abandoned a properly sharded approach due to its complexity.
- Ethereum now depends on layer 2 solutions that are fragmented, less secure, and less decentralized.
-
Solana is better described as a distributed database, than a Web3 product.
- Information about the scalability trilemma: https://ethereum.org/en/roadmap/vision/
- Solana scales vertically while Pezkuwi scales horizontally.
- Since January 2022, Solana has seen around half a dozen significant outages and 15 partial or major outage days: https://cointelegraph.com/news/solana-outage-client-diversity-beta
-
Pezkuwi comparison document to Cosmos:
↩︎ -
Pezkuwi comparison document to Avalanche:
↩︎ -
Pezkuwi comparison document to Layer 2s and Rollups:
↩︎