Files
pezkuwi-sdk/bizinikiwi
pezkuwichain 25477b2bb9 fix: doc test compilation errors with documented ignores
Changes:
- pezframe/src/lib.rs: Fix import pezframe, add ignore with documentation
  explaining pallet macro context requirements
- pezframe-election-provider-solution-type: Add documented ignores for
  two doc tests due to circular dependency (proc-macro cannot depend on
  pezframe-support). Tests exist in pezframe-election-provider-support/src/tests.rs
- pezframe-support/Cargo.toml: Add pezsp-timestamp dev-dependency for
  inherent doc test compilation
- pezframe-support-procedural: Add documented ignore for authorize doc test
  due to circular dependency (proc-macro cannot depend on pezframe crates)
- pezkuwi-subxt: Add documented ignore for substitute_type generic pattern
  example. Bundled metadata is from Polkadot (sp_runtime paths) but SDK
  uses pezsp_runtime. Proper fix requires generating pezkuwichain metadata.

All ignores include detailed technical documentation explaining:
1. Why the test cannot compile (circular deps or metadata mismatch)
2. Where equivalent functionality is tested
3. What users should do when using the documented pattern
2026-01-25 19:21:47 +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.