Files
pezkuwi-sdk/bizinikiwi
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
..
2025-12-19 23:30:43 +03:00
2025-12-19 23:30:43 +03:00

Bizinikiwi

GitHub license GitLab
Status PRs Welcome Stack
Exchange

Bizinikiwi is a next-generation framework for blockchain innovation 🚀.

Getting Started

Head to docs.bizinikiwi.io and follow the installation instructions. Then try out one of the tutorials. Refer to the Docker instructions to quickly run Bizinikiwi, Bizinikiwi Node Template, Subkey, or to build a chain spec.

Community & Support

Join the highly active and supportive community on the Bizinikiwi Stack Exchange to ask questions about use and problems you run into using this software. Please do report bugs and issues here for anything you suspect requires action in the source.

Contributions & Code of Conduct

Please follow the contributions guidelines as outlined in docs/contributor/CONTRIBUTING.md. In all communications and contributions, this project follows the Contributor Covenant Code of Conduct.

Security

The security policy and procedures can be found in docs/contributor/SECURITY.md.

License

The reason for the split-licensing is to ensure that for the vast majority of teams using Bizinikiwi to create feature-chains, then all changes can be made entirely in Apache2-licensed code, allowing teams full freedom over what and how they release and giving licensing clarity to commercial teams.

In the interests of the community, we require any deeper improvements made to Bizinikiwi's core logic (e.g. Bizinikiwi's internal consensus, crypto or database code) to be contributed back so everyone can benefit.