[ Published evidence // Independently verified ]

ExactZK independent circuit-provenance reproduction

A cryptographically signed record that Maha Strategies independently reproduced the expected MNIST MLP verifying-key digests at one pinned ExactZK bundle revision.

Recorded 2026-09-01EZKL 23.0.5~7 GB observed memory
← Integration evidence index

Evidence

The ExactZK bundle was pinned at revision 54637f58522169deff89f03bfaa4bb765ff92eca. Maha rebuilt the MNIST MLP verifying key and obtained both expected digests.

Context

The reproduction used EZKL 23.0.5. The record preserves the bundle revision, digest algorithms, memory observation and explicit exclusions.

Authority

Maha Strategies signed the attestation with did:key:zQ3shMymYG2u2NQqbPH9xLLSzo2FT5iqDoyqUbvtX8nJ9FY9T using RFC 8785 canonicalization and an RFC 7797 detached ES256K JWS.

Receipt

The upstream maintainer independently reconstructed the canonical bytes, derived the public key from the did:key identifier and verified the signature before publishing the attestation.

Evidence links

Machine-readable · signed JSON

Maha attestation

RFC 8785 canonicalized payload with detached ES256K JWS proof.

Machine-readable · JSON

Maha integration record

Pinned revisions, verification methods, digests and non-claims.

Upstream · immutable commit

Published independent attestation

Commit a2bc90d0a33a548fbcae09bb1756a4fc31286f4a

Upstream · source bundle

ExactZK reproduction repository

Bundle revision 54637f58522169deff89f03bfaa4bb765ff92eca

Pinned digests

Verifying key · SHA-256
1ed847e127419bc1d7db2a22779f75284975bf1908b33a43486ca9070e4ef627
Verifying key · Keccak-256
dd03fb0c69e96cc02cbcc6bed8ef51665f934c01cddaf2a855bd1c7fce94675f
Signed attestation file · SHA-256
39ef9f94bec3adf3a85c955ca40381a48c7d20e75afa613a18e600e8bbb8d009
Canonical signed payload · SHA-256
978523dfd9d96b2d3a598d6f6db3389a0cb28b9a69d52171218f130b755af87f

Scope boundary

  • This attestation is limited to reproduction of the identified circuit-provenance verifying-key digests.
  • It does not validate the full escrow system or establish that the test SRS is suitable for production.
  • It is not a security audit, an application-logic correctness proof, a commercial endorsement or a certification.