Update steps for reading bridge contracts address

This commit is contained in:
Adw8 2024-07-18 18:16:22 +05:30
parent fb88d0fe47
commit a2317c2ac4

View File

@ -412,7 +412,7 @@
- Read the bridge contract address from the L1 deployment records in the `op-node` container: - Read the bridge contract address from the L1 deployment records in the `op-node` container:
```bash ```bash
BRIDGE=$(laconic-so deployment --dir fixturenet-optimism-deployment exec op-node "cat /l1-deployment/$DEPLOYMENT_CONTEXT/.deploy" | jq -r .L1StandardBridgeProxy) BRIDGE=$(laconic-so deployment --dir fixturenet-optimism-deployment exec op-node "cat /l1-deployment/$DEPLOYMENT_CONTEXT-deploy.json" | jq -r .L1StandardBridgeProxy)
# Get the funded account's pk # Get the funded account's pk
ACCOUNT_PK=$(laconic-so deployment --dir fixturenet-optimism-deployment exec op-node "jq -r '.AdminKey' /l2-accounts/accounts.json") ACCOUNT_PK=$(laconic-so deployment --dir fixturenet-optimism-deployment exec op-node "jq -r '.AdminKey' /l2-accounts/accounts.json")
@ -582,7 +582,6 @@
``` ```
# In laconic-wallet # In laconic-wallet
yarn start yarn start
``` ```
- Press `a` to run the application on android and wait till the wallet app opens up on your phone - Press `a` to run the application on android and wait till the wallet app opens up on your phone
@ -850,7 +849,7 @@
- Fund the laconic account by clicking on the `REQUEST TOKENS FROM FAUCET` button - Fund the laconic account by clicking on the `REQUEST TOKENS FROM FAUCET` button
- Send transaction request to the Wallet - Send transaction request to the Wallet
- Approve and send transaction to laconicd chain - Approve and send transaction to laconicd chain
- Repeat onboarding for other (Charlies's) account - 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 1 (run in the directory where laconicd deployment was created):
```bash ```bash
@ -882,12 +881,9 @@
# Remove the temporary data directory # Remove the temporary data directory
sudo rm -rf stage1-genesis sudo rm -rf stage1-genesis
```
- Change directory to stage1 deployment directory # Go back to the directory where deployments are created
cd -
```bash
cd <stage1-deployment-directory-absolute-path>
``` ```
- 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`): - 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`):
@ -948,8 +944,8 @@
```bash ```bash
export BRIDGE_ADDRESS=0xBBB676f9cFF8D242e9eaC39D063848807d3D1D94 export BRIDGE_ADDRESS=0xBBB676f9cFF8D242e9eaC39D063848807d3D1D94
export A_ADDRESS=<Alice Ethereum address> export A_ADDRESS=<Alice Nitro address>
export C_ADDRESS=<Charlie Ethereum address> export C_ADDRESS=<Charlie Nitro address>
# Starts virtual fund objective on L2 to create virtual channel from A' to C' # Starts virtual fund objective on L2 to create virtual channel from A' to C'
nitro-rpc-client virtual-fund $C_ADDRESS $BRIDGE_ADDRESS -p 4008 nitro-rpc-client virtual-fund $C_ADDRESS $BRIDGE_ADDRESS -p 4008