Files
pezkuwi-sdk/bizinikiwi
pezkuwichain 233f6fcb9d fix(ci): remove all forklift usage and update runtime-interface UI test stderr
- Remove forklift cargo wrapper from build-only-wasm.sh (direct cause of
  build-linux-stable failures in container jobs)
- Add .env_remove("RUSTC_WRAPPER") to wasm-builder cargo subprocess to
  prevent inheriting forklift from Parity CI container images
- Remove forklift from cargo-check-runtimes action and cmd.py benchmark
  build command
- Update test_cmd.py expectations to match forklift removal
- Update no_feature_gated_method.stderr for rebrand: substrate_runtime →
  bizinikiwi_runtime, sp_runtime_interface_proc_macro →
  pezsp_runtime_interface_proc_macro, and expanded feature list
2026-03-01 07:58:42 +03: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.