Devnet Rosetta Docker images crash with epoch ledger "Tarball hash mismatch"

### Preliminary Checks - [x] This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/MinaProtocol/mina/issues - [x] This issue is not a question, feature request, RFC, or anything other than a bug report. Please post those things in GitHub Discussions: https://github.com/MinaProtocol/mina/discussions ### Description All available Mina Rosetta devnet Docker images (`3.3.0-alpha1-6929a7e` on GCR and` 3.2.0-97ad487` on Docker Hub) crash on startup with a fatal "Tarball hash mismatch" error when verifying the staking epoch ledger downloaded from S3. The config embedded in the image expects `s3_data_hash = b028464a7b7cf45da089a82f71f4faaa26035f9d24ca82a0e14ae50d4fa37143` for the staking epoch ledger, but the tarball currently on S3 has hash `84a349f6dd12c76b694b283975885994bcfb9117c3f41fa941e0229da3ce2a33`. This means the devnet epoch has advanced past what any published image supports, and no newer image has been released with updated hashes. ``` {"level":"Error","message":"Verification failure: downloaded $path and expected SHA3-256 = $expected_hash but it had $computed_hash", "computed_hash":"84a349f6dd12c76b694b283975885994bcfb9117c3f41fa941e0229da3ce2a33", "expected_hash":"b028464a7b7cf45da089a82f71f4faaa26035f9d24ca82a0e14ae50d4fa37143", "path":"/tmp/s3_cache_dir/epoch_ledger_3e2c138e3e014dcb66f5dcfbfd42e1c8cbbac7aeb5bbf90ed62907b91075a9f5.tar.gz"} {"level":"Fatal","message":"Unhandled top-level exception: Tarball hash mismatch"} ``` ### Steps to Reproduce 1. Pull the latest devnet Rosetta image: ``` docker pull gcr.io/o1labs-192920/mina-rosetta:3.3.0-alpha1-6929a7e-noble-devnet ``` 2. Run the container: ``` docker run -it --rm --name rosetta-devnet \ --entrypoint=./docker-start.sh \ -p 8302:8302 -p 3085:3085 -p 3086:3086 -p 3087:3087 \ -e MINA_NETWORK=devnet \ -e PEER_LIST_URL=https://storage.googleapis.com/o1labs-gitops-infrastructure/devnet/seed-list-devnet.txt \ -e MINA_ARCHIVE_DUMP_URL=https://storage.googleapis.com/mina-archive-dumps \ -e MINA_GENESIS_LEDGER_URL=http://673156464838-mina-genesis-ledgers.s3-website-us-west-2.amazonaws.com/devnet/genesis_ledger.json \ -e BLOCKS_BUCKET=https://storage.googleapis.com/mina_network_block_data \ gcr.io/o1labs-192920/mina-rosetta:3.3.0-alpha1-6929a7e-noble-devnet ``` 3. Observe the daemon crash after PostgreSQL initialization and archive dump import complete. ### Expected Result The Mina daemon should boot successfully, sync to devnet, and expose the Rosetta API. ### Actual Result The daemon crashes with a fatal "Tarball hash mismatch" error during epoch ledger verification. The Rosetta API never becomes functional. ### Daemon version ``` Release: 3.3.0-alpha1 Git SHA-1: 6929a7ecd1b5cf977ceb674baa6e32764576c109 ``` Also reproduced with `3.2.0-97ad487` (Docker Hub) — same crash. ### How frequently do you see this issue? Always ### What is the impact of this issue on your ability to run a node? Blocker ### Status ```shell Unable to run `mina client status` — the daemon crashes before the RPC server starts. ``` ### Additional information - Host OS: Ubuntu 24.04 (noble) - The mainnet Rosetta image (`3.3.0-8c0c2e6-focal-mainnet` / `3.3.1-7b34378-focal-mainnet`) works fine — this issue is devnet-only. - The archive dump downloads and imports successfully — the crash occurs only when the daemon tries to verify the staking epoch ledger. - Announcement reference: https://github.com/MinaProtocol/mina/discussions/17812