Website: rename repo from openmina to mina-rust

Author: dannywillems

website/docs/developers/getting-started.mdx

@@ -128,7 +128,7 @@ components:
 
 You can run a different set of tests. The command `make help` will give you the
 whole set of targets. You can also visit the file
-[ci.yaml](https://github.com/o1-labs/openmina/blob/develop/.github/workflows/ci.yaml)
+[ci.yaml](https://github.com/o1-labs/mina-rust/blob/develop/.github/workflows/ci.yaml)
 to explore the targets used for testing in our continuous integration
 environment.
 
@@ -286,7 +286,7 @@ make build-testing
 - **Discord**:
   [OpenMina Community](https://discord.com/channels/484437221055922177/1290662938734231552)
 - **Forums**: [Mina Protocol Forums](https://forums.minaprotocol.com/)
-- **Issues**: [GitHub Issues](https://github.com/o1-labs/openmina/issues)
+- **Issues**: [GitHub Issues](https://github.com/o1-labs/mina-rust/issues)
 - **API Docs**:
   [Rust Documentation](https://o1-labs.github.io/openmina/api-docs/)
 

website/docs/developers/libp2p.md

@@ -45,7 +45,7 @@ specific purpose, which lets us neatly organize the various functions of the P2P
 network. It allows us to separate concerns, making the network architecture
 easier to manage and debug.
 
-![LibP2P Stack Layers](https://github.com/openmina/openmina/assets/60480123/25bb08e8-d877-42b6-9c1f-b2ce29b14520)
+![LibP2P Stack Layers](https://github.com/o1-labs/mina-rust/assets/60480123/25bb08e8-d877-42b6-9c1f-b2ce29b14520)
 
 _Above: A simplified overview of the Rust node LibP2P networking stack. The
 abstraction is in ascending order, i.e. the layers at the top have more
@@ -117,7 +117,7 @@ efficient routing and data lookup.
 The term "XOR" stands for "exclusive or," which is a logical operation that
 outputs true only when the inputs differ (one is true, the other is false).
 
-![Kademlia Binary Tree](https://github.com/openmina/openmina/assets/60480123/4e57f9b9-9e68-4400-b0ad-ff17c14766a1)
+![Kademlia Binary Tree](https://github.com/o1-labs/mina-rust/assets/60480123/4e57f9b9-9e68-4400-b0ad-ff17c14766a1)
 
 _Above: A Kademlia binary tree organized into four distinct buckets (marked in
 orange) of varying sizes._
@@ -142,7 +142,7 @@ network consisting of devices with limited resources. To make the most of a
 single connection, we employ _multiplexing_, which means having multiple data
 streams transmitted over a single network connection concurrently.
 
-![Yamux Multiplexing](https://github.com/openmina/openmina/assets/60480123/5f6a48c7-bbae-4ca2-9189-badae2369f3d)
+![Yamux Multiplexing](https://github.com/o1-labs/mina-rust/assets/60480123/5f6a48c7-bbae-4ca2-9189-badae2369f3d)
 
 ### Yamux Implementation
 
@@ -184,11 +184,11 @@ The Noise protocol implemented by libp2p uses the
 [XX](http://www.noiseprotocol.org/noise.html#interactive-handshake-patterns-fundamental)
 handshake pattern, which happens in the following stages:
 
-![Noise Handshake Step 1](https://github.com/openmina/openmina/assets/60480123/a1b2b2bf-980e-459c-8375-9e8b6162b6d1)
+![Noise Handshake Step 1](https://github.com/o1-labs/mina-rust/assets/60480123/a1b2b2bf-980e-459c-8375-9e8b6162b6d1)
 
 **Step 1**: Alice sends Bob her ephemeral public key (32 bytes).
 
-![Noise Handshake Step 2](https://github.com/openmina/openmina/assets/60480123/721103dd-0bb9-4f0b-8998-97b0cc19f6fc)
+![Noise Handshake Step 2](https://github.com/o1-labs/mina-rust/assets/60480123/721103dd-0bb9-4f0b-8998-97b0cc19f6fc)
 
 **Step 2**: Bob responds to Alice with a message that contains:
 
@@ -199,7 +199,7 @@ handshake pattern, which happens in the following stages:
   `identity_sig`, Noise's static public key and the tag (MAC) of the payload (16
   bytes)
 
-![Noise Handshake Step 3](https://github.com/openmina/openmina/assets/60480123/b7ed062d-2204-4b94-87af-abc6eecd7013)
+![Noise Handshake Step 3](https://github.com/o1-labs/mina-rust/assets/60480123/b7ed062d-2204-4b94-87af-abc6eecd7013)
 
 **Step 3**: Alice responds to Bob with her own message that contains:
 

website/docs/developers/p2p-networking.md

@@ -170,7 +170,7 @@ propagation by leveraging the poll-based approach:
 #### Data Structure
 
 A special
-[distributed pool data structure](https://github.com/openmina/openmina/blob/develop/core/src/distributed_pool.rs)
+[distributed pool data structure](https://github.com/o1-labs/mina-rust/blob/develop/core/src/distributed_pool.rs)
 efficiently tracks sent messages:
 
 - **Append-Only Log**: Each entry indexed by number

website/docs/developers/scripts/setup/clone-and-build.sh

@@ -1,5 +1,5 @@
-git clone https://github.com/o1-labs/openmina.git
-cd openmina
+git clone https://github.com/o1-labs/mina-rust.git
+cd mina-rust
 
 # Download required circuits
 echo "Downloading required circuits..."

website/docs/developers/updating-ocaml-node.md

@@ -9,7 +9,7 @@ node references in the Mina Rust Node. The OCaml node releases are used to
 verify that the current Mina Rust Node version maintains compatibility with the
 official Mina Protocol implementation through end-to-end and scenario testing.
 This guide walks through the process based on the workflow used in
-[PR #1236](https://github.com/o1-labs/openmina/pull/1236).
+[PR #1236](https://github.com/o1-labs/mina-rust/pull/1236).
 
 ## 1. Check for New Releases
 
@@ -35,7 +35,7 @@ update process:
 **Example usage:**
 
 For example, to update from `3.2.0-alpha1` to `3.2.0-beta1` (as done in commit
-[31caeee6](https://github.com/o1-labs/openmina/commit/31caeee6af7bf20b8578a23bf69718dbe68fe5cc)):
+[31caeee6](https://github.com/o1-labs/mina-rust/commit/31caeee6af7bf20b8578a23bf69718dbe68fe5cc)):
 
 ```bash
 ./website/docs/developers/scripts/update-ocaml-node.sh 7f94ae0b 978866cd "3.2.0-alpha1" "3.2.0-beta1"
@@ -79,7 +79,7 @@ After making updates:
 ## 5. Commit Structure
 
 Following the pattern from commit
-[31caeee6](https://github.com/o1-labs/openmina/commit/31caeee6af7bf20b8578a23bf69718dbe68fe5cc):
+[31caeee6](https://github.com/o1-labs/mina-rust/commit/31caeee6af7bf20b8578a23bf69718dbe68fe5cc):
 
 1. **Main Update Commit**: "OCaml nodes: bump up to release [version]"
    - Updates 6 files: CI workflows, Docker compose, and testing configurations
@@ -90,5 +90,5 @@ Following the pattern from commit
 
 - [Mina Protocol Releases](https://github.com/MinaProtocol/mina/releases/)
 - [Mina Rust Node Architecture Documentation](./architecture.md)
-- [Example PR #1236](https://github.com/o1-labs/openmina/pull/1236)
+- [Example PR #1236](https://github.com/o1-labs/mina-rust/pull/1236)
 - [Node Operators Guide](../node-operators/getting-started.md)

website/docs/developers/webrtc.md

@@ -73,21 +73,21 @@ ICE dynamically selects the best path based on connectivity and performance.
 ## Mina Rust Node WebRTC Implementation
 
 The Mina Rust Node's WebRTC implementation is located in
-[`p2p/src/webrtc/`](https://o1-labs.github.io/openmina/api-docs/p2p/webrtc/index.html)
+[`p2p/src/webrtc/`](https://o1-labs.github.io/mina-rust/api-docs/p2p/webrtc/index.html)
 and provides a structured approach to peer-to-peer connections for blockchain
 communication.
 
 ### Key Components
 
-#### Host Resolution ([`host.rs`](https://o1-labs.github.io/openmina/api-docs/p2p/webrtc/host/index.html))
+#### Host Resolution ([`host.rs`](https://o1-labs.github.io/mina-rust/api-docs/p2p/webrtc/host/index.html))
 
 Handles different address types:
 
 - Domain names (with DNS resolution)
 - IPv4/IPv6 addresses
 - Multiaddr protocol integration
 
-#### Signaling Messages ([`signal.rs`](https://o1-labs.github.io/openmina/api-docs/p2p/webrtc/signal/index.html))
+#### Signaling Messages ([`signal.rs`](https://o1-labs.github.io/mina-rust/api-docs/p2p/webrtc/signal/index.html))
 
 Defines the core signaling data structures:
 
@@ -96,15 +96,15 @@ Defines the core signaling data structures:
 - **Answer**: Response containing SDP and identity information
 - **Connection Response**: Handles acceptance, rejection, and error states
 
-#### Signaling Methods ([`signaling_method/`](https://o1-labs.github.io/openmina/api-docs/p2p/webrtc/signaling_method/index.html))
+#### Signaling Methods ([`signaling_method/`](https://o1-labs.github.io/mina-rust/api-docs/p2p/webrtc/signaling_method/index.html))
 
 Supports multiple signaling transport methods:
 
 - HTTP/HTTPS direct connections
 - HTTPS proxy with cluster support
 - P2P relay through existing peers
 
-#### Connection Authentication ([`connection_auth.rs`](https://o1-labs.github.io/openmina/api-docs/p2p/webrtc/connection_auth/index.html))
+#### Connection Authentication ([`connection_auth.rs`](https://o1-labs.github.io/mina-rust/api-docs/p2p/webrtc/connection_auth/index.html))
 
 Provides cryptographic authentication:
 
@@ -127,32 +127,32 @@ The Mina Rust Node's WebRTC implementation includes several security measures:
 ### Connection Flow
 
 1. **Offer Creation**: Initiating peer creates an
-   [offer](https://o1-labs.github.io/openmina/api-docs/p2p/webrtc/signal/struct.Offer.html)
+   [offer](https://o1-labs.github.io/mina-rust/api-docs/p2p/webrtc/signal/struct.Offer.html)
    with SDP, identity, and target information using
-   [`Offer::new()`](https://o1-labs.github.io/openmina/api-docs/p2p/webrtc/signal/struct.Offer.html#method.new)
+   [`Offer::new()`](https://o1-labs.github.io/mina-rust/api-docs/p2p/webrtc/signal/struct.Offer.html#method.new)
 2. **Signaling**: Offer is transmitted through the configured
-   [signaling method](https://o1-labs.github.io/openmina/api-docs/p2p/webrtc/signaling_method/enum.SignalingMethod.html)
+   [signaling method](https://o1-labs.github.io/mina-rust/api-docs/p2p/webrtc/signaling_method/enum.SignalingMethod.html)
    using
-   [`SignalingMethod::http_url()`](https://o1-labs.github.io/openmina/api-docs/p2p/webrtc/signaling_method/enum.SignalingMethod.html#method.http_url)
+   [`SignalingMethod::http_url()`](https://o1-labs.github.io/mina-rust/api-docs/p2p/webrtc/signaling_method/enum.SignalingMethod.html#method.http_url)
    for HTTP-based methods
 3. **Offer Processing**: Receiving peer validates chain ID, identity, and
    capacity using
-   [`Offer::chain_id()`](https://o1-labs.github.io/openmina/api-docs/p2p/webrtc/signal/struct.Offer.html#method.chain_id)
+   [`Offer::chain_id()`](https://o1-labs.github.io/mina-rust/api-docs/p2p/webrtc/signal/struct.Offer.html#method.chain_id)
    and
-   [`Offer::identity()`](https://o1-labs.github.io/openmina/api-docs/p2p/webrtc/signal/struct.Offer.html#method.identity)
+   [`Offer::identity()`](https://o1-labs.github.io/mina-rust/api-docs/p2p/webrtc/signal/struct.Offer.html#method.identity)
 4. **Answer Generation**: If accepted, receiving peer creates an
-   [answer](https://o1-labs.github.io/openmina/api-docs/p2p/webrtc/signal/struct.Answer.html)
+   [answer](https://o1-labs.github.io/mina-rust/api-docs/p2p/webrtc/signal/struct.Answer.html)
    with SDP using
-   [`Answer::new()`](https://o1-labs.github.io/openmina/api-docs/p2p/webrtc/signal/struct.Answer.html#method.new)
+   [`Answer::new()`](https://o1-labs.github.io/mina-rust/api-docs/p2p/webrtc/signal/struct.Answer.html#method.new)
 5. **Connection Response**: Response is wrapped in
-   [`P2pConnectionResponse`](https://o1-labs.github.io/openmina/api-docs/p2p/webrtc/signal/enum.P2pConnectionResponse.html)
+   [`P2pConnectionResponse`](https://o1-labs.github.io/mina-rust/api-docs/p2p/webrtc/signal/enum.P2pConnectionResponse.html)
    indicating acceptance or rejection
 6. **Authentication**: Final handshake using encrypted
-   [connection authentication](https://o1-labs.github.io/openmina/api-docs/p2p/webrtc/connection_auth/struct.ConnectionAuth.html)
+   [connection authentication](https://o1-labs.github.io/mina-rust/api-docs/p2p/webrtc/connection_auth/struct.ConnectionAuth.html)
    created via
-   [`ConnectionAuth::new()`](https://o1-labs.github.io/openmina/api-docs/p2p/webrtc/connection_auth/struct.ConnectionAuth.html#method.new)
+   [`ConnectionAuth::new()`](https://o1-labs.github.io/mina-rust/api-docs/p2p/webrtc/connection_auth/struct.ConnectionAuth.html#method.new)
    and encrypted with
-   [`ConnectionAuth::encrypt()`](https://o1-labs.github.io/openmina/api-docs/p2p/webrtc/connection_auth/struct.ConnectionAuth.html#method.encrypt)
+   [`ConnectionAuth::encrypt()`](https://o1-labs.github.io/mina-rust/api-docs/p2p/webrtc/connection_auth/struct.ConnectionAuth.html#method.encrypt)
 
 ### Integration with Mina Rust Node Architecture
 

website/docs/node-operators/alpha-testing.md

@@ -20,7 +20,7 @@ Ensure you have **Docker** installed:
 
 1. **Download the Latest Release**:
    - Visit the
-     [Open Mina Releases](https://github.com/openmina/openmina/releases).
+     [Open Mina Releases](https://github.com/o1-labs/mina-rust/releases).
    - Download the latest `openmina-vX.Y.Z-docker-compose.zip`.
 
 2. **Extract the Files**:

website/docs/node-operators/archive-node.md

@@ -67,7 +67,7 @@ node. The archiver process is responsible for storing the blocks in the database
 by receiving the blocks from the openmina node.
 
 See
-[docker-compose.archive.devnet.yml](https://github.com/o1-labs/openmina/blob/develop/docker-compose.archive.devnet.yml)
+[docker-compose.archive.devnet.yml](https://github.com/o1-labs/mina-rust/blob/develop/docker-compose.archive.devnet.yml)
 for more details.
 
 ### Starting the setup

website/docs/node-operators/block-producer.md

@@ -15,7 +15,7 @@ Ensure Docker and Docker Compose are installed on your system -
 
 1. **Download the Latest Release**
 
-- Visit the [Open Mina Releases](https://github.com/openmina/openmina/releases)
+- Visit the [Open Mina Releases](https://github.com/o1-labs/mina-rust/releases)
 - Download the latest `openmina-vX.Y.Z-docker-compose.zip`
 - Extract the Files:
 
@@ -27,7 +27,7 @@ Ensure Docker and Docker Compose are installed on your system -
 
 2. **Prepare Your Keys**
 
-   [Docker Compose](https://github.com/o1-labs/openmina/blob/develop/docker-compose.block-producer.yml)
+   [Docker Compose](https://github.com/o1-labs/mina-rust/blob/develop/docker-compose.block-producer.yml)
    references `openmina-workdir`. It stores a private key and logs for block
    production. Place your block producer's private key into the
    `openmina-workdir` directory and name it `producer-key`:

website/docs/node-operators/building-from-source.md

@@ -59,7 +59,7 @@ overridden:
 
 For detailed information about all available command-line parameters and
 advanced configuration options, please refer to the
-[Rust API Documentation](https://o1-labs.github.io/openmina/api-docs/cli/commands/node/struct.Node.html)
+[Rust API Documentation](https://o1-labs.github.io/mina-rust/api-docs/cli/commands/node/struct.Node.html)
 which contains comprehensive documentation for all supported parameters
 including: