testnet-ops/nitro-bridge-setup/README.md
2024-09-05 17:36:51 +05:30

2.8 KiB

nitro-bridge-setup

Setup Ansible

To get started, follow the installation guide to setup ansible on your machine

Run nitro bridge

The following commands have to be executed in nitro-bridge-setup directory

  • Copy the bridge-vars-example.yml vars file

    cp bridge-vars-example.yml bridge-vars.yml
    
  • Edit bridge-vars.yml and fill in the following values

    # L1 WS endpoint
    nitro_l1_chain_url: ""
    
    # L2 WS endpoint
    nitro_l2_chain_url: ""
    
    # Private key for the bridge's nitro address
    nitro_sc_pk: ""
    
    # Private key for a funded account on L1
    # This account should have tokens for funding Nitro channels
    nitro_chain_pk: ""
    
    # L1 chain ID (Sepolia: 11155111)
    geth_chain_id: "11155111"
    
    # L1 RPC endpoint
    geth_url: ""
    
    # L2 RPC endpoint
    optimism_url: ""
    
    # Private key for a funded account on L1 to use for contracts deployment on L1
    geth_deployer_pk: ""
    
    # Private key for a funded account on L2 to use for contracts deployment on L2
    # Use the same account for L1 and L2 deployments
    optimism_deployer_pk: ""
    
  • To run the nitro bridge, execute the run-nitro-bridge.yml Ansible playbook by running the following command.

    NOTE: By default, deployments are created in the nitro-nodes-setup/out directory. To change this location, update the nitro_directory variable in the setup-vars.yml file.

    LANG=en_US.utf8 ansible-playbook -i localhost, --connection=local run-nitro-bridge.yml --extra-vars='{ "target_host": "localhost"}' --user $USER -kK
    
    • For skipping container build, run with "skip_container_build" : true in the --extra-vars parameter:

      LANG=en_US.utf8 ansible-playbook -i localhost, --connection=local run-nitro-bridge.yml --extra-vars='{ "target_host": "localhost", "skip_container_build": true }' --user $USER -kK
      

Check Deployment Status

  • Run the following command in the directory where the bridge-deployment is created:

    • Check logs for deployments:

      # Check the l2 nitro contract deployments
      laconic-so deployment --dir bridge-deployment logs l2-nitro-contracts -f
      
      # Check the logs, ensure that the node is running
      laconic-so deployment --dir bridge-deployment logs nitro-bridge -f
      

Get Contract Addresses

  • Run the following commands in the directory where the deployments are created:

    • Get addresses of L1 nitro contracts:

      laconic-so deployment --dir nitro-contracts-deployment exec nitro-contracts "cat /app/deployment/nitro-addresses.json"
      
    • Get addresses of L2 nitro contracts:

      laconic-so deployment --dir bridge-deployment exec nitro-bridge "cat /app/deployment/nitro-addresses.json"