Run make format-md

Author: dannywillems

ARCHITECTURE.md

@@ -4,16 +4,19 @@ This file helps understand and navigate the OpenMina codebase structure.
 
 ## Project Overview
 
-OpenMina is a Rust implementation of the Mina Protocol, a lightweight
-blockchain using zero-knowledge proofs. It follows a Redux-style state machine
-architecture for predictable, debuggable behavior.
+OpenMina is a Rust implementation of the Mina Protocol, a lightweight blockchain
+using zero-knowledge proofs. It follows a Redux-style state machine architecture
+for predictable, debuggable behavior.
 
-*For detailed architecture documentation, see [`docs/handover/`](docs/handover/)*
+_For detailed architecture documentation, see
+[`docs/handover/`](docs/handover/)_
 
 ## Architecture Overview
 
 ### State Machine Pattern
+
 The codebase follows Redux principles:
+
 - **State** - Centralized, immutable data structure
 - **Actions** - Events that trigger state changes
 - **Enabling Conditions** - Guards that prevent invalid state transitions
@@ -22,14 +25,17 @@ The codebase follows Redux principles:
 - **Services** - Separate threads handling I/O and heavy computation
 
 ### Architecture Styles
-- **New Style**: Unified reducers that handle both state updates and action dispatch
+
+- **New Style**: Unified reducers that handle both state updates and action
+  dispatch
 - **Old Style**: Separate reducer and effects files (being migrated)
 
 ## Project Structure
 
 ### Core Components
 
 **node/** - Main node logic
+
 - `block_producer/` - Block production
 - `transaction_pool/` - Transaction mempool
 - `transition_frontier/` - Consensus and blockchain state
@@ -40,6 +46,7 @@ The codebase follows Redux principles:
 - `service/` - Service implementations
 
 **p2p/** - Networking layer
+
 - Dual transport: libp2p and WebRTC
 - Channel abstractions for message types
 - Peer discovery and connection management
@@ -54,6 +61,7 @@ logic, staged ledger, scan state, and proof verification
 ## Code Organization
 
 ### File Patterns
+
 - `*_state.rs` - State definitions
 - `*_actions.rs` - Action types
 - `*_reducer.rs` - State transitions
@@ -62,6 +70,7 @@ logic, staged ledger, scan state, and proof verification
 - `summary.md` - Component documentation and technical debt notes
 
 ### Key Files
+
 - `node/src/state.rs` - Global state structure
 - `node/src/action.rs` - Top-level action enum
 - `node/src/reducer.rs` - Main reducer dispatch
@@ -77,14 +86,17 @@ logic, staged ledger, scan state, and proof verification
 ## Key Patterns
 
 ### Defensive Programming
+
 - `bug_condition!` macro marks theoretically unreachable code paths
 - Used after enabling condition checks for invariant validation
 
 ### State Methods
+
 - Complex logic extracted from reducers into state methods
 - Keeps reducers focused on orchestration
 
 ### Callbacks
+
 - Enable decoupled component communication
 - Used for async operation completion
 
@@ -107,6 +119,7 @@ find . -name "summary.md" -path "*/component/*"
 ## Component Documentation
 
 Each component directory contains a `summary.md` file documenting:
+
 - Component purpose and responsibilities
 - Known technical debt
 - Implementation notes

CLAUDE.md

@@ -8,5 +8,5 @@ Images are available at the Docker Hub repository `openmina/openmina`.
 For the branch itself, two tags produced, one derived from the commit hash
 (first 8 chars), and another one is `latest`.
 
-For a PR from a branch named `some/branch`, two tags are produced, one is `some-branch-<commit-hash>` and another one is `some-branch-latest`.
-
+For a PR from a branch named `some/branch`, two tags are produced, one is
+`some-branch-<commit-hash>` and another one is `some-branch-latest`.

docker.md

@@ -1,6 +1,8 @@
 # Run Non-Block Producing Node on Devnet
 
-This guide will walk you through running the **Alpha Rust Node** on Devnet using Docker. Follow these steps to set up the node and [Provide Feedback](#4-provide-feedback) on this Alpha release.
+This guide will walk you through running the **Alpha Rust Node** on Devnet using
+Docker. Follow these steps to set up the node and
+[Provide Feedback](#4-provide-feedback) on this Alpha release.
 
 ## 1. Prerequisites
 
@@ -11,8 +13,8 @@ Ensure you have **Docker** installed:
 ## 2. Download & Start the Node
 
 1. **Download the Latest Release**:
-
-   - Visit the [Open Mina Releases](https://github.com/openmina/openmina/releases).
+   - Visit the
+     [Open Mina Releases](https://github.com/openmina/openmina/releases).
    - Download the latest `openmina-vX.Y.Z-docker-compose.zip`.
 
 2. **Extract the Files**:
@@ -24,28 +26,32 @@ Ensure you have **Docker** installed:
 
    Additional optional parameters:
 
-   `OPENMINA_LIBP2P_EXTERNAL_IP` Sets your node’s external IP address to help other nodes find it.
+   `OPENMINA_LIBP2P_EXTERNAL_IP` Sets your node’s external IP address to help
+   other nodes find it.
 
    `OPENMINA_LIBP2P_PORT` Sets the port for Libp2p communication.
 
-3. **Start the Node on Devnet and Save Logs**:
-   Start the node and save the logs for later analysis:
+3. **Start the Node on Devnet and Save Logs**: Start the node and save the logs
+   for later analysis:
 
    ```bash
    docker compose up --pull always && docker compose logs > openmina-node.log
    ```
 
-4. **Access the Dashboard**:
-   Open `http://localhost:8070` in your browser.
+4. **Access the Dashboard**: Open `http://localhost:8070` in your browser.
 
    The dashboard will show the syncing process in real time.
    <img width="1417" alt="image" src="https://github.com/user-attachments/assets/d9a5f5b3-522f-479b-9829-37402c63bb98">
 
-   > **1. Connecting to Peers:** The node connects to peers. You’ll see the number of connected, connecting, and disconnected peers grow.
+   > **1. Connecting to Peers:** The node connects to peers. You’ll see the
+   > number of connected, connecting, and disconnected peers grow.
    >
-   > **2. Fetching Ledgers:** The node downloads key data: Staking ledger, Next epoch ledger, and Snarked ledger. Progress bars show the download status.
+   > **2. Fetching Ledgers:** The node downloads key data: Staking ledger, Next
+   > epoch ledger, and Snarked ledger. Progress bars show the download status.
    >
-   > **3. Fetching & Applying Blocks:** The node downloads recent blocks to match the network’s current state. The dashboard tracks how many blocks are fetched and applied.
+   > **3. Fetching & Applying Blocks:** The node downloads recent blocks to
+   > match the network’s current state. The dashboard tracks how many blocks are
+   > fetched and applied.
 
 ## 3. Monitoring and troubleshooting
 
@@ -68,10 +74,15 @@ docker compose up --pull always
 
 ## 4. Provide Feedback
 
-This Alpha release is for testing purposes. Your feedback is essential. Follow these steps to report any issues:
+This Alpha release is for testing purposes. Your feedback is essential. Follow
+these steps to report any issues:
 
-1. **Collect Logs**: Use the [commands above to save logs](#2-download--start-the-node)
-2. **Visit Discord**: [Open Mina Discord Channel](https://discord.com/channels/484437221055922177/1290662938734231552/1290667779317305354)
+1. **Collect Logs**: Use the
+   [commands above to save logs](#2-download--start-the-node)
+2. **Visit Discord**:
+   [Open Mina Discord Channel](https://discord.com/channels/484437221055922177/1290662938734231552/1290667779317305354)
 3. **Describe the Issue**: Briefly explain the problem and steps to reproduce it
-4. **Attach Logs**: Discord allows files up to 25MB. If your logs are larger, use Google Drive or similar
-5. **Include a Screenshot**: A dashboard screenshot provides details about node status, making it easier to diagnose the issue
+4. **Attach Logs**: Discord allows files up to 25MB. If your logs are larger,
+   use Google Drive or similar
+5. **Include a Screenshot**: A dashboard screenshot provides details about node
+   status, making it easier to diagnose the issue

docs/alpha-testing-guide.md

@@ -1,33 +1,40 @@
 # Run Archive Node on Devnet
 
-This guide is intended for setting up archive nodes on **Mina Devnet** only. Do not use this guide for Mina Mainnet
+This guide is intended for setting up archive nodes on **Mina Devnet** only. Do
+not use this guide for Mina Mainnet
 
 ## Archive Mode Configuration
 
-We start archive mode in openmina by setting one of the following flags along with their associated environment variables:
+We start archive mode in openmina by setting one of the following flags along
+with their associated environment variables:
 
 ### Archiver Process (`--archive-archiver-process`)
 
 Stores blocks in a database by receiving them directly from the openmina node
 
 **Required Environment Variables**:
+
 - `OPENMINA_ARCHIVE_ADDRESS`: Network address for the archiver service
 
 ### Local Storage (`--archive-local-storage`)
 
 Stores blocks in the local filesystem
 
 **Required Environment Variables**:
+
 - (None)
 
 **Optional Environment Variables**:
-- `OPENMINA_ARCHIVE_LOCAL_STORAGE_PATH`: Custom path for block storage (default: ~/.openmina/archive-precomputed)
+
+- `OPENMINA_ARCHIVE_LOCAL_STORAGE_PATH`: Custom path for block storage (default:
+  ~/.openmina/archive-precomputed)
 
 ### GCP Storage (`--archive-gcp-storage`)
 
 Uploads blocks to a Google Cloud Platform bucket
 
 **Required Environment Variables**:
+
 - `GCP_CREDENTIALS_JSON`: Service account credentials JSON
 - `GCP_BUCKET_NAME`: Target storage bucket name
 
@@ -36,6 +43,7 @@ Uploads blocks to a Google Cloud Platform bucket
 Uploads blocks to an AWS S3 bucket
 
 **Required Environment Variables**:
+
 - `AWS_ACCESS_KEY_ID`: IAM user access key
 - `AWS_SECRET_ACCESS_KEY`: IAM user secret key
 - `AWS_DEFAULT_REGION`: AWS region name
@@ -44,17 +52,22 @@ Uploads blocks to an AWS S3 bucket
 
 ## Redundancy
 
-The archive mode is designed to be redundant. We can combine the flags to have multiple options running simultaneously.
+The archive mode is designed to be redundant. We can combine the flags to have
+multiple options running simultaneously.
 
 ## Prerequisites
 
-Ensure Docker and Docker Compose are installed on your system - [Docker Installation Guide](./docker-installation.md)
+Ensure Docker and Docker Compose are installed on your system -
+[Docker Installation Guide](./docker-installation.md)
 
 ## Docker compose setup (with archiver process)
 
-The compose file sets up a PG database, the archiver process and the openmina node. The archiver process is responsible for storing the blocks in the database by receiving the blocks from the openmina node.
+The compose file sets up a PG database, the archiver process and the openmina
+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](../docker-compose.archive.devnet.yml) for more details.
+See [docker-compose.archive.devnet.yml](../docker-compose.archive.devnet.yml)
+for more details.
 
 ### Starting the setup
 

docs/archive-node-guide.md

@@ -1,13 +1,16 @@
 # Run Block Producing Node on Devnet
 
-This guide is intended for setting up block producer nodes on **Mina Devnet** only.  
-Do not use this guide for Mina Mainnet until necessary security audits are complete.
+This guide is intended for setting up block producer nodes on **Mina Devnet**
+only.  
+Do not use this guide for Mina Mainnet until necessary security audits are
+complete.
 
 ---
 
 ## Prerequisites
 
-Ensure Docker and Docker Compose are installed on your system - [Docker Installation Guide](./docker-installation.md)
+Ensure Docker and Docker Compose are installed on your system -
+[Docker Installation Guide](./docker-installation.md)
 
 ## Download & Start the Node
 
@@ -25,18 +28,22 @@ Ensure Docker and Docker Compose are installed on your system - [Docker Installa
 
 2. **Prepare Your Keys**
 
-   [Docker Compose](../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`:
+   [Docker Compose](../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`:
 
    ```bash
    cp /path/to/your/private_key openmina-workdir/producer-key
    ```
 
-   Replace `/path/to/your/private_key` with the actual path to your private key file.
+   Replace `/path/to/your/private_key` with the actual path to your private key
+   file.
 
 3. **Launch Block Producer**
 
-   Use `MINA_PRIVKEY_PASS` to set the private key password. Optionally, use `COINBASE_RECEIVER` to set a different coinbase receiver:
+   Use `MINA_PRIVKEY_PASS` to set the private key password. Optionally, use
+   `COINBASE_RECEIVER` to set a different coinbase receiver:
 
    ```bash
    env COINBASE_RECEIVER="YourWalletAddress" MINA_PRIVKEY_PASS="YourPassword" \
@@ -45,18 +52,24 @@ Ensure Docker and Docker Compose are installed on your system - [Docker Installa
 
    Optional parameters:
 
-   `OPENMINA_LIBP2P_EXTERNAL_IP` Sets your node’s external IP address to help other nodes find it.
+   `OPENMINA_LIBP2P_EXTERNAL_IP` Sets your node’s external IP address to help
+   other nodes find it.
 
    `OPENMINA_LIBP2P_PORT` Sets the port for Libp2p communication.
 
 4. **Go to Dashboard**
 
-   Visit [http://localhost:8070](http://localhost:8070) to [monitor sync](http://localhost:8070/dashboard) and [block production](http://localhost:8070/block-production).
+   Visit [http://localhost:8070](http://localhost:8070) to
+   [monitor sync](http://localhost:8070/dashboard) and
+   [block production](http://localhost:8070/block-production).
 
 ### Access Logs
 
-Logs are stored in `openmina-workdir` with filenames like `openmina.log.2024-10-14`, `openmina.log.2024-10-15`, etc.
+Logs are stored in `openmina-workdir` with filenames like
+`openmina.log.2024-10-14`, `openmina.log.2024-10-15`, etc.
 
 ### Provide Feedback
 
-Collect logs from `openmina-workdir` and report issues on the [rust-node-testing](https://discord.com/channels/484437221055922177/1290662938734231552) discord channel. Include reproduction steps if possible.
+Collect logs from `openmina-workdir` and report issues on the
+[rust-node-testing](https://discord.com/channels/484437221055922177/1290662938734231552)
+discord channel. Include reproduction steps if possible.

docs/block-producer-guide.md

@@ -1,6 +1,7 @@
 # How to build and launch a node from source
 
-This installation guide has been tested on Debian and Ubuntu and should work on most distributions of Linux.
+This installation guide has been tested on Debian and Ubuntu and should work on
+most distributions of Linux.
 
 ## Prerequisites
 
@@ -73,7 +74,8 @@ nvm install 20.11.1
 
 #### Windows
 
-Download [Node.js v20.11.1](https://nodejs.org/) from the official website, open the installer and follow the prompts to complete the installation.
+Download [Node.js v20.11.1](https://nodejs.org/) from the official website, open
+the installer and follow the prompts to complete the installation.
 
 ### 2. Angular CLI v16.2.0