Use alnt token in bond creation example

Part of [laconicd testnet validator enrollment](cerc-io/testnet-laconicd-stack#19)

Reviewed-on: cerc-io/testnet-laconicd-stack#20
Co-authored-by: Nabarun <nabarun@deepstacksoft.com>
Co-committed-by: Nabarun <nabarun@deepstacksoft.com>

.gitignore

@@ -0,0 +1,6 @@
+venv
+laconic_testnet.egg-info
+__pycache__
+
+*-deployment
+*-spec.yml

README.md

@@ -6,7 +6,12 @@ Stacks to run a node for laconic testnet
 - [laconic-console stack documentation](stack-orchestrator/stacks/laconic-console/README.md) (to run laconic registry CLI and console standalone)
 - [laconic-faucet stack documentation](stack-orchestrator/stacks/laconic-faucet/README.md)
 
-## Testnet onboarding demo
+## ops
 
-Follow steps in [testnet-onboarding-demo.md](./testnet-onboarding-demo.md) to run demo for onboarding testnet participants in laconicd chain
+- [Update deployments after code changes](./ops/update-deployments.md)
+- [Halt stage0 and start stage1](./ops/stage0-to-stage1.md)
+- [Create deployments from scratch (for reference only)](./ops/deployments-from-scratch.md)
 
+## Join LORO testnet
+
+Follow steps in [testnet-onboarding-validator.md](./testnet-onboarding-validator.md) to onboard your participant and join as a validator on the LORO testnet

cli/README.md

@@ -0,0 +1,32 @@
+# cli
+
+## Setup
+
+* Run commands in repo root directory
+  ```bash
+  python3 -m venv venv
+  source ./venv/bin/activate
+  ```
+
+* Install CLI in editable mode
+  ```bash
+  pip install --editable .
+  ```
+
+* Verify installation
+  ```bash
+  laconic-testnet --help
+  ```
+
+## Usage
+
+```bash
+laconic-testnet --onboarded-json path/to/onboarded-accounts.json --subscribers-csv path/to/subscribers.csv --output path/to/subscribed-onboarded-accounts.csv
+```
+
+## Cleanup
+
+Deactivate virtual environment
+```bash
+deactivate
+```

cli/cli.py

@@ -0,0 +1,15 @@
+import click
+from .core import process_subscribers
+
+@click.command()
+@click.option('--onboarded-json', required=True, type=click.Path(exists=True), help='Path to onboarded accounts JSON file.')
+@click.option('--subscribers-csv', required=True, type=click.Path(exists=True), help='Path to the subscribers CSV file.')
+@click.option('--output', required=True, type=click.Path(), help='Path to the output CSV file.')
+def main(onboarded_json, subscribers_csv, output):
+    """
+    CLI tool to match subscriber data with participant data and generate a CSV.
+    """
+    process_subscribers(onboarded_json, subscribers_csv, output)
+
+if __name__ == "__main__":
+    main()

cli/core.py

@@ -0,0 +1,50 @@
+import csv
+import hashlib
+import json
+
+def hash_subscriber_id(subscriber_id):
+    return '0x' + hashlib.sha256(subscriber_id.encode()).hexdigest()
+
+def process_subscribers(onboarded_json, subscribers_csv, output):
+    # Load JSON data from the file
+    with open(onboarded_json, 'r') as json_file:
+        json_data = json.load(json_file)
+
+    # Create a dictionary mapping kyc_id to participant data
+    kyc_map = {participant['kyc_id']: participant for participant in json_data['participants']}
+
+    # Load subscribers data from the CSV file and process it using map
+    with open(subscribers_csv, 'r') as csv_file:
+        csv_reader = csv.DictReader(csv_file)
+        subscribers = list(csv_reader)
+
+    # Use map to process subscribers
+    def process_subscriber(subscriber):
+        hashed_subscriber_id = hash_subscriber_id(subscriber['subscriber_id'])
+        participant = kyc_map.get(hashed_subscriber_id)
+
+        if participant:
+            return {
+                'subscriber_id': subscriber['subscriber_id'],
+                'email': subscriber['email'],
+                'cosmos_address': participant['cosmos_address'],
+                'nitro_address': participant['nitro_address'],
+                'role': participant['role'],
+                'hashed_subscriber_id': participant['kyc_id'],
+                'status': subscriber['status'],
+                'premium': subscriber['premium?'],
+                'created_at': subscriber['created_at']
+            }
+        return None
+
+    # Apply the map function and filter out None values
+    output_data = list(filter(None, map(process_subscriber, subscribers)))
+
+    # Write the matched data to a new CSV file
+    with open(output, 'w', newline='') as csv_file:
+        fieldnames = ['subscriber_id', 'email', 'cosmos_address', 'nitro_address', 'role', 'hashed_subscriber_id', 'status', 'premium', 'created_at']
+        csv_writer = csv.DictWriter(csv_file, fieldnames=fieldnames)
+        csv_writer.writeheader()
+        csv_writer.writerows(output_data)
+
+    print(f'Data has been written to {output}')

ops/deployments-from-scratch.md

@@ -0,0 +1,678 @@
+# Create deployments from scratch (for reference only)
+
+## Login
+
+* Log in as `dev` user on the deployments VM
+
+* All the deployments are placed in the `/srv` directory:
+
+  ```bash
+  cd /srv
+  ```
+
+<details open>
+  <summary>stage0 laconicd</summary>
+
+## stage0 laconicd
+
+* Stack: <https://git.vdb.to/cerc-io/fixturenet-laconicd-stack/src/branch/main/stack-orchestrator/stacks/fixturenet-laconicd>
+
+* Source repo: <https://git.vdb.to/cerc-io/laconicd>
+
+* Target dir: `/srv/laconicd/stage0-deployment`
+
+* Cleanup an existing deployment if required:
+
+  ```bash
+  cd /srv/laconicd
+
+  # Stop the deployment
+  laconic-so deployment --dir stage0-deployment stop --delete-volumes
+
+  # Remove the deployment dir
+  sudo rm -rf stage0-deployment
+
+  # Remove the existing spec file
+  rm stage0-spec.yml
+  ```
+
+### Setup
+
+* Clone the stack repo:
+
+  ```bash
+  laconic-so fetch-stack git.vdb.to/cerc-io/fixturenet-laconicd-stack --pull
+
+  # This should clone the fixturenet-laconicd-stack repo at `/home/dev/cerc/fixturenet-laconicd-stack`
+  ```
+
+* Clone required repositories:
+
+  ```bash
+  laconic-so --stack ~/cerc/fixturenet-laconicd-stack/stack-orchestrator/stacks/fixturenet-laconicd setup-repositories --pull
+
+  # This should clone the laconicd repo at `/home/dev/cerc/laconicd`
+  ```
+
+* Build the container images:
+
+  ```bash
+  laconic-so --stack ~/cerc/fixturenet-laconicd-stack/stack-orchestrator/stacks/fixturenet-laconicd build-containers --force-rebuild
+
+  # This should create the "cerc/laconicd" Docker image
+  ```
+
+### Deployment
+
+* Create a spec file for the deployment:
+
+  ```bash
+  cd /srv/laconicd
+
+  laconic-so --stack ~/cerc/fixturenet-laconicd-stack/stack-orchestrator/stacks/fixturenet-laconicd deploy init --output stage0-spec.yml
+  ```
+
+* Edit network in the spec file to map container ports to host ports:
+
+  ```bash
+  # stage0-spec.yml
+  network:
+    ports:
+      laconicd:
+        - '6060'
+        - '127.0.0.1:26657:26657'
+        - '26656'
+        - '127.0.0.1:9473:9473'
+        - '127.0.0.1:9090:9090'
+        - '127.0.0.1:1317:1317'
+  ```
+
+* Create a deployment from the spec file:
+
+  ```bash
+  laconic-so --stack ~/cerc/fixturenet-laconicd-stack/stack-orchestrator/stacks/fixturenet-laconicd deploy create --spec-file stage0-spec.yml --deployment-dir stage0-deployment
+  ```
+
+* Update the configuration:
+
+  ```bash
+  cat <<EOF > stage0-deployment/config.env
+  # Set to true to enable adding participants functionality of the onboarding module
+  ONBOARDING_ENABLED=true
+
+  # A custom human readable name for this node
+  MONIKER=LaconicStage0
+  EOF
+  ```
+
+### Start
+
+* Start the deployment:
+
+  ```bash
+  laconic-so deployment --dir stage0-deployment start
+  ```
+
+* Check status:
+
+  ```bash
+  # List down the containers and check health status
+  docker ps -a | grep laconicd
+
+  # Follow logs for laconicd container, check that new blocks are getting created
+  laconic-so deployment --dir stage0-deployment logs laconicd -f
+  ```
+
+* Verify that endpoint is now publicly accessible:
+
+  * <https://laconicd.laconic.com> is pointed to the node's RPC endpoint
+
+  * Check status query:
+
+    ```bash
+    curl https://laconicd.laconic.com/status | jq
+
+    # Expected output:
+    # JSON with `node_info`, `sync_info` and `validator_info`
+    ```
+
+</details>
+
+<details open>
+  <summary>faucet</summary>
+
+## faucet
+
+* Stack: <https://git.vdb.to/cerc-io/testnet-laconicd-stack/src/branch/main/stack-orchestrator/stacks/laconic-faucet>
+
+* Source repo: <https://git.vdb.to/cerc-io/laconic-faucet>
+
+* Target dir: `/srv/faucet/laconic-faucet-deployment`
+
+* Cleanup an existing deployment if required:
+
+  ```bash
+  cd /srv/faucet
+
+  # Stop the deployment
+  laconic-so deployment --dir laconic-faucet-deployment stop
+
+  # Remove the deployment dir
+  sudo rm -rf laconic-faucet-deployment
+
+  # Remove the existing spec file
+  rm laconic-faucet-spec.yml
+  ```
+
+### Setup
+
+* Clone the stack repo:
+
+  ```bash
+  laconic-so fetch-stack git.vdb.to/cerc-io/testnet-laconicd-stack --pull
+
+  # This should clone the testnet-laconicd-stack repo at `/home/dev/cerc/testnet-laconicd-stack`
+  ```
+
+* Clone required repositories:
+
+  ```bash
+  laconic-so --stack ~/cerc/testnet-laconicd-stack/stack-orchestrator/stacks/laconic-faucet setup-repositories --pull
+
+  # This should clone the laconicd repo at `/home/dev/cerc/laconic-faucet
+  ```
+
+* Build the container images:
+
+  ```bash
+  laconic-so --stack ~/cerc/testnet-laconicd-stack/stack-orchestrator/stacks/laconic-faucet build-containers --force-rebuild
+
+  # This should create the "cerc/laconic-faucet" Docker image
+  ```
+
+### Deployment
+
+* Create a spec file for the deployment:
+
+  ```bash
+  cd /srv/faucet
+
+  laconic-so --stack ~/cerc/testnet-laconicd-stack/stack-orchestrator/stacks/laconic-faucet deploy init --output laconic-faucet-spec.yml
+  ```
+
+* Edit network in the spec file to map container ports to host ports:
+
+  ```bash
+  # laconic-faucet-spec.yml
+  network:
+    ports:
+      faucet:
+        - '127.0.0.1:4000:3000'
+  ```
+
+* Create a deployment from the spec file:
+
+  ```bash
+  laconic-so --stack ~/cerc/testnet-laconicd-stack/stack-orchestrator/stacks/laconic-faucet deploy create --spec-file laconic-faucet-spec.yml --deployment-dir laconic-faucet-deployment
+
+  # Place in the same namespace as stage0
+  cp /srv/laconicd/stage0-deployment/deployment.yml laconic-faucet-deployment/deployment.yml
+  ```
+
+* Update the configuration:
+
+  ```bash
+  # Get the faucet account key from stage0 deployment
+  export FAUCET_ACCOUNT_PK=$(laconic-so deployment --dir /srv/laconicd/stage0-deployment exec laconicd "echo y | laconicd keys export alice --keyring-backend test --unarmored-hex --unsafe")
+
+  cat <<EOF > laconic-faucet-deployment/config.env
+  CERC_FAUCET_KEY=$FAUCET_ACCOUNT_PK
+  EOF
+  ```
+
+### Start
+
+* Start the deployment:
+
+  ```bash
+  laconic-so deployment --dir laconic-faucet-deployment start
+  ```
+
+* Check status:
+
+  ```bash
+  # List down the containers and check health status
+  docker ps -a | grep faucet
+
+  # Check logs for faucet container
+  laconic-so deployment --dir laconic-faucet-deployment logs faucet -f
+  ```
+
+* Verify that endpoint is now publicly accessible:
+
+  * <https://faucet.laconic.com> is pointed to the faucet endpoint
+
+  * Check faucet:
+
+    ```bash
+    curl -X POST https://faucet.laconic.com/faucet
+
+    # Expected output:
+    # {"error":"address is required"}
+    ```
+
+</details>
+
+<details open>
+  <summary>testnet-onboarding-app</summary>
+
+## testnet-onboarding-app
+
+* Stack: <https://git.vdb.to/cerc-io/testnet-onboarding-app-stack/src/branch/main/stack-orchestrator/stacks/onboarding-app>
+
+* Source repo: <https://git.vdb.to/cerc-io/testnet-onboarding-app>
+
+* Target dir: `/srv/app/onboarding-app-deployment`
+
+* Cleanup an existing deployment if required:
+
+  ```bash
+  cd /srv/app
+
+  # Stop the deployment
+  laconic-so deployment --dir onboarding-app-deployment
+
+  # Remove the deployment dir
+  sudo rm -rf onboarding-app-deployment
+
+  # Remove the existing spec file
+  rm onboarding-app-spec.yml
+  ```
+
+### Setup
+
+* Clone the stack repo:
+
+  ```bash
+  laconic-so fetch-stack git.vdb.to/cerc-io/testnet-onboarding-app-stack --pull
+
+  # This should clone the testnet-onboarding-app-stack repo at `/home/dev/cerc/testnet-onboarding-app-stack`
+  ```
+
+* Clone required repositories:
+
+  ```bash
+  laconic-so --stack ~/cerc/testnet-onboarding-app-stack/stack-orchestrator/stacks/onboarding-app setup-repositories --pull
+
+  # This should clone the testnet-onboarding-app repo at `/home/dev/cerc/testnet-onboarding-app`
+  ```
+
+* Build the container images:
+
+  ```bash
+  laconic-so --stack ~/cerc/testnet-onboarding-app-stack/stack-orchestrator/stacks/onboarding-app build-containers --force-rebuild
+
+  # This should create the Docker image "cerc/testnet-onboarding-app" locally
+  ```
+
+### Deployment
+
+* Create a spec file for the deployment:
+
+  ```bash
+  cd /srv/app
+
+  laconic-so --stack ~/cerc/testnet-onboarding-app-stack/stack-orchestrator/stacks/onboarding-app deploy init --output onboarding-app-spec.yml
+  ```
+
+* Edit network in the spec file to map container ports to host ports:
+
+  ```bash
+  network:
+    ports:
+      testnet-onboarding-app:
+        - '127.0.0.1:3000:80'
+  ```
+
+* Create a deployment from the spec file:
+
+  ```bash
+  laconic-so --stack ~/cerc/testnet-onboarding-app-stack/stack-orchestrator/stacks/onboarding-app deploy create --spec-file onboarding-app-spec.yml --deployment-dir onboarding-app-deployment
+  ```
+
+* Update the configuration:
+
+  ```bash
+  cat <<EOF > onboarding-app-deployment/config.env
+  WALLET_CONNECT_ID=63...
+
+  CERC_REGISTRY_GQL_ENDPOINT="https://laconicd.laconic.com/api"
+  CERC_LACONICD_RPC_ENDPOINT="https://laconicd.laconic.com"
+
+  CERC_FAUCET_ENDPOINT="https://faucet.laconic.com"
+
+  CERC_WALLET_META_URL="https://loro-signup.laconic.com"
+  EOF
+  ```
+
+### Start
+
+* Start the deployment:
+
+  ```bash
+  laconic-so deployment --dir onboarding-app-deployment start
+  ```
+
+* Check status:
+
+  ```bash
+  # List down the container
+  docker ps -a | grep testnet-onboarding-app
+
+  # Follow logs for testnet-onboarding-app container, wait for the build to finish
+  laconic-so deployment --dir onboarding-app-deployment logs testnet-onboarding-app -f
+  ```
+
+* The onboarding app can now be viewed at <https://loro-signup.laconic.com>
+
+</details>
+
+<details open>
+  <summary>laconic-wallet-web</summary>
+
+## laconic-wallet-web
+
+* Stack: <https://git.vdb.to/cerc-io/laconic-wallet-web/src/branch/main/stack/stack-orchestrator/stack/laconic-wallet-web>
+
+* Source repo: <https://git.vdb.to/cerc-io/laconic-wallet-web>
+
+* Target dir: `/srv/wallet/laconic-wallet-web-deployment`
+
+* Cleanup an existing deployment if required:
+
+  ```bash
+  cd /srv/wallet
+
+  # Stop the deployment
+  laconic-so deployment --dir laconic-wallet-web-deployment
+
+  # Remove the deployment dir
+  sudo rm -rf laconic-wallet-web-deployment
+
+  # Remove the existing spec file
+  rm laconic-wallet-web-spec.yml
+  ```
+
+### Setup
+
+* Clone the stack repo:
+
+  ```bash
+  laconic-so fetch-stack git.vdb.to/cerc-io/laconic-wallet-web --pull
+
+  # This should clone the laconic-wallet-web repo at `/home/dev/cerc/laconic-wallet-web`
+  ```
+
+* Build the container images:
+
+  ```bash
+  laconic-so --stack ~/cerc/laconic-wallet-web/stack/stack-orchestrator/stack/laconic-wallet-web build-containers --force-rebuild
+
+  # This should create the Docker image "cerc/laconic-wallet-web" locally
+  ```
+
+### Deployment
+
+* Create a spec file for the deployment:
+
+  ```bash
+  cd /srv/wallet
+
+  laconic-so --stack ~/cerc/laconic-wallet-web/stack/stack-orchestrator/stack/laconic-wallet-web deploy init --output laconic-wallet-web-spec.yml
+  ```
+
+* Edit network in the spec file to map container ports to host ports:
+
+  ```bash
+  network:
+    ports:
+      laconic-wallet-web:
+        - '127.0.0.1:5000:80'
+  ```
+
+* Create a deployment from the spec file:
+
+  ```bash
+  laconic-so --stack ~/cerc/laconic-wallet-web/stack/stack-orchestrator/stack/laconic-wallet-web deploy create --spec-file laconic-wallet-web-spec.yml --deployment-dir laconic-wallet-web-deployment
+  ```
+
+* Update the configuration:
+
+  ```bash
+  cat <<EOF > laconic-wallet-web-deployment/config.env
+  WALLET_CONNECT_ID=63...
+  EOF
+  ```
+
+### Start
+
+* Start the deployment:
+
+  ```bash
+  laconic-so deployment --dir laconic-wallet-web-deployment start
+  ```
+
+* Check status:
+
+  ```bash
+  # List down the container
+  docker ps -a | grep laconic-wallet-web
+
+  # Follow logs for laconic-wallet-web container, wait for the build to finish
+  laconic-so deployment --dir laconic-wallet-web-deployment logs laconic-wallet-web -f
+  ```
+
+* The web wallet can now be viewed at <https://wallet.laconic.com>
+
+</details>
+
+<details open>
+  <summary>stage1 laconicd</summary>
+
+## stage1 laconicd
+
+* Stack: <https://git.vdb.to/cerc-io/fixturenet-laconicd-stack/src/branch/main/stack-orchestrator/stacks/fixturenet-laconicd>
+
+* Source repo: <https://git.vdb.to/cerc-io/laconicd>
+
+* Target dir: `/srv/laconicd/stage1-deployment`
+
+* Cleanup an existing deployment if required:
+
+  ```bash
+  cd /srv/laconicd
+
+  # Stop the deployment
+  laconic-so deployment --dir stage1-deployment stop --delete-volumes
+
+  # Remove the deployment dir
+  sudo rm -rf stage1-deployment
+
+  # Remove the existing spec file
+  rm stage1-spec.yml
+  ```
+
+### Setup
+
+* Same as that for [stage0 laconicd](#setup), not required if already done for stage0
+
+### Deployment
+
+* Create a spec file for the deployment:
+
+  ```bash
+  cd /srv/laconicd
+
+  laconic-so --stack ~/cerc/fixturenet-laconicd-stack/stack-orchestrator/stacks/fixturenet-laconicd deploy init --output stage1-spec.yml
+  ```
+
+* Edit network in the spec file to map container ports to host ports:
+
+  ```bash
+  # stage1-spec.yml
+  network:
+    ports:
+      laconicd:
+        - '6060'
+        - '127.0.0.1:26657:26657'
+        - '26656:26656'
+        - '127.0.0.1:9473:9473'
+        - '127.0.0.1:9090:9090'
+        - '127.0.0.1:1317:1317'
+  ```
+
+* Create a deployment from the spec file:
+
+  ```bash
+  laconic-so --stack ~/cerc/fixturenet-laconicd-stack/stack-orchestrator/stacks/fixturenet-laconicd deploy create --spec-file stage1-spec.yml --deployment-dir stage1-deployment
+  ```
+
+* Update the configuration:
+
+  ```bash
+  cat <<EOF > stage1-deployment/config.env
+  AUTHORITY_AUCTION_ENABLED=true
+  AUTHORITY_AUCTION_COMMITS_DURATION=3600
+  AUTHORITY_AUCTION_REVEALS_DURATION=3600
+  AUTHORITY_GRACE_PERIOD=7200
+
+  MONIKER=LaconicStage1
+  EOF
+  ```
+
+### Start
+
+* Follow [stage0-to-stage1.md](./stage0-to-stage1.md) to halt stage0 deployment, generate the genesis file for stage1 and start the stage1 deployment
+
+</details>
+
+<details open>
+  <summary>laconic-console</summary>
+
+## laconic-console
+
+* Stack: <https://git.vdb.to/cerc-io/testnet-laconicd-stack/src/branch/main/stack-orchestrator/stacks/laconic-console>
+
+* Source repos:
+  * <https://git.vdb.to/cerc-io/laconic-registry-cli>
+  * <https://git.vdb.to/cerc-io/laconic-console>
+
+* Target dir: `/srv/console/laconic-console-deployment`
+
+* Cleanup an existing deployment if required:
+
+  ```bash
+  cd /srv/console
+
+  # Stop the deployment
+  laconic-so deployment --dir laconic-console-deployment stop --delete-volumes
+
+  # Remove the deployment dir
+  sudo rm -rf laconic-console-deployment
+
+  # Remove the existing spec file
+  rm laconic-console-spec.yml
+  ```
+
+### Setup
+
+* Clone the stack repo:
+
+  ```bash
+  laconic-so fetch-stack git.vdb.to/cerc-io/testnet-laconicd-stack --pull
+
+  # This should clone the testnet-laconicd-stack repo at `/home/dev/cerc/testnet-laconicd-stack`
+  ```
+
+* Clone required repositories:
+
+  ```bash
+  laconic-so --stack ~/cerc/testnet-laconicd-stack/stack-orchestrator/stacks/laconic-console setup-repositories --pull
+
+  # This should clone the laconic-registry-cli repo at `/home/dev/cerc/laconic-registry-cli`, laconic-console repo at `/home/dev/cerc/laconic-console`
+  ```
+
+* Build the container images:
+
+  ```bash
+  laconic-so --stack ~/cerc/testnet-laconicd-stack/stack-orchestrator/stacks/laconic-console build-containers --force-rebuild
+
+  # This should create the Docker images: "cerc/laconic-registry-cli", "cerc/webapp-base", "cerc/laconic-console-host"
+  ```
+
+### Deployment
+
+* Create a spec file for the deployment:
+
+  ```bash
+  cd /srv/console
+
+  laconic-so --stack ~/cerc/testnet-laconicd-stack/stack-orchestrator/stacks/laconic-console deploy init --output laconic-console-spec.yml
+  ```
+
+* Edit network in the spec file to map container ports to host ports:
+
+  ```bash
+  network:
+    ports:
+      console:
+        - '127.0.0.1:4001:80'
+  ```
+
+* Create a deployment from the spec file:
+
+  ```bash
+  laconic-so --stack ~/cerc/testnet-laconicd-stack/stack-orchestrator/stacks/laconic-console deploy create --spec-file laconic-console-spec.yml --deployment-dir laconic-console-deployment
+  ```
+
+* Update the configuration:
+
+  ```bash
+  cat <<EOF > laconic-console-deployment/config.env
+  # Laconicd (hosted) GQL endpoint
+  LACONIC_HOSTED_ENDPOINT=https://laconicd.laconic.com
+  EOF
+  ```
+
+### Start
+
+* Start the deployment:
+
+  ```bash
+  laconic-so deployment --dir laconic-console-deployment start
+  ```
+
+* Check status:
+
+  ```bash
+  # List down the container
+  docker ps -a | grep console
+
+  # Follow logs for console container
+  laconic-so deployment --dir laconic-console-deployment logs console -f
+  ```
+
+* The laconic console can now be viewed at <https://loro-console.laconic.com>
+
+</details>
+
+## Domains / Port Mappings
+
+```bash
+laconicd.laconic.com        -> 26657
+laconicd.laconic.com/api    -> 9473/api
+faucet.laconic.com          -> 4000
+loro-signup.laconic.com     -> 3000
+wallet.laconic.com          -> 5000
+loro-console.laconic.com    -> 4001
+```

ops/stage0-to-stage1.md

@@ -0,0 +1,110 @@
+# Halt stage0 and start stage1
+
+Once all the participants have completed their onboarding, stage0 laconicd chain can be halted and stage1 chain can be initialized and started
+
+## Login
+
+* Log in as `dev` user on the deployments VM
+
+* All the deployments are placed in the `/srv` directory:
+
+  ```bash
+  cd /srv
+  ```
+
+## Halt stage0
+
+* Confirm the the currently running node is for stage0 chain:
+
+  ```bash
+  cd /srv/laconicd
+
+  laconic-so deployment --dir stage0-deployment logs laconicd -f --tail 30
+  ```
+
+* List the participants on stage0:
+
+  ```bash
+  laconic-so deployment --dir stage0-deployment exec laconicd "laconicd query onboarding list"
+  ```
+
+* Stop the stage0 deployment:
+
+  ```bash
+  laconic-so deployment --dir stage0-deployment stop
+  ```
+
+## Start stage1
+
+* Use the scripts in fixturenet-laconicd stack to generate genesis file for stage1 using onboarding participants from stage0 chain with token allocations:
+
+  ```bash
+  cd /srv/laconicd
+
+  # Set current working dir path in a variable
+  DEPLOYMENTS_DIR=$(pwd)
+
+  cd ~/cerc/fixturenet-laconicd-stack/stack-orchestrator/stacks/fixturenet-laconicd
+
+  # Generate the genesis file
+  # Participant allocation: 1000000000000 (10^12)
+  # Validator allocation:   2000000000000000 (10^15)
+  ./scripts/generate-stage1-genesis-using-allocations.sh $DEPLOYMENTS_DIR/stage0-deployment 1000000000000 2000000000000000
+
+  # Expected output:
+  # Genesis file for stage1 written to output/genesis.json
+
+  # Remove the temporary data directory
+  sudo rm -rf stage1-genesis
+
+  # Go back to the directory where deployments are created
+  cd $DEPLOYMENTS_DIR
+  ```
+
+* Copy over the generated genesis file (`.json`) containing the onboarding module state with funded participants to data directory in stage1 deployment (`stage1-deployment/data/genesis-config`):
+
+  ```bash
+  cd /srv/laconicd
+
+  cp ~/cerc/fixturenet-laconicd-stack/stack-orchestrator/stacks/fixturenet-laconicd/output/genesis.json stage1-deployment/data/genesis-config/genesis.json
+  ```
+
+* Start the stage1 deployment:
+
+  ```bash
+  laconic-so deployment --dir stage1-deployment start
+  ```
+
+* Check status of stage1 laconicd:
+
+  ```bash
+  # List down the container and check health status
+  docker ps -a | grep laconicd
+
+  # Follow logs for laconicd container, check that new blocks are getting created
+  laconic-so deployment --dir stage1-deployment logs laconicd -f
+  ```
+
+* Query the list of registered participants in stage1 laconicd:
+
+  ```bash
+  laconic-so deployment --dir stage1-deployment exec laconicd "laconicd query onboarding list"
+
+  # Confirm that all onboarded participants on stage0 appear in the list
+  ```
+
+* Get the node's peer adddress and stage1 genesis file to share with the participants:
+
+  * Get the node id:
+
+    ```bash
+    echo $(laconic-so deployment --dir stage1-deployment exec laconicd "laconicd cometbft show-node-id")@laconicd.laconic.com:26656
+    ```
+
+  * Get the genesis file:
+
+    ```bash
+    scp dev@<deployments-server-hostname>:/srv/laconicd/stage1-deployment/data/laconicd-data/config/genesis.json </path/to/local/directory>
+    ```
+
+* Now users can follow the steps to [Join as a validator on stage1](https://git.vdb.to/cerc-io/testnet-laconicd-stack/src/branch/main/testnet-onboarding-validator.md#join-as-a-validator-on-stage1)

ops/update-deployments.md

@@ -0,0 +1,256 @@
+# Update deployments after code changes
+
+Instructions to reset / update the deployments
+
+## Login
+
+* Log in as `dev` user on the deployments VM
+
+* All the deployments are placed in the `/srv` directory:
+
+  ```bash
+  cd /srv
+  ```
+
+## stage0 laconicd
+
+* Deployment dir: `/srv/laconicd/stage0-deployment`
+
+* If code has changed, fetch and build with updated source code:
+
+  ```bash
+  # laconicd source
+  cd ~/cerc/laconicd
+
+  # Pull latest changes, or checkout to the required branch
+  git pull
+
+  # Confirm the latest commit hash
+  git log
+
+  # Rebuild the containers
+  cd /srv/laconicd
+
+  laconic-so --stack ~/cerc/fixturenet-laconicd-stack/stack-orchestrator/stacks/fixturenet-laconicd build-containers --force-rebuild
+  ```
+
+* Optionally, reset the data directory (this will remove all stage0 data!):
+
+  ```bash
+  # Stop the deployment
+  laconic-so deployment --dir stage0-deployment stop --delete-volumes
+
+  # Remove and recreate the required data dir
+  sudo rm -rf stage0-deployment/data/laconicd-data
+  mkdir stage0-deployment/data/laconicd-data
+  ```
+
+* Start the deployment:
+
+  ```bash
+  laconic-so deployment --dir stage0-deployment start
+
+  # Follow logs for laconicd container, check that new blocks are getting created
+  laconic-so deployment --dir stage0-deployment logs laconicd -f
+  ```
+
+* If the stage0 laconicd chain has been reset, reset the faucet deployment too with new faucet key:
+
+  ```bash
+  cd /srv/faucet
+
+  export FAUCET_ACCOUNT_PK=$(laconic-so deployment --dir /srv/laconicd/stage0-deployment exec laconicd "echo y | laconicd keys export alice --keyring-backend test --unarmored-hex --unsafe")
+
+  cat <<EOF > laconic-faucet-deployment/config.env
+  CERC_FAUCET_KEY=$FAUCET_ACCOUNT_PK
+  EOF
+
+  # Stop the deployment
+  laconic-so deployment --dir laconic-faucet-deployment stop --delete-volumes
+
+  # Remove and recreate the required data dir
+  sudo rm -rf laconic-faucet-deployment/data/faucet-data
+  mkdir laconic-faucet-deployment/data/faucet-data
+
+  # Start the deployment
+  laconic-so deployment --dir laconic-faucet-deployment start
+  ```
+
+## testnet-onboarding-app
+
+* Deployment dir: `/srv/app/onboarding-app-deployment`
+
+* If code has changed, fetch and build with updated source code:
+
+  ```bash
+  # testnet-onboarding-app source
+  cd ~/cerc/testnet-onboarding-app
+
+  # Pull latest changes, or checkout to the required branch
+  git pull
+
+  # Confirm the latest commit hash
+  git log
+
+  # Rebuild the containers
+  cd /srv/app
+
+  laconic-so --stack ~/cerc/testnet-onboarding-app-stack/stack-orchestrator/stacks/onboarding-app build-containers --force-rebuild
+  ```
+
+* Update the configuration, if required in `onboarding-app-deployment/config.env`:
+
+  ```bash
+  WALLET_CONNECT_ID=63...
+
+  CERC_REGISTRY_GQL_ENDPOINT="https://laconicd.laconic.com/api"
+  CERC_LACONICD_RPC_ENDPOINT="https://laconicd.laconic.com"
+
+  CERC_FAUCET_ENDPOINT="https://faucet.laconic.com"
+
+  CERC_WALLET_META_URL="https://loro-signup.laconic.com"
+
+  CERC_STAKING_AMOUNT=1000000000000000
+  ````
+
+* Restart the deployment:
+
+  ```bash
+  laconic-so deployment --dir onboarding-app-deployment stop
+
+  laconic-so deployment --dir onboarding-app-deployment start
+
+  # Follow logs for testnet-onboarding-app container, wait for the build to finish
+  laconic-so deployment --dir onboarding-app-deployment logs testnet-onboarding-app -f
+  ```
+
+* The updated onboarding app can now be viewed at <https://loro-signup.laconic.com>
+
+## laconic-wallet-web
+
+* Deployment dir: `/srv/wallet/laconic-wallet-web-deployment`
+
+* If code has changed, fetch and build with updated source code:
+
+  ```bash
+  # testnet-onboarding-app source
+  cd ~/cerc/laconic-wallet-web
+
+  # Pull latest changes, or checkout to the required branch
+  git pull
+
+  # Confirm the latest commit hash
+  git log
+
+  # Rebuild the containers
+  cd /srv/wallet
+
+  laconic-so --stack ~/cerc/laconic-wallet-web/stack/stack-orchestrator/stack/laconic-wallet-web build-containers --force-rebuild
+  ```
+
+* Update the configuration, if required in `laconic-wallet-web-deployment/config.env`:
+
+  ```bash
+  WALLET_CONNECT_ID=63...
+  ```
+
+* Restart the deployment:
+
+  ```bash
+  laconic-so deployment --dir laconic-wallet-web-deployment stop
+
+  laconic-so deployment --dir laconic-wallet-web-deployment start
+
+  # Follow logs for laconic-wallet-web container, wait for the build to finish
+  laconic-so deployment --dir laconic-wallet-web-deployment logs laconic-wallet-web -f
+  ```
+
+* The web wallet can now be viewed at <https://wallet.laconic.com>
+
+## stage1 laconicd
+
+* Deployment dir: `/srv/laconicd/stage1-deployment`
+
+* If code has changed, fetch and build with updated source code:
+
+  ```bash
+  # laconicd source
+  cd ~/cerc/laconicd
+
+  # Pull latest changes, or checkout to the required branch
+  git pull
+
+  # Confirm the latest commit hash
+  git log
+
+  # Rebuild the containers
+  cd /srv/laconicd
+
+  laconic-so --stack ~/cerc/fixturenet-laconicd-stack/stack-orchestrator/stacks/fixturenet-laconicd build-containers --force-rebuild
+  ```
+
+* Optionally, reset the data directory:
+
+  ```bash
+  # Stop the deployment
+  laconic-so deployment --dir stage1-deployment stop --delete-volumes
+
+  # Remove and recreate the required data dirs
+  sudo rm -rf stage1-deployment/data/laconicd-data stage1-deployment/data/genesis-config
+
+  mkdir stage1-deployment/data/laconicd-data
+  mkdir stage1-deployment/data/genesis-config
+  ```
+
+* Update the configuration, if required in `stage1-deployment/config.env`:
+
+  ```bash
+  AUTHORITY_AUCTION_ENABLED=true
+  AUTHORITY_AUCTION_COMMITS_DURATION=3600
+  AUTHORITY_AUCTION_REVEALS_DURATION=3600
+  AUTHORITY_GRACE_PERIOD=7200
+  ```
+
+* Follow [stage0-to-stage1.md](./stage0-to-stage1.md) to generate the genesis file for stage1 and start the deployment
+
+## laconic-console
+
+* Deployment dir: `/srv/console/laconic-console-deployment`
+
+* If code has changed, fetch and build with updated source code:
+
+  ```bash
+  # testnet-onboarding-app source
+  cd ~/cerc/laconic-console
+
+  # Pull latest changes, or checkout to the required branch
+  git pull
+
+  # Confirm the latest commit hash
+  git log
+
+  # Rebuild the containers
+  cd /srv/console
+
+  laconic-so --stack ~/cerc/testnet-laconicd-stack/stack-orchestrator/stacks/laconic-console build-containers --force-rebuild
+  ```
+
+* Update the configuration, if required in `laconic-console-deployment/config.env`:
+
+  ```bash
+  # Laconicd (hosted) GQL endpoint
+  LACONIC_HOSTED_ENDPOINT=https://laconicd.laconic.com
+  ```
+
+* Restart the deployment:
+
+  ```bash
+  laconic-so deployment --dir laconic-console-deployment stop
+
+  laconic-so deployment --dir laconic-console-deployment start
+
+  # Follow logs for console container
+  laconic-so deployment --dir laconic-console-deployment logs console -f
+  ```
+
+* The laconic console can now be viewed at <https://loro-console.laconic.com>

requirements.txt

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

setup.py

@@ -0,0 +1,15 @@
+from setuptools import setup, find_packages
+
+setup(
+    name="laconic-testnet",
+    version="0.1.0",
+    packages=find_packages(),
+    install_requires=[
+        "Click",
+    ],
+    entry_points={
+        'console_scripts': [
+            'laconic-testnet = cli.cli:main',
+        ],
+    },
+)

stack-orchestrator/stacks/testnet-laconicd/README.md

@@ -222,7 +222,7 @@ laconic-so deployment --dir laconic-console-deployment start
   # Edit the staking amount and other fields as required
   # Replace <your-node-moniker> with your node's moniker in command below
 
-  laconic-so deployment --dir testnet-laconicd-deployment exec laconicd 'cat <<EOF > <your-node-moniker>-validator.json
+  laconic-so deployment --dir testnet-laconicd-deployment exec laconicd 'cat <<EOF > my-validator.json
   {
     "pubkey": $(laconicd cometbft show-validator),
     "amount": "900000000alnt",
@@ -238,13 +238,13 @@ laconic-so deployment --dir laconic-console-deployment start
 * Create a validator:
 
   ```bash
-  laconic-so deployment --dir testnet-laconicd-deployment exec laconicd 'laconicd tx staking create-validator <your-node-moniker>-validator.json \
+  laconic-so deployment --dir testnet-laconicd-deployment exec laconicd 'laconicd tx staking create-validator my-validator.json \
   --fees 500000alnt \
   --chain-id=laconic_9000-1 \
   --from <key-name>'
   ```
 
-* View staking validators:
+* View validators:
 
   ```bash
   laconic-so deployment --dir testnet-laconicd-deployment exec laconicd "laconicd query staking validators"
@@ -277,7 +277,7 @@ laconic-so deployment --dir laconic-console-deployment start
 
   ```bash
   # Example
-  laconic-so deployment --dir laconic-console-deployment exec cli "laconic registry bond create --type photon --quantity 1000000000000"
+  laconic-so deployment --dir laconic-console-deployment exec cli "laconic registry bond create --type alnt --quantity 1000000000000"
   ```
 
 ## Clean up

testnet-onboarding-demo.md

@@ -2,8 +2,17 @@
 
 ## Setup
 
+### Stack Orchestrator
+
+- Follow these steps to install laconic-so: <https://git.vdb.to/cerc-io/stack-orchestrator#install>
+
 ### Laconic Wallet
 
+- The `laconic-wallet` can be installed using an APK on an Android device or run as a website using `laconic-wallet-web`
+- Follow one of the following (`Setup On Android` or `Setup As Website`) sections as desired
+
+#### Setup On Android
+
 - Install laconic wallet using [latest APK release](https://git.vdb.to/cerc-io/laconic-wallet/releases)
 
   - Download the APK file in latest release `laconic-wallet-debug.apk`
@@ -12,7 +21,7 @@
 
     - It will need third party installation permission to install the APK
 
-- (Optional) Build laconic wallet from source by following the steps below
+- Alternatively, build laconic wallet from source by following the steps below
 
   - Follow the [Install](https://git.vdb.to/cerc-io/laconic-wallet#install) steps from the laconic-wallet README to setup Android Studio
 
@@ -53,48 +62,124 @@
     cd ../
     ```
 
-### Testnet Onboarding App
+#### Setup As Website
 
-- Clone the repository
+- Use the hosted `laconic-wallet-web` at <https://wallet.laconic.com>
 
-  ```bash
+- Alternatively, setup the `laconic-wallet-web` stack
-  git clone git@git.vdb.to:cerc-io/testnet-onboarding-app.git
-  ```
 
-- Enter the project directory
+  - Clone the stack repo:
-
-  ```bash
-  cd testnet-onboarding-app
-  ```
-
-- Setup .env
-  - Copy and update `.env`
 
     ```bash
-    cp .env.example .env
+    laconic-so fetch-stack git.vdb.to/cerc-io/laconic-wallet-web
     ```
 
-  - In the `.env` file, add the  WalletConnect project ID used in your [laconic-wallet](https://git.vdb.to/cerc-io/laconic-wallet) setup.
+  - Build the container image:
 
     ```bash
-    WALLET_CONNECT_PROJECT_ID=39bc93c...
+    laconic-so --stack ~/cerc/laconic-wallet-web/stack/stack-orchestrator/stack/laconic-wallet-web build-containers
     ```
 
-- Install dependencies
+  - Create a spec file for the deployment:
+
+    ```bash
+    laconic-so --stack ~/cerc/laconic-wallet-web/stack/stack-orchestrator/stack/laconic-wallet-web deploy init --output laconic-wallet-web-spec.yml
+    ```
+
+  - Edit `network` in the spec file to map container ports to host ports as required:
+
+    ```bash
+    network:
+      ports:
+        laconic-wallet-web:
+          - '5000:80'
+    ```
+
+  - Create a deployment from the spec file:
+
+    ```bash
+    laconic-so --stack ~/cerc/laconic-wallet-web/stack/stack-orchestrator/stack/laconic-wallet-web deploy create --spec-file laconic-wallet-web-spec.yml --deployment-dir laconic-wallet-web-deployment
+    ```
+
+  - In the `laconic-wallet-web-deployment/config.env` file, set your wallet connect ProjectId:
+
+    ```bash
+    WALLET_CONNECT_ID=39bc93c...
+    ```
+
+### Testnet Onboarding App and Onboarding API Stacks
+
+- For running the onboarding API, create sumsub application token from <https://cockpit.sumsub.com>
+  - Reference: <https://docs.sumsub.com/docs/app-tokens>
+
+- Clone the stack repo:
 
   ```bash
-  yarn
+  laconic-so fetch-stack git.vdb.to/cerc-io/testnet-onboarding-app-stack
   ```
 
-- Exit project repo
+- Setup required repositories:
 
   ```bash
-  cd ../
+  laconic-so --stack ~/cerc/testnet-onboarding-app-stack/stack-orchestrator/stacks/onboarding-app setup-repositories --pull
+  laconic-so --stack ~/cerc/testnet-onboarding-app-stack/stack-orchestrator/stacks/onboarding-api setup-repositories --pull
   ```
 
-### Stack Orchestrator
+- Build the container image:
 
-- Follow these steps to install laconic-so: <https://git.vdb.to/cerc-io/stack-orchestrator#install>
+  ```bash
+  laconic-so --stack ~/cerc/testnet-onboarding-app-stack/stack-orchestrator/stacks/onboarding-app build-containers --force-rebuild
+  laconic-so --stack ~/cerc/testnet-onboarding-app-stack/stack-orchestrator/stacks/onboarding-api build-containers --force-rebuild
+  ```
+
+- Create spec files for deployments, which will map the stack's ports to the host:
+
+  ```bash
+  laconic-so --stack ~/cerc/testnet-onboarding-app-stack/stack-orchestrator/stacks/onboarding-app deploy init --output onboarding-app-spec.yml
+  laconic-so --stack ~/cerc/testnet-onboarding-app-stack/stack-orchestrator/stacks/onboarding-api deploy init --output onboarding-api-spec.yml
+  ```
+
+- Configure ports:
+
+  - `onboarding-app-spec.yml`:
+
+    ```bash
+    network:
+      ports:
+        testnet-onboarding-app:
+          - '3000:80'
+    ```
+
+  - `onboarding-api-spec.yml`:
+
+    ```bash
+    network:
+      ports:
+        testnet-onboarding-api:
+          - '3001:3000'
+    ```
+
+- Create deployments:
+
+  ```bash
+  laconic-so --stack ~/cerc/testnet-onboarding-app-stack/stack-orchestrator/stacks/onboarding-app deploy create --spec-file onboarding-app-spec.yml --deployment-dir onboarding-app-deployment
+
+  laconic-so --stack ~/cerc/testnet-onboarding-app-stack/stack-orchestrator/stacks/onboarding-api deploy create --spec-file onboarding-api-spec.yml --deployment-dir onboarding-api-deployment
+  ```
+
+- Env configuration:
+  - In the `onboarding-app-deployment/config.env` file, set your wallet connect ProjectId:
+
+    ```bash
+    WALLET_CONNECT_ID=39bc93c...
+    ```
+
+  - In the `onboarding-api-deployment/config.env` file, set your sumsub application token and secret key:
+
+    ```bash
+    SUMSUB_APP_TOKEN=sbx:Xig...
+    SUMSUB_SECRET_KEY=pIue...
+    ```
 
 ### fixturenet-laconicd and laconic-faucet Stacks
 
@@ -325,7 +410,7 @@
     ```
 
 - Create a deployment spec-file for Alice's L1 nitro-node:
-  - Create spec files for the deployment:
+  - Create spec file for the deployment:
 
     ```bash
     laconic-so --stack ~/cerc/nitro-stack/stack-orchestrator/stacks/nitro-node deploy init --output l1alice-nitro-spec.yml
@@ -363,7 +448,7 @@
     ```
 
 - Create a deployment spec-file for Alice's L2 nitro-node:
-  - Create spec files for the deployment:
+  - Create spec file for the deployment:
 
     ```bash
     laconic-so --stack ~/cerc/nitro-stack/stack-orchestrator/stacks/nitro-node deploy init --output l2alice-nitro-spec.yml
@@ -413,10 +498,10 @@
 
     - Check status of L1
 
-      - Run command in intervals of 3 seconds to check if new blocks are created
+      - Run status check:
 
         ```bash
-        laconic-so deployment --dir fixturenet-eth-deployment exec foundry "cast block-number"
+        laconic-so deployment --dir fixturenet-eth-deployment exec fixturenet-eth-bootnode-lighthouse "/scripts/status-internal.sh"
         ```
 
       - Check geth logs to ensure that new blocks are getting created
@@ -433,7 +518,13 @@
 
     NOTE: The `fixturenet-optimism-contracts` service will configure and deploy the Optimism contracts to L1, exiting when complete. This may take several minutes; you can follow the progress by following the container's logs
 
-    - Check L2 logs
+    - Follow optimism contracts deployment logs:
+
+      ```bash
+      laconic-so deployment --dir fixturenet-optimism-deployment logs -f fixturenet-optimism-contracts
+      ```
+
+    - Check L2 logs:
 
       ```bash
       laconic-so deployment --dir fixturenet-optimism-deployment logs -f op-geth
@@ -530,61 +621,70 @@
     laconic-so deployment --dir bridge-deployment exec nitro-contracts "cd packages/nitro-protocol && yarn hardhat transfer --contract $L1_ASSET_ADDRESS --to $C_CHAIN_ADDRESS --amount 1000 --network geth"
     ```
 
-- Start testnet-onboarding-app (run command in testnet-onboarding-app repo)
+- Start `onboarding-app` and `onboarding-api` deployments (run where deployments are created):
 
   ```bash
-  # In testnet-onboarding-app
+  # Builds and serves the app
-  yarn start
+  laconic-so deployment --dir onboarding-app-deployment start
+
+  # Serves the API to generate access tokens
+  laconic-so deployment --dir onboarding-api-deployment start
   ```
 
-  NOTE: Ignore source map warnings in the terminal
+  Check the health status for onboarding-app container:
+
+  ```bash
+  docker ps | grep testnet-onboarding-app
+  ```
+
+  Once the container is healthy, the `testnet-onboarding-app` will be accessible at <http://localhost:3000>
 
 - Run Laconic Wallet
 
-  - Connect your phone with the PC (Make sure that USB debugging is enabled on your phone)
+  - Follow the steps to `Run on Android` or `Run as a website` as per the chosen setup
 
-  - Setup port forwarding for your device using the following command:
+  - Run on Android:
+    - Connect your phone with the PC (Make sure that USB debugging is enabled on your phone)
 
-    ```bash
+    - Setup port forwarding for your device using the following command:
-    # Get device id
-    adb devices
-
-    # Setup port forwarding
-    adb -s <device-id> reverse tcp:26657 tcp:26657
-    ```
-
-  - Open Laconic Wallet app that was installed from the APK
-
-  - (Optional) Start `laconic-wallet` android app (run steps in laconic-wallet repo)
-
-    - Set up the Android device
-      - For a physical device, refer to the [React Native documentation for running on a physical device](https://reactnative.dev/docs/running-on-device)
-      - For a virtual device, continue with the steps
-
-    - Start the application:
 
       ```bash
-      # In laconic-wallet
+      # Get device id
-      yarn start
+      adb devices
+
+      # Setup port forwarding
+      adb -s <device-id> reverse tcp:26657 tcp:26657
       ```
 
-    - Press `a` to run the application on android and wait till the wallet app opens up on your phone
+    - Open Laconic Wallet app that was installed from the APK
+
+    - Alternatively, you can:
+      - Set up the Android device
+        - For a physical device, refer to the [React Native documentation for running on a physical device](https://reactnative.dev/docs/running-on-device)
+        - For a virtual device, continue with the steps
+
+      - Start the application:
+
+        ```bash
+        # In laconic-wallet
+        yarn start
+        ```
+
+      - Press `a` to run the application on android and wait till the wallet app opens up on your phone
+
+  - Alternatively, run as a website:
+    - Open `laconic-wallet-web` at <https://wallet.laconic.com>
+
+    - Alternatively, run the `laconic-wallet-web` stack:
+
+      ```bash
+      laconic-so deployment --dir laconic-wallet-web-deployment start
+      ```
+
+      Open `laconic-wallet-web` at <http://localhost:5000>
 
 ## Demo
 
-- In laconic-wallet app, click on `Create wallet` and add laconicd chain using `Add network` button:
-
-  ```bash
-  Network type - `COSMOS`
-  Chain ID - `laconic_9000-1`
-  Network name - `laconicd`
-  New RPC URL - `http://127.0.0.1:26657`
-  Coin Type - `118`
-  Native Denom - `alnt`
-  Address Prefix - `laconic`
-  Gas Price - `1`
-  ```
-
 - Start the stack for stage 0 laconicd (run command in directory where stage0-deployment had been created)
 
   ```bash
@@ -594,6 +694,14 @@
   laconic-so deployment --dir stage0-deployment logs laconicd -f
   ```
 
+- In laconic-wallet, click on `Create wallet` and update the `laconicd` network using `Edit Network` button:
+
+  ```bash
+  Network name    - laconicd
+  New RPC URL     - http://127.0.0.1:26657
+  Gas Price       - 1
+  ```
+
 - Run laconic-faucet:
 
   - Get private key of funded faucet account from stage 0 laconicd chain:
@@ -628,7 +736,7 @@
     export BRIDGE_ADDRESS=$(laconic-so deployment --dir bridge-deployment exec nitro-bridge "jq -r '.\"42069\"[0].contracts.Bridge.address' /app/deployment/nitro-addresses.json")
     ```
 
-- In the wallet, add 2 accounts (Alice and Charlie) for both the networks (ethereum and laconicd) by selecting the network and clicking on `Add account`
+- In the wallet, add 2 accounts (Alice and Charlie) for both the networks (`Ethereum` and `laconicd`) by selecting the network and clicking on `Add account`
 
 - Get Ethereum private keys for accounts Alice and Charlie from wallet using the `Show private key` link (to be used as statechannel PKs)
 
@@ -784,7 +892,7 @@
   - Create ledger channel between A and Bridge with custom token
 
     ```bash
-    laconic-so deployment --dir l1alice-nitro-deployment exec nitro-rpc-client "nitro-rpc-client direct-fund $BRIDGE_NITRO_ADDRESS --assetAddress $L1_ASSET_ADDRESS -p 4005 -h nitro-node"
+    laconic-so deployment --dir l1alice-nitro-deployment exec nitro-rpc-client "nitro-rpc-client direct-fund $BRIDGE_NITRO_ADDRESS --assetAddress $L1_ASSET_ADDRESS --alphaAmount 1000000 --betaAmount 1000000 -p 4005 -h nitro-node"
     ```
 
     - Once direct-fund objective is complete, bridge will create mirrored channel on L2
@@ -814,7 +922,7 @@
   - Create ledger channel between C and Bridge with custom token
 
     ```bash
-    laconic-so deployment --dir l1charlie-nitro-deployment exec nitro-rpc-client "nitro-rpc-client direct-fund $BRIDGE_NITRO_ADDRESS --assetAddress $L1_ASSET_ADDRESS -p 4005 -h nitro-node"
+    laconic-so deployment --dir l1charlie-nitro-deployment exec nitro-rpc-client "nitro-rpc-client direct-fund $BRIDGE_NITRO_ADDRESS --assetAddress $L1_ASSET_ADDRESS --alphaAmount 1000000 --betaAmount 1000000 -p 4005 -h nitro-node"
     ```
 
     - Once direct fund objective is complete, bridge will create mirrored channel on L2
@@ -861,16 +969,23 @@
 
 - Onboard participants
   - Open the `testnet-onboarding-app` at <http://localhost:3000>
-  - Connect to the testnet-onboarding app by clicking on the WalletConnect icon on the top right corner in the wallet and scanning QR code of the app
+  - Read and accept the `Terms and Conditions`
-  - Choose Alice's nitro and laconicd account to onboard
+  - Connect testnet-onboarding app to the wallet:
+    - Click on `CONNECT WALLET` button on the testnet-onboarding app
+    - Click on the WalletConnect icon on the top right corner in the wallet
+      - If using the wallet Android app, scan the QR code from the onboarding app
+      - If using the wallet website, enter WalletConnect URI for pairing
+  - In the onboarding app, choose Alice's nitro and laconicd account to onboard
     - Use nitro accounts for which ledger channels have been created on L2
   - Sign using the nitro key
     - Approve sign request on Wallet
-  - Fund the laconic account by clicking on the `REQUEST TOKENS FROM FAUCET` button
+  - Perform the user verification steps
-  - Send transaction request to the Wallet
+  - Select the desired participant role (`Validator` or `Participant`) and accept the onboarding terms and conditions
-    - Approve and send transaction to laconicd chain
+  - In the next step, fund your laconic account by clicking on the `REQUEST TOKENS FROM FAUCET` button; ensure that the displayed balance is updated
+  - Send transaction request to the wallet
+    - From wallet, approve and send transaction to laconicd chain
   - Repeat onboarding for other (Charlies's) account by clicking on the web app header "Testnet Onboarding"
-  - List the participants on stage 1 (run in the directory where laconicd deployment was  created):
+  - List the participants on stage 0 (run in the directory where laconicd deployment was created):
 
     ```bash
     laconic-so deployment --dir stage0-deployment exec laconicd "laconicd query onboarding list"
@@ -892,13 +1007,16 @@
   - Use the scripts in fixturenet-laconicd stack to generate genesis file for stage 1 with token allocations:
 
     ```bash
+    # Set current working dir path in a variable
+    DEPLOYMENTS_DIR=$(pwd)
+
     cd ~/cerc/fixturenet-laconicd-stack/stack-orchestrator/stacks/fixturenet-laconicd
 
     # Fetch account holdings from bridge
-    ./scripts/fetch-account-holdings.sh <bridge-deployment-absolute-path> eth-account-holdings.json
+    ./scripts/fetch-account-holdings.sh $DEPLOYMENTS_DIR/bridge-deployment eth-account-holdings.json
 
     # Generate the genesis file
-    ./scripts/generate-stage1-genesis.sh <stage0-deployment-absolute-path> eth-account-holdings.json
+    ./scripts/generate-stage1-genesis.sh $DEPLOYMENTS_DIR/stage0-deployment eth-account-holdings.json
 
     # Expected output:
     # Genesis file for stage1 written to output/genesis.json
@@ -986,7 +1104,7 @@
   #   ID: '0xb29aeb32c9495a793ebf7bd116232075d1e7bfe89fc82281c7d498e3ffd3e3bf',
   #   Status: 'Open',
   #   Balance: {
-  #     AssetAddress: '<Token address on L2>',
+  #     AssetAddress: '0x0000000000000000000000000000000000000000',
   #     Payee: '0xa8d2d06ace9c7ffc24ee785c2695678aecdfd7a0',
   #     Payer: '0xaaa6628ec44a8a742987ef3a114ddfe2d4f7adce',
   #     PaidSoFar: 0n,
@@ -1128,7 +1246,27 @@
 - Reset wallet and stop the app:
   - In laconic-wallet, click on the `Reset Wallet` button to disconnect all apps and clear the accounts
 
-  - Stop (`Ctrl+C`) both `laconic-wallet` and `testnet-onboarding-app`
+  - Stop (`Ctrl+C`) the `laconic-wallet` if running locally in dev mode
+
+  - Stop and cleanup the `laconic-wallet-web` deployment:
+
+    ```bash
+    # Run where deployments are created
+    laconic-so deployment --dir laconic-wallet-web-deployment stop
+
+    sudo rm -rf laconic-wallet-web-deployment
+    ```
+
+  - Stop and cleanup the `onboarding-app` and `onboarding-api` deployments:
+
+    ```bash
+    # Run where deployments are created
+    laconic-so deployment --dir onboarding-app-deployment stop
+    laconic-so deployment --dir onboarding-api-deployment stop
+
+    sudo rm -rf onboarding-app-deployment
+    sudo rm -rf onboarding-api-deployment
+    ```
 
 - Clean up stage 0 and stage 1 laconicd deployments:
   - Stop deployment and remove volumes:

testnet-onboarding-validator.md

@@ -0,0 +1,285 @@
+# testnet-onboarding-validator
+
+## Onboard as a participant / validator on stage0
+
+* Visit <https://wallet.laconic.com/> and click on `Create wallet`
+  * Save the mnemonic for further usage
+
+* Register your laconic address as a participant using the [Onboarding App](https://loro-signup.laconic.com)
+
+  * Read and accept the `Terms and Conditions`
+
+  * On next page, enter your email to register to join the LORO testnet
+
+  * Visit the confirmation link sent on the registered email (email delivery might take a few minutes)
+
+    * It should take you to the `Testnet Onboarding` app
+
+    * Note: The confirmation link will only work the first time, visit <https://loro-signup.laconic.com/sign-with-nitro-key> for further attempts if required
+
+  * Connect testnet-onboarding app to the wallet:
+
+    * Click on `CONNECT WALLET` button on the testnet-onboarding app
+
+    * Click on the WalletConnect icon on the top right corner in the wallet
+
+      * If using the wallet website, enter WalletConnect URI for pairing
+
+  * In the onboarding app, choose your nitro and laconicd account to onboard
+
+  * Sign using the nitro key
+
+    * Approve sign request on Wallet
+
+  * Select the desired participant role (`Validator` or `Participant`) and accept the onboarding terms and conditions
+
+  * In the next step, fund your laconic account by clicking on the `REQUEST TOKENS FROM FAUCET` button; ensure that the displayed balance is updated
+
+  * Send transaction request to the wallet
+
+    * From wallet, approve and send transaction to stage0 laconicd chain
+
+## Join as a validator on stage1
+
+### Prerequisites
+
+* Minimum hardware requirements:
+
+  ```bash
+  RAM: 8-16GB
+  Disk space: 200GB
+  CPU: 2 cores
+  ```
+
+* Testnet genesis file and peer node address
+
+* Mnemonic from the [wallet](https://wallet.laconic.com)
+
+* Participant onboarded on stage0
+
+### Setup
+
+* Clone the stack repo:
+
+  ```bash
+  laconic-so fetch-stack git.vdb.to/cerc-io/testnet-laconicd-stack
+  ```
+
+* Clone required repositories:
+
+  ```bash
+  laconic-so --stack ~/cerc/testnet-laconicd-stack/stack-orchestrator/stacks/testnet-laconicd setup-repositories --pull
+
+  # If this throws an error as a result of being already checked out to a branch/tag in a repo, remove the repositories and re-run the command
+  ```
+
+* Build the container images:
+
+  ```bash
+  laconic-so --stack ~/cerc/testnet-laconicd-stack/stack-orchestrator/stacks/testnet-laconicd build-containers
+  ```
+
+  This should create the following docker images locally:
+
+  * `cerc/laconicd`
+
+### Create a deployment
+
+* Create a spec file for the deployment:
+
+  ```bash
+  laconic-so --stack ~/cerc/testnet-laconicd-stack/stack-orchestrator/stacks/testnet-laconicd deploy init --output testnet-laconicd-spec.yml
+  ```
+
+* Edit `network` in the spec file to map container ports to host ports as required:
+
+  ```bash
+  # testnet-laconicd-spec.yml
+  ...
+  network:
+    ports:
+      laconicd:
+        - '6060:6060'
+        - '26657:26657'
+        - '26656:26656'
+        - '9473:9473'
+        - '9090:9090'
+        - '1317:1317'
+  ```
+
+* Create the deployment from the spec file:
+
+  ```bash
+  laconic-so --stack ~/cerc/testnet-laconicd-stack/stack-orchestrator/stacks/testnet-laconicd deploy create --spec-file testnet-laconicd-spec.yml --deployment-dir testnet-laconicd-deployment
+  ```
+
+* Copy over the published testnet genesis file (`.json`) to data directory in deployment (`testnet-laconicd-deployment/data/laconicd-data/tmp`):
+
+  ```bash
+  # Example
+  mkdir -p testnet-laconicd-deployment/data/laconicd-data/tmp
+  cp genesis.json testnet-laconicd-deployment/data/laconicd-data/tmp/genesis.json
+  ```
+
+### Configuration
+
+* Inside the `testnet-laconicd-deployment` deployment directory, open `config.env` file and set following env variables:
+
+  ```bash
+  # Comma separated list of nodes to keep persistent connections to
+  # Example: "node-1-id@laconicd.laconic.com:26656"
+  # Use the provided node id
+  CERC_PEERS=""
+
+  # A custom human readable name for this node
+  CERC_MONIKER=
+  ```
+
+### Start the deployment
+
+```bash
+laconic-so deployment --dir testnet-laconicd-deployment start
+```
+
+### Check status
+
+* To list down and monitor the running containers:
+
+  ```bash
+  # With status
+  docker ps -a
+
+  # Follow logs for laconicd container
+  laconic-so deployment --dir testnet-laconicd-deployment logs laconicd -f
+  ```
+
+* Check the sync status of your node:
+
+  ```bash
+  laconic-so deployment --dir testnet-laconicd-deployment exec laconicd "laconicd status | jq .sync_info"
+
+  # `catching_up: false` indicates that node is completely synced
+  ```
+
+* After the node has caught up, view current list of validators:
+
+  ```bash
+  laconic-so deployment --dir testnet-laconicd-deployment exec laconicd "laconicd query staking validators"
+  ```
+
+  * Confirm that in the list of validators, your node moniker does not exist
+
+### Join as testnet validator
+
+* Open the wallet: <https://wallet.laconic.com/>
+
+* Create a validator from the onboarding app:
+
+  * Visit the [validator creation](https://loro-signup.laconic.com/validator) page
+
+    * If required, connect testnet-onboarding app to the wallet with which onboarding was done on stage0
+
+  * Select the Laconic account (same as the one used while onboarding) using which you wish to send the create validator request
+
+    * This should display the details of your onboarded participant
+
+    * You can proceed if the participant has `validator` role
+
+  * Enter your node's moniker (use the same one used while [configuring](#configuration) the `testnet-laconicd-deployment`)
+
+  * Fetch and enter your validator's pubkey:
+
+    ```bash
+    laconic-so deployment --dir testnet-laconicd-deployment exec laconicd "laconicd cometbft show-validator" | jq -r .key
+    ```
+
+  * Send the transaction request to wallet
+
+    * From wallet, approve and send transaction to stage1 laconicd chain
+
+* Alternatively, create a validator using the laconicd CLI:
+
+  * Import a key pair:
+
+    ```bash
+    KEY_NAME=alice
+
+    # Restore existing key with mnemonic seed phrase
+    # You will be prompted to enter mnemonic seed
+    laconic-so deployment --dir testnet-laconicd-deployment exec laconicd "laconicd keys add $KEY_NAME --recover"
+
+    # Query the keystore for your account's address
+    laconic-so deployment --dir testnet-laconicd-deployment exec laconicd "laconicd keys show $KEY_NAME -a"
+    ```
+
+  * Check balance for your account:
+
+    ```bash
+    laconic-so deployment --dir testnet-laconicd-deployment exec laconicd "laconicd query bank balances <account-address>"
+    ```
+
+  * Create required validator configuration:
+
+    ```bash
+    # Note:
+    # Edit the staking amount and other fields as required
+    # Replace <your-node-moniker> with your node's moniker in command below
+
+    laconic-so deployment --dir testnet-laconicd-deployment exec laconicd 'cat <<EOF > my-validator.json
+    {
+      "pubkey": $(laconicd cometbft show-validator),
+      "amount": "1000000000000000alnt",
+      "moniker": "<your-node-moniker>",
+      "commission-rate": "0.1",
+      "commission-max-rate": "0.2",
+      "commission-max-change-rate": "0.01",
+      "min-self-delegation": "1"
+    }
+    EOF'
+    ```
+
+  * Create a validator:
+
+    ```bash
+    laconic-so deployment --dir testnet-laconicd-deployment exec laconicd "laconicd tx staking create-validator my-validator.json \
+    --fees 500000alnt \
+    --chain-id=laconic_9000-1 \
+    --from $KEY_NAME"
+    ```
+
+* View validators:
+
+  ```bash
+  laconic-so deployment --dir testnet-laconicd-deployment exec laconicd "laconicd query staking validators"
+  ```
+
+  * Check that in the list of validators `<your-node-moniker>` exists
+
+* View validator set:
+
+  ```bash
+  laconic-so deployment --dir testnet-laconicd-deployment exec laconicd "laconicd query consensus comet validator-set"
+  ```
+
+### Clean up
+
+* Stop all `testnet-laconicd` services running in the background:
+
+  ```bash
+  # Stop the docker containers
+  laconic-so deployment --dir testnet-laconicd-deployment stop
+  ```
+
+* To stop all services and also delete data:
+
+  ```bash
+  # Stop the docker containers
+  laconic-so deployment --dir testnet-laconicd-deployment stop --delete-volumes
+
+  # Remove deployment directory (deployment will have to be recreated for a re-run)
+  sudo rm -r testnet-laconicd-deployment
+  ```
+
+## Troubleshooting
+
+* If you face any issues in the onboarding app or the web-wallet, clear your browser cache and reload