How should the system run?
Runtime, peer communication, consensus, storage, cryptography, coordination, and deterministic testing.
FOUNDATION / COMMONWARE
The low-level primitives beneath Nunchi SDK.
Commonware is a collection of replaceable Rust primitives for specialized blockchain systems. Nunchi uses that foundation to organize finance-specific state, modules, and examples.
Role in the stack
Commonware deliberately avoids a fixed block format, state layout, mempool policy, execution rule, or security assumption. Teams select the primitives that fit the application.
How should the financial product compose?
Assets, authority, data, market logic, finance-oriented state, application scaffolding, and examples.
Primitive index
Commonware's website acts as an index into crate-level Rust documentation. These six primitives are the clearest starting points for understanding the Nunchi foundation.
01↗02↗03↗04↗05↗06↗
Open the complete Commonware index commonware-actorSafely coordinate concurrent components.
commonware-runtimeExecute asynchronous tasks in production or deterministic simulation.
commonware-p2pCommunicate with authenticated peers over encrypted connections.
commonware-consensusOrder opaque messages in a Byzantine environment.
commonware-storagePersist and retrieve data from an abstract store.
commonware-glueUse default constructions that span multiple primitives.
Runtime and testing
Commonware Runtime provides a production-focused Tokio environment and a deterministic environment for tests and simulations. Both expose a common set of runtime responsibilities through traits.
| Environment | Purpose | Useful for |
|---|---|---|
| runtime::tokio | Production-focused asynchronous execution. | Network, storage, clock, metrics, and task execution. |
| runtime::deterministic | Repeatable task scheduling from a fixed seed. | Simulating network conditions, faults, and concurrent behavior. |
WHY IT MATTERS
Financial infrastructure needs reproducible failure testing.
Deterministic simulation makes complex concurrent interactions repeatable, which helps teams inspect faults and validate system behavior.
Versioning and stability
Commonware uses calendar versions such as 2026.7.0 so compatible crate releases are easy to identify. Maturity is tracked separately for each primitive.
ALPHA
Breaking changes expected. Migration support is undefined.
BETA
Wire and storage formats are stable with migration paths.
GAMMA
The API is stable and extensively tested.
DELTA
The primitive is battle-tested and bug-bounty eligible.
EPSILON
The feature set is frozen to fixes and performance work.
RELEASE CHECK
Confirm the exact primitive set before deployment.
A shared calendar version signals compatibility across the library. Each selected primitive still carries its own stability level. Use the Nunchi lockfile and Commonware crate documentation together.
When to use each reference
Use Commonware docs for
- Runtime traits and execution environments
- P2P and consensus primitive APIs
- Storage structures and persistence behavior
- Cryptographic constructions and maturity levels
Use Nunchi docs for
- Finance-specific module responsibilities
- Application composition and examples
- Workflow and architecture planning
- The boundary between modules and product logic