pezkuwichain
0dbe3a7032
- Regenerate EQUIVOCATION_PROOF_BLOB in pezpallet-babe benchmarking: the old blob contained stale header hashes that caused check_equivocation_proof to fail with assertion error - Exclude pezpallet_revive from quick-benchmarks via --exclude-pezpallets flag: revive benchmarks require PolkaVM toolchain (riscv64emac-unknown-none-polkavm) for fixture compilation which is not available in CI. This removes continue-on-error so real benchmark failures are now visible - Increase build-rustdoc timeout from 180 to 240 minutes for VPS runner
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.