fix: update outdated links (#905)

matter-labs · Feb 8, 2024 · 1a90563 · 1a90563
1 parent 27f5274
commit 1a90563
Show file tree

Hide file tree

Showing 6 changed files with 6 additions and 6 deletions.
diff --git a/docs/build/sdks/python/getting-started.md b/docs/build/sdks/python/getting-started.md
@@ -39,7 +39,7 @@ sdk = ZkSyncBuilder.build("https://sepolia.era.zksync.dev")
 
 ## Examples
 
-Full code for all examples is available [here](https://github.com/zksync-sdk/zksync2-examples/python). Examples are configured to interact with `zkSync`, and `Sepolia` test networks.
+Full code for all examples is available [here](https://github.com/zksync-sdk/zksync2-examples/tree/main/python). Examples are configured to interact with `zkSync`, and `Sepolia` test networks.
 
 ## Creating a wallet
 

diff --git a/docs/build/support/faq.md b/docs/build/support/faq.md
@@ -101,7 +101,7 @@ While there are a few, rarely used opcodes that we do not support, we have not f
 
 At a very high level, Account Abstraction allows us to make authorizations _programmable_, enabling a greater diversity of wallet and protocol design with use cases including:
 
-- The implementation of smart contract wallets that improve the user experience of private key storage and recovery (eg. [social recovery](https://vitalik.ca/general/2021/01/11/recovery.html), multisig).
+- The implementation of smart contract wallets that improve the user experience of private key storage and recovery (eg. [social recovery](https://vitalik.eth.limo/general/2021/01/11/recovery.html), multisig).
 - The ability to natively pay gas fees in tokens other than ETH.
 - The ability for accounts to change public and private keys.
 - The addition of non-cryptographic modifications, where users can require transactions to have expiry times, confirm slightly out-of-order, and more.

diff --git a/docs/build/tutorials/tooling-guides/subquery.md b/docs/build/tutorials/tooling-guides/subquery.md
@@ -238,4 +238,4 @@ You should now see the results displayed below in the GraphQL playground, and yo
 
 Congratulations! You have successfully set up a SubQuery project running locally, ready to handle GraphQL API requests pertaining to data transfers.
 
-To ensure your SubQuery project operates efficiently and to sidestep common pitfalls, delve into the [Project Optimization](https://doc.subquery.network/projectoptimisation.html) section. Happy querying!
+To ensure your SubQuery project operates efficiently and to sidestep common pitfalls, delve into the [Project Optimization](https://academy.subquery.network/build/optimisation.html) section. Happy querying!
diff --git a/docs/infra/component-breakdown.md b/docs/infra/component-breakdown.md
@@ -60,7 +60,7 @@ the root hashes for the latest available L1 batch do not match, the Reorg Detect
 responsible for the divergence. Subsequently, it rolls back the local state and restarts the node. Upon restart, the EN
 resumes normal operation.
 
-[finality]: https://docs.zksync.io/dev/developer-guides/finality.html
+[finality]: https://docs.zksync.io/zk-stack/concepts/finality.html
 
 ## Consistency Checker
 

diff --git a/docs/zk-stack/components/prover/overview.md b/docs/zk-stack/components/prover/overview.md
@@ -63,7 +63,7 @@ is described in more detail in
 
 The process of turning code into constraints is called arithmetization. Our arithmetization is based on a variation of
 “Plonk”. The details are abstracted away from the circuits, but if you’d like to learn more, read about Plonk in
-[Vitalik’s blog](https://vitalik.ca/general/2019/09/22/plonk.html) or the
+[Vitalik’s blog](https://vitalik.eth.limo/general/2019/09/22/plonk.html) or the
 [Plonky2 paper](https://github.com/mir-protocol/plonky2/blob/main/plonky2/plonky2.pdf).
 
 More details of our proving system can be found in the [Redshift Paper](https://eprint.iacr.org/2019/1400.pdf).
diff --git a/docs/zk-stack/concepts/hyperchains-hyperscaling.md b/docs/zk-stack/concepts/hyperchains-hyperscaling.md
@@ -63,7 +63,7 @@ Besides cross-hyperchain calls, it will be also possible to execute cross-hyperc
 
 ### Hyperchain User Experience
 
-As we aim to onboard billions of users to Web3, user experience has to be a priority. Users will have wallets on different chains, unified by cross-hyperchain wallet management. This is still a hot research topic, as seen in Vitalik's [post](https://vitalik.ca/general/2023/06/20/deeperdive.html). These solutions will be integrated into Account Abstractions, which are natively supported on ZK Stack powered chains.
+As we aim to onboard billions of users to Web3, user experience has to be a priority. Users will have wallets on different chains, unified by cross-hyperchain wallet management. This is still a hot research topic, as seen in Vitalik's [post](https://vitalik.eth.limo/general/2023/06/20/deeperdive.html). These solutions will be integrated into Account Abstractions, which are natively supported on ZK Stack powered chains.
 
 The users' wallets will show all of their assets, and relayers will handle bridging, burning, and minting assets to be used at the destination. Hyperchains will have unique identifiers that, when paired with ENS, will make recipient addresses look like email addresses. Of course, the default will be the use of traditional Ethereum addresses together with the Hyperchain identifiers.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -238,4 +238,4 @@ You should now see the results displayed below in the GraphQL playground, and yo

		Congratulations! You have successfully set up a SubQuery project running locally, ready to handle GraphQL API requests pertaining to data transfers.

		To ensure your SubQuery project operates efficiently and to sidestep common pitfalls, delve into the [Project Optimization](https://doc.subquery.network/projectoptimisation.html) section. Happy querying!
		To ensure your SubQuery project operates efficiently and to sidestep common pitfalls, delve into the [Project Optimization](https://academy.subquery.network/build/optimisation.html) section. Happy querying!