Monitoring: Migrate to latest SDK #819
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lukasz-zimnoch
changed the title
lukasz-zimnoch
force-pushed
the
migrate-monitoring-to-new-sdk
branch
from
407a23d
to
a59d300
Compare
tomaszslabon
reviewed
Jul 5, 2024
tomaszslabon
approved these changes
Jul 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Depends on: #818
Depends on: #820
Here we migrate the monitoring package to the latest version of tBTC SDK. We are using the latest
developmentversion of the SDK for now as it contains some unreleased features and fixes that are useful for the monitoring tool. Migration of the monitoring to the new tBTC SDK pays off some tech debt but also reduces the number of requests sent to the Ethereum node due to some optimizations introduced in the recent versions of the SDK.