Kurdistan Tech Ministry
a2a37dca32
- deny.toml: add all-features=true to [graph] — prevents krates 0.20+ panic on workspace crates that have std feature but don't enable it by default - deny.toml: allow pezkuwichain/serde.git in [sources] (our wasm32v1-none fork) - deny.toml: remove stale RUSTSEC ignores (2023-0071, 2024-0428, 2025-0055) - deny.toml: add new wasmtime/rand/webpki advisories to ignore list - ci: remove --exclude flag from cargo-deny jobs (flag removed in new versions) - ci: rewrite cargo-audit to use JSON + python summary (prevents 4MB log overflow) and add all current advisories to ignore set with documented rationale - ci: fix check-zepter to use --force (not --locked) so 1.82.1 actually installs - Cargo.toml: add default=[std] to bizinikiwi-test-runtime-transaction-pool (std crate that was missing default feature, confusing krates graph builder)
Bizinikiwi
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
- Bizinikiwi Primitives (
pezsp-*), Frame (frame-*) and the pallets (pallets-*), binaries (/bin) and all other utilities are licensed under Apache 2.0. - Bizinikiwi Client (/client/*/pezsc-*) is licensed under GPL v3.0 with a classpath linking exception.
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.