Checksum mismatch for light_client.zkey (stable alternate hash e5cb635f...)

[Dua-Alsoudi]

Summary

While downloading the light_client.zkey file from the official blob URL
https://dendrethstorage.blob.core.windows.net/light-client/light-client.zkey,
the file consistently produces a different BLAKE3 checksum from the one documented in DendrETH scripts.

Details

• Observed checksum:

e5cb635fd494414d599fb22fc132f8ff9ecbc811d7cfc2557b1d8af55165fdad

• Expected checksum (from project scripts / process-compose.yaml):

7bd1baf6e4aa1b3e7a6b0df7e93cbe43c8728ab245cd41e5e80d3b22f6e7d104

• File size: ~51.5 GB
• Tried from multiple tools / environments:
  curl, docker run alpine curl, and direct Azure blob access — same hash each time.

This suggests that the blob currently served under that URL may be an older circuit version (e.g. capella_94), or a CDN edge is caching an outdated file.

Steps to Reproduce

1. Run:

curl -L --fail -o light_client.zkey \
     https://dendrethstorage.blob.core.windows.net/light-client/light-client.zkey
b3sum light_client.zkey

2. Compare hash with expected.

Environment

• OS: Windows 11 + WSL2 (Ubuntu)
• Docker Desktop backend
• External disk used for data storage

Question

Could you confirm the current valid checksum for light_client.zkey
and whether the public blob link above points to the latest circuit build?

Thank you!