Beta
Release scope and maturity
The documentation distinguishes current release-candidate behavior from previews and future design.
Status vocabulary
- Current: reviewed public policy or stable project fact.
- Beta: available or being validated; compatibility and behavior may change.
- Draft: proposal or documentation contract; do not depend on it as shipped behavior.
- Historical: retained for context and explicitly superseded.
Current v0.3 release-candidate boundary
- Mobazha Node and Mobazha Unified are release candidates for evaluation and testnet use.
- The default open-source Node enables BTC, BCH, and LTC payment methods, subject to effective runtime capabilities and seller configuration.
- Identifiers or adapters present in source do not enable a payment method or create a compatibility commitment.
- Stable signed binaries and reproducibility attestations remain pending final release approval.
- Clients must fail closed when a valid runtime-capability snapshot is unavailable.