Merge branch 'main' into patch-1

Author: dkijania

.github/dependabot.yml

@@ -0,0 +1,10 @@
+version: 2
+updates:
+  - package-ecosystem: "npm"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"

.github/workflows/algolia-search.yml

@@ -21,7 +21,7 @@ jobs:
     runs-on: ubuntu-latest
     needs: [wait-for-vercel]
     steps:
-      - uses: actions/checkout@v2
+      - uses: actions/checkout@v4
       - name: Run algolia/docsearch-scraper
         run: |
           docker pull algolia/docsearch-scraper

.github/workflows/o1js-api-reference.yml

@@ -6,18 +6,18 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Setup Node
-        uses: actions/setup-node@v3
+        uses: actions/setup-node@v4
         with:
           # In case of version change, update README.md accordingly
           node-version: 16
 
       - name: Checkout Docs repo
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
         with:
           path: docs
 
       - name: Checkout o1js repo
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
         with:
           repository: o1-labs/o1js
           path: o1js

.github/workflows/validate-docker-images.yml

@@ -0,0 +1,34 @@
+name: Validate Docker Images
+
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+    branches:
+      - main
+    paths:
+      - 'docs/**/*.mdx'
+      - 'docs/**/*.md'
+      - 'scripts/validate-docker-images.js'
+      - '.github/workflows/validate-docker-images.yml'
+  workflow_dispatch: {}
+
+jobs:
+  validate-docker-images:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 22
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Validate Docker images in documentation
+        run: npm run validate-docker-images

docs/berkeley-upgrade/archive-migration/docker-example.mdx

@@ -42,7 +42,7 @@ psql -c "CREATE DATABASE mainnet_balances_migrated;"
 psql -c "CREATE DATABASE mainnet_really_migrated;"
 
 # Retrieve Archive Node Backup
-wget https://673156464838-mina-archive-node-backups.s3.us-west-2.amazonaws.com/mainnet/mainnet-archive-dump-2024-04-29_0000.sql.tar.gz
+wget https://storage.googleapis.com/mina-archive-dumps/mainnet-archive-dump-2024-04-29_0000.sql.tar.gz
 tar -xf mainnet-archive-dump-2024-04-29_0000.sql.tar.gz
 
 # Replace the database name in the dump
@@ -57,7 +57,7 @@ psql mainnet_really_migrated -f create_schema.sql
 # Start migration
 docker create --name mainnet-db-migration \
        -v $(pwd)/mainnet-migration:/data \
-       --network mainnet gcr.io/o1labs-192920/mina-archive-migration:3.0.1-e848ecb-bullseye -- bash -c '
+       --network mainnet minaprotocol/mina-archive-migration:3.0.1-e848ecb-bullseye -- bash -c '
         wget http://673156464838-mina-genesis-ledgers.s3-website-us-west-2.amazonaws.com/mainnet/genesis_ledger.json; mina-berkeley-migration-script initial \
           --genesis-ledger genesis_ledger.json \
           --source-db postgres://mina:minamina@postgres:5432/mainnet_balances_migrated \

docs/berkeley-upgrade/archive-migration/mainnet-database-maintenance.mdx

@@ -76,7 +76,7 @@ apt-get install --allow-downgrades -y "mina-archive-maintenance=$VERSION"
 To get the Docker image:
 
 ```sh
-docker pull gcr.io/o1labs-192920/mina-archive-maintenance:1.4.1
+docker pull minaprotocol/mina-archive-maintenance:1.4.1-060f0a5-bullseye
 ```
 
 ## Usage for missing or invalid nonces

docs/berkeley-upgrade/flags-configs.mdx

@@ -24,7 +24,7 @@ Git SHA-1
 ae112d3a96fe71b4ccccf3c54e7b7494db4898a4
 
 Seed List
-https://storage.googleapis.com/mina-seed-lists/mainnet_seeds.txt
+https://bootnodes.minaprotocol.com/networks/mainnet.txt
 
 Node build
 https://github.com/MinaProtocol/mina/releases/tag/3.0.3
@@ -42,7 +42,7 @@ mina daemon
 --generate-genesis-proof true
 --libp2p-keypair <keyfile path>
 --log-json
---peer-list-url https://storage.googleapis.com/mina-seed-lists/mainnet_seeds.txt
+--peer-list-url https://bootnodes.minaprotocol.com/networks/mainnet.txt
 
 ENVIRONMENT VARIABLES
 RAYON_NUM_THREADS=6
@@ -60,7 +60,7 @@ mina daemon
 --file-log-rotations 500
 --libp2p-keypair <keyfile path>
 --log-json
---peer-list-url https://storage.googleapis.com/mina-seed-lists/mainnet_seeds.txt
+--peer-list-url https://bootnodes.minaprotocol.com/networks/mainnet.txt
 --run-snark-coordinator <public key>
 --snark-worker-fee 0.001
 --work-selection [seq|rand|roffset]
@@ -100,7 +100,7 @@ mina daemon
 --generate-genesis-proof true
 --libp2p-keypair <keyfile path>
 --log-json
---peer-list-url https://storage.googleapis.com/mina-seed-lists/mainnet_seeds.txt
+--peer-list-url https://bootnodes.minaprotocol.com/networks/mainnet.txt
 
 ENVIRONMENT VARIABLES
 MINA_LIBP2P_PASS

docs/exchange-operators/faq.mdx

@@ -26,7 +26,7 @@ The latest third-party audit reports are publicly available here:
 
 :::note
 
-Any news and updates related to exchange listing shared by the Mina Foundation are on [www.minaprotocol.com](https://minaprotocol.com) or the official [Mina Protocol]](https://x.com/MinaProtocol) X (Twitter). Mina Foundation cannot individually answer any listing questions.
+Any news and updates related to exchange listing shared by the Mina Foundation are on [www.minaprotocol.com](https://minaprotocol.com) or the official [Mina Protocol](https://x.com/MinaProtocol) X (Twitter). Mina Foundation cannot individually answer any listing questions.
 
 :::
 

docs/exchange-operators/index.mdx

@@ -29,7 +29,7 @@ Use Rosetta API if you are:
 - Integrating the Mina blockchain with your exchange
 - Building blockchain applications, such as explorers and wallets
 
-Using Rosetta for building your application is preferrable, as it's API is more appropriate for applications and far more stable than GraphQL.
+Using Rosetta for building your application is preferable, as it's API is more appropriate for applications and far more stable than GraphQL.
 
 
 - [Running with Docker](/exchange-operators/rosetta/run-with-docker) - How to install Rosetta from Docker image
@@ -49,4 +49,4 @@ For answers to the most frequently asked questions about listing MINA, see [FAQ
 
 ## Questions?
 
-Post any questions in Mina’s Github Discussions: https://github.com/MinaProtocol/mina/discussions
+Post any questions in Mina’s Github Discussions: https://github.com/MinaProtocol/mina/discussions

docs/exchange-operators/rosetta/build-from-sources.mdx

@@ -21,7 +21,7 @@ If you already have mina-archive up and running, you can also build and run the
 
 :::tip
 
-To run mina daemon and mina-archive natively, follow the [Archive Node page](node-operators/archive-node/getting-started) instructions.
+To run mina daemon and mina-archive natively, follow the [Archive Node page](/node-operators/archive-node/getting-started) instructions.
 
 :::