Merge branch 'main' into node16

Author: pdyraga

.github/workflows/contracts.yml

@@ -57,6 +57,15 @@ jobs:
           node-version: "14.x"
           cache: "yarn"
 
+      # This step forces Git to download dependencies using `https://` protocol,
+      # even if `yarn.json` refers to some package via `git://`. Using `git://`
+      # is no longer supported by GH. One of the `coverage-pools` dependencies
+      # by default uses `git://` and we needed to manually remove it every time
+      # it re-appeares in the lock file. Now even if it does re-appear, the
+      # `yarn install --frozen-lockfile` will not fail.
+      - name: Configure git to don't use unauthenticated protocol
+        run: git config --global url."https://".insteadOf git://
+
       - name: Install dependencies
         run: yarn install
 
@@ -76,6 +85,15 @@ jobs:
           cache: "yarn"
           registry-url: "https://registry.npmjs.org"
 
+      # This step forces Git to download dependencies using `https://` protocol,
+      # even if `yarn.json` refers to some package via `git://`. Using `git://`
+      # is no longer supported by GH. One of the `coverage-pools` dependencies
+      # by default uses `git://` and we needed to manually remove it every time
+      # it re-appeares in the lock file. Now even if it does re-appear, the
+      # `yarn install --frozen-lockfile` will not fail.
+      - name: Configure git to don't use unauthenticated protocol
+        run: git config --global url."https://".insteadOf git://
+
       - name: Install dependencies
         run: yarn install --frozen-lockfile
 
@@ -156,6 +174,15 @@ jobs:
           node-version: "14.x"
           cache: "yarn"
 
+      # This step forces Git to download dependencies using `https://` protocol,
+      # even if `yarn.json` refers to some package via `git://`. Using `git://`
+      # is no longer supported by GH. One of the `coverage-pools` dependencies
+      # by default uses `git://` and we needed to manually remove it every time
+      # it re-appeares in the lock file. Now even if it does re-appear, the
+      # `yarn install --frozen-lockfile` will not fail.
+      - name: Configure git to don't use unauthenticated protocol
+        run: git config --global url."https://".insteadOf git://
+
       - name: Install needed dependencies
         run: yarn install --frozen-lockfile
 
@@ -186,6 +213,15 @@ jobs:
           node-version: "14.x"
           cache: "yarn"
 
+      # This step forces Git to download dependencies using `https://` protocol,
+      # even if `yarn.json` refers to some package via `git://`. Using `git://`
+      # is no longer supported by GH. One of the `coverage-pools` dependencies
+      # by default uses `git://` and we needed to manually remove it every time
+      # it re-appeares in the lock file. Now even if it does re-appear, the
+      # `yarn install --frozen-lockfile` will not fail.
+      - name: Configure git to don't use unauthenticated protocol
+        run: git config --global url."https://".insteadOf git://
+
       - name: Install dependencies
         run: yarn install
 
@@ -207,11 +243,11 @@ jobs:
 
       - uses: actions/setup-python@v4
         with:
-          python-version: 3.8.5
+          python-version: 3.10.8
 
       - name: Install Solidity
         env:
-          SOLC_VERSION: 0.8.5 # according to solidity.version in hardhat.config.js
+          SOLC_VERSION: 0.8.9 # according to solidity.version in hardhat.config.ts
         run: |
           pip3 install solc-select
           solc-select install $SOLC_VERSION

.github/workflows/format.yml

@@ -18,6 +18,13 @@ jobs:
           node-version: "14"
           cache: "yarn"
 
+      # This step forces Git to download dependencies using `https://` protocol,
+      # even if `yarn.json` refers to some package via `git://`. Using `git://`
+      # is no longer supported by GH. One of the `coverage-pools` dependencies
+      # by default uses `git://` and we needed to manually remove it every time
+      # it re-appeares in the lock file. Now even if it does re-appear, the
+      # `yarn install --frozen-lockfile` will not fail.
+
       - name: Install dependencies
         run: yarn install
 

.github/workflows/npm.yml

@@ -24,11 +24,21 @@ jobs:
           registry-url: "https://registry.npmjs.org"
           cache: "yarn"
 
+      # This step forces Git to download dependencies using `https://` protocol,
+      # even if `yarn.json` refers to some package via `git://`. Using `git://`
+      # is no longer supported by GH. One of the `coverage-pools` dependencies
+      # by default uses `git://` and we needed to manually remove it every time
+      # it re-appeares in the lock file. Now even if it does re-appear, the
+      # `yarn install --frozen-lockfile` will not fail.
+      - name: Configure git to don't use unauthenticated protocol
+        run: git config --global url."https://".insteadOf git://
+
       - name: Resolve latest contracts
         run: |
-          yarn upgrade \
+          yarn upgrade --exact \
             @keep-network/keep-core \
-            @keep-network/tbtc
+            @keep-network/tbtc \
+            @threshold-network/solidity-contracts
 
       # Deploy contracts to a local network to generate deployment artifacts that
       # are required by dashboard compilation.

README.adoc

@@ -2,6 +2,8 @@
 
 = Coverage pool
 
+https://github.com/keep-network/coverage-pools/actions/workflows/contracts.yml[image:https://img.shields.io/github/actions/workflow/status/keep-network/coverage-pools/contracts.yml?branch=main&event=push&label=Coverage%20pool%20contracts%20build[Coverage pool contracts build status]]
+
 A governable, fee-earning asset pool to cover low-likelihood on-chain events.
 
 toc::[]
@@ -89,6 +91,19 @@ yarn build
 ```
 Compiled contracts will land in the `build/` directory.
 
+*NOTE:* The `coverage-pools` package contains an indirect dependency to
+`@summa-tx/[email protected]` package, which downloads one of its sub-dependencies
+via unathenticated `git://` protocol. That protocol is no longer supported by
+GitHub. This means that in certain situations installation of the package or
+update of its dependencies using Yarn may result in `The unauthenticated git
+protocol on port 9418 is no longer supported` or `unable to connect to
+github.com` error. +
+As a workaround, we advise changing Git configuration to use `https://` protocol
+instead of `git://` by executing:
+```
+git config --global url."https://".insteadOf git://
+```
+
 === Test contracts
 
 There are multiple test scenarios living in the `test` directory.

artifacts/.chainId

@@ -0,0 +1 @@
+1