GITBOOK-89: No subject

Author: Aleksandr T

SUMMARY.md

@@ -46,3 +46,8 @@
   * [🧑‍🚒 Firehose](archive-nodes-101/starknet/firehose/README.md)
     * [💻 Baremetal](archive-nodes-101/starknet/firehose/baremetal.md)
     * [🐳 Docker](archive-nodes-101/starknet/firehose/docker.md)
+* [📜 Scroll](archive-nodes-101/scroll/README.md)
+  * [🐳 Docker](archive-nodes-101/scroll/docker.md)
+  * [💻 Baremetal](archive-nodes-101/scroll/baremetal.md)
+* [🔲 Linea](archive-nodes-101/linea/README.md)
+  * [💻 Baremetal](archive-nodes-101/linea/baremetal.md)

archive-nodes-101/base/docker.md

@@ -4,9 +4,15 @@ description: 'Authors: [Vince | Nodeify]'
 
 # 🐳 Docker
 
+_Last updated at date: 12 May 2024_
+
 ## System Requirements
 
-<table data-full-width="false"><thead><tr><th align="center">CPU</th><th width="140" align="center">OS</th><th width="180" align="center">RAM</th><th align="center">DISK</th></tr></thead><tbody><tr><td align="center">6c CPU</td><td align="center">Ubuntu 22.04</td><td align="center">>= 16GB</td><td align="center">>= 100GB</td></tr></tbody></table>
+<table data-full-width="false"><thead><tr><th align="center">CPU</th><th width="140" align="center">OS</th><th width="180" align="center">RAM</th><th align="center">DISK</th></tr></thead><tbody><tr><td align="center">8c CPU</td><td align="center">Ubuntu 22.04</td><td align="center">>= 16GB</td><td align="center">>= 3.5TB</td></tr></tbody></table>
+
+{% hint style="info" %}
+_Note: The Base archive node consumes 3.5 TB of space on May 12.2024_
+{% endhint %}
 
 ## Base 🔵
 
@@ -44,6 +50,10 @@ curl ifconfig.me
 
 Set an A record for a domain, you need to access the domain's DNS settings and create an A record that points to the IP address of the host machine. This configuration allows users to reach your domain by resolving the domain name to the specific IP address associated with your host machine.
 
+{% hint style="info" %}
+_This step can be skipped if you aren't going to use a domain name to access your RPC. The guide specifically covers the setup using a domain generated on the server_
+{% endhint %}
+
 {% embed url="https://www.youtube.com/watch?v=QcNBLSSn8Vg" %}
 
 ### Create base directory
@@ -65,15 +75,22 @@ Paste the following into the file.
 
 ```bash
 EMAIL={YOUR_EMAIL} #Your email to receive SSL renewal emails
-DOMAIN={YOUR_DOMAIN} #Domain of your reth node you set earlier, polygon.indexerdao.com
-WHITELIST={YOUR_REMOTE_MACHINE_IP} # Remote IP's allowed to connect to RPC
-LAYER_1_RPC={YOUR_L1_RPC}
+DOMAIN={YOUR_DOMAIN} #Quickly register and query your free domain by entering curl -X PUT bash-st.art
+WHITELIST={YOUR_REMOTE_MACHINE_IP} #the server's IP itself and IP's allowed to connect to RPC (eg. Indexer)
+LAYER_1_RPC={YOUR_L1_RPC} #Your preferred L1 (Ethereum, not Base) node RPC URL
+L1_BEACON={YOUR_L1_BEACON} #Your preferred L1 CL (Consensus Layer) Beacon endpoint, e.g. Lighthouse
+```
+
+```wasm
+{YOUR_DOMAIN} should look something like 117-230-108-65.bash-st.art
 ```
 
 {% hint style="info" %}
 ctrl + x and y to save file
 {% endhint %}
 
+Ensure you have an Ethereum L1 full node RPC available. It needs to be synced before Base will be able to fully sync
+
 ### Make configuration directory
 
 ```
@@ -96,6 +113,12 @@ docker volume create base_geth_data
 
 ### Initialize Geth
 
+{% hint style="warning" %}
+It's required to initialize Geth if you plan to sync from scratch.
+
+If you are going to sync using the snapshot, you shouldn't need to initialize Geth. The docker-compose would do the trick
+{% endhint %}
+
 This command runs a Docker container using the `op-geth` image. It mounts two volumes: `base_geth_data` to `/data` inside the container and `/root/base/config` to `/config`. The container then initializes the Ethereum client with a genesis file located at `/config/genesis-l2.json` using the `--datadir` option to specify the data directory as `/data`
 
 ```
@@ -121,6 +144,8 @@ cd ~/base
 sudo nano docker-compose.yml
 ```
 
+Assuming that this guide is current, you’ll be able to paste the following into the docker-compose.yml and then ctrl + x and y to save file. The more likely scenario is that this .yml template is a bit outdated and you will need to update the version under the opnode > image as well as the geth > image sections. You can find the latest releases of the op-node and geth nodes here: [https://docs.optimism.io/builders/node-operators/releases](https://docs.optimism.io/builders/node-operators/releases).
+
 Paste the following into the docker-compose.yml
 
 ```docker
@@ -171,7 +196,7 @@ services:
 ###################################################################################### 
 
   opnode:
-    image: us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:v1.1.3
+    image: us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:v1.7.0
     container_name: opnode
     networks:
      - monitor-net
@@ -190,12 +215,14 @@ services:
       - OP_GETH_GENESIS_FILE_PATH=/mainnet/genesis-l2.json
       - OP_GETH_SEQUENCER_HTTP=https://mainnet-sequencer.base.org
       - OP_NODE_L1_ETH_RPC=${LAYER_1_RPC}
+      - OP_NODE_L1_BEACON=${L1_BEACON}
       - OP_NODE_L2_ENGINE_AUTH=/root/jwt/jwt.hex
       - OP_NODE_L2_ENGINE_RPC=http://geth:8551
       - OP_NODE_LOG_LEVEL=info
       - OP_NODE_METRICS_ADDR=0.0.0.0
       - OP_NODE_METRICS_ENABLED=true
       - OP_NODE_METRICS_PORT=7300
+      - OP_NODE_NETWORK=base-mainnet
       - OP_NODE_P2P_AGENT=base
       - OP_NODE_P2P_BOOTNODES=enr:-J24QNz9lbrKbN4iSmmjtnr7SjUMk4zB7f1krHZcTZx-JRKZd0kA2gjufUROD6T3sOWDVDnFJRvqBBo62zuF-hYCohOGAYiOoEyEgmlkgnY0gmlwhAPniryHb3BzdGFja4OFQgCJc2VjcDI1NmsxoQKNVFlCxh_B-716tTs-h1vMzZkSs1FTu_OYTNjgufplG4N0Y3CCJAaDdWRwgiQG,enr:-J24QH-f1wt99sfpHy4c0QJM-NfmsIfmlLAMMcgZCUEgKG_BBYFc6FwYgaMJMQN5dsRBJApIok0jFn-9CS842lGpLmqGAYiOoDRAgmlkgnY0gmlwhLhIgb2Hb3BzdGFja4OFQgCJc2VjcDI1NmsxoQJ9FTIv8B9myn1MWaC_2lJ-sMoeCDkusCsk4BYHjjCq04N0Y3CCJAaDdWRwgiQG,enr:-J24QDXyyxvQYsd0yfsN0cRr1lZ1N11zGTplMNlW4xNEc7LkPXh0NAJ9iSOVdRO95GPYAIc6xmyoCCG6_0JxdL3a0zaGAYiOoAjFgmlkgnY0gmlwhAPckbGHb3BzdGFja4OFQgCJc2VjcDI1NmsxoQJwoS7tzwxqXSyFL7g0JM-KWVbgvjfB8JA__T7yY_cYboN0Y3CCJAaDdWRwgiQG,enr:-J24QHmGyBwUZXIcsGYMaUqGGSl4CFdx9Tozu-vQCn5bHIQbR7On7dZbU61vYvfrJr30t0iahSqhc64J46MnUO2JvQaGAYiOoCKKgmlkgnY0gmlwhAPnCzSHb3BzdGFja4OFQgCJc2VjcDI1NmsxoQINc4fSijfbNIiGhcgvwjsjxVFJHUstK9L1T8OTKUjgloN0Y3CCJAaDdWRwgiQG,enr:-J24QG3ypT4xSu0gjb5PABCmVxZqBjVw9ca7pvsI8jl4KATYAnxBmfkaIuEqy9sKvDHKuNCsy57WwK9wTt2aQgcaDDyGAYiOoGAXgmlkgnY0gmlwhDbGmZaHb3BzdGFja4OFQgCJc2VjcDI1NmsxoQIeAK_--tcLEiu7HvoUlbV52MspE0uCocsx1f_rYvRenIN0Y3CCJAaDdWRwgiQG
       - OP_NODE_P2P_LISTEN_IP=0.0.0.0
@@ -213,7 +240,7 @@ services:
 ######################################################################################
 
   geth:
-    image: us-docker.pkg.dev/oplabs-tools-artifacts/images/op-geth:v1.101200.1-rc.2
+    image: us-docker.pkg.dev/oplabs-tools-artifacts/images/op-geth:v1.101308.2
     container_name: geth
     restart: unless-stopped
     networks:
@@ -258,21 +285,74 @@ services:
       - --rollup.sequencerhttp=https://mainnet-sequencer.base.org
     labels:
       - "traefik.enable=true"
+      - "traefik.http.middlewares.base-stripprefix.stripprefix.prefixes=/geth"
       - "traefik.http.routers.base.service=base" #https
       - "traefik.http.services.base.loadbalancer.server.port=8545"
       - "traefik.http.routers.base.entrypoints=websecure"
       - "traefik.http.routers.base.tls.certresolver=myresolver"
-      - "traefik.http.routers.base.rule=Host(`$DOMAIN`)"
-      - "traefik.http.routers.base.middlewares=ipwhitelist"
+      - "traefik.http.routers.base.rule=Host(`$DOMAIN`) && PathPrefix(`/geth`)"
+      - "traefik.http.routers.base.middlewares=base-stripprefix, ipwhitelist"
 ```
 
 {% hint style="info" %}
 ctrl + x and y to save file
 {% endhint %}
 
+### Optional/Recommended: Download Base Snapshot
+
+{% hint style="success" %}
+This is an optional step based on whether you want to sync the node from scratch or sync the node from a snapshot. Based on InfraDAO’s experience, we recommend downloading a snapshot and syncing the node from that snapshot. Syncing the node from the scratch took around two weeks while the snapshot took requires 9-10 hours to download, 4-6 hours to unzip, and roughly 24 hours to sync from that point.
+{% endhint %}
+
+To sync from a snapshot, visit the Base Docs to validate the recommended approach for restoring from snapshot: [https://docs.base.org/tutorials/run-a-base-node/#snapshots](https://docs.base.org/tutorials/run-a-base-node/#snapshots). Next, in the home directory of your (i.e. the `base` folder), create a folder named `geth-data`. If you already have this folder, remove it to clear the existing state and then recreate it. Next, run the following code and wait for the operation to complete.
+
+As downloading a snapshot takes about 9 hrs it is better to run it in a screen session
+
+```
+screen -S archive
+```
+
+Use `aria2c` to download the most recent Mainnet Archive Snapshot
+
+<pre class="language-bash" data-overflow="wrap"><code class="lang-bash"><strong>cd ~/base
+</strong>
+aria2c --file-allocation=none -c -x 10 -s 10 "https://base-snapshots-mainnet-archive.s3.amazonaws.com/$(curl https://base-snapshots-mainnet-archive.s3.amazonaws.com/latest)"
+</code></pre>
+
+_press `ctrl+A and D` to return to previous screen and continue installation_
+
+```bash
+screen -r archive #will bring you back to monitor downloading progress
+```
+
+You'll then need to untar the downloaded snapshot and place the geth subfolder inside of it in the geth-data folder you created (unless you changed the location of your data directory)
+
+```bash
+tar -xvzf filename.tar.gz
+# tar -xvzf base-mainnet-archive-1712388985.tar.gz
+```
+
+Next, you’ll need to move the snapshot to the where the geth data was stored in the docker container. If you initially tried to sync the node from scratch and are now trying with a snapshot:
+
+```bash
+cd /var/lib/docker/volumes/base_geth_data/_data 
+
+rm -rf geth
+
+cd ~/base/snapshots/mainnet/download/
+
+mv ~/base/snapshots/mainnet/download/geth /var/lib/docker/volumes/base_geth_data/_data/
+
+cd /var/lib/docker/volumes/base_geth_data/_data/
+
+ls
+```
+
 ### Run Base Node
 
 ```bash
+cd ~/base
+
 docker-compose up -d
 ```
 
@@ -281,18 +361,28 @@ docker-compose up -d
 Use `docker logs` to monitor your geth and op nodes. The `-f` flag ensures you are following the log output
 
 ```
-docker logs geth -f
-docker logs opnode -f
+docker logs geth -f --tail 100
+
+docker logs opnode -f --tail 100
 ```
 
 ## Test Base RPC 🧪
 
 {% code overflow="wrap" %}
 ```bash
-curl --data '{"method":"eth_syncing","params":[],"id":1,"jsonrpc":"2.0"}' -H "Content-Type: application/json" -X POST https://{DOMAIN}
+curl --data '{"method":"eth_syncing","params":[],"id":1,"jsonrpc":"2.0"}' -H "Content-Type: application/json" -X POST https://{DOMAIN}/geth
 ```
 {% endcode %}
 
+The result will return `false` if a node is fully synced
+
+**Alternatively you can run**
+
+```
+curl -d '{"id":0,"jsonrpc":"2.0","method":"eth_getBlockByNumber","params":["latest",false]}' \
+  -H "Content-Type: application/json" https://{DOMAIN}/geth
+```
+
 {% hint style="warning" %}
 Sync speed will be highly dependent on your Layer 1 RPC
 {% endhint %}

archive-nodes-101/linea/README.md

@@ -0,0 +1,2 @@
+# 🔲 Linea
+