docs: Update URL's from solanalabs.com to anza.xyz (#7505)

CHANGELOG.md

@@ -5,7 +5,7 @@ All notable changes to this project will be documented in this file.
 Please follow the [guidance](#adding-to-this-changelog) at the bottom of this file when making changes
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
 This project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html)
-and follows a [Backwards Compatibility Policy](https://docs.solanalabs.com/backwards-compatibility)
+and follows a [Backwards Compatibility Policy](https://docs.anza.xyz/backwards-compatibility)
 
 Release channels have their own copy of this changelog:
 * [edge - v3.0](#edge-channel)

README.md

@@ -70,12 +70,12 @@ $ ./cargo test
 
 ### Starting a local testnet
 
-Start your own testnet locally, instructions are in the [online docs](https://docs.solanalabs.com/clusters/benchmark).
+Start your own testnet locally, instructions are in the [online docs](https://docs.anza.xyz/clusters/benchmark).
 
 ### Accessing the remote development cluster
 
 * `devnet` - stable public cluster for development accessible via
-devnet.solana.com. Runs 24/7. Learn more about the [public clusters](https://docs.solanalabs.com/clusters)
+devnet.solana.com. Runs 24/7. Learn more about the [public clusters](https://docs.anza.xyz/clusters)
 
 # Benchmarking
 

accounts-db/src/append_vec.rs

@@ -2,7 +2,7 @@
 //!
 //! For more information, see:
 //!
-//! <https://docs.solanalabs.com/implemented-proposals/persistent-account-storage>
+//! <https://docs.anza.xyz/implemented-proposals/persistent-account-storage>
 
 mod meta;
 pub mod test_utils;

clap-utils/src/nonce.rs

@@ -9,7 +9,7 @@ pub const NONCE_ARG: ArgConstant<'static> = ArgConstant {
     help: "Provide the nonce account to use when creating a nonced \n\
            transaction. Nonced transactions are useful when a transaction \n\
            requires a lengthy signing process. Learn more about nonced \n\
-           transactions at https://docs.solanalabs.com/cli/examples/durable-nonce",
+           transactions at https://docs.anza.xyz/cli/examples/durable-nonce",
 };
 
 pub const NONCE_AUTHORITY_ARG: ArgConstant<'static> = ArgConstant {

clap-v3-utils/src/nonce.rs

@@ -9,7 +9,7 @@ pub const NONCE_ARG: ArgConstant<'static> = ArgConstant {
     help: "Provide the nonce account to use when creating a nonced \n\
            transaction. Nonced transactions are useful when a transaction \n\
            requires a lengthy signing process. Learn more about nonced \n\
-           transactions at https://docs.solanalabs.com/cli/examples/durable-nonce",
+           transactions at https://docs.anza.xyz/cli/examples/durable-nonce",
 };
 
 pub const NONCE_AUTHORITY_ARG: ArgConstant<'static> = ArgConstant {

core/tests/fork-selection.rs

@@ -1,6 +1,6 @@
 //! Fork Selection Simulation
 //!
-//! Description of the algorithm can be found in [Managing Forks](https://docs.solanalabs.com/consensus/managing-forks).
+//! Description of the algorithm can be found in [Managing Forks](https://docs.anza.xyz/consensus/managing-forks).
 //!
 //! A test library function exists for configuring networks.
 //! ```

docs/README.md

@@ -39,7 +39,7 @@ The build script generates static content into the `build` directory and can be
 ./build.sh
 ```
 
-Running this build script requires **Docker**, and will auto fetch the [solanalabs/rust](https://hub.docker.com/r/solanalabs/rust) image from Docker hub to compile the desired version of the [Solana CLI](https://docs.solanalabs.com/cli) from source.
+Running this build script requires **Docker**, and will auto fetch the [solanalabs/rust](https://hub.docker.com/r/solanalabs/rust) image from Docker hub to compile the desired version of the [Solana CLI](https://docs.anza.xyz/cli) from source.
 
 This build script will also:
 
@@ -66,9 +66,9 @@ The docs are built and published in Github Actions with the `docs.yml` workflow.
 
 In each post-commit build, docs are built and published using `vercel` to their respective domain depending on the build branch.
 
-- Master branch docs are published to `edge.docs.solanalabs.com`
-- Beta branch docs are published to `beta.docs.solanalabs.com`
-- Latest release tag docs are published to `docs.solanalabs.com`
+- Master branch docs are published to `edge.docs.anza.xyz`
+- Beta branch docs are published to `beta.docs.anza.xyz`
+- Latest release tag docs are published to `docs.anza.xyz`
 
 ## Common Issues
 

docs/src/operations/requirements.md

@@ -23,7 +23,7 @@ The hardware recommendations below are provided as a guide.  Operators are encou
 | **CPU**   | - 2.8GHz base clock speed, or faster<br />- SHA extensions instruction support<br />- AMD Gen 3 or newer<br />- Intel Ice Lake or newer<br />- Higher clock speed is preferable over more cores<br />- AVX2 instruction support (to use official release binaries, self-compile otherwise)<br />- Support for AVX512f is helpful<br />||
 | | 12 cores / 24 threads, or more  | 16 cores / 32 threads, or more |
 | **RAM**   | Error Correction Code (ECC) memory is suggested<br />Motherboard with 512GB capacity suggested ||
-| | 256GB or more| 512 GB or more for **all [account indexes](https://docs.solanalabs.com/operations/setup-an-rpc-node#account-indexing)** |
+| | 256GB or more| 512 GB or more for **all [account indexes](https://docs.anza.xyz/operations/setup-an-rpc-node#account-indexing)** |
 | **Disk**  | PCIe Gen3 x4 NVME SSD, or better, on each of: <br />- **Accounts**: 1TB, or larger. High TBW (Total Bytes Written)<br />- **Ledger**: 1TB or larger. High TBW suggested<br />- **Snapshots**: 500GB or larger. High TBW suggested<br />- **OS**: (Optional) 500GB, or larger. SATA OK<br /><br />The OS may be installed on the ledger disk, though testing has shown better performance with the ledger on its own disk<br /><br />Accounts and ledger *can* be stored on the same disk, however due to high IOPS, this is not recommended<br /><br />The Samsung 970 and 980 Pro series SSDs are popular with the validator community | Consider a larger ledger disk if longer transaction history is required<br /><br />Accounts and ledger **should not** be stored on the same disk |
 | **GPUs**  | Not necessary at this time<br />Operators in the validator community do not use GPUs currently | |
 

ledger/src/blockstore.rs

@@ -5260,7 +5260,7 @@ fn adjust_ulimit_nofile(enforce_ulimit_nofile: bool) -> Result<()> {
     // usually not enough
     // AppendVecs and disk Account Index are also heavy users of mmapped files.
     // This should be kept in sync with published validator instructions.
-    // https://docs.solanalabs.com/operations/guides/validator-start#increased-memory-mapped-files-limit
+    // https://docs.anza.xyz/operations/guides/validator-start#system-tuning
     let desired_nofile = 1_000_000;
 
     fn get_nofile() -> libc::rlimit {

run.sh

@@ -7,9 +7,9 @@ cat <<'EOF'
   You almost certainly do not want to run this script!
 
   If you are a dapp developer and looking for a way to run a local validator, please
-  see https://docs.solanalabs.com/cli/examples/test-validator
+  see https://docs.anza.xyz/cli/examples/test-validator
 
-  If you are a prospective validator, please see https://docs.solanalabs.com/operations
+  If you are a prospective validator, please see https://docs.anza.xyz/operations
 
   If you are a core developer, many apologies for what you're about to endure, but
   you may be in the right place.  This script is now located at `./scripts/run.sh`.

validator/src/commands/run/execute.rs

@@ -751,7 +751,7 @@ pub fn execute(
             info!("OS network limits test passed.");
         } else {
             Err("OS network limit test failed. See \
-                https://docs.solanalabs.com/operations/guides/validator-start#system-tuning"
+                https://docs.anza.xyz/operations/guides/validator-start#system-tuning"
                 .to_string())?;
         }
     }

zk-token-sdk/src/instruction/fee_sigma.rs

@@ -6,7 +6,7 @@
 //! A formal documentation of how transfer fees and fee sigma proof are computed can be found in
 //! the [`ZK Token proof`] program documentation.
 //!
-//! [`ZK Token proof`]: https://docs.solanalabs.com/runtime/zk-token-proof
+//! [`ZK Token proof`]: https://docs.anza.xyz/runtime/zk-elgamal-proof
 
 #[cfg(not(target_os = "solana"))]
 use {
@@ -43,7 +43,7 @@ pub struct FeeSigmaProofData {
 ///
 /// We refer to [`ZK Token proof`] for the formal details on how the fee sigma proof is computed.
 ///
-/// [`ZK Token proof`]: https://docs.solanalabs.com/runtime/zk-token-proof
+/// [`ZK Token proof`]: https://docs.anza.xyz/runtime/zk-elgamal-proof
 #[derive(Clone, Copy, Pod, Zeroable)]
 #[repr(C)]
 pub struct FeeSigmaProofContext {

zk-token-sdk/src/instruction/mod.rs

@@ -1,6 +1,6 @@
 //! The instruction data types for the [`ZK Token proof`] instruction.
 //!
-//! [`ZK Token proof`]: https://docs.solanalabs.com/runtime/zk-token-proof
+//! [`ZK Token proof`]: https://docs.anza.xyz/runtime/zk-elgamal-proof
 
 pub mod batched_grouped_ciphertext_validity;
 pub mod batched_range_proof;

zk-token-sdk/src/sigma_proofs/fee_proof.rs

@@ -8,7 +8,7 @@
 //! The protocol guarantees computational soundness (by the hardness of discrete log) and perfect
 //! zero-knowledge in the random oracle model.
 //!
-//! [`ZK Token proof program`]: https://docs.solanalabs.com/runtime/zk-token-proof
+//! [`ZK Token proof program`]: https://docs.anza.xyz/runtime/zk-elgamal-proof
 
 #[cfg(not(target_os = "solana"))]
 use {

zk-token-sdk/src/sigma_proofs/mod.rs

@@ -3,7 +3,7 @@
 //! Formal documentation and security proofs for the sigma proofs in this module can be found in
 //! [`ZK Token proof`] program documentation.
 //!
-//! [`ZK Token proof`]: https://docs.solanalabs.com/runtime/zk-token-proof
+//! [`ZK Token proof`]: https://docs.anza.xyz/runtime/zk-elgamal-proof
 
 pub mod errors;
 

zk-token-sdk/src/zk_token_proof_instruction.rs

@@ -29,8 +29,8 @@
 //! this instruction must be signed by the context account's owner. This instruction can be used by
 //! the account owner to reclaim lamports for storage.
 //!
-//! [`ZK Token proof`]: https://docs.solanalabs.com/runtime/zk-token-proof
-//! [`context-state`]: https://docs.solanalabs.com/runtime/zk-token-proof#context-data
+//! [`ZK Token proof`]: https://docs.anza.xyz/runtime/zk-elgamal-proof
+//! [`context-state`]: https://docs.anza.xyz/runtime/zk-elgamal-proof#context-data
 
 pub use crate::instruction::*;
 use {

zk-token-sdk/src/zk_token_proof_program.rs

@@ -5,7 +5,7 @@
 //! the program as well as the technical details of some of the proof instructions can be found in
 //! the [`ZK Token proof`] documentation.
 //!
-//! [`ZK Token proof`]: https://docs.solanalabs.com/runtime/zk-token-proof
+//! [`ZK Token proof`]: https://docs.anza.xyz/runtime/zk-elgamal-proof
 
 // Program Id of the ZkToken Proof program
 pub use solana_sdk_ids::zk_token_proof_program::{check_id, id, ID};