Merge remote-tracking branch 'origin/master' into pxrl/refactor2

Author: pxrl

.circleci/config.yml

@@ -2,7 +2,7 @@ version: 2.1
 jobs:
   install:
     docker:
-      - image: cimg/node:20.19.2
+      - image: cimg/node:22.18.0
     working_directory: ~/relayer-v2
     resource_class: medium+
     steps:
@@ -21,7 +21,7 @@ jobs:
             - node_modules
   test:
     docker:
-      - image: cimg/node:20.19.2
+      - image: cimg/node:22.18.0
     working_directory: ~/relayer-v2
     resource_class: medium+
     parallelism: 20
@@ -105,7 +105,7 @@ jobs:
             yarn test --bail $(cat /tmp/test-files)
   lint:
     docker:
-      - image: cimg/node:20.19.2
+      - image: cimg/node:22.18.0
     working_directory: ~/relayer-v2
     resource_class: medium+
     steps:

.env.example

@@ -269,7 +269,7 @@ RELAYER_TOKENS='["0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2", "0xA0b86991c6218b
 # and ARWEAVE_GATEWAY must be set to valid values.
 PERSIST_DATA_TO_ARWEAVE=false
 
-# This wallet JWK is used to sign transactions intended for permenant storage of bundle
+# This wallet JWK is used to sign transactions intended for permanent storage of bundle
 # data on Arweave. Ensure that the wallet has enough AR to cover the cost of storage.
 ARWEAVE_WALLET_JWK=$({"kty":"", "e":"", "n":"", "d":"", "p":"", "q":"", "dp":"", "dq":"", "qi":""})
 

.github/workflows/dependency-review.yml

@@ -12,3 +12,6 @@ jobs:
         uses: actions/checkout@v4
       - name: "Dependency Review"
         uses: actions/[email protected]
+        with:
+          allow-ghsas: |
+            GHSA-h755-8qp9-cq85

.github/workflows/deploy.yml

@@ -10,3 +10,6 @@ jobs:
       - name: Curl build and deploy webhook for GCP for UMA protocol repo
         run: ${{ secrets.PROTOCOL_BUILD_DEPLOY_WEBHOOK }}
         shell: bash
+      - name: Curl build and deploy webhook for GCP for UMA across repo
+        run: ${{ secrets.ACROSS_BUILD_DEPLOY_WEBHOOK }}
+        shell: bash

.github/workflows/publish.yml

@@ -10,7 +10,7 @@ jobs:
       # Setup .npmrc file to publish to npm
       - uses: actions/setup-node@v4
         with:
-          node-version: "20"
+          node-version: "22.18"
           registry-url: "https://registry.npmjs.org"
           cache: "yarn"
       - run: yarn

.gitignore

@@ -26,3 +26,6 @@ addresses.json
 
 # AI context files
 CLAUDE.md
+
+# yalc
+.yalc

CODEOWNERS

@@ -6,4 +6,4 @@
 
 # These owners will be the default owners for everything in
 # the repo unless a later match takes precedence.
-*       @mrice32 @nicholaspai @pxrl @james-a-morris @dohaki @bmzig
+* @mrice32 @nicholaspai @pxrl @dohaki @bmzig

Dockerfile

@@ -1,6 +1,6 @@
-FROM node:20
+FROM node:22.18
 
-WORKDIR /relayer
+WORKDIR /across-relayer
 
 COPY . ./
 

README.md

@@ -17,7 +17,7 @@ Check out [this guide](https://docs.across.to/relayers/running-a-relayer) for de
 
 ## Prerequisites
 
-To install dependencies successfully, node version should be higher or equal to v20.18.0 && lower than v22. After installing dependencies and building the repository, be sure to [install RedisDB](https://redis.io/docs/getting-started/installation/), an in-memory storage layer that is required to make the bots work. The bots query blockchain RPCs for a lot of smart contract events so it's important that the bot
+To install dependencies successfully, node version should be higher or equal to v20.18.0 && lower than v22. After installing dependencies and building the repository, be sure to [install RedisDB](https://redis.io/docs/latest/get-started), an in-memory storage layer that is required to make the bots work. The bots query blockchain RPCs for a lot of smart contract events so it's important that the bot
 cache some of this data in order to maintain its speed.
 
 The first time that the bot runs, it might be slower than usual as the Redis DB fills up. This slowdown should disappear on subsequent runs.
@@ -81,19 +81,20 @@ To test local changes to the SDK alongside this repository you can use `yalc`:
 npm install -g yalc
 ```
 
-2. Inside the `@across-protocol/sdk` directory, publish the local SDK to your local yalc server:
+2. Inside the `@across-protocol/sdk` directory, watch for changes and publish the local SDK to your local yalc server:
 
 ```sh
-yalc publish
+yalc yalc:watch
 ```
 
-3. Link the local SDK in this repository:
+3. Add/Link the local SDK in this repository:
 
 ```sh
 yalc add @across-protocol/sdk
 ```
+use `yalc link @across-protocol/sdk` if you dont want yalc to modify package.json file
 
-To make updates to the SDK, you can run `yalc update @across-protocol/sdk` in this repository.
+Any changes to the SDK will be automatically published to your local yalc server.
 
 Once you are done testing, you can remove the local SDK by running `yalc remove @across-protocol/sdk` in this repository.
 

STYLE.md

@@ -0,0 +1,8 @@
+This repo adpots [Google TypeScript Style Guide](https://google.github.io/styleguide/tsguide.html) for the sake of consistency and clarity of code.
+
+In addition to the style guide above, the following principles should be followed:
+- functions should be short, < 100 LOC
+- files should be short, < 1000 LOC
+- functions should rarely have more than a couple of indentations within them, e.g. max 3. If there's more, it's usually a sign that functionality can be extracted to a separate function with readable name
+- within the same file / class, there should be minimal redundancy
+- comment line length should not exceed the configured max code line length: 120 characters