bump OffchainLabs/nitro to v3.0.2 (#77)

* bump OffchainLabs/nitro to v3.0.2

* apply docker tag

append commit hash for proper docker tag `v3.0.2-9efbc16`

* bump checkout version to v4 and adjust workflows, fix formatting of getting started

---------

Co-authored-by: alexpeterson91 <[email protected]>
Co-authored-by: Voss <[email protected]>

.github/workflows/auto_check.yml

@@ -12,7 +12,7 @@ jobs:
   build:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v3
+      - uses: actions/checkout@v4
       - run: npx @dappnode/dappnodesdk github-action bump-upstream
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/build.yml

@@ -7,8 +7,8 @@ jobs:
   build:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v3
-      - run: npx @dappnode/dappnodesdk github-action build
+      - uses: actions/checkout@v4
+      - run: npx @dappnode/dappnodesdk github-action build --provider remote --timeout 1h
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           PINATA_API_KEY: ${{ secrets.PINATA_API_KEY }}

.github/workflows/main.yml

@@ -16,15 +16,19 @@ jobs:
     if: github.event_name != 'push'
     steps:
       - name: Checkout
-        uses: actions/checkout@v3
-      - run: npx @dappnode/dappnodesdk build --provider remote --skip_save
+        uses: actions/checkout@v4
+      - run: npx @dappnode/dappnodesdk build --provider remote --timeout 1h
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          PINATA_API_KEY: ${{ secrets.PINATA_API_KEY }}
+          PINATA_SECRET_API_KEY: ${{ secrets.PINATA_SECRET_API_KEY }}
 
   release:
     name: Release
     runs-on: ubuntu-latest
     if: github.event_name == 'push' || github.event_name == 'repository_dispatch'
     steps:
-      - uses: actions/checkout@v3
+      - uses: actions/checkout@v4
       - name: Publish
         run: npx @dappnode/dappnodesdk publish patch --dappnode_team_preset --timeout 1h
         env:

dappnode_package.json

@@ -8,7 +8,7 @@
     "0xAtum (https://github.com/0xAtum)",
     "Voss <[email protected]> (https://github.com/alexpeterson91)"
   ],
-  "upstreamVersion": "v3.0.0-e6f81cb",
+  "upstreamVersion": "v3.0.2-9efbc16",
   "upstreamRepo": "OffchainLabs/nitro",
   "upstreamArg": "UPSTREAM_VERSION",
   "categories": ["Developer tools", "Blockchain"],

docker-compose.yml

@@ -4,7 +4,7 @@ services:
     build:
       context: build
       args:
-        UPSTREAM_VERSION: v3.0.0-e6f81cb
+        UPSTREAM_VERSION: v3.0.2-9efbc16
     volumes:
       - data:/home/user/.arbitrum
     environment:

getting-started.md

@@ -1,22 +1,22 @@
 
 # Arbitrum One Nitro Node Getting Started
 
-If this is your first time starting this Arbitrum One Nitro Node, you'll need to initialize the DB with pre-nitro blocks for ArbitrumOne. 
+If this is your first time starting this Arbitrum One Nitro Node, you'll need to initialize the DB with pre-nitro blocks for Arbitrum One.
 WHen starting to sync a new install or after wiping the volume of the package it will automatically download the initial database for you before beginning full node sync.
 
 ## Note
 
-If you check the log during the initial download, you'll see `transferred XXXXX / XXXX bytes (X.XX%) [XXX Mbps, -XmXXs remaining]` and then nothing else. 
-It seems like this is stuck but in reality, the messages are just continuing without any jump line (They forgot to add one). 
-You can scroll sideways in the terminal to see progress and ETAs until the initial DB is downloaded and extracted. 
+If you check the log during the initial download, you'll see `transferred XXXXX / XXXX bytes (X.XX%) [XXX Mbps, -XmXXs remaining]` and then nothing else.
+It seems like this is stuck but in reality, the messages are just continuing without any jump line (They forgot to add one).
+You can scroll sideways in the terminal to see progress and ETAs until the initial DB is downloaded and extracted.
 After this step completes, the node starts to fully sync up and acts normally with logs continuing with new lines.
 
 ### More info
 
-You may want to take a look at [Arbitrum's documentation](https://docs.arbitrum.io/node-running/how-tos/running-a-full-node#optional-parameters). 
+You may want to take a look at [Arbitrum's documentation](https://docs.arbitrum.io/node-running/how-tos/running-a-full-node#optional-parameters).
 There are some interesting parameters that you may want to add into the EXTRA_OPTS field.
 
-i.e: `--execution.caching.archive` for a full archive node, or `--init.prune="full"` to prune blocks older than the latest 128 blocks, this will cut storage space roughly in half. 
+i.e: `--execution.caching.archive` for a full archive node, or `--init.prune="full"` to prune blocks older than the latest 128 blocks, this will cut storage space roughly in half.
 But pruning has other consequences if you need data older than that for example relaying this Chain with Pokt or your use case requires block data older than the previous 128 blocks.
 
 Finally there is no protocol level incentive to run a Arbitrum One Nitro Full Node like this package.