SSX360/matrixscroll: Matrix Scroll 0.11.0: protocol v2

Abstract

Matrix Scroll 0.11.0 introduces protocol v2 with mandatory pure, hedged ML-DSA-87 signatures, attached COSE_Sign1 and RFC 8785 canonical JSON. SHA-384 ledgers use RFC 9162 trees and authenticated checkpoint coverage. Python, Rust, Node WebCrypto and the bundled browser verifier share CONSISTENT / INDETERMINATE / INCONSISTENT verdicts. This is a breaking protocol baseline. Generate a fresh v2 identity, explicitly enroll it in your trust policy and start a new v2 ledger. Current interfaces accept v2 only. Preserve historical signatures and use the separately labeled legacy artifact for historical verification. Migration guide Protocol specification Research and source register Randomness diagnostics and limits Software keys use seed-based PKCS#8. Every signing path uses IdentityProvider and verifies its output. Unsupported providers and FIPS custody mode fail closed. MCP exports stay local unless hosted mode is explicit, and raw exports do not claim verification results. Install with python -m pip install "matrixscroll[mcp]==0.11.0" after the Trusted Publishing workflow confirms PyPI availability. The attached offline HTML verifier bundles its dependencies and requires no network. Check its attached SHA-256 file before use. Release source: 7b0d26d61b885686a5d0d0cdd7054882733927e3. Wheel and source archive were built on Linux with Python 3.12.14, build 1.6.1, hatchling 1.32.4 and SOURCE_DATE_EPOCH from that commit. Repeated clean builds produced identical bytes. The digest manifest records exact source and artifact hashes. The publishing workflow rebuilds and compares the artifacts before upload. The maintainer explicitly approved merging and finalization on October 5, 2026. PRs #74 and #77 used the maintainer override, with repository review settings retained. This approval is not an independent GitHub code-owner review. Historical releases and tags remain unchanged. Verification boundaries: a valid signature establishes consistency of supplied bytes, not signer authorization or trusted time. CNSA alignment applies to the ML-DSA-87 signature and SHA-384 ledger algorithm profile, as evidence mapping, not a certification claim. Optional sealed-pack encryption has a separate profile. Module validation, physical resistance, KMS/HSM custody, witnesses and hardware remain outside this release's assurance. Validation on this source: 759 installed-wheel tests and 78 subtests pass, with one expected Rust-wrapper skip in that job. All four verifier backends agree on 10,000 generated documents and 39 fixture/parser cases. The offline browser passes 25 cases with zero HTTP requests. Eight TLC configurations, Rust and JavaScript tests, strict docs, Vale and package validation pass. Some additional GitHub platform jobs remain queued during the October 5 Actions runner incident; the recorded local checks remain distinct from those pending runs.