Commonware primary sources

Reviewed: 2026-05-14 UTC

Core site / library surface

https://commonware.xyz/
- Best concise index of what Commonware actually ships.
- Used to confirm the primitive families: actor, broadcast, codec, coding, collector, conformance, consensus, cryptography, deployer, invariants, math, p2p, parallel, resolver, runtime, storage, and stream.
- Also useful because it exposes the example surface: Alto, bridge, chat, estimator, flood, log, reshare, and sync.

https://github.com/commonwarexyz/monorepo
- Best single source for the project’s packaging, stability taxonomy, and production-vs-example distinction.
- Used to confirm the ALPHA/BETA/GAMMA/DELTA/EPSILON model, transitive stability expectations, compiler-flag enforcement, and the fact that examples are intentionally ALPHA while primitives can graduate.
- Also helpful because the README shows the project as one coordinated library rather than scattered crates with separate maturity claims.

https://commonware.xyz/blogs/commonware-the-anti-framework
- Best source for the project’s core thesis.
- Used to confirm that Commonware explicitly rejects one-size-fits-all blockchain frameworks and instead presents a pick-and-choose primitive collection with no hardcoded block format, state layout, finality definition, mempool policy, execution rules, or fee metering.
- Also used to confirm that consensus::simplex is presented as minimal BFT agreement over opaque blobs with externalized broadcast, state sync, slashing, and reward logic.

https://commonware.xyz/blogs/is-it-ready-yet
- Best source for how Commonware thinks about production readiness.
- Used to confirm claims of 17 primitives, 50+ primitive dialects, 93% repository test coverage, 1500 daily benchmarks, BETA-level long-term-support commitments, calendar versioning, and compiler-enforced minimum stability selection.
- Important because it turns “maturity” into a first-class mechanism instead of a marketing adjective.

https://commonware.xyz/blogs/threshold-simplex
- Best source for Commonware’s interoperability-facing consensus dialect.
- Used to confirm that consensus::threshold_simplex embeds BLS12-381 threshold cryptography, emits succinct finalized-view certificates, supports VRF-based leader election/execution randomness, and is explicitly positioned as a route toward many-to-many consensus-secured interoperability between independent blockchains.
- Also useful because it shows Commonware as more than a generic toolkit: it packages concrete blockchain constructions developers can deploy or adapt.

https://commonware.xyz/blogs/minimmit
- Best source for Commonware’s newer fast-path consensus direction.
- Used to confirm that Minimmit is framed as a propose-and-vote construction optimized for block time, with ~20% Byzantine tolerance, 40% quorum advancement, 80% quorum finalization, and target latencies around 130ms block time / 250ms finality in Alto-like settings.
- Important mainly as evidence that Commonware spans both reusable production-minded primitives and more experimental consensus design work in the same ecosystem.

Commonware is worth cataloging separately because it sits below ordinary chain or rollup brands and exposes the underlying control surfaces for specialized blockchain construction.
The most reusable analytical split is between primitive composition, example systems, and maturity enforcement. Many projects talk about modularity; Commonware makes the module boundaries concrete at the library level.
The compiler-enforced stability tiers are one of the strongest distinguishing mechanisms in the source set and should be carried into future comparisons with appchain SDKs, consensus libraries, and cryptography middleware.
Threshold-simplex makes Commonware especially useful as a comparison point for interoperability and certificate-based bridge designs, while Minimmit and Alto make it useful for low-latency consensus comparisons.