Compare commits
4
Commits
| Author | SHA1 | Date | |
|---|---|---|---|
 prathamesh
|
2691274351 | ||
 IshaVenikar
|
2830ca81b5 | ||
|
IshaVenikar
|
b2ea5dc050 | ||
 
|
a5623ba854 |
@@ -12,7 +12,42 @@ Instructions for running a laconicd testnet full node and joining as a validator
|
||||
CPU: 2 cores
|
||||
```
|
||||
|
||||
* Testnet genesis file (file or an URL) and peer node addresses
|
||||
* Testnet genesis file and peer node address
|
||||
|
||||
* Mnemonic from the [wallet](https://wallet.laconic.com)
|
||||
|
||||
### Participant Onboarded
|
||||
|
||||
* 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`
|
||||
|
||||
* 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 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 laconicd chain
|
||||
|
||||
## Setup
|
||||
|
||||
@@ -25,31 +60,19 @@ Instructions for running a laconicd testnet full node and joining as a validator
|
||||
* Clone required repositories:
|
||||
|
||||
```bash
|
||||
# laconicd
|
||||
laconic-so --stack ~/cerc/testnet-laconicd-stack/stack-orchestrator/stacks/testnet-laconicd setup-repositories --pull
|
||||
|
||||
# laconic cli and console
|
||||
laconic-so --stack ~/cerc/testnet-laconicd-stack/stack-orchestrator/stacks/laconic-console 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
|
||||
# laconicd
|
||||
laconic-so --stack ~/cerc/testnet-laconicd-stack/stack-orchestrator/stacks/testnet-laconicd build-containers
|
||||
|
||||
# laconic cli and console
|
||||
laconic-so --stack ~/cerc/testnet-laconicd-stack/stack-orchestrator/stacks/laconic-console build-containers
|
||||
```
|
||||
|
||||
This should create the following docker images locally:
|
||||
|
||||
* `cerc/laconicd`
|
||||
* `cerc/laconic-registry-cli`
|
||||
* `cerc/webapp-base`
|
||||
* `cerc/laconic-console-host`
|
||||
|
||||
## Create a deployment
|
||||
|
||||
@@ -57,11 +80,9 @@ Instructions for running a laconicd testnet full node and joining as a validator
|
||||
|
||||
```bash
|
||||
laconic-so --stack ~/cerc/testnet-laconicd-stack/stack-orchestrator/stacks/testnet-laconicd deploy init --output testnet-laconicd-spec.yml
|
||||
|
||||
laconic-so --stack ~/cerc/testnet-laconicd-stack/stack-orchestrator/stacks/laconic-console deploy init --output laconic-console-spec.yml
|
||||
```
|
||||
|
||||
* Edit `network` in both the spec files to map container ports to host ports as required:
|
||||
* Edit `network` in the spec file to map container ports to host ports as required:
|
||||
|
||||
```bash
|
||||
# testnet-laconicd-spec.yml
|
||||
@@ -75,24 +96,12 @@ Instructions for running a laconicd testnet full node and joining as a validator
|
||||
- '9473:9473'
|
||||
- '9090:9090'
|
||||
- '1317:1317'
|
||||
|
||||
# laconic-console-spec.yml
|
||||
...
|
||||
network:
|
||||
ports:
|
||||
console:
|
||||
- '8080:80'
|
||||
```
|
||||
|
||||
* Create deployments from the spec files:
|
||||
* 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
|
||||
|
||||
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
|
||||
|
||||
# Place them both in the same namespace (cluster)
|
||||
cp testnet-laconicd-deployment/deployment.yml laconic-console-deployment/deployment.yml
|
||||
```
|
||||
|
||||
* Copy over the published testnet genesis file (`.json`) to data directory in deployment (`testnet-laconicd-deployment/data/laconicd-data/tmp`):
|
||||
@@ -109,56 +118,18 @@ Instructions for running a laconicd testnet full node and joining as a validator
|
||||
|
||||
```bash
|
||||
# Comma separated list of nodes to keep persistent connections to
|
||||
# Example: "node-1-id@node-1-host:26656,node-2-id@node-2-host:26656"
|
||||
# Example: "node-1-id@laconicd.laconic.com:26656"
|
||||
# Use the provided node id
|
||||
CERC_PEERS=""
|
||||
|
||||
# Optional
|
||||
|
||||
# A custom human readable name for this node (default: TestnetNode)
|
||||
CERC_MONIKER=
|
||||
|
||||
# Network chain ID (default: laconic_9000-1)
|
||||
CERC_CHAIN_ID=
|
||||
|
||||
# Output log level (default: info)
|
||||
CERC_LOGLEVEL=
|
||||
```
|
||||
|
||||
* Inside the `laconic-console-deployment` deployment directory, open `config.env` file and set following env variables:
|
||||
|
||||
```bash
|
||||
# All optional
|
||||
|
||||
# CLI configuration
|
||||
|
||||
# laconicd chain id (default: laconic_9000-1)
|
||||
CERC_LACONICD_CHAIN_ID=
|
||||
|
||||
# laconicd user private key for txs
|
||||
CERC_LACONICD_USER_KEY=
|
||||
|
||||
# laconicd bond id for txs
|
||||
CERC_LACONICD_BOND_ID=
|
||||
|
||||
# Gas limit for txs (default: 200000)
|
||||
CERC_LACONICD_GAS=
|
||||
|
||||
# Max fees for txs (default: 200000alnt)
|
||||
CERC_LACONICD_FEES=
|
||||
|
||||
# Console configuration
|
||||
|
||||
# Laconicd (hosted) GQL endpoint (default: http://localhost:9473)
|
||||
LACONIC_HOSTED_ENDPOINT=
|
||||
```
|
||||
|
||||
Note: Use `host.docker.internal` as host to access ports on the host machine
|
||||
|
||||
## Start the deployments
|
||||
## Start the deployment
|
||||
|
||||
```bash
|
||||
laconic-so deployment --dir testnet-laconicd-deployment start
|
||||
laconic-so deployment --dir laconic-console-deployment start
|
||||
```
|
||||
|
||||
## Check status
|
||||
@@ -181,34 +152,21 @@ laconic-so deployment --dir laconic-console-deployment start
|
||||
# `catching_up: false` indicates that node is completely synced
|
||||
```
|
||||
|
||||
* View the laconic console at <http://localhost:8080>
|
||||
|
||||
* Use the cli service for registry CLI operations:
|
||||
|
||||
```bash
|
||||
# Example
|
||||
laconic-so deployment --dir laconic-console-deployment exec cli "laconic registry status"
|
||||
```
|
||||
|
||||
## Join as testnet validator
|
||||
|
||||
* Create / import a new key pair:
|
||||
* Import a key pair:
|
||||
|
||||
```bash
|
||||
# Create new keypair
|
||||
laconic-so deployment --dir testnet-laconicd-deployment exec laconicd "laconicd keys add <key-name>"
|
||||
KEY_NAME=alice
|
||||
|
||||
# OR
|
||||
# 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"
|
||||
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"
|
||||
laconic-so deployment --dir testnet-laconicd-deployment exec laconicd "laconicd keys show $KEY_NAME -a"
|
||||
```
|
||||
|
||||
* Request tokens from the testnet faucet for your account if required
|
||||
|
||||
* Check balance for your account:
|
||||
|
||||
```bash
|
||||
@@ -218,15 +176,14 @@ laconic-so deployment --dir laconic-console-deployment start
|
||||
* 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
|
||||
# Replace <your-node-moniker> with your node's moniker
|
||||
NODE_MONIKER=<your-node-moniker>
|
||||
|
||||
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 > $NODE_MONIKER-validator.json
|
||||
{
|
||||
"pubkey": $(laconicd cometbft show-validator),
|
||||
"amount": "900000000alnt",
|
||||
"moniker": "<your-node-moniker>",
|
||||
"amount": "1000000000000000alnt",
|
||||
"moniker": "$NODE_MONIKER",
|
||||
"commission-rate": "0.1",
|
||||
"commission-max-rate": "0.2",
|
||||
"commission-max-change-rate": "0.01",
|
||||
@@ -238,10 +195,10 @@ 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 $NODE_MONIKER-validator.json \
|
||||
--fees 500000alnt \
|
||||
--chain-id=laconic_9000-1 \
|
||||
--from <key-name>'
|
||||
--from $KEY_NAME'
|
||||
```
|
||||
|
||||
* View staking validators:
|
||||
@@ -252,34 +209,6 @@ laconic-so deployment --dir laconic-console-deployment start
|
||||
|
||||
* Check that in the list of validators `<your-node-moniker>` exists
|
||||
|
||||
## Perform operations
|
||||
|
||||
* To perform txs against the chain using registry CLI, set your private key in config in the CLI container:
|
||||
|
||||
```bash
|
||||
# (Optional) Get the PK from your node
|
||||
laconic-so deployment --dir testnet-laconicd-deployment exec laconicd "laconicd keys export <key-name> --unarmored-hex --unsafe"
|
||||
|
||||
# Set your PK as 'userKey' in the config file
|
||||
laconic-so deployment --dir laconic-console-deployment exec cli "nano config.yml"
|
||||
|
||||
# services:
|
||||
# registry:
|
||||
# ...
|
||||
# userKey: <your-private-key>
|
||||
# ...
|
||||
|
||||
# Note: any changes made to the config will be lost when the cli Docker container is brought down
|
||||
# So set / update the values in 'laconic-console-deployment/config.env' accordingly before restarting
|
||||
```
|
||||
|
||||
* Adjust / set other config values (`bondId`, `gas`, `fees`) as required and perform txs:
|
||||
|
||||
```bash
|
||||
# Example
|
||||
laconic-so deployment --dir laconic-console-deployment exec cli "laconic registry bond create --type photon --quantity 1000000000000"
|
||||
```
|
||||
|
||||
## Clean up
|
||||
|
||||
* Stop all `testnet-laconicd` services running in the background:
|
||||
@@ -298,5 +227,3 @@ laconic-so deployment --dir laconic-console-deployment start
|
||||
# Remove deployment directory (deployment will have to be recreated for a re-run)
|
||||
rm -r testnet-laconicd-deployment
|
||||
```
|
||||
|
||||
* For `laconic-console`, see [laconic-console clean up](../laconic-console/README.md#clean-up)
|
||||
|
||||
+218
-80
@@ -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
|
||||
git clone git@git.vdb.to:cerc-io/testnet-onboarding-app.git
|
||||
```
|
||||
- Alternatively, setup the `laconic-wallet-web` stack
|
||||
|
||||
- Enter the project directory
|
||||
|
||||
```bash
|
||||
cd testnet-onboarding-app
|
||||
```
|
||||
|
||||
- Setup .env
|
||||
- Copy and update `.env`
|
||||
- Clone the stack repo:
|
||||
|
||||
```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
|
||||
yarn start
|
||||
# Builds and serves the app
|
||||
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
|
||||
# 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:
|
||||
- Setup port forwarding for your device using the following command:
|
||||
|
||||
```bash
|
||||
# In laconic-wallet
|
||||
yarn start
|
||||
# Get device id
|
||||
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
|
||||
- Choose Alice's nitro and laconicd account to onboard
|
||||
- Read and accept the `Terms and Conditions`
|
||||
- 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
|
||||
- Send transaction request to the Wallet
|
||||
- Approve and send transaction to laconicd chain
|
||||
- Perform the user verification steps
|
||||
- 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 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:
|
||||
|
||||
Reference in New Issue
Block a user