docs: changing prover keys json structure (matter-labs#378)

Co-authored-by: hatemosphere <[email protected]>

.github/workflows/ci.yml

@@ -37,7 +37,7 @@ jobs:
               - 'prover/**'
               - '!prover/CHANGELOG.md'
               - '!prover/setup-data-cpu-keys.json'
-              - '!prover/setup-data-keys.json'
+              - '!prover/setup-data-gpu-keys.json'
               - 'docker/prover*/**'
               - '.github/workflows/build-prover-template.yml'
               - '.github/workflows/ci-prover-reusable.yml'

docs/advanced/prover_keys.md

@@ -29,11 +29,10 @@ SNARK based with KZG commitment. This results in slightly different contents of
 
 ## Keys
 
-> You can find links to buckets with latest keys
-> [here](https://github.com/matter-labs/zksync-era/blob/main/prover/setup-data-keys.json).
-
 ### Setup key (big, 14GB)
 
+> In the following [CPU](https://github.com/matter-labs/zksync-era/blob/main/prover/setup-data-cpu-keys.json) and [GPU](https://github.com/matter-labs/zksync-era/blob/main/prover/setup-data-gpu-keys.json) links, you'll find GCS buckets containing the latest keys.
+
 The primary key for a given circuit is called `setup key`. These keys can be substantial in size - approximately 14GB
 for our circuits. Due to their size, we don't store them directly on GitHub; instead, they need to be generated.
 

prover/setup-data-cpu-keys.json

@@ -1,10 +1,5 @@
-[
-  {
-    "26ee1fb":
-    {
-      "us": "gs://matterlabs-setup-data-us/26ee1fb/",
-      "europe": "gs://matterlabs-setup-data-europe/26ee1fb/",
-      "asia": "gs://matterlabs-setup-data-asia/26ee1fb/"
-    }
-  }
-]
+{
+  "us": "gs://matterlabs-setup-data-us/26ee1fb/",
+  "europe": "gs://matterlabs-setup-data-europe/26ee1fb/",
+  "asia": "gs://matterlabs-setup-data-asia/26ee1fb/"
+}

prover/setup-data-gpu-keys.json

@@ -0,0 +1,5 @@
+{
+  "us": "gs://matterlabs-setup-data-us/26ee1fb-gpu/",
+  "europe": "gs://matterlabs-setup-data-europe/26ee1fb-gpu/",
+  "asia": "gs://matterlabs-setup-data-asia/26ee1fb-gpu/"
+}