Isildur's Bane release/v0.5.0

.github/workflows/golangci-lint.yml

@@ -22,15 +22,15 @@ jobs:
       - name: golangci-lint gas-oracle
         uses: golangci/golangci-lint-action@v2
         with:
-          version: v1.45.2
+          version: v1.51.0
           working-directory: go/gas-oracle
       - name: golangci-lint batch-submitter
         uses: golangci/golangci-lint-action@v2
         with:
-          version: v1.45.2
+          version: v1.51.0
           working-directory: go/batch-submitter
       - name: golangci-lint bss-core
         uses: golangci/golangci-lint-action@v2
         with:
-          version: v1.45.2
+          version: v1.51.0
           working-directory: go/bss-core

.gitignore

@@ -71,3 +71,6 @@ ops_boba/api/metatransaction-api/yarn.lock
 
 #
 packages/boba/contracts/coverage/
+
+packages/boba/account-abstraction/deployments/hardhat/
+packages/boba/bundler_sdk/coverage/

README.md

@@ -76,7 +76,7 @@ You'll need the following:
 * [Docker](https://docs.docker.com/get-docker/)
 * [Docker Compose](https://docs.docker.com/compose/install/)
 
-**Note: this is only relevant to developers who wish to work on Boba core services. For most test uses, e.g. deploying your contracts, it's simpler to use https://rinkeby.boba.network**.
+**Note: this is only relevant to developers who wish to work on Boba core services. For most test uses, e.g. deploying your contracts, it's simpler to use https://goerli.boba.network**.
 
 Clone the repository, open it, and install nodejs packages with `yarn`:
 
@@ -122,7 +122,7 @@ When the command returns with `Pass: Found L2 Liquidity Pool contract address`,
 To run unit tests for a specific package:
 
 ```bash
-cd packages/package-to-test
+cd packages/<package-to-test>
 yarn test
 ```
 

boba_community/boba-node/README.md

@@ -6,13 +6,13 @@ The [boba_community/boba-node](../../boba_community/boba-node) repo runs a repli
 
 1. Running a local Boba node (replica) does not allow you to mine ETH, OMG, or BOBA. There is no mining on L2.
 
-2. If you looking for best possible rpc read data (lowest possible latency) you are **strongly advised** not to run your own node, but to use **https://lightning-replica.boba.network**. This is an autoscaling rpc endpoint that speaks directly to the core Boba L2 geth.
+2. If you looking for best possible rpc read data (lowest possible latency) you are **strongly advised** not to run your own node, but to use **https://replica.boba.network**. This is an autoscaling rpc endpoint that speaks directly to the core Boba L2 geth.
 
 3. The Boba L2 is (at present) a single proposer/sequencer system and the only way to write transactions is via **https://mainnet.boba.network**. You cannot use a local node to write transactions.
 
-4. If your application _does not need autoscaling and low latency_, and can tolerate sync delays, you can run your own Boba node (replica). This replica will try to follow the core L2 geth via data provided by Infura and **https://lightning-replica.boba.network**, so it will necessarily lag behind **https://lightning-replica.boba.network**.
+4. If your application _does not need autoscaling and low latency_, and can tolerate sync delays, you can run your own Boba node (replica). This replica will try to follow the core L2 geth via data provided by Infura and **https://replica.boba.network**, so it will necessarily lag behind **https://replica.boba.network**.
 
-5. Please design your rpc connectors in a resource efficient manner. Notably, calling `eth_getLogs(fromBlock: 0)` 1000 times per second serves no conceivable purpose since the Ethereum blocktime is 12 seconds and the Boba blocktime is > 1 second. All that does is to degrade your replica and trigger rate-limiting and/or IP blocking at **https://lightning-replica.boba.network**.
+5. Please design your rpc connectors in a resource efficient manner. Notably, calling `eth_getLogs(fromBlock: 0)` 1000 times per second serves no conceivable purpose since the Ethereum blocktime is 12 seconds and the Boba blocktime is > 1 second. All that does is to degrade your replica and trigger rate-limiting and/or IP blocking at **https://replica.boba.network**.
 
 ## Prerequisites
 
@@ -30,15 +30,11 @@ $ git clone https://github.com/bobanetwork/boba.git
 $ cd boba_community/boba-node
 ```
 
-**Create a .env file**. Create a  `.env` file in `boba_community/boba-node`.  If you do not have an Infura key, you can obtain one for free from [Infura](https://infura.io) or any other node provider.
+**Create a .env file**. Create a  `.env` file in `boba_community/boba-node`. 
 
 ```yaml
 # release tag
 RELEASE_VERSION=v0.X.X
-
-L1_NODE_WEB3_URL=https://mainnet.infura.io/v3/YOUR_INFURA_KEY # for mainnet
-# Or ...
-L1_NODE_WEB3_URL=https://goerli.infura.io/v3/YOUR_INFURA_KEY # for goerli
 ```
 
 **Pull images**