Add Stablenet Repl and Minor Docs (#403)

This patch makes it easy to connect to Stablenet via `chains> yarn repl -c stablenet`. Then you can see everything on stablenet, submit extrinsics, etc.

We additionally take a quick pass at the docs to improve them with our current state. There is more work to be done, but I've removed some truly outdated documentation and replaced some items with now-correct versions.

Author: hayesgm

Diff for: Dockerfile

@@ -10,7 +10,7 @@ RUN git clone --depth 1 https://github.com/compound-finance/gateway.git -b hayes
 WORKDIR /code/gateway
 
 RUN scripts/pull_release.sh m16
-RUN chmod +x releases/m16/gateway-linux-x86 
+RUN chmod +x releases/m16/gateway-linux-x86
 
 CMD releases/m16/gateway-linux-x86 \
   --chain chains/stablenet/chain-spec-raw.json \

Diff for: README.md

@@ -29,17 +29,17 @@ Once the development environment is set up, build Gateway. This command will bui
 [native](https://substrate.dev/docs/en/knowledgebase/advanced/executor#native-execution) code:
 
 ```bash
-cargo +nightly build --release
+cargo build --release
 ```
 
-Note that we require the rust `nightly` toolchain as we rely on unstable features (notably `const_generics`).
+Note: that we require the rust `nightly` toolchain as we rely on unstable features (notably `const_generics`). You should make `nightly` your default rust toolchain.
 
 ## Test
 
 To test, run:
 
 ```sh
-SKIP_WASM_BUILD=true cargo test --features stubnet
+cargo test -- -Z unstable-options --test-threads 1
 ```
 
 ## Run
@@ -206,34 +206,25 @@ A FRAME pallet is compromised of a number of blockchain primitives:
 
 ### Run in Docker
 
-First, install [Docker](https://docs.docker.com/get-docker/) and
-[Docker Compose](https://docs.docker.com/compose/install/).
+First, install [Docker](https://docs.docker.com/get-docker/).
 
-Then run the following command to start a single node development chain.
+Then build the Dockerfile:
 
-```bash
-./scripts/docker_run.sh
+```sh
+docker build -t gateway .
 ```
 
-This command will firstly compile your code, and then start a local development network. You can
-also replace the default command (`cargo +nightly build --release && ./target/release/gateway --dev --ws-external`)
-by appending your own. A few useful ones are as follow.
-
-```bash
-# Run Substrate node without re-compiling
-./scripts/docker_run.sh ./target/release/gateway --dev --ws-external
+Next, start your chain:
 
-# Purge the local dev chain
-./scripts/docker_run.sh ./target/release/gateway purge-chain --dev
-
-# Check whether the code is compilable
-./scripts/docker_run.sh cargo +nightly check
+```sh
+docker run --rm -it gateway -- /bin/sh
 ```
 
 ## Release Process
 
 All upgrades to Gateway should happen via the release process.
 We need to track which features were included in the release, usually including a changelog that covers each PR that was merged.
+
 Proper release management is important here, especially since releases include many varieties of breaking changes.
 A scenario test should be written to show that things work as expected after the upgrade takes place.
 The goal is to not break things on release.
@@ -244,67 +235,44 @@ Releases should be cut from the `develop` (default) branch on [Github](https://g
 
 First increment the spec version in `runtime/src/lib.rs`.
 
-### Update Chain Spec
-
-Note: this is *only* necessary if you are deploying a new chain, the chain spec is defined at genesis.
+### Build Your Release Version
 
-The WASM blob in the chain spec should be updated via:
-
-```
-$ CHAIN_BIN=target/<MILESTONE TAG>/gateway-<PLATFORM> chains/build_spec.js -s -c testnet
+```sh
+scripts/build_release.sh m88 # replace with your milestone version
 ```
 
-Where `<PLATFORM>` is your local platform used to name the binary build.
+### Update the Dockerfile
 
-### Using Github Workflows Release Process (Easier -- Recommended)
+Replace the release in the Dockerfile, using your tag (e.g. here `m88`):
 
-Github actions have been created to respond to git tags that are pushed to the repo that begin with `m`, followed by the spec version, e.g. `m3`.
-
-This process will create a draft/prerelease that can be modified and published on github once ready.
-
-Create a tag and push to this repo:
-
-```sh
-$ git tag -a <MILESTONE TAG> <OPTIONAL COMMIT HASH>
-$ git push origin <MILESTONE TAG>
+```diff
+- RUN scripts/pull_release.sh m16
+- RUN chmod +x releases/m16/gateway-linux-x86
++ RUN scripts/pull_release.sh m88
++ RUN chmod +x releases/m88/gateway-linux-x86
 ```
 
-### Manual Release Process
-
-Cutting a release can also be accomplished manually by following the steps below.
-
-#### Build Release Artifacts
+### Update Chain Spec
 
-Build the release artifacts using the included script:
+Note: this is *only* necessary if you are deploying a new chain, the chain spec is defined at genesis.
 
 ```
-$ scripts/build_release.sh <MILESTONE TAG>
+$ gateway> chains/build_spec.js -r m88 -c stablenet # replace m88 with your version
 ```
 
-Where `<MILESTONE TAG>` should be a sequentially increasing counter beginning with `m`, followed by the spec version, e.g. `m7`, `m8`, `m9`.
-
-#### Upload Release Artifacts
+### Using Github Workflows Release Process
 
-The changes above should be committed to the `develop` branch and included in the version that is tagged in the repository below.
+Github actions have been created to respond to git tags that are pushed to the repo that begin with `m`, followed by the spec version, e.g. `m88`.
 
-Draft a [new release on GitHub](https://github.com/compound-finance/gateway/releases/new).
-Tag it with the appropriate milestone tag.
-Title it in a style similar to other releases, describing its purpose.
-Put any other context or information describing what it does in the description.
+This process will create a draft / pre-release that can be modified and published on github once ready.
 
-Attach the following files to the release, from the repository where you built the release artifacts:
+Create a tag and push to this repo:
 
-```
-contracts.json
-gateway-darwin-arm64           # optional
-gateway-darwin-arm64.checksum  # optional
-gateway-testnet.wasm
-gateway-testnet.wasm.checksum
-rpc.json
-types.json
+```sh
+$ git tag -a m88 # use your milestone tag
+$ git push origin m88
 ```
 
-These files should all exist in the `releases/<MILESTONE TAG>` directory of the repository you built from,
- you should be able to simply drag and drop them.
+### Contributing
 
-This will, in the future, be automated by the process of merging certain release branches into the main development branch.
+Contributors are welcome, and will be held to a high standard. Please consider making an issue to discuss larger changes before making pull requests. All contributions will fall under the license on this repo, which **currently does not grant open permission of use**. Additionally, **you agree that your code will be subject to any license which is later attached to this repository as if it had been initially licensed thusly**.

Diff for: chains/README.md

@@ -25,6 +25,12 @@ Then:
 yarn repl -c testnet
 ```
 
+Or:
+
+```sh
+yarn repl -c stablenet
+```
+
 This will connect you to a REPL to testnet, including to the Ethereum contracts.
 
 ### Repl Examples

Diff for: chains/stablenet/chain-config.json

@@ -1,8 +1,8 @@
 {
   "eth_network": "goerli",
   "base_chain": "testnet",
-  "websocket": "wss://sarge.compound.cash",
-  "rpc": "http://sarge-rpc.compound.cash:5000",
+  "websocket": "wss://sally.compound.cash",
+  "rpc": "http://sally-rpc.compound.cash:2095",
   "validators": [
     {
       "substrate_id": "5H6Wzjt1nQ5aFx5E4FDVnpYDCWb1JHcQSwHgdqUyiiZUdbc9",