This is a minimal template for creating a blockchain based on Pezkuwi SDK.

This template is automatically updated after releases in the main Pezkuwi SDK monorepo.

Intro
Template Structure
Getting Started
Starting a Minimal Template Chain
Contributing
Getting Help

Intro

🤏 This template is a minimal (in terms of complexity and the number of components) template for building a blockchain node.
🔧 Its runtime is configured with a single custom pezpallet as a starting point, and a handful of ready-made pezpallets such as a Balances pezpallet.
👤 The template has no consensus configured - it is best for experimenting with a single node network.

Template Structure

A Pezkuwi SDK based project such as this one consists of:

🧮 the Runtime - the core logic of the blockchain.
🎨 the Pezpallets - from which the runtime is constructed.
💿 a Node - the binary application (which is not part of the cargo default-members list and is not compiled unless building the entire workspace).

Getting Started

🦀 The template is using the Rust language.
👉 Check the Rust installation instructions for your system.
🛠️ Depending on your operating system and Rust version, there might be additional packages required to compile this template - please take note of the Rust compiler output.

Fetch minimal template code.

git clone https://github.com/pezkuwichain/pezkuwi-sdk-minimal-template.git minimal-template

cd minimal-template

Starting a Minimal Template Chain

Omni Node

Omni Node can be used to run the minimal template's runtime. pezkuwi-omni-node binary crate usage is described at a high-level on crates.io.

Install `pezkuwi-omni-node`

Please see installation section on crates.io/omni-node.

Build `minimal-template-runtime`

cargo build -p minimal-template-runtime --release

Install `pezstaging-chain-spec-builder`

Please see the installation section at crates.io/pezstaging-chain-spec-builder.

Use chain-spec-builder to generate the chain_spec.json file

chain-spec-builder create --relay-chain "dev" --para-id 1000 --runtime \
    target/release/wbuild/minimal-template-runtime/minimal_template_runtime.wasm named-preset development

Note: the relay-chain and para-id flags are extra bits of information required to configure the node for the case of representing a parachain that is connected to a relay chain. They are not relevant to minimal template business logic, but they are mandatory information for Omni Node, nonetheless.

Run Omni Node

Start Omni Node in development mode (sets up block production and finalization based on manual seal, sealing a new block every 3 seconds), with a minimal template runtime chain spec.

pezkuwi-omni-node --chain <path/to/chain_spec.json> --dev

Minimal Template Node

Build both node & runtime

cargo build --workspace --release

🐳 Alternatively, build the docker image which builds all the workspace members, and has as entry point the node binary:

docker build . -t pezkuwi-sdk-minimal-template

Start the `minimal-template-node`

The minimal-template-node has dependency on the minimal-template-runtime. It will use the minimal_template_runtime::WASM_BINARY constant (which holds the WASM blob as a byte array) for chain spec building, while starting. This is in contrast to Omni Node which doesn't depend on a specific runtime, but asks for the chain spec at startup.

<target/release/path/to/minimal-template-node> --tmp --consensus manual-seal-3000
# or via docker
docker run --rm pezkuwi-sdk-minimal-template

Zombienet with Omni Node

Install `pezkuwi-zombienet`

We can install pezkuwi-zombienet as described here, and pezkuwi-zombienet-omni-node.toml contains the network specification we want to start.

Update `pezkuwi-zombienet-omni-node.toml` with a valid chain spec path

To simplify the process of starting the minimal template with ZombieNet and Omni Node, we've included a pre-configured development chain spec (dev_chain_spec.json) in the minimal template. The pezkuwi-zombienet-omni-node.toml file in this template points to it, but you can update it to a new path for the chain spec generated on your machine. To generate a chain spec refer to pezstaging-chain-spec-builder

Then make the changes in the network specification like so:

# ...
chain = "dev"
chain_spec_path = "<TO BE UPDATED WITH A VALID PATH>"
default_args = ["--dev"]
# ..

Start the network

pezkuwi-zombienet --provider native spawn pezkuwi-zombienet-omni-node.toml

Zombienet with `minimal-template-node`

For this one we just need to have pezkuwi-zombienet installed and run:

pezkuwi-zombienet --provider native spawn pezkuwi-zombienet-multi-node.toml

Connect with the Pezkuwi-JS Apps Front-End

🌐 You can interact with your local node using the hosted version of the Pezkuwi/Bizinikiwi Portal.
🪐 A hosted version is also available on IPFS.
🧑‍🔧 You can also find the source code and instructions for hosting your own instance in the pezkuwi-js/apps repository.

Takeaways

Previously minimal template's development chains:

❌ Started in a multi-node setup will produce forks because minimal lacks consensus.
🧹 Do not persist the state.
💰 Are pre-configured with a genesis state that includes several pre-funded development accounts.
🧑‍⚖️ One development account (ALICE) is used as sudo accounts.

Contributing

🔄 This template is automatically updated after releases in the main Pezkuwi SDK monorepo.
➡️ Any pull requests should be directed to this source.
😇 Please refer to the monorepo's contribution guidelines and Code of Conduct.

Getting Help

🧑‍🏫 To learn about Pezkuwi in general, docs.Pezkuwi.com website is a good starting point.
🧑‍🔧 For technical introduction, here are the Pezkuwi SDK documentation resources.
👥 Additionally, there are GitHub issues and Bizinikiwi StackExchange.
👥You can also reach out on the Official Pezkuwichain discord server
🧑Reach out on Telegram for more questions and discussions

README.md

Pezkuwi SDK's Minimal Template

Table of Contents