Publish watcher 3.1.1

⚠️ NOTE: We've implemented a breaking change from version 3.0.0, but we'll continue to support older versions for now. While updating your watcher service to the latest version is highly recommended for compatibility with new features, If you don't update, you won't lose your permits because most watchers have updated their services. However, you may not be able to participate in events.

Note: We highly recommend consolidating your boxes in your watcher's wallet. You can achieve this by restoring your mnemonic phrase on an Ergo wallet like nautilus-wallet.

ChangeLog:

@rosen-bridge/watcher

3.1.1

Patch Changes

• Fix initialization spend info

• Fix box duplication and asset calculation in watcher service

• Updated dependencies:

  • @rosen-bridge/scanner
  • @rosen-bridge/address-extractor
  • @rosen-bridge/bitcoin-esplora-scanner
  • @rosen-bridge/bitcoin-rpc-scanner
  • @rosen-bridge/bitcoin-observation-extractor
  • @rosen-bridge/watcher-data-extractor

Publish watcher 3.1.0

⚠️ NOTE: A breaking change has been implemented from 3.0.0. We will continue to support older versions until ** 19 JUN, 12 AM UTC**. Please update your watcher service as soon as possible, If you don't update your watcher before that time, your permits may be considered fraudulent, and you will lose them.

ChangeLog:

@rosen-bridge/watcher

3.1.0

Minor Changes

• Add authentication for bitcoin rpc
• Add random id to bitcoin rpc requests

Patch Changes

• Update koios default url to v1
• Add fee constraints at observation validation
• Use authentication for bitcoin rpc health-check
• Updated dependencies:
  • @rosen-bridge/scanner
  • @rosen-bridge/address-extractor
  • @rosen-bridge/bitcoin-esplora-scanner
  • @rosen-bridge/bitcoin-observation-extractor
  • @rosen-bridge/bitcoin-observation-extractor
  • @rosen-bridge/watcher-data-extractor

NOTE: In this version authentication options added for bitcoin-rpc, you can find related configs here

Publish watcher 3.0.0

@rosen-bridge/watcher

3.0.0

Major Changes

• Update minimum-fee to v1

Minor Changes

• Upgrade health check package to latest
• Add bitcoin network
• Integrate rpc scanner for bitcoin network

Patch Changes

• Update typeorm version to 0.3.20
• Update minimum-fee and health-check packages

Publish watcher 2.1.0

@rosen-bridge/watcher

2.1.0

Minor Changes

• Support Raspberry Pi from version 3 and above, check document here

Publish watcher 2.0.2

@rosen-bridge/watcher

2.0.2

Patch Changes

• fix unlock api response schema
• add salt to the apiKey to prevent precomputed hash attacks
• solve mocha test coverage hanging problem

⚠️ Notes: We have made a security enhancement in the watcher-service apiKey authentication. While we will continue to support the old algorithm (generating just a blake2b hash of your apiKey), we have transitioned to using salted hash instead of a plain hash. It is important to note that the previous method of creating the apiKeyHash may be vulnerable to precomputed attacks. We recommend regenerating your apiKey using the latest version of our CLI application. You can find instructions on how to do this in our documentation.

Full Changelog: 2.0.1...2.0.2

Publish watcher 2.0.1

@rosen-bridge/watcher

2.0.1

Patch Changes

• Update scanner sync critical threshold and limit the watcher not to work with scanner Broken status.
• Fix commitmentTimeoutConfirmation in default config
• Use the repo box value instead of min box value in lock and unlock transactions

NOTE: Please do not upgrade to this version without referring to the migration documentation from the previous release!

Publish 2.0.0

ChangeLog:

• update watcher according to contract v3

How to Migrate from 1.1.2 to 2.0.0?

Notes: Follow the instructions step by step and do not pull the image until you have completed all steps.

• Update your local.yaml and add or update (if it already exists) the configurations below based on your watcher network:

  • Ergo Watcher:

    observation:
      confirmation: 1440
      validThreshold: 1440
    ergo:
      transaction:
        commitmentTimeoutConfirmation: 10

  • Cardano Watcher:

    observation:
      confirmation: 8640
    ergo:
      transaction:
        commitmentTimeoutConfirmation: 10

• After updating your config, restart your watcher using the following instructions and wait until all your permits become available:

  • For the new version of Docker:

    - docker compose down
    - docker compose up -d
    

    • For the old version of Docker:

    - docker-compose down
    - docker-compose up -d
    

• Once all your permits were available, you should unlock all your permits and collateral via the actions section in your watcher dashboard and wait for all permits to unlock.

  Notes: There may be network congestion causing delays in unlocking permits, so please be patient.

• Finally, update your watcher to version 2.0.0 by following these steps:

  • Revert your local.yaml file to the state before step one.

    • Ergo Watcher remove the transaction.commitmentTimeoutConfirmation configuration and update observation configuration:

    observation:
    -  confirmation: 1440
    +  confirmation: 10
    -  validThreshold: 1440
    +  validThreshold: 2160
    ergo:
    -  transaction:
    -    commitmentTimeoutConfirmation: 10

    • Cardano Watcher remove both added configurations.

  • Pull the image and restart your service:

    For the new version of Docker:

    - docker compose pull
    - docker compose down
    - docker compose up -d
    

    For the old version of Docker:

    - docker-compose pull
    - docker-compose down
    - docker-compose up -d
    

  • Lock collateral and permits.

What Should You Do If You Update Your Watcher Image to 2.0.0 Without Unlocking Your Permits?

• You should downgrade your watcher to 1.1.2. In your .env file in the watcher directory, set WATCHER_IMAGE_VERSION and UI_IMAGE_VERSION as follows:

  WATCHER_IMAGE_VERSION=1.1.2
  UI_IMAGE_VERSION=1.1.1

• Restart your watcher.
• Follow the main instructions.
• To update your images to the latest version (watcher 2.0.0), simply remove the specified version from your .env file.

Publish 1.1.2

ChangeLog:

• Add some environment variables to the watcher's configuration
• Add api-key for action-based APIs (ex: lock, unlock, ....)

Notes:

• ApiKey is a mandatory configuration. To run your watcher with this version, you must configure the ApiKey. Refer to the apiKeyHash documentation for more details.
• Instead of setting secrets in the local YAML config, you can configure them using environment variables. For guidance, please refer to Environment Variable References.

Full Changelog: 1.0.8...1.1.2

Publish 1.1.1

ChangeLog:

• Add some environment variables to the watcher's configuration
• Add api_key for action-based APIs (ex: lock, unlock, ....)

Notes:

• Instead of setting secrets in the local YAML config, you can configure them using environment variables. For guidance, please refer to Environment Variable References.
• ApiKey is a mandatory configuration. To run your watcher with this version, you must configure the ApiKey. Refer to the apiKeyHash documentation for more details.

Full Changelog: 1.0.8...1.1.1

Publish 1.1.0

ChangeLog:

• Add some environment variables to the watcher's configuration
• Add api_key for action-based APIs (ex: lock, unlock, ....)

Notes:

• Instead of setting secrets in the local YAML config, you can configure them using environment variables. For guidance, please refer to Environment Variable References.
• ApiKey is a mandatory configuration. To run your watcher with this version, you must configure the ApiKey. Refer to the apiKeyHash documentation for more details.

Full Changelog: 1.0.8...1.1.0