fix: rename zk chains (#1073)

Author: zk-Lumi

docs/.vuepress/config.ts

@@ -37,7 +37,7 @@ export default defineUserConfig({
     ],
     [
       "meta",
-      { name: "description", content: "zkSync Docs bring you all information you need about our protocol, APIs, SDKs, ZK Stack, and hyperchains. Start with our guides and tutorials, or go deep into our architecture and protocol specification." },
+      { name: "description", content: "zkSync Docs bring you all information you need about our protocol, APIs, SDKs, ZK Stack, and ZK Chains. Start with our guides and tutorials, or go deep into our architecture and protocol specification." },
     ],
     ["meta", { name: "author", content: "https://matter-labs.io" }],
 
@@ -51,7 +51,7 @@ export default defineUserConfig({
       "meta",
       {
         name: "og:description",
-        content: "zkSync Docs bring you all information you need about our protocol, APIs, SDKs, ZK Stack, and hyperchains. Start with our guides and tutorials, or go deep into our architecture and protocol specification.",
+        content: "zkSync Docs bring you all information you need about our protocol, APIs, SDKs, ZK Stack, and ZK Chains. Start with our guides and tutorials, or go deep into our architecture and protocol specification.",
       },
     ],
     ["meta", { name: "twitter:card", content: "summary" }],
@@ -60,7 +60,7 @@ export default defineUserConfig({
       "meta",
       {
         name: "twitter:description",
-        content: "zkSync Docs bring you all information you need about our protocol, APIs, SDKs, ZK Stack, and hyperchains. Start with our guides and tutorials, or go deep into our architecture and protocol specification.",
+        content: "zkSync Docs bring you all information you need about our protocol, APIs, SDKs, ZK Stack, and ZK Chains. Start with our guides and tutorials, or go deep into our architecture and protocol specification.",
       },
     ],
     ["meta", { name: "twitter:image", content: "https://docs.zksync.io/share_image.png" }],

docs/.vuepress/public/images/landing/run-a-hyperchain.png

@@ -611,8 +611,8 @@ export const enSidebar = sidebar({
           link: "/zk-stack/concepts/system-upgrades.md"
         },
         {
-          text: "Hyperchains / Hyperscaling",
-          link: "/zk-stack/concepts/hyperchains-hyperscaling.md"
+          text: "ZK Chains",
+          link: "/zk-stack/concepts/zk-chains.md"
         },
         {
           text: "Data Availability",
@@ -945,20 +945,20 @@ export const enSidebar = sidebar({
       ],
     },
     {
-      text: "Running a Hyperchain",
+      text: "Running a ZK Chain",
       collapsible: true,
       children: [
         {
           text: "Locally",
-          link: "/zk-stack/running-a-hyperchain/locally.html",
+          link: "/zk-stack/running-a-zk-chain/locally.html",
         },
         {
           text: "In Production",
-          link: "/zk-stack/running-a-hyperchain/production.md"
+          link: "/zk-stack/running-a-zk-chain/production.md"
         },
         {
           text: "Rollup as a Service",
-          link: "/zk-stack/running-a-hyperchain/raas.html",
+          link: "/zk-stack/running-a-zk-chain/raas.html",
         },
       ]
     },

docs/.vuepress/public/images/landing/run-a-zk-chain.png

@@ -30,17 +30,17 @@ contributors: false
       </div>
     </RouterLink>
     <RouterLink to="/zk-stack" class="card">
-      <img src="/images/landing/hyperchain.png" alt="zkStack">
+      <img src="/images/landing/zk-chain.png" alt="ZK Stack">
       <div class="content">
         <h3>ZK Stack</h3>
-        <p>Understand the protocol powering zkSync hyperchains, including zkSync Era.</p>
+        <p>Understand the protocol powering zkSync ZK Chains, including zkSync Era.</p>
       </div>
     </RouterLink>
     <RouterLink to="/infra" class="card">
       <img src="/images/landing/run-a-node.png" alt="run a node">
       <div class="content">
         <h3>Run a Node</h3>
-        <p>All the information you need to run a node for zkSync Era or your hyperchain.</p>
+        <p>All the information you need to run a node for zkSync Era or your ZK Chain.</p>
       </div>
     </RouterLink>
   </div>

docs/.vuepress/public/images/landing/hyperchain.png renamed to docs/.vuepress/public/images/landing/zk-chain.png

@@ -51,8 +51,8 @@ Each zkEVM bytecode must adhere to the following format:
 - Its length must be divisible by 32.
 - Its length in words (32-byte chunks) should be odd. In other words, `bytecodeLength % 64 == 32`.
 - There is a VM limit, the bytecode can not be more than `2^16` 32-byte words, i.e. `2^21` bytes.
-- The bootloader has a memory limit for supplying pubdata of 450999 bytes, therefore limiting the contract size to it as well. This limit is valid for Validium hyperchains, that don’t have to publish the bytecode to the base layer.
-- For rollups that must publish the deployed bytecode to the base layer (e.g. Ethereum), there is an additional pubdata limit, which is normally smaller. By default, for each batch, this limit is set to 100000 bytes for hyperchains using calldata DA, or 120000\*number_of_blobs, for hyperchains using EIP-4844 blobs.
+- The bootloader has a memory limit for supplying pubdata of 450999 bytes, therefore limiting the contract size to it as well. This limit is valid for Validium ZK Chains, that don’t have to publish the bytecode to the base layer.
+- For rollups that must publish the deployed bytecode to the base layer (e.g. Ethereum), there is an additional pubdata limit, which is normally smaller. By default, for each batch, this limit is set to 100000 bytes for ZK Chains using calldata DA, or 120000\*number_of_blobs, for ZK Chains using EIP-4844 blobs.
 
 The 32-byte hash of the bytecode of a zkSync contract is calculated in the following way:
 

docs/.vuepress/sidebar/en.ts

@@ -397,7 +397,7 @@ All linking happens at compile-time. Deploy-time linking is not supported.
 ## Precompiles
 
 Some EVM cryptographic precompiles (notably pairings and RSA) aren't currently available. However, pairing is
-prioritized to allow deployment of both Hyperchains and protocols like Aztec/Dark Forest without modifications.
+prioritized to allow deployment of both ZK Chains and protocols like Aztec/Dark Forest without modifications.
 
 Ethereum cryptographic primitives like `ecrecover`, `keccak256`, `sha256`, `ecadd` and `ecmul` are supported as precompiles.
 No actions are required from your side as all the calls to the precompiles are done by the compilers under the hood.

docs/README.md

@@ -23,7 +23,7 @@ zkSync Era is a gigantic leap forward in Layer 2 technologies. It is a long-awai
 - **Future Proof** - Ecosystem projects that adopt zkSync Era now will enjoy all future improvements without the need to change their code, in particular coming from:
   - The prover technology: hardware acceleration and [new proof systems](https://zksync.mirror.xyz/HJ2Pj45EJkRdt5Pau-ZXwkV2ctPx8qFL19STM5jdYhc).
   - The compiler: integration of LLVM-enabled modern programming languages. [Learn more about our compiler toolchain](../../zk-stack/components/compiler/toolchain/overview.md).
-  - Other innovations like [Hyperchains, Hyperbridges and ZK Stack](../../zk-stack/concepts/hyperchains-hyperscaling.md).
+  - Other innovations like [ZK Chains, Hyperbridges and ZK Stack](../../zk-stack/concepts/zk-chains.md).
 
 ## What is the zkEVM?
 
@@ -85,7 +85,7 @@ Almost every smart contract written for EVM will be supported by zkSync Era and
 You can find more information about the [differences between Ethereum and zkSync Era in this section of the docs](../../build/developer-reference/differences-with-ethereum.md).
 :::
 
-There are a few other distinctions, for example, gas metering will be different (as is the case for other L2s as well). Some EVM’s cryptographic precompiles (notably pairings and RSA) won’t be available in the very first release but will be implemented soon after the launch, with pairing being a priority to allow both Hyperchains and protocols like Aztec/Dark Forest to be deployed without modifications too.
+There are a few other distinctions, for example, gas metering will be different (as is the case for other L2s as well). Some EVM’s cryptographic precompiles (notably pairings and RSA) won’t be available in the very first release but will be implemented soon after the launch, with pairing being a priority to allow both ZK Chains and protocols like Aztec/Dark Forest to be deployed without modifications too.
 
 ## Security expectations
 
@@ -131,7 +131,7 @@ Optimistic rollups suffer from the following key downsides:
   In contrast, zkSync Era is based on zero-knowledge proofs which have important characteristics that optimistic methods do not - they can hyperscale.
 
 ::: tip Hyperscalability
-Read more about [Hyperscalability and ZK Stack here](../../zk-stack/concepts/hyperchains-hyperscaling.md).
+Read more about [Hyperscalability and ZK Stack here](../../zk-stack/concepts/zk-chains.md).
 :::
 
 ## Which Wallets are supported?