Website: add section regarding the archive node

Author: dannywillems

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

@@ -4,25 +4,89 @@ This guide is intended for setting up archive nodes on **Mina Devnet** only. Do
 not use this guide for Mina Mainnet until necessary security audits are
 complete.
 
+## What is an Archive Node?
+
+An archive node is a specialized Mina node that stores the complete blockchain
+history in a structured database. Unlike regular nodes that only maintain recent
+state for consensus, archive nodes:
+
+- **Store all blocks**: Maintains every block from genesis to the current tip
+- **Preserve transaction history**: Keeps a complete record of all transactions
+- **Provide historical queries**: Enables querying of past blockchain states
+- **Support analytics**: Facilitates blockchain analysis and data exploration
+- **Enable compliance**: Helps meet regulatory requirements for data retention
+
+### Synchronization Behavior
+
+<!-- prettier-ignore-start -->
+
+:::note Current Limitation
+
+Archive nodes currently sync and store blocks from the point when they are
+started. There is no built-in option to automatically replay and store the
+complete blockchain history from genesis block.
+
+To obtain complete historical data, you would need to:
+
+1. Start the archive node from genesis (when the network was launched)
+2. Import historical data from another archive node's database
+3. Use existing archive services that have been running since genesis
+
+:::
+
+<!-- prettier-ignore-stop -->
+
+The archive node consists of three components:
+
+1. **Mina node**: Syncs with the network and receives new blocks
+2. **Archiver process**: Processes blocks and stores them in the database
+3. **PostgreSQL database**: Stores the structured blockchain data
+
 ---
 
 ## Prerequisites
 
 Ensure Docker and Docker Compose are installed on your system -
 [Docker Installation Guide](../appendix/docker-installation)
 
-## Download & Start the Archive Node
+## Using Docker Compose
+
+1. **Download the Docker Compose File**
+
+   Create a directory for your archive node and download the docker-compose
+   file:
+
+   ```bash
+   # Create a directory for your archive node
+   mkdir mina-archive-node && cd mina-archive-node
+
+   # Download the archive node docker-compose file (choose one method)
+   # Using wget:
+   wget https://raw.githubusercontent.com/o1-labs/mina-rust/v0.17.0/docker-compose.archive.devnet.yml
+
+   # Or using curl:
+   curl -O https://raw.githubusercontent.com/o1-labs/mina-rust/v0.17.0/docker-compose.archive.devnet.yml
+
+   # Create required .env file with PostgreSQL settings
+   cat > .env << EOF
+   POSTGRES_PASSWORD=mina
+   PG_PORT=5432
+   PG_DB=archive
+   MINA_RUST_TAG=latest
+   EOF
+   ```
+
+   For the latest development version, replace `v0.17.0` with `develop` in the
+   URL.
 
-1. **Download the Latest Release**
-   - Visit the
-     [Mina Rust Releases](https://github.com/o1-labs/mina-rust/releases)
-   - Download the latest `mina-rust-vX.Y.Z-docker-compose.zip`
-   - Extract the Files:
+   <!-- prettier-ignore-start -->
 
-     ```bash
-     unzip mina-rust-vX.Y.Z-docker-compose.zip
-     cd mina-rust-vX.Y.Z-docker-compose
-     ```
+   :::warning Required Configuration The archive node requires a `.env` file
+   with PostgreSQL database settings. The example above provides the minimum
+   required configuration. You can customize the database password and other
+   settings as needed. :::
+
+   <!-- prettier-ignore-stop -->
 
 2. **Launch Archive Node**
 
@@ -55,9 +119,60 @@ Ensure Docker and Docker Compose are installed on your system -
 
 3. **Monitor the Archive Node**
 
-   The archive node will be accessible at:
-   - **Archive API**: http://localhost:3086
-   - **Node API**: http://localhost:3000
+   The archive node components will be accessible at:
+   - **Archive Service**: localhost:3086 (RPC protocol, not HTTP)
+   - **Node GraphQL API**: http://localhost:3000/graphql
+   - **PostgreSQL Database**: localhost:5432
+
+## Analyzing and Querying Archive Data
+
+Once your archive node is running, you can analyze the stored blockchain data
+through multiple interfaces:
+
+### Database Access
+
+The archive node stores data in a PostgreSQL database with over 45 tables
+containing complete blockchain history. You can:
+
+- **Direct SQL queries** - Connect directly to PostgreSQL for complex analysis
+- **GraphQL API** - Use the node's GraphQL endpoint for programmatic access
+- **Pre-built queries** - Use existing SQL templates for common operations
+
+### Quick Database Test
+
+```bash
+# Connect to the database
+docker exec postgres-mina-rust psql -U postgres -d archive -c "\dt"
+
+# Check recent blocks
+docker exec postgres-mina-rust psql -U postgres -d archive -c "SELECT COUNT(*) as total_blocks FROM blocks;"
+```
+
+### Documentation for Developers
+
+For comprehensive guides on querying and analyzing archive data:
+
+- **[Archive Database Queries](../developers/archive-database-queries)** -
+  Complete SQL reference, schema documentation, and analysis examples
+- **[GraphQL API Reference](../developers/graphql-api)** - Full GraphQL endpoint
+  documentation and query examples
+
+These developer guides include:
+
+- Complete database schema and table relationships
+- Working SQL queries for blockchain analysis
+- GraphQL queries for real-time data access
+- Performance optimization techniques
+- Data export and backup procedures
+
+### Common Use Cases
+
+1. **Compliance and Auditing**: Track all transactions for regulatory compliance
+2. **Analytics Dashboards**: Build real-time blockchain analytics
+3. **Research**: Analyze network behavior, transaction patterns, and economics
+4. **Block Explorers**: Power blockchain explorer websites
+5. **Tax Reporting**: Generate transaction history for tax purposes
+6. **Network Monitoring**: Track network health and validator performance
 
 ## Node Parameters Reference
 
@@ -102,45 +217,56 @@ the Makefile target. This method requires building from source.
 ### Archive Mode Configuration
 
 Mina Rust supports multiple archive modes that can be run simultaneously for
-redundancy:
+redundancy. Each mode stores blockchain data in a different location or format.
+
+#### Available Archive Modes
 
-**Archiver Process (`--archive-archiver-process`)**
+##### 1. Archiver Process (`--archive-archiver-process`)
 
-Stores blocks in a database by receiving them directly from the Mina Rust node.
+- **Purpose**: Stores blocks in a PostgreSQL database
+- **Method**: Receives blocks directly from the Mina Rust node via RPC
+- **Use case**: Primary archive method for database queries and analysis
 
-**Required Environment Variables:**
+**Required environment variables:**
 
-- `MINA_ARCHIVE_ADDRESS`: Network address for the archiver service
+- `MINA_ARCHIVE_ADDRESS`: Network address for the archiver service (e.g.,
+  `http://localhost:3086`)
 
-**Local Storage (`--archive-local-storage`)**
+##### 2. Local Storage (`--archive-local-storage`)
 
-Stores blocks in the local filesystem.
+- **Purpose**: Stores blocks in the local filesystem
+- **Method**: Saves precomputed blocks as files on disk
+- **Use case**: Local backup and offline analysis
 
-**Optional Environment Variables:**
+**Optional environment variables:**
 
-- `MINA_ARCHIVE_LOCAL_STORAGE_PATH`: Custom path for block storage (default:
-  `~/.mina/archive-precomputed`)
+- `MINA_ARCHIVE_LOCAL_STORAGE_PATH`: Custom storage path
+  - Default: `~/.mina/archive-precomputed`
 
-**GCP Storage (`--archive-gcp-storage`)**
+##### 3. GCP Storage (`--archive-gcp-storage`)
 
-Uploads blocks to a Google Cloud Platform bucket.
+- **Purpose**: Uploads blocks to Google Cloud Platform bucket
+- **Method**: Stores precomputed blocks in GCP Cloud Storage
+- **Use case**: Cloud backup with GCP integration
 
-**Required Environment Variables:**
+**Required environment variables:**
 
 - `GCP_CREDENTIALS_JSON`: Service account credentials JSON
-- `GCP_BUCKET_NAME`: Target storage bucket name
+- `GCP_BUCKET_NAME`: Target GCP storage bucket name
 
-**AWS Storage (`--archive-aws-storage`)**
+##### 4. AWS Storage (`--archive-aws-storage`)
 
-Uploads blocks to an AWS S3 bucket.
+- **Purpose**: Uploads blocks to AWS S3 bucket
+- **Method**: Stores precomputed blocks in Amazon S3
+- **Use case**: Cloud backup with AWS integration
 
-**Required Environment Variables:**
+**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
-- `AWS_SESSION_TOKEN`: Temporary session token for temporary credentials
+- `AWS_DEFAULT_REGION`: AWS region (e.g., `us-west-2`)
 - `MINA_AWS_BUCKET_NAME`: Target S3 bucket name
+- `AWS_SESSION_TOKEN`: Temporary session token (for temporary credentials)
 
 ### Setup and Run