Files
pezkuwi-sdk/bizinikiwi
pezkuwichain 4c13406c00 fix: resolve pez-kitchensink-runtime compilation errors
Umbrella Crate Fixes:
- Add pezpallet-root-testing to umbrella (std, try-runtime, runtime-full)
- Add pezpallet-xcm-benchmarks to umbrella (std, runtime-benchmarks, runtime-full)
- Add re-exports in umbrella/src/lib.rs for both crates

getrandom WASM Fix:
- Move subxt crates from runtime-full to node feature
- Prevents getrandom dependency leak into WASM builds

Vendor Updates:
- Fix pezkuwi-subxt for web/wasm target compatibility
- Update pezkuwi-zombienet-sdk keystore imports

Documentation:
- Update WORKFLOW_PLAN.md with completed tasks
- Update REBRAND_PROGRESS.md with umbrella fixes
- Remove obsolete tracking files
2025-12-23 23:02:41 +03:00
..
2025-12-23 09:37:12 +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.