Skip to content

File and image checksums

  • for Docker images, docker images --digests will show sha256 checksums that can be used to verify their authenticity
  • for other files, use sha256sum
File / Image SHA256 Checksum
ghcr.io/clearmatics/eth-keys-generator:v1.0.1 4734002caa9ea158db1b4db2082c0995a1e6f47c8a2fcbdc959de32db32a0df4
ghcr.io/clearmatics/autonity:v0.7.1 e368e2d7938183478570aae79de7a7ffbd1b86ef2d8c2319f670da758a168caf
nodejsconsole-linux-amd64-0.7.1.tar.gz ab1cf33d07f47f298d9a565f08f379788ffacf492a1be3c5faaf7e41e5b6323c
ghcr.io/clearmatics/services-testnet-agc:v0.7.1-bakerloo06 83cbca39de28ab73c7df396a5e33df2b6cab773b38c587934d2bc9ebd1a1716a
ghcr.io/clearmatics/zeth:0.5.0-prover 794e77317e1ab72b368cf2d9c892984a9a1336e949455838ed5300798922efcc
genesis.json 48618efac312fcc833a98aa06477c7518a69f078aa1565d9ebc1e1d5bf655b54

Zeth recover_keypair script

See "Configure and start the prover server" in the Zeth protocol documentation.

The script should return 80be1a34bd4e7c03adb7de8e5e9d3a5ee81b062e as the keypair hash digest.

Clearmatics RPC endpoint certificate

  • for crt certificate files, use openssl x509 -in rpc3.bakerloo.autonity.network.crt -noout -fingerprint

Clearmatics-signed certificates:

Certificate SHA1 fingerprint
rpc1.bakerloo.autonity.network cert E8:C1:BB:85:38:16:B7:9C:B8:F6:88:E5:D8:44:92:62:B3:B7:C2:81
rpc3.bakerloo.autonity.network cert 0F:D1:4B:68:E0:42:9F:0F:29:6D:F6:A5:E5:48:06:0A:B4:50:F4:BA

Help

If you need help, you can: